Skip to Content

In this document, I will explain about V1, V2 and V3 updates and different update methods.

V1, V2 and V3 updates are different work processors on application server that takes the update LUW (Logistic Unit of Work) from running the program and executing it

V1 Update:

  • V1 updates are processed consecutively in a single update work process on the same application server
  • V1 update ensures serialization of data and it denoted primary changes that are time critical
  • V1 run uses more resources when compared to V3 run
  • In the figure below, when an order number is created in the tcode VA01, it goes into application tables and statistical tables in V1 update. Hence, it ensures serialization

v1 update.bmp

Note: The statistical tables are BI related tables such as Delta Queue, Extraction Queue and Update tables whereas the application tables are the database tables

V2 Update:

  • V2 updates are less critical secondary changes
  • They are statistical changes such as result calculation


v2.JPG

V3 Update:

  • V3 updates are similar to V2 updates and specifically used for BW extractions
  • Serialization is not ensured (Disadvantage)
  • V3 uses less number of resources when compared to V1 update

v3.JPG

Update Methods:

There are three different update methods. They are

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

Note: Pre-requisites for all the data flow diagrams are

  1. Make sure that the RFC Connection exists between SAP ECC and SAP BI
  2. Delete the data in setup tables

  1. Direct Delta:
  • In this update method, data is directly transferred to Delta Queue and application tables at same time, with every document posting
  • Here, 1 document = 1 LUW (Logistic Unit of Work)

(Click on the image to enlarge it)

  • By writing to delta queue with V1 posting process, serialization is ensured
  • This update method is recommended for customers with few documents
  • Additional monitoring of update tables or extraction queue is not required

2. Queued Delta:

  • In this update method, the records are first sent to ‘Extraction Queue’ using V1 update
  • From ‘Extraction Queue’, we need to send the records to ‘Delta Queue’ using collection run
  • In this update method, we can collect up to 10,000 documents in one LUW

(Click on the image to enlarge it)

  • By posting the documents to extraction queue using V1 update, serialization is ensured
  • We can reduce the downtime by using queued delta method

3.  Unserialized V3 update:

  • Here, the extracted data of an application is written to update tables using V3 update
  • We need to send the data from Update Tables (SM13) to Delta Queue (RSA7) using Collection Run
  • In this, serialization of documents is not guaranteed

(Click on the image to enlarge it)

  • Updating to a DSO with Overwrite mode is not recommended using this update method
  • This is recommended when we want to send the data to info cubes or DSO’s with additive mode


Related documents:

SAP Note 505700 – LBWE: New update methods as of PI 2002.1

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Jason Lax

    It’s very difficult to read and find the information posted when you share screenshots instead of using the text editor. Please reconsider.

    (0) 
    1. Ning Wang

      This is actually a very excellent document . You just need to click and enlarge the pic to have a clear image.

      A picture is worth a thousand words

      (0) 
  2. pratish balasubramanian

    Hi Saideep,

    I am a fresher to BI. I have a doubt. As per my understanding in all the updates we exract data from delta queue, by means of infopackage to SAP BI. But why there is a seperate flow VA01-> database tables ->setup tables and then using an infopackage to extract to BI. Can u please clarify?

    (0) 
  3. NIgam Mishra

    Hi Saideep,

    I have a doubt in Unserialized V3 update, i.e. if this is unserialized then how it is recommended for Info cubes/DSOs in additive mode(this might add something in wrong sequence resulting a wrong output) ?


    Thanks in advance.

    (0) 
  4. Arthur Rodrigues

    Dear Saideep,

    You have no idea how grateful I am for this great article with diagrams. I read this link

    SAP BW BI end-end information: LO-COCKPIT extraction

    and I was not quite getting exactly where is this extraction and update and delta queue thing.But you helped. Only thing I found missing in your document is the 4th delta load method (which is explained as 1st method in the link. i.e. serialized V3 ). But apart from that your document was best to get my understanding clear. God Bless.

    Regards,

    King Arthur

    (0) 

Leave a Reply