SAP BW LO Data Extraction Continued

Setup Extraction

When you extract transaction data with the LO method, you need a so-called extraction setup, which is similar in its usage to the LIS method for refreshing statistical data.The extraction setup reads the data set you want to edit (for example , customer orders with the tables VBAK, VBAP and so on) and fills the relevant communication structure. The data is stored in cluster tables (_SETUP), from where they are read when initialization is run.n You can also carry out a full update into BW with the tables setup.

Creating Info Packages

Data requests sent to the source system are managed with the Scheduler. These requests are formulated for each Info Source and source system and are divided into master and transaction data.An Info Source in a source system can have several different extraction jobs with different selection criteria. These are referred to as Info Packages.Info Packages or groups of Info Packages can be distributed to background processes using the R/3 job planning facility. This means that you can fully automate the data transfer process and decide when and at what intervals data is to be extracted. Or, for example, you can use a factory calendar to specify that data is not to be extracted on public holidays, and so on.The term 'transaction' in the Business Information Warehouse covers data retrieval in the OLTP and the successful updating of this data to the relevant Info Cubes. You can monitor the transfer and processing of the data closely using the Monitor function in the Administrator Workbench.You can compile lists containing information on Info Package processing for each user, source system, day, etc.

Initializing the Delta Process (Scheduler)

If you want to transfer data in the delta process, the process must be initialized in the first data request. In this process, the selection conditions for connecting delta uploads are set and its complete data set is loaded into BW from the R/3 System.To do this, you must select the check box Initialize delta process for the Info Package under the update parameters of the Scheduler.

Monitoring the Upload Procedure

The data transfer procedure is handled by a series of IDocs that facilitate communication and data transfer across system boundaries. These IDocs are divided into info IDocs and data IDocs.The task of the individual info IDocs is indicated by their status: Status 0: data request received by source system, source system starts to select data.

Status 1: this status indicates a data IDoc that contains further data processing information.
....
Status 5: an error has occurred in the source system.
...
Status 9: data selection in the OLTP System has been successfully completed.

With data IDocs, you can display a list of the processing steps that have been carried out to date.These steps are described by call numbers, such as: 50: start of update 51: determine Info Cubes to be updated 52: InfoCube successfully updated
.…
70: end of IDoc processing

Status

The traffic light changes color depending on the context.
Note that a red light does not necessarily mean that an error has occurred.

Delta Update (Scheduler)

Generally speaking, the volume of transaction data is considerably higher.Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are required to implement a performance-oriented, periodical data transfer strategy.Therefore, when sales figures are updated every week in the Business Information Warehouse, only the sales document information that has been added or changed in the last week should be extracted.In this case, you have to activate the 'Delta Update' check box for the Info Package in the updating parameters of the Scheduler.