Professional Documents
Culture Documents
Data Flow During Different Update Mode in LO Cockpit PDF
Data Flow During Different Update Mode in LO Cockpit PDF
Mode in LO Cockpit
Applies to:
SAP BW 3.x & SAP BI NetWeaver 2004s. For more information, visit the Business Intelligence homepage.
Summary
The objective of this Article is to explain the Data Flow during different Update Mode in LO Cockpit.
Author: Chandiraban singu
Company: Capgemini
Created on: 13 August 2009
Author Bio
The author is a NetWeaver 2004s Certified Consultant. He has been involved in SAP BW
Implementation and Support Services.
Table of Contents
Overview ............................................................................................................................................................. 3
Scenario .............................................................................................................................................................. 3
Direct Delta: .................................................................................................................................................... 4
Observation:................................................................................................................................................................. 4
Queued Delta: ................................................................................................................................................. 6
Observation:................................................................................................................................................................. 7
Unserialized V3 Update: ............................................................................................................................... 10
Observation:............................................................................................................................................................... 10
Related Content ................................................................................................................................................ 16
Disclaimer and Liability Notice .......................................................................................................................... 17
Overview
Logistics Extraction Structure Customizing Cockpit (LBWE).
Once the maintenance of Data source with the required update mode in LBWE is completed the data starts
to flow into Delta queue via various paths corresponding to the mode selected.
As a BW consultant its always good to know the track of data movement, may be in case of any failure it
would be easy to locate the problem point.
In this subject I have taken all the three update modes of LO cockpit and described the data flows during
delta run with the snap shots.
The three Update modes available in LO Cockpit.
Direct Delta
Queued Delta
Unserialized V3 Update
In this entire subject we will be coming across three different updates V1, V2 and V3.
V1 Update (Synchronous)
Its a time-critical update used for updating the actual transaction tables.
V2 Statistical Update (Asynchronous)
Its a non-time-critical update used for updating statistics tables related to the transaction tables.
For instance, after a Sales order entry transaction is completed, the corresponding sales order tables would
be updated in V1 mode, and the corresponding statistics tables would be updated in V2 mode.
V3 Collective Update (Asynchronous with background scheduling)
V3 update mode (Uses delta queue technology) is similar to the V2 update mode. The main difference is that
V2 updates are always triggered by applications, while V3 updates may be scheduled independently. Many
extraction programs available for mySAP.com applications today use the delta queue technology to identify
deltas.
Scenario
The Sales data source 2LIS_11_VAITM is activated to record the sales order transactions in the item level
for BW loading. (Assuming that the data flowing into BW is in continuous run after the successful
Initialization) Let us see how the data flow into delta queue in different Update modes during Creation /
Modification / Deletion of Sales order.
Creation of Sales order, this same scenario is taken to explain each Update mode.
Direct Delta
Queued Delta
Unserialized V3 Update
Direct Delta:
The extracted data is transferred directly to the delta queue with the Document Posting. Thus the sequence
of the transfer of document agrees with the chronological order of data creation.
Observation:
LO cockpit setting: Update mode as Direct Delta for the application (11) in LBWE transaction.
Initial situation:
On successful completion (Save), the successful Save message in the status bar, the document posting in
application table as well as a record in Delta queue is written at the same time.
i.e. Extraction is independent of V2 updating.
The delta queue is within the V1 posting process, thus serialization by document is ensured with the
enqueue concept of applications.
Queued Delta:
The extraction data from the concerned application is collected in an Extraction Queue.
Then the data will be transferred to Delta queue, in a similar manner to the V3 update, with an update
collection run.
Observation:
LO cockpit setting: Update mode as Queued Delta for the application (11) in LBWE transaction.
Initial situation:
of Sale order as shown below. Simultaneously a new record is written for an application (11) in the Extraction
queue.
On successful completion (Save), the successful Save message in the status bar, the document posting in
application table as well as a record in extraction queue is written at the same time.
i.e. Extraction is independent of V2 updating.
The extraction queue writing is taken in the V1 update process itself, thus serialization by document is
ensured with the enqueue concept for applications.
Once V3 Collective run job runs for an application 11, all the records for the application 11 will be moved
from the Extraction queue to the Delta queue.
So on successful Order creation, if it is the first record in Extraction queue after the successful Delta, then a
new queue with the reference MCEX11 is created along with record. If its a subsequent process, then it
will be sequentially written under already existing queue MCEX11 of Extraction Queue.
This is the top level information for MCEX11; Double click on the line it will take to further detailed level.
Similarly, all Creation / Modification / Deletion of Sales orders are written into the queue.
When the V3 collective run job is executed, all the records are moved from Extraction queue to Delta queue.
In general the V3 collective run job would be schedule to move the data in regular frequency, for an exercise
purpose the job is scheduled with Immediate option.
Now it can be seen that the records have been moved from Extraction Queue to Delta Queue.
Unserialized V3 Update:
The extraction data of the application being viewed is written to the Update Queue with an V3 update module
and is kept there until the data is read with an update collection run and processed.
Observation:
LO cockpit setting: Update mode as Unserialized V3 update for the application (11) in LBWE transaction.
Initial situation:
The above screen is in the assumption that all the application delta data has been moved into delta queue
On successful completion (Save), the successful Save message in the status bar, the document posting in
application table as well as a record in Update queue is written at the same time.
Extraction is dependent on V2 updating.
Note: In this mode, the delta records may not arrive in the same order in the BW as they were generated in the OLTP
system. In particular, this can cause problems in the BW when using ODS objects.
i.e. The method Unserialized V3 Update does not ensure serialization of the document data. Update to the
DataStore objects is not recommended if serialization is desired
Thus the posted record with T-code VA01 is written in the Update Queue.
Similarly, all Creation / Modification / Deletion of Sales orders are written into the queue.
When the V3 collective run job is executed, all the records are moved from Update queue to Delta queue.
In general the V3 collective run job would be schedule to move the data in regular frequency, for a exercise
purpose the job is scheduled with Immediate option.
Now it can be seen that the records have been moved from Update Queue to Delta Queue.
Related Content
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5310
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3785
http://forums.sdn.sap.com/thread.jspa?messageID=2935863#2935863
For more information, visit the Business Intelligence homepage