Data Flow During Different Update Mode in LO Cockpit

Size: px

Start display at page:

Download "Data Flow During Different Update Mode in LO Cockpit"

Elwin Berry
6 years ago
Views:

1 Data Flow During Different Update 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 SAP AG 1

2 Table of Contents Overview... 3 Scenario... 3 Direct Delta:... 4 Observation:... 4 Queued Delta:... 6 Observation:... 7 Unserialized V3 Update: Observation: Related Content Disclaimer and Liability Notice SAP AG 2

3 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 it s 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 mode s 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) It s a time-critical update used for updating the actual transaction tables. V2 Statistical Update (Asynchronous) It s 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 2009 SAP AG 3

4 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. The exercise starts after the successful completion of nth Delta. Initial situation: Delta queue (RSA7): 2009 SAP AG 4

5 Data flow recording for Direct Delta: Creation of Sales order. Once all the required business data have been filled and Save button is clicked from the Transaction code VA01 (Creation of Sales order), success message will be displayed at the status bar on successful creation of Sale order as shown below. Simultaneously a record is written for a Datasource (2LIS_11_VAITM) in the 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 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. Note: V1 is more burdened by this process than with V3 or Queued Delta. Delta queue (RSA7): Data in Delta queue: Mark a line and press F2 to see data 2009 SAP AG 5

6 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 SAP AG 6

Observation: LO cockpit setting: Update mode as Queued Delta for the application (11) in LBWE transaction. The exercise starts after the successful completion of nth Delta.

7 Observation: LO cockpit setting: Update mode as Queued Delta for the application (11) in LBWE transaction. The exercise starts after the successful completion of nth Delta. Initial situation: Extraction queue (LBWQ): Delta queue (RSA7): Data flow recording for Queued Delta: Creation of Sales order. Once all the required business data have been filled and Save button is clicked from the Transaction code VA01 (Creation of Sales order), success message will be displayed at the status bar on successful creation 2009 SAP AG 7

of Sale order as shown below. Simultaneously a new record is written for an application (11) in the Extraction queue.

The extraction queue writing is taken in the V1 update process itself, thus serialization by document is ensured with the enqueue concept for applications.

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.

8 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 it s a subsequent process, then it will be sequentially written under already existing queue MCEX11 of Extraction Queue. Extraction Queue (LBWQ): Double click on the line to see details. 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 SAP AG 8

In general the V3 collective run job would be schedule to

the job is scheduled with Immediate option.

9 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. Extraction Queue (LBWQ): Delta Queue (RSA7) Data in Delta queue: Mark a line and press F2 to see data 2009 SAP AG 9

with an update collection run and processed.

10 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 SAP AG 10

11 The exercise starts after the successful completion of nth Delta. Initial situation: Update Queue (SM13): The above screen is in the assumption that all the application delta data has been moved into delta queue Delta queue (RSA7): Data flow recording for Unserialized V3 : Creation of Sales order. Once all the required business data have been filled and Save button is clicked from the Transaction code VA01 (Creation of Sales order), success message will be displayed at the status bar on successful creation of Sale order as shown below. Simultaneously a new record is written in the Update 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 SAP AG 11

(SM13): Fill the known data to filter the set of value and execute with V2 update selection

12 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 Update Queue (SM13): Fill the known data to filter the set of value and execute with V2 update selection Output: Update queue. Thus the posted record with T-code VA01 is written in the Update Queue SAP AG 12

13 Content in the Queue: Display MCEX_UPDATE_XX to see the content. Double click on corresponding line MC11VA0ITM_TAB 2009 SAP AG 13

14 Content in the queue are displayed SAP AG 14

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.

15 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. Update Queue (SM13): Delta Queue (RSA7) Data in Delta queue: Mark a line and press F2 to see data 2009 SAP AG 15

16 Related Content For more information, visit the Business Intelligence homepage 2009 SAP AG 16

17 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 17

Cut Over Activities Specific for LIS* Data Sources

Cut Over Activities Specific for LIS* Data Sources Applies to: SAP BW 3.5/SAP BI 7.0. For more information visit the Enterprise Data Warehousing Homepage Summary The basic purpose of this document is to