Logistic extraction 2lis_11_vahdr,2lis_11_vaitm

Hi
our logistic extractors are not turned active in R3 development from some time.
bw development is also not loading Logistic information from last 6 months
but since last couple weeks new Sales orders and billing documents are getting created with new documents.
so i refered sdn and followed the steps.
1. delete setup tables in transaction LBWG
2. FILL up setup tables using  SBIW -->Settings for Application-Specific Data Sources ->Logistics --> Managing Extract Structures->Initialization -->Filling in the Setup Table --> choose Application -- >Setup of Statistical Data-->SD Sales order perform setup
3. this filled up setup tables....
now if i do rsa3 and enter 2lis_11_vaitm i still cant see the records that were created in last month
i can only see records that are created last year and year before....
question--   i can still see the records in transaction VA03
how do i solve this??

First of all delete the setup table if already filled for application 11 and if there is entry in LBWQ delte that also you will get something like MCEX11 in LBWQ and corresponding entries in RSA7 if any exist. Now go to LBWE and acitvate the data sources you want in your case 2lis_11_vahdr,2lis_11_vaitm. Now fill the setup table for SD-Sales Orders - Perform Setup.
After filling of setup table check the entries in RSA3, also you need to run init infopackage to get the deltas in LBWQ and then in RSA7. For pulling data from LBWQ to RSA7 you have to schedule the job using job control in LBWE.
Hope you will get the desired results.
Assign point if useful.

Similar Messages

  • Logistic extraction 2lis_11_vahdr,2lis_11_vaitm,2lis_13_vdhdr,2lis_13_vditm

    hi
    recently our R3 development got system copy
    now we are doing logistic extraction in sales and distribution, so after reading different threads it seems i have to re org the delta queues
    here are things i can list out
    check active structures in BW:
    so i went into lbwe and they are 2lis_11_vahdr,2lis_11_vaitm,2lis_13_vdhdr,2lis_13_vditm
    delete the init from bw in infopackage
    delete set up tables
    so i went in LBWQ and deleted entries for MCEX11 & MCEX13
    now refill the setup tables...
       how to fill setup tables ???
    i am doing rsa3 and all this extractors are throwing empty or 0 records!!!!
    i tried oli3bw and oli7bw
    what options to select
    how to fill setup tables ???
    are this correct tcodes oli3bw & oli7bw  for 2lis_11_vahdr,2lis_11_vaitm,2lis_13_vdhdr,2lis_13_vditm

    thanks very very much
    when you say deleted data? that mean delete all the requests ???
    there are like 200 requests in cube 0SD_C03 because the data was loading from last 5 months..
    do i have to manually turn all requests in to red and delete it ???
    also when i ran oli9bw
    it ended up in error saying PROGRAM TERMINATed
    time limit exceeded!!!
    and then in smq1 there r no queues visible for 13 and 11
    do i run it again ????

  • How to extract 2LIS_11_VAHDR

    Dear Consultants,
    When i extract 2LIS_11_VAHDR, I can not gain datas.
    About using tcode: LBWE, RSA5, RSA6, RSA3.
    What executing procedure i ought to implement ?  And what other
    tcodes  i  ought  to  execute ?
    Please consultants provide good advises and executing processes.
    Thanks a lot &Best Regards
    Ricky

    Did you fill the setup tables for application 11?
    If not, please do the same.
    Please check this thread. It has all details..
    LO Extraction Questions
    Edited by: Archana on Mar 24, 2009 11:26 AM

  • Problem to extract data using DS 2LIS_11_VAHDR & 2LIS_11_VAITM

    Hello Experts,
    my requirement is to extract the SD sales Item & sales header data int BI.  while executing the Reports in BI  I find some incosistencies in data
    Ex:  for for some Sales organizations  
          0CRM_NUMDOC = 17 and the corresponding   0NETVALORD = 0,00  
    and for some sales organization
         0CRM_NUMDOC = 0 and the corresponding   0NETVALORD = 5200,00  
    we are using  the data sopurce 2LIS_11_VAHDR to load Document header data  and the data sopurce 2LIS_11_VAITM to get  Item Net value data. and used two trtansformations to the same SAP standard cubes 0CSAL_C05 & 0CSAL_C03.
    asper  my analysis in development system I find 
           VBAK contains  1405 records but the DS 2LIS_11_VAHDR extracts only 1235 records.
    but
           VBAP conains   2665  records and the DS 2LIS_11_VAITM extracts all 2665  records.
    is it creats the problem?
    I deleted the setuptables and again fill them  even thought I have the same problem ?
    If you have any idea regarding this issue please share with me.
    Thanks in advance.
    cheers.............

    HI,
    Check indeed the extraction in your source system with RSA3.
    Also perform the load and check your data in PSA (before any transformation takes place).
    Are you going to use delta or full loading? I assume it's delta? So if you perform your initial load with data, no use of the setup table is required...
    If you have too much data to do this, try an initial load without data, first delta load and next a full repair load (which will read your setup table). Do not forget to fill your setup table with all the historical data you need in transaction SBIW.
    Hope this helps.
    Best Regards,
    Michel Hoefkens

  • Sales Report problem with 2LIS_11_VAHDR, 2LIS_11_VAITM and other DS

    Hi Experts,
    I need your help in following topic. I have a requirement to build a big (overall) sales report in BI (NW2004s).
    I would like to use BI Content because I'm running out of time and try to use all preconfigured stuff if possible.
    In the requirement a bunch of fields of different SD DataSources are used (mostly 2LIS_11_VAHDR and 2LIS_11_VAITM but also some fields of other Datasources).
    In SE16 I know how to locate all the field in the tables VBAK, VBAP, KNA1, VBKD,
    LIKP, VBRK and of course some texts. Some fields could already be located by me, others couldn't even be found in BI.
    The difficulty I have is to bring all the DataSources together so that the data is displayed correct - even if there are redundant parts.
    For example:
    For sales orders the doc no, sales org, distr. channel (and a lot of other header data) should be displayed in each line together with item data such as item no., material code, quantity (and a lot of other item data). If an order has multiple items each item should be diplayed in one row in the report.
    In the Query the report should look like a common table (e.g. as in an ALV Grid if you model a query with SQ01) --> a lot of columns.
    I'm not sure if I should use one big DSO with multiple InfoSources or if I should create a MultiCube and add the BI DSOs 0SD_O03 (Orders) and 0SD_O01(Order Items).
    I know this is a very common requirement in SD. Do you know how to combine the most common SD datasources that no issues come up?
    Thank you very much in advance,
    Horst
    Message was edited by:
            Horst Henkel

    Hi Horst,
    Reporting on ODS / DSo is slow. I'm here at a cleint where we have lots of reports on SD_O01 and SD_O03. The best way to have good  query performance is to build cubes on top of your ODS. Build a sales cube on top of SD_O03 with all fields and a billing cube on top of SD_O01. Load the data from your ODS to your new cubes. Then create a multipovider on top of both cubes, identify the keyfigures and characteristics required for your queries. Build the queries on top of the multiprovider.
    You can display all items of a bill in one row if you choose drill-across for the irems in the query, instead of drill-down. So it looks for a standard SD report.
    Regards,
    Juergen

  • SD Delta Extraction over 2LIS_11_VAITM

    Hi,
    is there anybody out there who can help me?
    After enhancing the DS 2LIS_11_VAITM by 2 fields on the development system and checking an upload to BW development system (only in FullUpdate mode) we
    1. stopped posting in productive R/3
    2. transported the DS to the productive BW, replicated the DataSource & activated the InfoSource.
    3a. deleted the rebuild table (“Neuaufbautabelle”) for application 11 in productive R/3 [SBIW]
    3b. deleted the extraction queue in productive R/3 [LBWQ]
    3c. deleted the delta queue in productive R/3 [RSA7]
    4. filled the rebuild table again [SBIW]
    From now on we tried to upload the data in the BW productive system.
    A.In the first place we uploaded all data into the PSA by sharing it onto several FullUpload-InfoPackages (on behalf of sales organisations) running in parallel and in batch. From the PSA we loaded the full update requests into the ODS (also in batch). So far everything was ok. Now we wanted to set the delta management. But when trying to set the Delta-Initialization (without data), the system stroke: “Full-Uploads are already in data targets, delta initialization not possible.”
    B.So we deleted all requests from the data target ODS and set an Delta-initialization without data again, which worked. Subsequently we loaded the data from the PSA into the ODS in FullUpdate mode. This encountered an error, when activating the ODS data: some of the data from the init request overlapped the data of the full up-date request, the system said.
    My questions:
    -     in which order should be the data loaded, so that we can manage it fastest and safest? (note, that the posting in R/3 is still stopped, so that the delta queue is empty)
    -     what requirements has the R/3 system to fulfil for this aim?
    Thank you a lot in advance,
    aussi43

    Nagesh,
    After setting the monitor status on red and deleting the loaded data requests and the initialization request we restarted the whole upload session with a correct delta initialization <u>with</u> data transfer (with no selections) into the PSA. As I wrote yesterday (and as it wasn’t mentioned in my original mail), this was the way we started the upload one week ago. As one week ago the upload speed is very low – for 2LIS_11_VAITM we expect some 9 millions of records and after almost 3 days only the half of it is in BW.
    I’m eager to find out if there is a modality to speed up the whole a little bit. That’s why I’ll try to test the strategy you mentioned yesterday (full uploads with repair flags) on the BW test mashine. Would please correct the following flow, which I took from your description? (in order to have it complete I also inserted the first steps 1.-4. from my original mail)
    <u>Already done steps</u>:
    1. stopped posting in productive R/3
    2. deleted in productive R/3 the setup table for application 11 [SBIW], the extraction queue [LBWQ] and the delta queue [RSA7]
    3. transported the DS to the productive BW, replicated the DataSource & activated the InfoSource.
    4. filled the setup table [SBIW]
    <u>Further steps to be cleared out (after step 4 comes either branch xxx or branch yyy)</u>:
    Branch xxx:
        5. load data using full load
        6. Initialize delta without data transfer
        7. schedule the V3 job (and start posting in productive system)
    Branch yyy:
        5’. load data using initialize delta without data transfer
        6’. Full load with repair request.
        7’. schedule the V3 job  (and start posting in productive system)
    Thank you a lot.
    Regards,
    Aussi Saxon

  • Failed to enhance the extract structure 2lis_11_vaitm

    Hi,
    I would like to enhance the datasource 2lis_11_vaitm, therefore I go to RSA6 tcode, mark the required datasource and when press Enhance Extarct Structure button, I get this error message:
    "DataSource 2LIS_11_VAITM does not allow append structures".
    Is it possible to enhance 2lis_11_vaitm? if so how to do?
    Thanks,
    Mohamad.

    Hi Mohammed,
        Go To T-Code SE11 , In Data Type give your extract structure name MC11VA0ITM . Select display . Click on Append structure button and add the fields you want to enhance with. Then activate the append structure.
    Regards,
    Prakash

  • Change Extract Structure 2LIS_11_VAITM

    Hi,
    I have to change structure of 2lis_11_vaitm.
    I would like to know if it is necessary / required, in addition to empty the queue, blocking users in R/3 transactions using Sales (VA01, VA02, etc.).
    Thanks.
    Charly

    Hi
    It depends on requirement. Say you made changes to the structures(added to more fields) and your business need historical data of those fields also then you need system downtime as you are going perform setup tables filling for historical data.
    You made changes to the data source and you don't want historical data then no need of going for downtime. Is this case after you import the transport perform re-init for your data source.
    it is better to perform all these data source enhancement transport in non-business hours.
    check below thread
    Precautions for Enhancing LO Datasource
    Regards,
    Venkatesh.

  • Problem in data extraction using 2LIS_11_VAITM

    Hi,
    For sales order item detail I am using a standard data source 2LIS_11_VAITM.
    And for this I have not written any code in exit.
    But for a particular date some of Sales Document: Item Data has pulled to BI using delta upload and some of not pulled.
    As some of sales order items are missing in BI. So i dentified those sales order detail in R/3
    So the Problem is coming for only those records which have created on 04.10.2008,27.10.2008, 01.11.2008.
    And the process chain for 05.10.2008, 28.10.2008, 02.11.2008 has not executed which suppose to pull the data for 04.10.2008,27.10.2008, 01.11.2008. The error is in delta uploading.
    On 05.10.2008, 28.10.2008, 02.11.2008  the server is down at the scheduled time of process chain.
    So the data suppose to come on next delta upload.
    So 0n 06.10.2008, 29.10.2008, 03.11.2008 the delta executed successfully.
    But all the records which are created on  04.10.2008,27.10.2008, 01.11.2008 hv not pulled to BI which I checked in PSA.
    Only some of records which are created on  04.10.2008,27.10.2008, 01.11.2008. are in PSA.
    Please suggest your idea.
    Point will be awarded for this.

    Hi,
    Are you loading to the DSO??
    Then
    1)fill the set up table for the following dates only for which you have misssed the records.
    2) Do a full repair to the targets for these date after the set up table is filled.
    3) schedule a normal delta to the further targets from this DSO.
    If loading to the cube directly??
    1)do a selective deletion from the cube for these dates
    2)fill the set up table for the following dates only
    3) Do a full repair to the targets for these date.
    No need to delete or do anything with the existing init in any case.
    Thanks
    Ajeet

  • Difference between Logistic extraction( Lo Cockpit) and Finance extraction

    Hi All,
                   Can anyone explain me, Why Finance data sources are not included in the LO-COCKPIT. Why logistics data sources are given this much care. Why there is no Filling /Deleting Set up tables in the FI extractors. Can any one explain how the FI extractors pull the data from the base tables.
    With Regards,
    Naveen

    Hi,
    Difference starts with Setup table and delta Processes  etc.....
    Please refer below link
    http://scn.sap.com/thread/1169207
    Best regards,
    Varun gandhi

  • Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

    Hi all
    I used the old data load process(3.5) in 2004s system.
    There are errors in detla extraction with SAP data source
    2LIS_11_VAHDR
    2LIS_11_VAITM
    2LIS_12_VCHDR
    2LIS_12_VCITM
    The delta data(before/after image) aren't right.
    Has anyone experices with this problem?
    thanks in advance

    No Problems yet,explain the error message with error number in details here for some one to help you.
    Hope it Helps
    Chetan
    @CP..

  • 2lis_11_vascl and 2lis_11_vaitm delta issues

    Hi ALL,
    I am pulling data from Sales order datasources like 2lis_11_vahdr, 2lis_11_vaitm, 2lis_11_vascl, 2lis_11_vasti and 2lis_11_vasth.
    I have some problem with standard extractor of 2lis_11_vascl and 2lis_11_vaitm of not capturing the delta properly. I am currently analysing the issue.
    Could any one please clear my below doubts.
    1. When ever there is a change to schedule line 2lis_11_vascl to a sales order - does the header and item level also come as a delta?.
    2. Secondly i find the delta is correctly captured in Item status datasource 2lis_11_vasti whereas i am missing many documents in item level details datasource 2lis_11_vaitm. Have any one faced this issue. Really finding it difficult to debug the standard extractor.
    I could sense that i am missing documents in item level only for a particular item category(Third part order).
    It would be great if anyone could explain the above two questions to clear my doubt.
    Thanks,
    Aravind

    Hi Fazal,
    Please find the details below
    2LIS_11_VASCL  : This DataSource provides the BW with data from the Sales area and supplies the InfoSource               
                                    2AF_SD_SLS_1 with data. Extraction records are generated for the sales order event.
    2LIS_11_V_SCL  : This DataSource provides the BW with data from the Sales area and supplies the key figure Open Order
                                  Quantity in the InfoSource 2AF_SD_SLS_2 with data. Extraction records are generated for the sales order
                                   and delivery events.
    For More details check the below link :
    http://help.sap.com/saphelp_nw70/helpdata/en/ba/0b853c01c89d7ce10000000a11405a/frameset.htm.
    Note : To understand more about the open order quatity and sales order details contact SD Cconsultat.Then you will understand about the details.
    Regards
    Ram.

  • ODP Data Source Delta issue 2lis_11_VAHDR 2lis_11_VAKON

    Hi Expert,
    I am pulling the data from SAP using ODP data sources. 2LIS_11_VAHDR 2LIS_11_VAITM 2LIS_11_VAKON.
    For all the data sources I am doing the initloads. For 2LIS_11_VAITM data source after init load its enabling the delta.
    For remaining data sources even if you try to pull the delta it's loading full load.
    Steps I am following
    LBWG do the deletion of setup tables.
    OLI7BW fill the setup tables.
    Run the data services job which pull the initial load. It loads all the data.
    Change the ODP data source settings to Init load to No (Capture only delta)
    In SMQ1 all the delta records will be captured
    Run the Jobs which pull the delta records to ODQMON from there if you run Job in data services it has to pull the Delta records.
    This is happening for 2LIS_11_VAITM but not for other data sources 2LIS_11_VAHDR and 2LIS_11_VAKON.
    Event if you try to pull the delta records its loading all the records.
    Can some one throw some light on this
    Regards,
    Murali.

    In RSMO, go to the details tab and check in which stage the load has failed. If the issue is with extraction then go to Environment > Job Overview in the source system. Check if this job is complete.
    I hope you must have cleared the Delta Queue, so now go and check if any entry is being displayed for 2lis_11_vahdr

  • Issue with 2LIS_11_VAITM

    Hi,
    we are extracting sales related information from ECC through 2LIS_11_VAHDR & 2LIS_11_VAITM  to the BW Evironment. but last few delta runs we are missing new/chanaged records from the VBAK/VBAP.
    I am not able to understand why we are missing these documents in the the standard extractor. this was working fine till last week and never had any issues with the missing records.
    I have tried to run RSA3 in ECC , but i am not able to get this records in ECC while running the extractor in Full update mode.
    please suggest how to resolve the issue.
    Regards,
    Gowrisankar Nk

    Durgesh,
    I have checked with the functional team and they informed, while submitting the sales orders it ran in to Idoc errors, then they have manually processed this sales order via we21.
    Moreover there are quite few documents like this are missing in RSA3 Extraction itself and all this documents are from one paritcular date(02/18/2012)
    How we can pull this missing records to BW, (i.e. re-running the set up table for the missing records and run the repair full update to BW, is this right way ? if we do whats the pros and cons ?)
    Regards,
    Gowrisankar Nk

  • LO extraction VS Generic

    Hi everyone, a general question as I'm new SAP BW world
    which extraction method is used most in the market
    2nd question is we use Generic to Extract data from two or more tables but I can also use generic for one table (I think not because that's why we have LO ?)
    Let me know, thanks Dave

    Hi..
    in Application Specific there are two divison..
    <b>Customer Generated Extractors and
    BW Content Extractors in this  LO COCKPIT</b>
    Cross Application-----Generic Extractors.. in this we have db view ..info set and function module
    Logistics Customizing Cockpit provides a simplified way to extract logistics data and transfer it to SAP Business Information Warehouse.
    As shown in the figure the document data for various applications like Customer order, delivery and billing is first transferred to various Communication Structures.
    These communication structures are used to form various extract structures in R/3 which consist of various DataSources like 2LIS_11_VAHDR, 2LIS_11_VAITM etc.
    These DataSources then can be replicated to BW and assigned to Infosources.
    Then by creating transfer rules and update rules and defining the transformation the data is loaded into various data targets like InfoCube and ODS, thus available for reporting.
    There are four Update Modes in LO Extraction
    Serialized V3 Update
    Direct Delta
    Queued Delta
    Un-serialized V3 Update
    Simple Handling
    BW Customizing Cockpit: Central, single, maintenance tool for Logistics applications  No LIS functionality: No knowledge of  LIS Customizing  update settings, etc, required
    Function enhancement: Creating simply and without modifications
    Others
    Delta tables (SnnnBIW1/-2): duplicated update, duplicated data storage
    Generic Extractors are Cross Application Extractors used in scenarios where the other type of extractors are unavailable.
    Generic extractors are of three types:
    Based on Database view/Table
    Based on InfoSet
    Based on Function Module
    When should you use generic extractors  should be used ...
    Business Content does not contain a DataSource for your application.
    The application does not feature its own generic delta       extraction method
    You are using your own programs in SAP R/3 to populate the tables
    The tools for generic data extraction can be used to generate an extractor for all applications.
    with regards,

Maybe you are looking for