Logistics Extraction Cockpit

LO extraction refers to the process of extracting logistics data.Depending on the application area,it extracts the transaction data. For example, if you chose extract Sales order information, it picsk all the sales order data from the R/3 system.LO Extractors contains datasources and extraction logic criteria which is specific to logistics data.

1. Positioning of Cockpit extraction
2. Overview data flow
3. Update Methods

Positioning of Cockpit extraction

Overview data flow

Transaction postings lead to:

1. Records in transaction tables
2. For an initial load a setup needs to be executed which reads the transaction data and stores the data in a setup table.
3. These setup tables are read during an initial or full load.
4. Further transactions are posted into the transaction tables and also caught into Update tables / Extraction Queue.
5. A periodically scheduled job transfers these postings into the BW delta queue
6. This BW Delta queue is read when a delta load is executed.

Update methods In Logistics Extraction:

1. Direct Delta
2. Queued Delta 
3. Unserialized v3 update

 Direct Delta:

1. Each document posting is directly transferred into the BW delta queue
2. Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues 

Transaction postings lead to:

1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed

1. Not suitable for environments with high number of document changes
2. Setup and delta initialization have to be executed successfully before document postings are resumed
3. V1 is more heavily burdened
4. Extraction is independent of V2 update
5. Less monitoring overhead of update data or extraction queue

Queued Delta :-

In this Extraction data is collected for the affected application in an extraction queue the collective run as    usual for transferring data into the BW delta queue.

1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
4. V1 is more heavily burdened compared to V3
5. Administrative overhead of extraction queue
6. Extraction is independent of V2 update
7. Suitable for environments with high number of document changes
8. Downtime is reduced to running the setup
9. Up to 10000 delta extractions of documents for an LUW are compressed for each DataSource into the BW delta queue, depending on the application.

Un Serialized v3 update:

1.  Extraction data for written as before into the update tables with a V3 update module
2.  V3 collective run transfers the data to BW Delta queue
3. Records in transaction tables and in update tables
4. A periodically scheduled job transfers these postings into the BW delta queue
5. This BW Delta queue is read when a delta load is executed
6. Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements.
7. V2 update has to be successful

Preferred update method:

Queued delta: Up to 10000 delta extractions of documents for an LUW are compressed for each  DataSource into the BW delta queue.
Direct delta for small volumes and sufficient downtime possible.

By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi .