Run Setup Jobs in Parallel and Minimize Production Downtime When Using the Logistics Extraction Cockpit

  • by Hari Srinivasan, Senior Principal, Inforte
  • Andreas Wilmsmeier, Managing Director, Compendit DE
  • April 1, 2003
Running a setup job through the Logistics Extraction Cockpit requires that you to turn off your logistics application. It is therefore important that the job run as quickly as possible. The fastest way to complete the setup job is to break it up into parts and run those parts in parallel. The authors show how and explain the setup tables that are involved.


One of the ways you can take advantage of BW's tool for extracting data from R/3 logistics applications, the Logistics (LO) Extraction Cockpit, is by executing setup jobs parallel. This significantly speeds up the process and reduces downtime in your production system while maintaining a high level of data integrity.

Setup jobs execute in the R/3 system to initialize data for the respective logistics application (such as Material Management, Production Planning, or Sales and Distribution) in preparation for loading into BW. You must run setup jobs with the application turned off. It is important, therefore, to execute these jobs as quickly and accurately as possible to minimize downtime in your production system.

As a single job running in the background, the setup process might take a few minutes or as long as a few days to complete depending on the data volume for that application. This isn't your only worry when running setup jobs. They can only be run when no documents are posted in the logistics application for which the setup job is run. Depending on the physical update strategy of the R/3 kernel and the underlying database system, the setup job might not capture updates that have been run in parallel, making it impossible to securely delimit the initial load from the first delta load. Finally, it is often difficult and time-consuming to secure downtime in production systems for running setup jobs.

Running setup jobs in parallel using the LO Extraction Cockpit will help you address all these issues. We will show you the steps you have to follow to run the setup jobs in parallel to one another and provide advice based on our experience on how to avoid pitfalls and minimize the downtime for the application. In addition, we will explain the basic concepts of the LO Extraction Cockpit, the meaning and use of setup tables, and the prerequisites for running the setup jobs.

Hari Srinivasan

Hari Srinivasan is an SAP NetWeaver BW specialist with more than a decade of experience in implementing SAP FI/CO, IS Retail, and SAP NetWeaver BW. Hari specializes in implementing SAP NetWeaver BW solutions including the SAP BusinessObjects suite of products and planning applications. Hari has also conducted numerous BW data warehousing and upgrade assessments, conducted reporting strategy assignments, and developed migration strategies from SAP NetWeaver BW to the SAP BusinessObjects suite of products. Hari is now focusing on working with the EPM and SAP BusinessObjects suites. Prior to working with SAP systems and applications, Hari worked in several managerial positions in accounting, finance, project acquisitions, and infrastructure investment. Hari is a chartered accountant from India and a certified information systems auditor.

See more by this author

Andreas Wilmsmeier

Andreas Wilmsmeier is a managing director of Compendit in Germany. He was a member of the initial SAP BW core development team, where he was responsible for designing and implementing parts of the staging engine (specifically the Staging BAPI). Andreas has been managing multiple SAP BW implementations from the early days of the SAP BW 1.2A first customer shipment to today's SAP BW 3.0B release. He is a co-author of Mastering the SAP Business Information Warehouse (McDonald, Wilmsmeier, Dixon, and Inmon; Wiley 2002).

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.