Skip to Content

Data flow from ECC to BW/BI:Locockpit

Experts,

Gone through so many documents and threads.Confused with the flow.If you are 100% sure,kindly help me.

How delta data flows from ECC to BW/BI in Direct delta, Queued delta and Unserialised V3 update in Locockpit?What are V1,V2 and V3 updates.

Please, give me clear idea with simple words.

Anand

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    Jul 03, 2012 at 02:17 PM
    Add comment
    10|10000 characters needed characters exceeded

  • Jun 26, 2012 at 04:27 AM

    I don't have proper authorizations in ECC to check my self

    Add comment
    10|10000 characters needed characters exceeded

    • Aravind,

      We don't use v2 update mode in lo extraction, v2 update mode is used to load the statistical tables that are used in abap reporting.This is useful point for me in our whole discussion, if you are 100% sure.😕

      How come these statisticals are usefull in data extraction(excuse me if it is basic question)

      Could you please reply to my previous post which was replied by Mr. Babu.Because he came with a concept that V3 update method and V3 periodic job are different.

      Anand.

  • avatar image
    Former Member
    Jun 26, 2012 at 07:00 PM

    Hi,

       Go to this documents, i think it would be helpful

    http://scn.sap.com/people/happy.tony/blog/2006/11/24/gist-of-lo-cockpit-delta

    and for v1 and v2

    • V1 Update – Synchronous Update
      • If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
    • V2 Update – Asynchronous Update

    If you create/change a purchase order (me21n/me22n), when you press 'SAVE' it takes few seconds to update to underlying tables EKKO/EKPO depending on system load. This update was executed in the V2 work process.


    Add comment
    10|10000 characters needed characters exceeded

  • Jul 06, 2012 at 09:13 AM

    Hi folks,

    Kindly, share your final views for conclusion.

    Queued delta:

    How data flows, Document posting --------->LBWQ?

    Unserialised V3 update:

    How data flows from Document posting ----------------.SM13?

    Chandra SekharVenkateswarlu NandimandalamKiran Vasant KereAravind Nag M, Ravi Chandra

    Anand.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi chandu,

      Helpful blog,but

      How serialized delta is dependent of V2 update?I don't understand where it is in the LO flow.

      And confirm me, any difference between V3 module call and V3 collective run in seriaized delta method?

      Anand.

  • avatar image
    Former Member
    Feb 11, 2015 at 09:08 PM

    Hi Anand,

    Refer the below document help  you atleast what are V* jobs and how they are using in LO cockpit extraction.

    V1  Job:  V1 job is  Synchronous Update Method – When we use this type of update method after the first successfully entered the signal comes back as the first record is entered successfully. Then only the next record will enters into the file. If the first record fails, then there is no further process. Even though the first record enters into the file successfully, the 2nd record will wait until the signal comes back. So here a performance is decreases. One more point is that there is no background process for V1 update method.

    V2 Job: It is  Asynchronous Update Method –When we use this type of method there no need to the signal comes back to enter the second record. It automatically the 2nd record will enters into the file. If there is any in the first record, it will not wait until it is corrected; the 2nd record enters into the file. Here the first drawback is over comes here. But the 2nd one is there i.e. here also there no background process.

    V3  Job:  Asynchronous Background Update Method – Here by seeing name itself we can understand this. I.e. it is Asynchronous Update Method with background job. below are the update methods

    A) Direct Delta:- In case of Direct delta LUW’s are directly posted to Delta Queue RSA7 and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW’s are directly posted to Delta QueueRSA7 the application is kept waiting until all the enhancement code is executed.


    B) Queued Delta: - In case of Queued Delta LUW’s are posted to Extractor queue LBWQ by scheduling the V3 job we move the documents from Extractor queue LBWQ to Delta Queue RSA7and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUW’s, which are missed.


    Set up tables is to store and pull the historic data in BW.

    Once you do an init and start  to filling the set up tables the delta queue is created in RSA7 which stores the delta.

    So once your set up tables are finished you do full repair or full load from the data source to target and then you run the delta's in BW.

    Kind Regards,

    Sam

    Add comment
    10|10000 characters needed characters exceeded