Regarding the Extractor Queue (Queued Delta) In LO

Hi guyz,
             Can anyone let me know where can we see all the Erroneous records which are in Extractor LOG, while performing Queued Delta In LO-Extraction.
I mean the T-code as well as navigational Steps.
Thanks and Regards,
Hawkin.

Hi,
what kind of error do you have exactly?
some of them can bee seen in SM13 (updates) and also tRFC (SM58)....
hope this helps...
Olivier.

Similar Messages

  • What is the Difference between Delta Queue and Extractor Queue?

    What is the Difference between Delta Queue and Extractor Queue?

    Hi,
    please have a look at:
    DELTA  QUEUE&EXTRACTION QUEUE
    Hope this helps.
    Regards,
    Andrew van Schooneveld
    Assigning Points is the way of saying thanks

  • How to delete the data in update queue and delta queue for Queued delta?

    Dear BWers,
    How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
    Thanks
    Raj

    Hi Raj,
    I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance. 
    Please let me know if these material has been suffecient enough.
    regarda,
    raj

  • Queued delta slowing the production R/3 server!!!

    Hi,
    After we activeted the datasource in LO cockpit, for application 11,12 & 13,
    The normal transactions in R/3 have slowed dramatically.
    Has anyone encountered this problem ?

    Sounds like you might be doing direct delta, where logistics trans are written directly tothe BW delta queue.  This method is not recommended for high volume due to it's adverse impact on R3.  There are other options queued delta and unserialized V3 which are less of a burden.  You might want to do some more reading on logistics delta and verify the method you are using.
    One link with a decent writeup on the topic
    http://chandranonline.webasyst.net/files/1d168425/ZmlsZT1Nems9

  • What are the differences among LO deltas(Queued,serialized,direct ,Unseril)

    Hi friends,
    Please tell me what is Difference between Queued delta,serialized, unsterilized, direct delta.
    What are deltas We follow in BI7X.
    With regards,
    Raju.

    Hi,
    for difference pls chk
    Re: reg : BW references

  • REgarding the 'Open print Queue' IT WON'T OPEN

    I CAN NO LONGER OPEN THE PRINT QUEUE.
    Any ideas out there?

    Please don't shout!  I.e., post in all caps. Paste this into your browser's URL window and set things up:
    http://127.0.0.1:631/

  • What is a queued delta?

    SDN experts
    I like to know what is a queued delta and whe we use this?
    What is a data dictionary can you explain me in detail?
    Thank you,
    York

    Hi Les,
    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 to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. Generally we prefer Queued Delta as it maintain the Extractor Log which us to handle the LUW's which are missed.
    Direct Delta:
    In case of Direct Delta LUW's are directly posted to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW's are directly posted to Delta Queue (RSA7) the application is kept waiting untill all the enhancement code is executed.
    Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
    https://websmp102.sap-ag.de/~sapdownload/011000358700007535452002E/HOWTOCREATEGENERICDELTA.PDF (need id)
    http://help.sap.com/saphelp_bw33/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
    Business Intelligence Performance Tuning [original link is broken]
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
    How to load data
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    Delta Types and methods;�
    Hope this helps.
    ****Assign Points if Helpful*****
    Regards,
    Ravikanth

  • Urgent Entries for application 11 still exist in the extraction queue

    Hi All,
    In LBWE when i am trying to mainting structure its not allowing to add fields to ExtractStrucutre.
    Following is the error iam getting.
    Entries for application 11 still exist in the extraction queue ->
    I have set the Update to inactive and trying to add fields to Extract strucutre .
    Morover,
    I have already deleted setuptable entries for this application Component 11 and i checked in rsa3, no records are there.
    Regards,
    C.V.
    Message was edited by: P.C.V.

    PCV,
    Here are the steps. Make sure you do them when there is no posting going on.
    1) Using transaction SA38, execute program RMBWV311. This will send the data from the extraction queue to delta queue for application 11.
    2) Run your 2lis_11_***** info packages to bring the delta records into BW. Make sure to run these info packages twice because the delta is cleared on R/3 only if you run them twice. It is designed this way to accomodate the delta repetition functionality.
    Just to make sure, verify that you don't see any data in RSA7, LBWQ and if you use RSA3, the system should not extract any data.
    You should be able to change the extract structure now.
    Abdul

  • Queued delta enable extractions having entries in SM13. Is this correct?

    I Have the following issue:
    The 11 application module in LBWE is Queue delta enabled
    But I am seeing the changes to VA02 in SM13. why is this?
    Thanks
    Simmi

    Hi simmi:
    when ever we change the structure (enhancements, user exit) to any LO extractor its always a good practice to make sure we transport the request to prod on the same day and also make sure we do our setup tables and re-initilization's on the same day. as mentioned by you, you have a time lag and i think thats causing you some discrepancies. any ways, check in SM13 and if you think you can sustain with the data volume go and do a INIT to capture everything. or else go according to the date whe you do a load.
    assign points if helpful
    kalyan

  • Queued delta, unserialised v3 update, direct delta

    Can you any body tell what are the advantages between queued and other(Un serilised, direct) deltas.

    Chk these links
    What is a queued delta?
    Disadvantages of Queued Delta
    P.S : Always search the forums before creating a new thread.
            Avoid redundant threads.
    Regards,
    Balaji V

  • R/3 extraction.{direct delta and queued delta and V3}

    Hi,
    I am new to BW.Can anyone explain me about R/3 extraction in detail and steps to extract from R/3 to BW.
    I understood direct delta.But i couldn't understand queued delta.Can anyone please explain queued delta and also V3.Are queued delta and V3 same?
    Detail explanation or links will help a lot.
    Thanks,
    Sunny.

    Hi Sunny,
    Procurement - MM :
    MM is a part of SCM. There are several section in this, say Procurement, manufacturing, vendor evaluation etc... All can be found under follwoing link.
    Please find the procedure and important links for LO extraction..
    LO'S Procedure:
    Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
    Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
    In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
    Go to transaction RSA3 and check the data.
    Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
    Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
    Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
    Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
    Now you can go to your data target and see the delta record.
    Re: LO-Cockpit  V1 and V2 update
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Also Refer this link:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    Inventory.. dwload go thru it
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    *Steps*:
    1st delet the septup table----lbwg(for application 3)(need to cleanup the setup tables in r/3 side by using (LBWG for AC:03)
    1) Fill setup table (fill up the set up tables BX, BF and UM by using (MCNB,OLI1BW and OLIZBW).
    for BX(Open stock)-tcode--MCNB,
    for BF Tcode(oli1bw)
    for UM tcode(olizbw)
    after that pull data to BW with (Once the data is ready in RSA3, then in BW you have to set up compression for zero marker update for the Cube (coz is related to Noncummulative Keyfiger scenario) then load BX data. onces its completed load normally the BF and UMs.
    BW side:-
    make the compression
    for BX load normally
    and BF&UM(step table data):-compression with zero mark update(select that check box option)
    after completion of compression do delta(Note: for deltas follow the compression normally)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/a26f37eb997866e10000009b38f8cf/frameset.htm
    SD - Enterprise Sales and Distribution
    SD comes under CRM application component (ERP Analytics).
    sd flow
    salesorder:
    VBRK - header
    VBAP - item
    VBEP - scheduling
    delivery:
    LIKP - header
    LIPS - item
    billing:
    VBRK - header
    VBRP - item
    shipement
    VTTK - header
    VTTP - item
    customer data
    SD links FI table
    salesarea data general data companycode data
    knvp kna1 knb1
    material master data
    SD link to MM table
    salesdata Basic data salestext data
    MARC MARA STXH(Textfile header)
    MVKE MAKT STXL
    process:
    1.sales reresntive enter sales order in R/3 system, it sotres the transaction into three
    SD tables.
    2.delivery due list is executed for all sales orders and delivers are created in table LIKP, LIPS.
    A goodsissue updating MKPF & MSEG.
    3.invoice due list is then executed for all deliviers. after an invoice is created, which creates an acct.doc ( BKPF & BSEG, FI TABLES) and set up the receivalbe in table BSID (open tem).
    4.The receivalbe is cleared when paymen check is required. anoher acct.doc is created ( BKPF & BSEG) the open receivable is cleared and table BSAD (closed line item) is updated
    First u select application component.. SD,MM,FI,PM
    then got to rsa5.. u can install data source...
    after next step RSA6-Display data sources
    Then select our ds which we need to enhance then click on the
    append structure (application tool bar)
    u can see start with ZAGTFIGL_4 ( fi example)
    u given component name and component type ( here given to existing
    data element)
    save + activate....
    then go to the t code CMOD...>there select the project
    name--> go to the exit in RSAP0001->
    or also u can goto tcode se37 fuction module.. EXIT_SAPLRSAP_001
    transactional data
    click on display...
    then u can see INCLUDE ZXRSAU01( program ) double click it.....
    then u can change option click it.
    So please follow the link below:
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/bbe737a294946fe10000009b38f8cf/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/17/cd5e407aa4c44ce10000000a1550b0/frameset.htm
    Check these links,
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
    http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
    http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
    http://www.erpgenie.com/abap/tables_sd.htm
    http://www.erpgenie.com/abap/tables_mm.htm
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Re: LO-Cockpit  V1 and V2 update
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    Regards
    CSM Reddy

  • Difference between Queued Delta vs Unserialized V3 update

    Dear Experts,
    I am using 2LIS_02_ITM datasource.
    PO is created using a program.
    The next step in the program, it can change a field in the PO depending on logic, using a abap command 'update'.
    Sometimes, this change is not captured in the delta queue, it seems.
    why i say this is the PO shows the field value but BI delta load does not.
    It is using Queued Delta now.
    I am wondering would changing to Unserialised V3 update help solve the problem since when documents are posted it writes to update table and from there it is processed to delta queue using collection run.
    What is the difference between writing to the Extraction Queue compared to writing to Update table? Will using the update table mean abap command 'update' changes to a PO document will be captured ?
    regards
    Pascal

    Hi Pascal ,
    The basic difference between these two is how the delta moves from R/3 to BW side .
    When we do any transaction in R/3, first the data goes into a Temporary table called V1 Update and from here data moves to Final table (Application)say VBPA,VBRK etc. this is called V2 Update.
    After this we have queued delta or Unserialized V3 update at between R/3 and BW side .
    1. Queued Delta
    At V1 update data goes to  "Extraction Queue" (irrespective of V2 happen or not).Then when we run a "Extraction Run" program it pulls the data from  Extraction Queue  and sends it to  DELTA Queue  table (called V3 Update) from where it is transported to BW when a delta request is generated.
    So if something is saved to application table, also get saved to Extraction Queue ( this is difference with direct delta) and you have to schedule a V3 job to move the data to the delta queue periodically .
    2. Unserialized V3 Update
    In this case when data is generated V1 update  takes place and data moves to another table known "Update Table" but only after V2 takes palce. So it waits for V2 update to happen and does not miss any record.After that from "Update Table" data goes to Delta Queue when update collection Run is executed and then  it goes to BW when Delta upload Request is generated.
    The difference here is the sequence of document data in the BW delta queue that may be different from posting sequence of data so it is good when sequence of data does not matter due to the design of the data targets in BW.
    ex: Inventory Management.
    Hope this will throw some light on the concept you want to understand.
    Regards,
    Jaya

  • Defference in Queued Delta  and V3 Upadte

    Hi Gurus,
    Can any one please explain about the difference in Bitween Queued Delta and V3 Upadate.
    if i will maintain Queued Delta,then i don't want to maintain V3 Update?
    Thanks In Adavane
    Regards.

    Hi Choudary,
    Please find below the difference between the Queued Delta  and V3 Update..
    >>Queued Delta:
    With queued delta update mode, the extraction data is written in an extraction queue and is transferred to the BW Delta Queues by an update collective run.
    Upto 10000 document delta/change to one LUW are cumulated per Datasource in the BW Delta Queue.
    Queued Delta - Advantages:
    Serialization is ensured using the enqueue concept.
    Works good when the occurrence of documents is high.
    Queued Delta - Disadvantages:
    In this case we would need to schedule a job (LBWE-Job Control) to regularly transfer the data to BW Delta Queue.
    Subsequently additional monitoring of the extraction queue is required.
    Queued Delta – Recommended For:
    Customers with high occurrence of documents (more than 10000 document changes between delta extractions).
    >>Unserialized V3 Update :
    The extraction data continues to be written to the update tables using a V3 update module and then is read and processed by a collective update run through LBWE.
    Data is read in the update collective run without taking the sequence number into account.
    Unserialized V3 Update - Advantages:
    Works good when the occurrence of documents is high.
    Unserialized V3 Update - Disadvantages:
    Serialization is not ensured.
    In this case we would need to schedule a job (LBWE-Job Control) to regularly transfer the data.
    Subsequently additional monitoring of the extraction queue is required.
    Unserialized V3 Update – Recommended For:
    Only if its irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence (serialization) in which the data was generated in R/3. Basically the functional data flow should not require a correct temporal sequence.
    Hope this helps.
    Thanks & Regards,
    SH

  • What is differences extraction queue, delta queue and uddate queue ?

    hi guru's
    What is differences  between extraction queue, delta queue and uddate queue ? can u describe briefly?
    Thanks & Regards
    nandi

    Dear Prabha,
    Basically when any document is posted in R/3, it is updated to the update table, from there it is taken to our delta queue for send it to BW side.
    When extraction starts, data is sent to BW from delta queue. then again this cycle starts.
    When you post any document in OLTP system (eg SAP R3),
    say create sales order by VA01, then posting is made to application tables (VBAK/VBAP) through V1 and also to sm other tables through V2, Communication structure written to update queue/extraction queue/delta queue(directly) as per the update mode selected. V3 is always followed by V2 and we are supposed to schedule it.
    From this delta queue, data is extracted by BW infopackages.
    There are various update methods according to which extraction or delta queue are used, so when document posting takes place it also write data into extraction queue (through V1 update) and if we use queued delta method then this data is collected in collection run and written to delta queue and from this delta queue we request for data from BW.
    There are lots of posts on SDN for this, please have a look on those.
    one for your reference...
    https://www.sdn.sap.com/irj/sdn/profile?userid=3507509
    Hope it helps...
    Message was edited by:
            Ashish Tewari

  • Do we necessarily need to clear the BW queues in preprocessing steps of SAP

    Hello Experts,
    A quick question.
    I am doing EHP upgrade on BW system
    Do we necessarily need to clear the BW queues in preprocessing steps of SAPehpi?
    OR the same can be done just before downtime?
    A fast response is much appreciated.
    Best Regards
    Sachin Bhatt

    Hello Markus,
    Thanks for the info.
    We finished EHP4 implementation successfully last saturday.
    However to my surprise didnt receive any message by EHPI to clear delta queues.
    We cleared it just before down time.
    Anyways thanks for the answer.
    We wil take a close look when implementing next time during the phase mentioned.
    Regards
    Sachin Bhatt

Maybe you are looking for