SlideShare una empresa de Scribd logo
1 de 14
Descargar para leer sin conexión
LO Extraction – Part 2 Database
 Update Logic




Applies to:
SAP BI, NW2004s Business Intelligence, ABAP, BI For more information, visit the EDW homepage.

Summary
This article explains about LO extraction logic, architecture and background tables involved.
Author :         P. Renjith Kumar
Company      :   SAP Labs India
Created on :     1 January 2010

Author Bio

                  P Renjith Kumar is presently working in SAP Labs India Pvt Ltd and specializes in
                  Extraction and Modeling areas of BI. Basically as an ABAP consultant, he has extensive
                  cross functional experience and has been with end to end SAP ERP and BI
                  implementation projects across manufacturing domain.




SAP COMMUNITY NETWORK                  SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                      1
LO Extraction – Part 2 Database Update Logic




Table of Contents
Prerequisite................................................................................................................................................... 3
Introduction ................................................................................................................................................... 3
The update process ...................................................................................................................................... 3
V1 and V2 Update Modules........................................................................................................................... 4
Update Request ............................................................................................................................................ 5
Transactions and Logical Units of Work......................................................................................................... 6
LUW: Logical Unit of Work: ........................................................................................................................... 7
DB LUW........................................................................................................................................................ 7
SAP LUW ..................................................................................................................................................... 8
The Update Mechanism: ............................................................................................................................... 8
How to check update status .......................................................................................................................... 8
Update status.............................................................................................................................................. 12
Related Content .......................................................................................................................................... 13
Copyright .................................................................................................................................................... 14




SAP COMMUNITY NETWORK                                    SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                                        2
LO Extraction – Part 2 Database Update Logic


Prerequisite
Once you are done with the first part of the article you can understand this article clearly. You can find the
first part here.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1034bcbe-b459-2d10-2a89-ecdeb4e53ff1

Introduction
This part deals with the LO extraction logic, its architecture, working mechanism and background tables and
reports involved.

The update process
When you do some transaction like creating/changing sales order, purchase order and press save what
happens? It is either saved into database or some error occurs. We will see how this happen.
The update system is used to lighten the workload of the SAP transactions when time-consuming changes
are made to the database. The changes are carried out asynchronously  usually with short delays in
between  by special update work processes.
At the end of a transaction COMMIT WORK and the update task are called; the dialog part of the SAP
transaction is closed, and the update part of the SAP logical unit of work (LUW) is started. The following
graphic illustrates the necessary actions and the sequence in which they execute the different workprocess




                                                                                             .
After the transaction has been processed, the dialog process completes the VBHDR entry (the update
header of the update request) and searches an update server for the V1 update

The update server distributes the tasks to an update work process. This processes the V1 modules of the
update request, triggers a COMMIT to the database, and releases the SAP locks on the update request The
work process then searches for an update server for the V2 update, providing V2 update modules exist.

A V2 update server then passes this onto a V2 work process, which processes the V2 modules and triggers
a COMMIT to the database.




SAP COMMUNITY NETWORK                   SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                       3
LO Extraction – Part 2 Database Update Logic




Processing the V1 modules involves transferring the contents of the update tables VBMOD and VBDATA to
the application tables of the database. The changes are not actually made to the tables in the database until
the database LUW in which this takes place is completed. The SAP locks are released and, if V2 update
modules exist, the V2 update is started. This is similar to the V1 update with the exception that there are no
locks that have to released and no search for a process for further processing.
Now we need to see about V1 and V2 updates in detail

V1 and V2 Update Modules

An update is divided into different modules. Each module corresponds to an update function module.

There are two types of module.

The SAP System makes a distinction between primary, time-critical (V1) and secondary, non-time-critical
(V2) update modules. The system also supports collective runs for function modules that are used on a
regular basis.

This distinction allows the system to process critical database changes before less critical changes.

       V1 modules describe critical or primary changes; these affect objects that have a controlling
        function in the SAP System, for example order creation or changes to material stock.
       V2 modules describe less critical secondary changes. These are pure statistical updates, for
        example, such as result calculations.

The V1 modules are processed consecutively in a single update work process on the same application
server. This means that they belong to the same database LUW and can be reversed. Furthermore, V1
updates are carried out under the SAP locks of the transaction that creates the update. This ensures that the
data remains consistent; simultaneous changes to the objects to be updated are not possible.

All V2 updates are carried out in a separate LUW and not under the locks of the transaction that creates
them. If your SAP System contains a work process for V2 updates, these are only carried out in this work
process. If this is not the case, the V2 components are processed by a V1 update process.



SAP COMMUNITY NETWORK                  SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                      4
LO Extraction – Part 2 Database Update Logic


All V1 modules of an update must be processed before the V2 modules.

Now we see about update request

Update Request

An update request or update record describes the data changes defined in an SAP LUW, which are carried
out either in full or not at all (in a database LUW). (This only applies to V1 updates. V2 updates are triggered
once the V1 update has been completed, and therefore take place in a separate database LUW.)

Structure of update record




An update request comprises an update header, V1 modules (or components), V2 modules and a collective
run.

An update module corresponds to a function module, and contains the update data and, in certain cases,
error information, which is generated if the update is canceled.




SAP COMMUNITY NETWORK                   SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                       5
LO Extraction – Part 2 Database Update Logic


The following update tables in the database contain the following information:


Update Table                                Contents/Description

VBHDR                                       Update headers (one per update record)

VBMOD                                       Update modules (one per function module), n V1 modules and m
                                            V2 modules per update request.

VBDATA                                      Data which is transferred to the modules (variables, structures,
                                            internal tables)

VBERROR                                     Error information which is generated if an update is canceled
Now we need to know about LUW.

Transactions and Logical Units of Work

In everyday language, a transaction is a sequence of actions that logically belong together in a business
sense and those either procure or process data. It covers a self-contained procedure, for example,
generating a list of customers, creating a flight booking, or sending reminders to customers. From the user’s
viewpoint, it forms a logical unit.

The completeness and correctness of data must be assured within this unit. In the middle of a transaction,
the data will usually be inconsistent. For example, when you transfer an amount in financial accounting, this
must first be deducted from one account before being credited to another. In between the two postings, the
data is inconsistent, since the amount that you are posting does not exist in either account. It is essential for
application programmers to know that their data is consistent at the end of the transaction. If an error occurs,
it must be possible to undo the changes made within a logical process.

In the R/3 System, there are three terms frequently used in this context:

Database Logical Unit of Work (DB LUW)

A database LUW is the mechanism used by the database to ensure that its data is always consistent.

SAP LUW

An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a
single database LUW.

SAP Transaction

An SAP transaction is an application program that you start using a transaction code. It may contain one or
more SAP LUWs.




SAP COMMUNITY NETWORK                   SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                       6
LO Extraction – Part 2 Database Update Logic


LUW: Logical Unit of Work:
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations
which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database
is once again in a correct state. If, however, an error occurs within an LUW, all database changes made
since the beginning of the LUW are canceled and the database is then in the same state as before the LUW
started.
An LUW ends
1. When the database changes have been confirmed (database commit) or
2. When the database changes have been canceled (database rollback)
An LUW begins
1. Each time you start a transaction
2. When the database changes of the previous LUW have been confirmed (database commit)
3. When the database changes of the previous LUW have been cancelled (database rollback)

DB LUW
From the point of view of database programming, a database LUW is an inseparable sequence of database
operations that ends with a database commit. The database LUW is either fully executed by the database
system or not at all. Once a database LUW has been successfully executed, the database will be in a
consistent state. If an error occurs within a database LUW, all of the database changes since the beginning
of the database LUW are reversed. This leaves the database in the state it was in before the transaction
started.




The database changes that occur within a database LUW are not actually written to the database until after
the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3
System, database commits and rollbacks can be triggered either implicitly or using explicit commands.




SAP COMMUNITY NETWORK                   SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                       7
LO Extraction – Part 2 Database Update Logic



SAP LUW
The Open SQL statements INSERT, UPDATE, MODIFY, and DELETE allow you to program database
changes that extend over several dialog steps. Even if you have not explicitly programmed a database
commit, the implicit database commit that occurs after a screen has been processed concludes the database
LUW. The following diagram shows the individual database LUWs in a typical screen sequence:

Note
A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called
       an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a
       series of different work processes. If an SAP LUW contains database changes, you should either write all of them
       or none at all to the database. To ensure that this happens, you must include a database commit when your
       transaction has ended successfully, and a database rollback in case the program detects an error.


An example for V1 and V2 update

The Update Mechanism:
V1 - Synchronous update
V2 - Asynchronous update
V3 - Batch asynchronous update
If you create/change a sales order (VA01/VA02), when you press 'SAVE' and see a success message (Sales
Order.... created/ changed..), the update to underlying tables VBAK/VBAP has happened (before you saw
the message). This update was executed in the V1 work process.
There are some statistics collecting tables in the system which can capture data for reporting. For example,
LIS table S*** stores sales data (it is the same data as VBAK/VBAP stored redundantly, but in a different
structure to optimize reporting).Now, these tables are updated with the transaction you just posted, in a V2
process. Depending on system load, this may happen a few seconds later (after you saw the success
message). You can see V1/V2/V3 queues in SM12 or SM13.
V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately.
You have to schedule a job (LBWE definitions) to process these. This is again to optimize performance. V2
and V3 are separated from V1 as these are not as real-time critical (updating statistical data). If all these
updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.
We will see V3 in the later part.

How to check update status

    1. Start Update System Administration. To do this, choose Tools > Administration > Monitor
       > Update. Alternatively enter transaction code SM13.
    2. Check if the update is active. One of the following messages is output at the bottom of the
       initial screen of the Update System:

             o    Update is active
             o    Update is deactivated

Make sure that you see “Update is active”
Here is an example to see, this is a screen shot from SM13 transaction




SAP COMMUNITY NETWORK                     SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                         8
LO Extraction – Part 2 Database Update Logic




Update management (SM13) is used for the following:

      Display update requests
      Analyze problems pertaining to the update
      Test and debug canceled update requests
      Display and reset the status of update requests
      Display statistics on updates

Now we will see how to find the cancelled update




SAP COMMUNITY NETWORK                SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                    9
LO Extraction – Part 2 Database Update Logic




Here if you double click on first one you will see the detailed info.




Get the update key from here.

Update key: 45E79BDF6891F199BB140019BBCCEC70
Now as we know we can check the status of update in the update header table, we will check that
SE11: VBHDR




SAP COMMUNITY NETWORK                    SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                        10
LO Extraction – Part 2 Database Update Logic




Similarly you can find the records that are yet to be updated




Like this you can find the V1 executed, V2 executed etc.
Now we will see the detailed explanation for the update status.




SAP COMMUNITY NETWORK                  SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                      11
LO Extraction – Part 2 Database Update Logic




Update status

Status                  Phase

initial                 The update request has been created, but has not yet been completely
                        processed. (This status applies from the moment the dialog work
                        process transfers the update request to the update work process to the
                        COMMIT in the update work process).

Error                   An error occurred in the init phase, which prevents the update from
                        being carried out.

Error (no               The update request has been canceled and the update cannot be
retry)                  repeated.

V1 processed            The init phase has been successfully completed, and the V2
                        modules are being passed on for further processing. If no V2 modules
                        exist, this update request no longer appears in the overview.

V2 processed            The V2 modules have also been processed correctly, but there is still a
                        collective run (can be regarded as V3) to be carried out.

                        If there is no collective processing to be carried out, this update
                        request no longer appears in the overview.

processed               If the parameter rdisp/vb_delete_after_execution is set to 2 - in other
                        words, if automatic deletion is deactivated - an update that has been
                        successfully completed has the status ok. If automatic deletion is
                        activated (default), the update record no longer appears in the
                        overview.

to delete               This update request has been marked for deletion.

Enqueues                The SAP locks belonging to this update request were manually deleted
deleted                 (SM12).

Like this you can identify the status of the update records.
In my next part I will explain about the LO extractors and their working logic…..




SAP COMMUNITY NETWORK                   SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                       12
LO Extraction – Part 2 Database Update Logic




Related Content
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1034bcbe-b459-2d10-2a89-ecdeb4e53ff1
For more information, visit the EDW homepage




SAP COMMUNITY NETWORK               SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                   13
LO Extraction – Part 2 Database Update Logic




Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this docume nt
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("S AP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Gro up shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.




SAP COMMUNITY NETWORK                            SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG                                                                                                                14

Más contenido relacionado

La actualidad más candente

How to write a routine for 0 calday in infopackage selection
How to write a routine for 0 calday in infopackage selectionHow to write a routine for 0 calday in infopackage selection
How to write a routine for 0 calday in infopackage selectionValko Arbalov
 
How to use abap cds for data provisioning in bw
How to use abap cds for data provisioning in bwHow to use abap cds for data provisioning in bw
How to use abap cds for data provisioning in bwLuc Vanrobays
 
Enhancing data sources with badi in SAP ABAP
Enhancing data sources with badi in SAP ABAPEnhancing data sources with badi in SAP ABAP
Enhancing data sources with badi in SAP ABAPAabid Khan
 
BW Adjusting settings and monitoring data loads
BW Adjusting settings and monitoring data loadsBW Adjusting settings and monitoring data loads
BW Adjusting settings and monitoring data loadsLuc Vanrobays
 
Using error stack and error dt ps in sap bi 7.0
Using error stack and error dt ps in sap bi 7.0Using error stack and error dt ps in sap bi 7.0
Using error stack and error dt ps in sap bi 7.0gireesho
 
Customer exit variables in sap
Customer exit variables in sapCustomer exit variables in sap
Customer exit variables in sapsaborhade
 
Errors in process chains
Errors in process chainsErrors in process chains
Errors in process chainsSiva Kollipara
 
Introduction to extracting data from sap s 4 hana with abap cds views
Introduction to extracting data from sap s 4 hana with abap cds viewsIntroduction to extracting data from sap s 4 hana with abap cds views
Introduction to extracting data from sap s 4 hana with abap cds viewsLuc Vanrobays
 
Line item dimension and high cardinality dimension
Line item dimension and high cardinality dimensionLine item dimension and high cardinality dimension
Line item dimension and high cardinality dimensionPraveen Kumar
 
SAP BI Generic Extraction Using a Function Module.pdf
SAP BI Generic Extraction Using a Function Module.pdfSAP BI Generic Extraction Using a Function Module.pdf
SAP BI Generic Extraction Using a Function Module.pdfKoushikGuna
 
Hybrid provider based on dso using real time data acquisition in sap bw 7.30
Hybrid provider based on dso using real time data acquisition in sap bw 7.30Hybrid provider based on dso using real time data acquisition in sap bw 7.30
Hybrid provider based on dso using real time data acquisition in sap bw 7.30Sabyasachi Das
 
Analysis process designer (apd) part 2
Analysis process designer (apd) part   2Analysis process designer (apd) part   2
Analysis process designer (apd) part 2dejavee
 
Data ingestion and Acquisition on SAP Analytics Cloud
Data ingestion and Acquisition on SAP Analytics CloudData ingestion and Acquisition on SAP Analytics Cloud
Data ingestion and Acquisition on SAP Analytics CloudMadhumita Banerjee
 
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...Luc Vanrobays
 
How to run v3 job
How to run v3 jobHow to run v3 job
How to run v3 jobAnil Kumar
 
Find out userexits in sap
Find out userexits in sapFind out userexits in sap
Find out userexits in sapDau Thanh Hai
 

La actualidad más candente (20)

How to write a routine for 0 calday in infopackage selection
How to write a routine for 0 calday in infopackage selectionHow to write a routine for 0 calday in infopackage selection
How to write a routine for 0 calday in infopackage selection
 
How to use abap cds for data provisioning in bw
How to use abap cds for data provisioning in bwHow to use abap cds for data provisioning in bw
How to use abap cds for data provisioning in bw
 
Enhancing data sources with badi in SAP ABAP
Enhancing data sources with badi in SAP ABAPEnhancing data sources with badi in SAP ABAP
Enhancing data sources with badi in SAP ABAP
 
SAP BI/BW
SAP BI/BWSAP BI/BW
SAP BI/BW
 
BW Adjusting settings and monitoring data loads
BW Adjusting settings and monitoring data loadsBW Adjusting settings and monitoring data loads
BW Adjusting settings and monitoring data loads
 
Using error stack and error dt ps in sap bi 7.0
Using error stack and error dt ps in sap bi 7.0Using error stack and error dt ps in sap bi 7.0
Using error stack and error dt ps in sap bi 7.0
 
Customer exit variables in sap
Customer exit variables in sapCustomer exit variables in sap
Customer exit variables in sap
 
Errors in process chains
Errors in process chainsErrors in process chains
Errors in process chains
 
SAP BW - Info cube
SAP BW - Info cubeSAP BW - Info cube
SAP BW - Info cube
 
Co pa extraction
Co pa extractionCo pa extraction
Co pa extraction
 
Introduction to extracting data from sap s 4 hana with abap cds views
Introduction to extracting data from sap s 4 hana with abap cds viewsIntroduction to extracting data from sap s 4 hana with abap cds views
Introduction to extracting data from sap s 4 hana with abap cds views
 
Line item dimension and high cardinality dimension
Line item dimension and high cardinality dimensionLine item dimension and high cardinality dimension
Line item dimension and high cardinality dimension
 
Extractioncockpit
Extractioncockpit Extractioncockpit
Extractioncockpit
 
SAP BI Generic Extraction Using a Function Module.pdf
SAP BI Generic Extraction Using a Function Module.pdfSAP BI Generic Extraction Using a Function Module.pdf
SAP BI Generic Extraction Using a Function Module.pdf
 
Hybrid provider based on dso using real time data acquisition in sap bw 7.30
Hybrid provider based on dso using real time data acquisition in sap bw 7.30Hybrid provider based on dso using real time data acquisition in sap bw 7.30
Hybrid provider based on dso using real time data acquisition in sap bw 7.30
 
Analysis process designer (apd) part 2
Analysis process designer (apd) part   2Analysis process designer (apd) part   2
Analysis process designer (apd) part 2
 
Data ingestion and Acquisition on SAP Analytics Cloud
Data ingestion and Acquisition on SAP Analytics CloudData ingestion and Acquisition on SAP Analytics Cloud
Data ingestion and Acquisition on SAP Analytics Cloud
 
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...
Dmm300 – mixed scenarios for sap hana data warehousing and BW: overview and e...
 
How to run v3 job
How to run v3 jobHow to run v3 job
How to run v3 job
 
Find out userexits in sap
Find out userexits in sapFind out userexits in sap
Find out userexits in sap
 

Destacado

Extractions and performance monitoring
Extractions and performance monitoringExtractions and performance monitoring
Extractions and performance monitoringJNTU University
 
Analysis process designer (apd) part 1
Analysis process designer (apd) part   1Analysis process designer (apd) part   1
Analysis process designer (apd) part 1dejavee
 
Bw writing routines in update rules
Bw writing routines in update rulesBw writing routines in update rules
Bw writing routines in update rulesknreddyy
 
Building the Business Case for SAP HANA
Building the Business Case for SAP HANABuilding the Business Case for SAP HANA
Building the Business Case for SAP HANABluefin Solutions
 
Delivering digital devolution in local authorities bluefin solutions - dece...
Delivering digital devolution in local authorities   bluefin solutions - dece...Delivering digital devolution in local authorities   bluefin solutions - dece...
Delivering digital devolution in local authorities bluefin solutions - dece...Bluefin Solutions
 
SAP Accounts Reveivable Financial Transaction | http://sapdocs.info
SAP Accounts Reveivable Financial Transaction | http://sapdocs.infoSAP Accounts Reveivable Financial Transaction | http://sapdocs.info
SAP Accounts Reveivable Financial Transaction | http://sapdocs.infosapdocs. info
 
List Processing in ABAP
List Processing in ABAPList Processing in ABAP
List Processing in ABAPsapdocs. info
 
2015 04 Preparing for the SAP S/4HANA Migration
2015 04 Preparing for the SAP S/4HANA Migration2015 04 Preparing for the SAP S/4HANA Migration
2015 04 Preparing for the SAP S/4HANA MigrationBluefin Solutions
 
Message, Debugging, File Transfer and Type Group
Message, Debugging, File Transfer and Type GroupMessage, Debugging, File Transfer and Type Group
Message, Debugging, File Transfer and Type Groupsapdocs. info
 

Destacado (13)

Extractors sapr3
Extractors sapr3Extractors sapr3
Extractors sapr3
 
Extractions and performance monitoring
Extractions and performance monitoringExtractions and performance monitoring
Extractions and performance monitoring
 
Field symbols
Field symbolsField symbols
Field symbols
 
Analysis process designer (apd) part 1
Analysis process designer (apd) part   1Analysis process designer (apd) part   1
Analysis process designer (apd) part 1
 
Usgage of ABAP in BI
Usgage of ABAP in BIUsgage of ABAP in BI
Usgage of ABAP in BI
 
Bw writing routines in update rules
Bw writing routines in update rulesBw writing routines in update rules
Bw writing routines in update rules
 
Building the Business Case for SAP HANA
Building the Business Case for SAP HANABuilding the Business Case for SAP HANA
Building the Business Case for SAP HANA
 
Delivering digital devolution in local authorities bluefin solutions - dece...
Delivering digital devolution in local authorities   bluefin solutions - dece...Delivering digital devolution in local authorities   bluefin solutions - dece...
Delivering digital devolution in local authorities bluefin solutions - dece...
 
SAP Accounts Reveivable Financial Transaction | http://sapdocs.info
SAP Accounts Reveivable Financial Transaction | http://sapdocs.infoSAP Accounts Reveivable Financial Transaction | http://sapdocs.info
SAP Accounts Reveivable Financial Transaction | http://sapdocs.info
 
List Processing in ABAP
List Processing in ABAPList Processing in ABAP
List Processing in ABAP
 
2015 04 Preparing for the SAP S/4HANA Migration
2015 04 Preparing for the SAP S/4HANA Migration2015 04 Preparing for the SAP S/4HANA Migration
2015 04 Preparing for the SAP S/4HANA Migration
 
Message, Debugging, File Transfer and Type Group
Message, Debugging, File Transfer and Type GroupMessage, Debugging, File Transfer and Type Group
Message, Debugging, File Transfer and Type Group
 
ABAP Advanced List
ABAP Advanced ListABAP Advanced List
ABAP Advanced List
 

Similar a Lo extraction part 2 database update logic

Spring_Boot_Microservices-5_Day_Session.pptx
Spring_Boot_Microservices-5_Day_Session.pptxSpring_Boot_Microservices-5_Day_Session.pptx
Spring_Boot_Microservices-5_Day_Session.pptxPrabhakaran Ravichandran
 
Performance tuning in sap bi 7.0
Performance tuning in sap bi 7.0Performance tuning in sap bi 7.0
Performance tuning in sap bi 7.0gireesho
 
SAP BI/DW Training with BO Integration
SAP BI/DW Training with BO IntegrationSAP BI/DW Training with BO Integration
SAP BI/DW Training with BO Integrationmishra4927
 
Errors while sending packages from oltp to bi (one of error at the time of da...
Errors while sending packages from oltp to bi (one of error at the time of da...Errors while sending packages from oltp to bi (one of error at the time of da...
Errors while sending packages from oltp to bi (one of error at the time of da...bhaskarbi
 
Abap slide lock Enqueue data clusters auth checks
Abap slide lock Enqueue data clusters auth checksAbap slide lock Enqueue data clusters auth checks
Abap slide lock Enqueue data clusters auth checksMilind Patil
 
Abap slide lockenqueuedataclustersauthchecks
Abap slide lockenqueuedataclustersauthchecksAbap slide lockenqueuedataclustersauthchecks
Abap slide lockenqueuedataclustersauthchecksMilind Patil
 
InnovizeIT for DB2_Product Overview_may2014
InnovizeIT for DB2_Product Overview_may2014InnovizeIT for DB2_Product Overview_may2014
InnovizeIT for DB2_Product Overview_may2014Eliezer Harkavi
 
Potential Solutions Co Existence
Potential Solutions   Co ExistencePotential Solutions   Co Existence
Potential Solutions Co ExistenceRoman Agaev
 
Planning guide sap business suite 7 2013 landscape implementation
Planning guide sap business suite 7 2013  landscape implementationPlanning guide sap business suite 7 2013  landscape implementation
Planning guide sap business suite 7 2013 landscape implementationLeonardo Parpal Roig
 
Why Does Modular Middleware Matters
Why Does Modular Middleware MattersWhy Does Modular Middleware Matters
Why Does Modular Middleware MattersWSO2
 
Pivotal Cloud Foundry 2.6: A First Look
Pivotal Cloud Foundry 2.6: A First LookPivotal Cloud Foundry 2.6: A First Look
Pivotal Cloud Foundry 2.6: A First LookVMware Tanzu
 
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...IRJET Journal
 
Optimized dso data activation using massive parallel processing in sap net we...
Optimized dso data activation using massive parallel processing in sap net we...Optimized dso data activation using massive parallel processing in sap net we...
Optimized dso data activation using massive parallel processing in sap net we...Nuthan Kishore
 
Upgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsUpgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsMarna Walle
 

Similar a Lo extraction part 2 database update logic (20)

SAP Basis CCMS
SAP Basis CCMSSAP Basis CCMS
SAP Basis CCMS
 
Spring_Boot_Microservices-5_Day_Session.pptx
Spring_Boot_Microservices-5_Day_Session.pptxSpring_Boot_Microservices-5_Day_Session.pptx
Spring_Boot_Microservices-5_Day_Session.pptx
 
SAP BOBJ Rapid Marts Overview I
SAP BOBJ Rapid Marts Overview ISAP BOBJ Rapid Marts Overview I
SAP BOBJ Rapid Marts Overview I
 
Performance tuning in sap bi 7.0
Performance tuning in sap bi 7.0Performance tuning in sap bi 7.0
Performance tuning in sap bi 7.0
 
SAP BI/DW Training with BO Integration
SAP BI/DW Training with BO IntegrationSAP BI/DW Training with BO Integration
SAP BI/DW Training with BO Integration
 
Errors while sending packages from oltp to bi (one of error at the time of da...
Errors while sending packages from oltp to bi (one of error at the time of da...Errors while sending packages from oltp to bi (one of error at the time of da...
Errors while sending packages from oltp to bi (one of error at the time of da...
 
Abap slide lock Enqueue data clusters auth checks
Abap slide lock Enqueue data clusters auth checksAbap slide lock Enqueue data clusters auth checks
Abap slide lock Enqueue data clusters auth checks
 
Abap slide lockenqueuedataclustersauthchecks
Abap slide lockenqueuedataclustersauthchecksAbap slide lockenqueuedataclustersauthchecks
Abap slide lockenqueuedataclustersauthchecks
 
InnovizeIT for DB2_Product Overview_may2014
InnovizeIT for DB2_Product Overview_may2014InnovizeIT for DB2_Product Overview_may2014
InnovizeIT for DB2_Product Overview_may2014
 
Potential Solutions Co Existence
Potential Solutions   Co ExistencePotential Solutions   Co Existence
Potential Solutions Co Existence
 
Planning guide sap business suite 7 2013 landscape implementation
Planning guide sap business suite 7 2013  landscape implementationPlanning guide sap business suite 7 2013  landscape implementation
Planning guide sap business suite 7 2013 landscape implementation
 
Why Does Modular Middleware Matters
Why Does Modular Middleware MattersWhy Does Modular Middleware Matters
Why Does Modular Middleware Matters
 
309675745
309675745309675745
309675745
 
Pivotal Cloud Foundry 2.6: A First Look
Pivotal Cloud Foundry 2.6: A First LookPivotal Cloud Foundry 2.6: A First Look
Pivotal Cloud Foundry 2.6: A First Look
 
Cellediting bex
Cellediting bexCellediting bex
Cellediting bex
 
X-2E Modernize
X-2E ModernizeX-2E Modernize
X-2E Modernize
 
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...
Limited Budget but Effective End to End MLOps Practices (Machine Learning Mod...
 
Optimized dso data activation using massive parallel processing in sap net we...
Optimized dso data activation using massive parallel processing in sap net we...Optimized dso data activation using massive parallel processing in sap net we...
Optimized dso data activation using massive parallel processing in sap net we...
 
Sdlc
SdlcSdlc
Sdlc
 
Upgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsUpgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actions
 

Último

2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptxSandy Millin
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17Celine George
 
Education and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxEducation and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxraviapr7
 
How to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesHow to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesCeline George
 
3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptxmary850239
 
Drug Information Services- DIC and Sources.
Drug Information Services- DIC and Sources.Drug Information Services- DIC and Sources.
Drug Information Services- DIC and Sources.raviapr7
 
HED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfHED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfMohonDas
 
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINT
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINTARTICULAR DISC OF TEMPOROMANDIBULAR JOINT
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINTDR. SNEHA NAIR
 
CapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapitolTechU
 
Optical Fibre and It's Applications.pptx
Optical Fibre and It's Applications.pptxOptical Fibre and It's Applications.pptx
Optical Fibre and It's Applications.pptxPurva Nikam
 
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptx
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptxSOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptx
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptxSyedNadeemGillANi
 
Riddhi Kevadiya. WILLIAM SHAKESPEARE....
Riddhi Kevadiya. WILLIAM SHAKESPEARE....Riddhi Kevadiya. WILLIAM SHAKESPEARE....
Riddhi Kevadiya. WILLIAM SHAKESPEARE....Riddhi Kevadiya
 
Diploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfDiploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfMohonDas
 
Ultra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxUltra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxDr. Asif Anas
 
Work Experience for psp3 portfolio sasha
Work Experience for psp3 portfolio sashaWork Experience for psp3 portfolio sasha
Work Experience for psp3 portfolio sashasashalaycock03
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...Nguyen Thanh Tu Collection
 
Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxraviapr7
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17Celine George
 

Último (20)

2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17
 
Education and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptxEducation and training program in the hospital APR.pptx
Education and training program in the hospital APR.pptx
 
How to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 SalesHow to Manage Cross-Selling in Odoo 17 Sales
How to Manage Cross-Selling in Odoo 17 Sales
 
3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptx
 
Drug Information Services- DIC and Sources.
Drug Information Services- DIC and Sources.Drug Information Services- DIC and Sources.
Drug Information Services- DIC and Sources.
 
HED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfHED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdf
 
Prelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quizPrelims of Kant get Marx 2.0: a general politics quiz
Prelims of Kant get Marx 2.0: a general politics quiz
 
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINT
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINTARTICULAR DISC OF TEMPOROMANDIBULAR JOINT
ARTICULAR DISC OF TEMPOROMANDIBULAR JOINT
 
CapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptx
 
Optical Fibre and It's Applications.pptx
Optical Fibre and It's Applications.pptxOptical Fibre and It's Applications.pptx
Optical Fibre and It's Applications.pptx
 
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptx
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptxSOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptx
SOLIDE WASTE in Cameroon,,,,,,,,,,,,,,,,,,,,,,,,,,,.pptx
 
Riddhi Kevadiya. WILLIAM SHAKESPEARE....
Riddhi Kevadiya. WILLIAM SHAKESPEARE....Riddhi Kevadiya. WILLIAM SHAKESPEARE....
Riddhi Kevadiya. WILLIAM SHAKESPEARE....
 
Diploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdfDiploma in Nursing Admission Test Question Solution 2023.pdf
Diploma in Nursing Admission Test Question Solution 2023.pdf
 
Ultra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptxUltra structure and life cycle of Plasmodium.pptx
Ultra structure and life cycle of Plasmodium.pptx
 
Work Experience for psp3 portfolio sasha
Work Experience for psp3 portfolio sashaWork Experience for psp3 portfolio sasha
Work Experience for psp3 portfolio sasha
 
Finals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quizFinals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quiz
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
 
Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptx
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17
 

Lo extraction part 2 database update logic

  • 1. LO Extraction – Part 2 Database Update Logic Applies to: SAP BI, NW2004s Business Intelligence, ABAP, BI For more information, visit the EDW homepage. Summary This article explains about LO extraction logic, architecture and background tables involved. Author : P. Renjith Kumar Company : SAP Labs India Created on : 1 January 2010 Author Bio P Renjith Kumar is presently working in SAP Labs India Pvt Ltd and specializes in Extraction and Modeling areas of BI. Basically as an ABAP consultant, he has extensive cross functional experience and has been with end to end SAP ERP and BI implementation projects across manufacturing domain. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 1
  • 2. LO Extraction – Part 2 Database Update Logic Table of Contents Prerequisite................................................................................................................................................... 3 Introduction ................................................................................................................................................... 3 The update process ...................................................................................................................................... 3 V1 and V2 Update Modules........................................................................................................................... 4 Update Request ............................................................................................................................................ 5 Transactions and Logical Units of Work......................................................................................................... 6 LUW: Logical Unit of Work: ........................................................................................................................... 7 DB LUW........................................................................................................................................................ 7 SAP LUW ..................................................................................................................................................... 8 The Update Mechanism: ............................................................................................................................... 8 How to check update status .......................................................................................................................... 8 Update status.............................................................................................................................................. 12 Related Content .......................................................................................................................................... 13 Copyright .................................................................................................................................................... 14 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 2
  • 3. LO Extraction – Part 2 Database Update Logic Prerequisite Once you are done with the first part of the article you can understand this article clearly. You can find the first part here. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1034bcbe-b459-2d10-2a89-ecdeb4e53ff1 Introduction This part deals with the LO extraction logic, its architecture, working mechanism and background tables and reports involved. The update process When you do some transaction like creating/changing sales order, purchase order and press save what happens? It is either saved into database or some error occurs. We will see how this happen. The update system is used to lighten the workload of the SAP transactions when time-consuming changes are made to the database. The changes are carried out asynchronously  usually with short delays in between  by special update work processes. At the end of a transaction COMMIT WORK and the update task are called; the dialog part of the SAP transaction is closed, and the update part of the SAP logical unit of work (LUW) is started. The following graphic illustrates the necessary actions and the sequence in which they execute the different workprocess . After the transaction has been processed, the dialog process completes the VBHDR entry (the update header of the update request) and searches an update server for the V1 update The update server distributes the tasks to an update work process. This processes the V1 modules of the update request, triggers a COMMIT to the database, and releases the SAP locks on the update request The work process then searches for an update server for the V2 update, providing V2 update modules exist. A V2 update server then passes this onto a V2 work process, which processes the V2 modules and triggers a COMMIT to the database. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 3
  • 4. LO Extraction – Part 2 Database Update Logic Processing the V1 modules involves transferring the contents of the update tables VBMOD and VBDATA to the application tables of the database. The changes are not actually made to the tables in the database until the database LUW in which this takes place is completed. The SAP locks are released and, if V2 update modules exist, the V2 update is started. This is similar to the V1 update with the exception that there are no locks that have to released and no search for a process for further processing. Now we need to see about V1 and V2 updates in detail V1 and V2 Update Modules An update is divided into different modules. Each module corresponds to an update function module. There are two types of module. The SAP System makes a distinction between primary, time-critical (V1) and secondary, non-time-critical (V2) update modules. The system also supports collective runs for function modules that are used on a regular basis. This distinction allows the system to process critical database changes before less critical changes.  V1 modules describe critical or primary changes; these affect objects that have a controlling function in the SAP System, for example order creation or changes to material stock.  V2 modules describe less critical secondary changes. These are pure statistical updates, for example, such as result calculations. The V1 modules are processed consecutively in a single update work process on the same application server. This means that they belong to the same database LUW and can be reversed. Furthermore, V1 updates are carried out under the SAP locks of the transaction that creates the update. This ensures that the data remains consistent; simultaneous changes to the objects to be updated are not possible. All V2 updates are carried out in a separate LUW and not under the locks of the transaction that creates them. If your SAP System contains a work process for V2 updates, these are only carried out in this work process. If this is not the case, the V2 components are processed by a V1 update process. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 4
  • 5. LO Extraction – Part 2 Database Update Logic All V1 modules of an update must be processed before the V2 modules. Now we see about update request Update Request An update request or update record describes the data changes defined in an SAP LUW, which are carried out either in full or not at all (in a database LUW). (This only applies to V1 updates. V2 updates are triggered once the V1 update has been completed, and therefore take place in a separate database LUW.) Structure of update record An update request comprises an update header, V1 modules (or components), V2 modules and a collective run. An update module corresponds to a function module, and contains the update data and, in certain cases, error information, which is generated if the update is canceled. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 5
  • 6. LO Extraction – Part 2 Database Update Logic The following update tables in the database contain the following information: Update Table Contents/Description VBHDR Update headers (one per update record) VBMOD Update modules (one per function module), n V1 modules and m V2 modules per update request. VBDATA Data which is transferred to the modules (variables, structures, internal tables) VBERROR Error information which is generated if an update is canceled Now we need to know about LUW. Transactions and Logical Units of Work In everyday language, a transaction is a sequence of actions that logically belong together in a business sense and those either procure or process data. It covers a self-contained procedure, for example, generating a list of customers, creating a flight booking, or sending reminders to customers. From the user’s viewpoint, it forms a logical unit. The completeness and correctness of data must be assured within this unit. In the middle of a transaction, the data will usually be inconsistent. For example, when you transfer an amount in financial accounting, this must first be deducted from one account before being credited to another. In between the two postings, the data is inconsistent, since the amount that you are posting does not exist in either account. It is essential for application programmers to know that their data is consistent at the end of the transaction. If an error occurs, it must be possible to undo the changes made within a logical process. In the R/3 System, there are three terms frequently used in this context: Database Logical Unit of Work (DB LUW) A database LUW is the mechanism used by the database to ensure that its data is always consistent. SAP LUW An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. SAP Transaction An SAP transaction is an application program that you start using a transaction code. It may contain one or more SAP LUWs. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 6
  • 7. LO Extraction – Part 2 Database Update Logic LUW: Logical Unit of Work: A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit. LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started. An LUW ends 1. When the database changes have been confirmed (database commit) or 2. When the database changes have been canceled (database rollback) An LUW begins 1. Each time you start a transaction 2. When the database changes of the previous LUW have been confirmed (database commit) 3. When the database changes of the previous LUW have been cancelled (database rollback) DB LUW From the point of view of database programming, a database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started. The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3 System, database commits and rollbacks can be triggered either implicitly or using explicit commands. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 7
  • 8. LO Extraction – Part 2 Database Update Logic SAP LUW The Open SQL statements INSERT, UPDATE, MODIFY, and DELETE allow you to program database changes that extend over several dialog steps. Even if you have not explicitly programmed a database commit, the implicit database commit that occurs after a screen has been processed concludes the database LUW. The following diagram shows the individual database LUWs in a typical screen sequence: Note A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of different work processes. If an SAP LUW contains database changes, you should either write all of them or none at all to the database. To ensure that this happens, you must include a database commit when your transaction has ended successfully, and a database rollback in case the program detects an error. An example for V1 and V2 update The Update Mechanism: V1 - Synchronous update V2 - Asynchronous update V3 - Batch asynchronous update If you create/change a sales order (VA01/VA02), when you press 'SAVE' and see a success message (Sales Order.... created/ changed..), the update to underlying tables VBAK/VBAP has happened (before you saw the message). This update was executed in the V1 work process. There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S*** stores sales data (it is the same data as VBAK/VBAP stored redundantly, but in a different structure to optimize reporting).Now, these tables are updated with the transaction you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13. V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (LBWE definitions) to process these. This is again to optimize performance. V2 and V3 are separated from V1 as these are not as real-time critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted. We will see V3 in the later part. How to check update status 1. Start Update System Administration. To do this, choose Tools > Administration > Monitor > Update. Alternatively enter transaction code SM13. 2. Check if the update is active. One of the following messages is output at the bottom of the initial screen of the Update System: o Update is active o Update is deactivated Make sure that you see “Update is active” Here is an example to see, this is a screen shot from SM13 transaction SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 8
  • 9. LO Extraction – Part 2 Database Update Logic Update management (SM13) is used for the following:  Display update requests  Analyze problems pertaining to the update  Test and debug canceled update requests  Display and reset the status of update requests  Display statistics on updates Now we will see how to find the cancelled update SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 9
  • 10. LO Extraction – Part 2 Database Update Logic Here if you double click on first one you will see the detailed info. Get the update key from here. Update key: 45E79BDF6891F199BB140019BBCCEC70 Now as we know we can check the status of update in the update header table, we will check that SE11: VBHDR SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 10
  • 11. LO Extraction – Part 2 Database Update Logic Similarly you can find the records that are yet to be updated Like this you can find the V1 executed, V2 executed etc. Now we will see the detailed explanation for the update status. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 11
  • 12. LO Extraction – Part 2 Database Update Logic Update status Status Phase initial The update request has been created, but has not yet been completely processed. (This status applies from the moment the dialog work process transfers the update request to the update work process to the COMMIT in the update work process). Error An error occurred in the init phase, which prevents the update from being carried out. Error (no The update request has been canceled and the update cannot be retry) repeated. V1 processed The init phase has been successfully completed, and the V2 modules are being passed on for further processing. If no V2 modules exist, this update request no longer appears in the overview. V2 processed The V2 modules have also been processed correctly, but there is still a collective run (can be regarded as V3) to be carried out. If there is no collective processing to be carried out, this update request no longer appears in the overview. processed If the parameter rdisp/vb_delete_after_execution is set to 2 - in other words, if automatic deletion is deactivated - an update that has been successfully completed has the status ok. If automatic deletion is activated (default), the update record no longer appears in the overview. to delete This update request has been marked for deletion. Enqueues The SAP locks belonging to this update request were manually deleted deleted (SM12). Like this you can identify the status of the update records. In my next part I will explain about the LO extractors and their working logic….. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 12
  • 13. LO Extraction – Part 2 Database Update Logic Related Content http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1034bcbe-b459-2d10-2a89-ecdeb4e53ff1 For more information, visit the EDW homepage SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 13
  • 14. LO Extraction – Part 2 Database Update Logic Copyright © Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this docume nt serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("S AP Group") for informational purposes only, without representation or warranty of any kind, and SAP Gro up shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 14