Missing PO in 2lis_02_itm init extraction / setup tables

Hello Gurus,
could anyone please help me out with this toppic:
I want to extract Purchase Orders to BW via DS 2lis_02_itm. Source System is R/3 4.6c. Filling up the setup tables is working. My problem is, that there are several Purchase Orders which are not filled in the setup tables (so no extraction to bw)! I have checked these PO and for me they seem fine. I can´t find any reason why they aren´t extracted. Of course i am running all programms whithout any restrictions. I have debugged the programm rmceneua with one specific po which is not extracted but can not find a reason why it is not written to table MC02M_SETUP.
Did i miss some customizing settings? Are there some kind of PO which are not extracted because of there PO Type (ZCO/ZB) do they eventually have a wrong status?
I can not find any information about the functionality of programm rmceneua. Maybe you can help me out of this?
Thanks a lot
JANOS

Did you check whether the process key is maintained properly?

Similar Messages

  • Inventory Load - Running Init of Setup tables

    I'm planning the initial load of Inventory data and want to make sure that I understand what needs to be done. 
    Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel.  Or do I have to wait for one to finish before I submit the next?
    Thanks,
    Chris

    Chris,
    Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel. Or do I have to wait for one to finish before I submit the next?
    --> You can run parallel, you can also run parallel for each datasouce(eg: BF) by providing proper selection(like, Plant, date..ect)
    Hope it Helps
    Srini

  • SETUP tables not filling for 2LIS_02_ITM

    Hello all,
    I am trying to run the SETUP process from OLI3BW for few Purchasing doc's
    But I do not see any entries  in the setup table 'MC02M_0ITMSETUP' after the SETUP run.
    and Yes,I have DELETED setup tables data prior to running the Setup process.
    I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 .
    I could not find any Info on this kind of issue in SDN.
    Any help is much appreciated !
    Thanks,
    Jb

    Yes, I did check RSA3,RSA6 and LBWE .
    LBWE has active DS for Item/Hdr/Scl(with Green light) and RSA6 has active DS's
    But RSA3 has 0 records since SETUP process itself did not run and no data in SETUP table to pull from RSA3.
    I schedule the job in the back ground and seems the job runtime was too short with no proper log.
    Here are the messages from the Job log.
    11:51:49 Job started                          00           516          S
    11:51:49 Step 001 started (program RMCENEUA, variant &0000000000016, user name   XXXXXX)   00           550          S
    11:52:00 Job finished                                                                        00           517          S       
    I am confused as whats happening here,I did not encounter such problem before doing SETUP's for Billing etc.
    Thanks,
    Jb

  • 2lis_02_itm setup table successfull but rsa 3 no data

    Hi @all,
    we have an problem with one R3 source system. Following Issue. The system connection is okay we get data from some FI extractors.
    But the 2lis_02_itm extractor sends no data to bw:
    Following is done:
    1. we have datas (ekko,ekpo)
    2. 2lis_02_itm Structure is active
    3. Processkeys are maintained
    4. setup table are built sucessful and he collects data(setuolog)
    But the extractor checker doesn't work he collects 0 data.
    Does anybody know where lost the datas? Why we don't get any datas ? For other application componnent like FI we can extract data.
    Help would be great.
    thanks in advance!
    Br
    rene
    Edited by: Renè Lechtenböhmer on Aug 20, 2008 11:52 AM

    Hi,
    Can you please check if the following settings mentioned in the best practice document have been maintained,
    3. Configuration
    1. Customizing for the Extractors
    1. Order Update Parameters Setting
    Procedure
    This step has to be carried out in the R/3 System.
    R/3 – Role Menu Order Update Parameters Setting
    Transaction code OPL5
    Carry out the following steps:
    1. If the view is in Display mode, change it to change mode.
    2. Select the lines in which there are transaction data you want to upload to BW.
    3. Select the Details button.
    4. Ensure that the four indicators (Update, Header, Item and Operation) are chosen.
    5. Press F8 to choose the next entry.
    6. Choose Save.
    Here is the link for the best practice document.
    http://www.google.com/url?sa=t&ct=res&cd=2&url=http%3A%2F%2Fhelp.sap.com%2Fbestpractices%2FBBLibrary%2Fdocumentation%2FB80_BB_ConfigGuide_EN_DE.doc&ei=ZmO6R5qKFaTsgQKBrtDoDQ&usg=AFQjCNGINah5eM2RYjnbp2d10VuwfsfyCQ&sig2=GyGDHsqg8FOL2BSdpWBsvA
    From thread,
    Re: No data in PP datasources
    regards,
    Raj

  • Do we need to fill setup table if we change extract structure of D/S

    Hello Experts,
    as we are in need of adding new filed to existing delta enable Datasources.
    Do we need to fill the setup table if we change the Extract structure of Data source which is already loading Delta data to bw system?
    case 1) we are planning to add new field directly in maintain structure in TCode LBWE.
    case 2) adding new field to Extract structure and writing relavent code in CMOD.
    Thanks in advance
    Regards
    Ravi

    Hello Ravi,
    If you are adding new field to a structure, even though you do not need historical data in the new fields it is a mandate that you have to replicate the datasource and then reinitialize the datasource, in both the cases you have mentioned. The reason for this is, the RSA7 contains your existing structure, as you are changing it, a new replica needs to be created in RSA7. You have to run a INIT without datatransfer, dont need to refill the setup tables for the INIT without data transfer.
    After you activate the new fields and poppulate it using CMOD. First transfer all the records in SMQ1 to RSA7, using a V3 update. Then run a delta in BW, by this way you will load all the existing records from source system to BW. Then replicate the datasource and create the required InfoObject and mapping in BW (Please note that without deleting data, you wont be able to change the DataTarget structure unless you are using remodelling in BI 7.0). Delete the datasource entry in RSA7. Runa INIT without datatransfer.
    Please let me know if you need any more information.
    Regards,
    Pankaj

  • Extraction Problem- while filling the setup table

    Hi all,
    I have a problem when i  fill the setup table for LO cockpit Extraction on any SD datasources (2_LIS_VAHDR,2lis_13_vdkon etc.,). i am done with LBWQ successfully. i also verified the datasources in RSA6. They are in active status in RSA7-delta queue.
    After i submit the request to fill the setup table, i am getting
    "datasource 2_LIS_VAHDR contains data still to be transferred". if i check the extract checker (RSA3) i am getting the error msg "data source is not defined in the source system"
    Can anybody help me on this?
    one of my friend suggested that it could be the reason that some jobs are in active status that loads/updates data into base tables which the datasources refers.
    Any idea on the reason and resolutions?
    Greatly appreciated !

    Hi Vijaya,
    We too got the same Error : " the datasources are not defined in the source system".
    This is source system connection problem.  Check whether connection between R/3 and BW is active.
    This error occurs when the connection is inactive.
    Also, if it is copy client, then check data exists in other client. If so delete the setup tables data in that client as well.
    This will resolve your issue.
    Thanks
    Edited by: Allen Fyne on Aug 9, 2008 6:47 PM

  • What is the use of setup tables in LO extraction

    Hi Friends,
    What is the use of setup tables in LO extraction, what is the functionality of setup tables
    Thanks in advance

    hi,
    to prepare data to be extracted to bw,
    more details take a look Roberto's weblog
    /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/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    hope this helps.

  • Statistical Setup Tables and Full Extractions

    For Full Extractions what is the relationship with the statistical setup tables i.e. no of records in the table = no of records to be extracted? Thanks

    Hi,
    The relationship is 1 -> 1 you  have to fill the setup table, the full load only reads this structure. So if you would like to load a 2LISxx full load every night, you have to delete and refill the setup table in R/3.
    Kind regards, Patrick Rieken.

  • Data loading for Logistics Data Extraction 2LIS_06_INV through setup tables

    Hi Guyz,
    I have LO Datasource 2LIS_06_INV which I am using for extracting Invoice Verification Data.
    I had intialized and loaded invoice data in BI system and was using chais to load daily.
    Now I want to load data again from scratch from source system.
    As of now I know we need to delete and fill up setup tables in source system keeping the users locked so that no new records are created that particular moment.
    But what about the delta queue and extraction queues.
    Do I need to do something over there because as I understand there will be records in both of them so before filling the setup tables I need to delete both the queues and then fill the setup tables so that duplicate records should be avoided.
    Please let me know what exactly should I do in detail.
    Appreciated in advance.
    Regards,
    raps.

    hi,
    this entirely depends upon the DS, if the DS delta type supports overwrite mode then you need not lock the users, you can start the setup job without deleting the delta queues as well coz even if the record is extracted twice the values won't mess up as the flow will be in overwrite mode. If delta type of DS is Additive in table ROOSOURCE then you need to lock down the users or run the job over a weekend when no users are logged in.
    regard,
    Arvind,

  • Whats the Actual use of the Setup table apart from the Full/Init  loads

    Hi  guru's
      could u explain  whats the Actual use of the Setup table apart from the Full/Init  loads  in Lo Extraction

    Hello Guru,
    The Setup table is used mainly for storing the Historical data whereas the new and changed records will be maintained in the Update table.
    By storing the Historical data in the setup table you don't need to disturb the Application table anymore.
    Please go through the following blogs
    /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/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
    https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002719062002E
    Hope it helps
    Thanks,
    Chandran

  • Why we have setup tables in LO extraction and why not in CO-PA,Generic

    Hi Friends
                   Why we have setup tables in LO extraction and why not in CO-PA,Generic
    Please give me reply
                                       ****************Points are assured********************
    Thanks&Regards
    Revathi

    Hi Revathi,
    Please check the following Threads :
    [why set up tables ?;
    [Why LO only having Setup tables not Others.......?;
    Regards
    Hemant Khemani

  • 8 hrs downtime, how to do the init setup tables

    Hello BW Experts,
    I have 8 hrs downtime per day and i have to do the fill of 30 million records to the init setup tables. If i could breakdown each day init setup table fill based on the company code + sales org.
    day 1 fill cc1
    day 2 fill cc2
    How what happens if someone does any records changess in the cc1 on day2. how is that captured. what is the solution.
    Please explain.
    Regards,
    BWer

    After your initialization Setup Tables you must do a Init Delta Queue for that company only.....the delta load is cummulative respecto to the init delta loads....
    If yo u have three init delta one for each company ...the delta loads load the data for alll three companies at same time.....you can initialize companies one by one and load delta..
    This prevents lost changes in companies that you have setting up...
    I hope this helps you
    Regards
    Message was edited by:
            Oscar Díaz

  • Why we have setup tables in LO extraction and why not in CO-PA,Generic,FI-S

    HI Friends
                    Why we have setup tables in LO extraction and why not in CO-PA,Generic,FI-SL. Please clarify.
    Thanks&Regards
    Revathi
    <removed by moderator>
    Edited by: Siegfried Szameitat on Nov 13, 2008 12:07 PM

    Hi revathi,
    The R/3 database structure for accounting is much more easier than the Logistical structure.
    Once you post in a ledger that is done. You can correct, but that give just another posting.
    BI can get information direct out of this (relatively) simple database structure.
    In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.
    When 1 item (orderline) changes, this can have its reflection on order, supply, delivery, invoice, etc.
    Therefore a special record structure is build for Logistical reports.and this structure now is used for BI.
    In order to have this special structre filled with your starting position, you must run a set-up. from that moment on R/3 will keep filling this LO-database.
    If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistica cocpit)
    I hope I have been clear.
    Udo

  • Why to use setup tables in LO extraction

    Hi gurus
    please send me answer

    Hi,
    Think of the SAP application tables as Production system. Now why dont we directly do reporting on these tables or why cant we use these tables instead of ODS as these already have detailed data.
    One of the major reasons is performance. If you want to load this data to BW directly with out setup tables, you cannot be sure that you have correct data in the BW system as these tables are changed by the transactions. If you still do not want to use setup tables, you should stop any changes to the tables, which is impossible (will impact the business).
    I believe this is why SAP does not allow direct access to application tables and has brought in the concept of setup tables. The setup tables hold the data for us to transfer and any changes in the data records is moved to the delta queue.
    Please correct me if I am wrong.
    Hope this helps!
    Regards,
    Maddy

  • Need to convince manager on posting downtime during build of setup tables

    Can any one suggest some pointers in writing a business case for downtime during build up of setup tables
    this is for Sales Application component.

    Delta loads especially for LO extraction is governed by the V3 jobs scheduled in the source system.
    These V3 jobs will post into the delta queue even if there is some activity in the R/3 system.
    To ensure that no transactions get missed - a downtime is taken in the source system so that no documents are changed.
    If you want to avoid downtime :
    1. You should know which documents changed during the period the extractors were refreshed. this is in order to fo a full repair request.
    Typical procedure involves :
    1. Take downtime.
    2. Clear delta queues into SAP BI
    3. Deschedule V3 jobs
    4. Move enhancements into the production R/3 system.
    5. Do an init without data transfer into SAP BI to create the delta queues
    6. Schedule the V3 collection jobs
    7. open the system for users to post / change documents etc
    8. Continue deltas into SAP BI
    If you want to avoid downtime then
    1. Clear delta queues into SAP BI
    2. Deschedule V3 jobs
    3. Move enhancements into R/3 production
    4. Init without data transfer
    5. Schedule V3 jobs
    6. Continue deltas
    7. Perform full repair request for documents that have changed between steps 1 and 5 into SAP BI.
    I have gioven the steps for an enhancement - but then any activity involving changes to V3 extractions or Upgrade activity in SAP BI would fall into the same category.

Maybe you are looking for