Skip to Content
author's profile photo Former Member
Former Member

What's the sequence for inventory data initialization?

Dear all,

We need to re-initialize the inventory data in BW, and only need the data posted after 2010. Below is our planned sequence, please kindly let me know if they are correct or any steps I missed.

1. Tcode LBWQ to delete the inventory related setup tables.
2. On BW side delete the existing initilization for the inventory datasources.
3. Lock system users and background jobs.
4. Tcode MCNB to fill setup table for current material stock.
5. Tcode OLI1BW to fill setup table for material movement.
6. Tcode OLIZBW to fill setup table for revaluation.
7. On BW run the initial without data transfer on all the 3 inventory datasources.
8. Resume posstings in ECC.
9. On BW run full load for all the 3 inventory datasources.
10. Schedule queued delta job for all the 3 inventory datasources.
11. On BW run delta load for all the 3 inventory datasources.

Also I have below 3 additional questions:
1. is there any way that I do not need to block the ECC postings during the inventory initialization?
2. as we only need inventory data posted after 2010, any selection/restriction can I make when running the setup table?
3. As inventory setup is run by company code/plant, we have more than 40 company codes, is there any way to parallel or accelerate the process?

Any post will be appreciated and thank you all for your time in advance!

Best regards,

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jun 28, 2012 at 04:38 PM


    Stpes are ok but some changes..

    1. Setup tables are deleted using LBWG and you also required to check if any LUW's in RSA7 and delete queues using LBWQ.

    Remaining steps are fine if you dont get down time for initialization with data transfer, but if you chance to get down time then better to load with data.

    Since you are loading data after 2010 so it may not requires more time.

    MCNB and OLI1BW, OLIZBW have date selections so you can restrict setup tables filling.

    For UM setup tables you reuired to use single entry company code to fill setup tables i dont think so there is other way to fill all company codes at a time.

    You should block the users at the time of setup tables filling and initialization to avoid data mismatch.


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Go through the below notes which will help in dealing with setup table filling:

      SAP Note : 753654.......... 'How can downtime be reduced for setup table update'

      and SAP Note :436393 'Performance improvement for filling the setup tables'



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.