SAP BW LO Data Extraction

The transaction data entering the Business Information Warehouse by means of extractors originates from very different modules. Due to past developments, very different extraction mechanisms are necessary.Your company uses the previous SD data extraction with the LIS transfer structures S26*; The extraction  must be converted to the new LO extractor. You are responsible for extractor conversion - you still want the reports to be available in the BW system.

The Logistics Customizing Cockpit is the central administration tool for extract structures, which you use to transfer Logistics transaction data of the tool from OLTP into BW. The extract structures are filled with the communication structures of the individual Logistics applications.The Cockpit contains the following functionality, as specified in the procedure sequence:

Maintaining extract structures
Maintaining Data Sources
Activating the update
Controlling V3 update

Maintaining the Extract Structure

The extract structure is filled with the assigned communication structures. You can only use selected fields from the communication structures (SAP internal control fields, for example, are not offered). SAP already delivers extract structures, which you can enhance (by connecting to the communication structure). Every extract structure can be maintained by you and by SAP.After you set up the extract structure, the system automatically generates it. This completes missing fields (their units and characteristics). The extract structure is created hierarchically according to the communication structures. Every communication structure leads to the generation of a substructure that belongs to the actual extract structure.



At this point, call up the general maintenance screen for Data Sources by selecting the extract structure fields that you want to transfer into the BW System. This selection forms the basis for the generating process of the Data Source.


There is a Data Source (for example ‘2LIS_11_VAITM‘) for each extract structure that is made available (for example, ‘MC11VA0ITM‘) in the OLTP System. A maintenance screen is displayed in which you can to assign other 'properties' to the fields of the extract structure (S5nnBIWS).

ŸSelection fields
ŸHide fields
ŸCancellation fields (field is inverted when canceled (*-1))


Replicating Data Sources

OLTP extraction tables make up the basis of a Data Source as far as BW is concerned.An R/3 System connected to BW provides a variety of Data Sources. These can be uploaded into BW by replicating them in the source system tree.

The Data Sources are delivered in a so-called 'D version' and can be transferred to the 'A version' when they are activated. They can be also changed and forwarded to the 'A version' (one that deviates from the default).

If Data Sources have changed in the source system (for example, when your R/3 System is upgraded), you can decide if you want to activate them to the 'A version', or continue using the existing ones. The Data Source must be replicated before it can be used in BW. To do this, choose the 'Source Systems' tab strip in the BW Administrator Workbench. Select the relevant OLTP system and choose Replicate Data Sources from the context menu. All the Data Sources that do not exist yet in BW are then transferred from the OLTP to the BW System.


Maintaining the Communication Structure

Communication structures are created for Info Sources and thus represent part of an application in the OLTP System (for example, order data from Sales, purchase order data from Purchasing, and so on). The total number of Info Objects in the communication structure and extract structure may be different, since Info Objects can be copied to the communication structure from all extract structures
(several source systems).

Maintaining Transfer Rules

Transfer rules specify which fields in the transfer structure are to be transferred to which fields in the communication structure. You can create detailed conversion rules to change or add to data.You can only choose one of the three types of transfer rules for each Info Object in the communication structure:

Ÿ The fields are copied from the transfer structure and not modified.
ŸA field in the communication structure can be supplied with a fixed value for this source system.
ŸA local transfer routine is used to supply the content of the communication structure with data when uploaded from this source system. The routine defined only applies to the selected Info Object.
The transfer rules do not take effect until they have been activated.


Maintaining Info Cubes and Update Rules

Before data can be uploaded from the OLTP System to BW and evaluated in an Info Cube, the Info Cube must be created with the relevant update rules.You maintain Info Cubes and update rules in the Administrator Workbench, Modeling > Info Cubes.Update rules are always defined for a combination of an Info Cube and Info Source. For this reason, an Info Source can update several Info Cubes. An Info Cube, however, can be linked to several Info Sources via update rules.

There are various ways of updating Info Cube key figures into the update rules. Possible: Field to field assignment, formula and fixed value. You can also specify which date field in the Info Source is
to supply the time characteristics of the Info Cube with data. Similarly, a key figure can only be updated under certain conditions. In the same way, a currency translation can also be triggered when a key figure is updated to the Info Cube.

Activating Extract Structures

When you activate the extract structure for updating, the data is written to the extract structures immediately - online as well as when you fill the tables for restructuring.




V3 Update - Settings

The data is updated with the V3 update and is ready to be transferred with the batch operator to the central delta management.You need to define job parameters such as start time and printer settings, and schedule the batch jobs at this point.



Related Posts
  

SAP Business Warehouse LIS Data Extraction Part Three

Initializing the Delta Process

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.

 
When the initialization of the delta update for an Info Source is started, all the data from the associated info structure in the OLTP System is uploaded to BW and fills the specified Info Cubes specified in the Info Source.Make sure that update of the info structure in the OLTP System is inactive. This prerequisite is only necessary for the initialization run.If one or more selective initialization runs (selection according to plant, for example) is carried out, all the selection conditions must be entered in the selection screen for the subsequent delta upload.





Monitoring the Upload Procedure

Enable communication and data transfer beyond the limits of the system. 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 InfoCubes to be updated 52: InfoCube successfully updated
.…
70: end of IDoc processing

Status Display in the Monitor

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

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.


Process: First Delta Update

When you start the delta update process from the OLTP to the BW, the tables S5nnnBIW1 and S5nnBIW2 are used.The info structure in the OLTP is active. The data from S5nnBIW1 is transferred to the BW for the first delta update.While the first delta update to the BW is being carried out, the LIS update process updates the LIS info structure in the OLTP system as well as the table S5nnBIW2, which is then used for the second delta update request to the BW.

At the start of each delta update request, the system switches between the S5nnBIW1 and S5nnBIW2 tables to prevent inconsistencies while the data is being uploaded to BW. (The 'BIW status' flag in the 'TMCBIW' table on the OLTP system is automatically changed from 1 (for table S5nnBIW1) to 2 (for table S5nnBIW2) during the delta update to BW.)The data in a delta table remains in the table until the next delta upload to ensure that the data can be reloaded up to that point.


Process: Second Delta Update


Related Posts
  

SAP Business Warehouse LIS Data Extraction Continuation

We are going to continue discuss data extraction from SAP data base and we are going to use LIS  for this.n Transfer rules specify which fields in the transfer structure are to be transferred to which fields in the communication structure. You can create detailed conversion rules to change or add to data.You can only choose one of the three types of transfer rules for each Info Object in the communication structure:
Ÿ
The fields are copied from the transfer structure and not modified.A field in the communication structure can be supplied with a fixed value for this source system. A local transfer routine is used to supply the content of the communication structure with data when uploaded from this source system. The routine defined only applies to the selected Info Object. The transfer rules do not take effect until they have been activated.


Maintain Info Cubes and Update Rules

Before data can be uploaded from the OLTP System to BW and evaluated in an Info Cube, the InfoCube must be created with the relevant update rules.You maintain Info Cubes and update rules in the Administrator Workbench, Modeling > Info Cubes.Update rules are always defined for a combination of an Info Cube and Info Source. For this reason,an Info Source can update several  Info Cubes. An Info Cube, however, can be linked to several Info Sources via update rules.

There are various ways of updating Info Cube key figures into the update rules. Possible: Field to field assignment, formula and fixed value. You can also specify which date field in the InfoSource is to supply the time characteristics of the Info Cube with data. Similarly, a key figure can only be updated under certain conditions. In the same way, a currency translation can also be triggered when a key figure is updated to the Info Cube. 



Extracting Application Data

When application data is extracted, the mater data must be transferred first. It is useful if the Business Information Warehouse knows attributes in addition to the vendor number, for example, vendor name, address or region.Hierarchy information such as product hierarchy for the material, and so on, must be accessible when you transfer data into BW.

Generally speaking, the volume of transaction data is considerably higher. A full update here is mostly only justified for the first time data is transferred or if the statistics data has to be rebuilt following a system failure.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.


LIS Delta Update

Before you start a delta update request in BW, you have to make sure that the delta update process in the OLTP System is supported.To do this, you have to activate the 'Delta updating in the LIS' setting in the report 'RMCSBIWC'. The 'Activate/deactivate' radio button activates or deactivates the update function to the delta tables S5nnBIW1 and S5nnBIW2. The active table for the delta update is defined in the table 'TMCBIW'.

'Generate updating' regenerates the update program (RMCX....) and ensures that a delta update is possible in the delta tables (S5nnBIW1/S5nnBIW2). (For this purpose, the original LIS update program ‘RMCX....’ was enhanced within the FORM routines ‘form S5nnbiw1_update_....' and ‘form S5nnbiw2_update_....').

the update programs for an information structure can only be regenerated if the LIS updating function is inactive!The update is regenerated in the customer name range only.Delta updates are client specific!




 
Activating the Update

The InfoStructures can then only be updated when you have activated the info structures. You can do this in the Customizing screen of BW in the OLTP System (transaction SBIW) under Generated DataSources > Logistics > Logistics Information System > Activate update.

You must activate the associated info structures that you want to fill with data for each application in LIS (for example, Sales and Distribution, Purchasing).You enter the period split (for example, monthly, weekly) and specify the update mode (for example, synchronous or asynchronous).

Some info structures that are shipped by SAP especially for BW have to be activated in Customizing under Generated InfoSources > Logistics > Transaction Data > Managing Transfer Information Structures > Activate/Deactivate Update Rules.


Creating an Info Package

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.