Skip to Content
Author's profile photo Anjali P

Inventory Data Loading (MM) to BW PRD system

We were performing Inventory data loading to BW PRD (BI 7.0) system from ECC 6.0 and I would like to share the pointers I prepared during the activity.  

There are 3 DataSources for Inventory;

  • 2LIS_03_BX (Stock Initialization for Inventory Management)
  • 2LIS_03_BF (Goods Movements from Inventory Management)
  • 2LIS_03_UM (Revaluations) – captures revaluation data.

We have used Un-serialized V3 as the update mode for inventory in LBWE.

Before starting with extraction, login to ECC PRD, check the number of records in the MKPF – Header: Material Document and BKPF – Accounting Document Header. MKPF is the source table for 2LIS_03_BF and BKPF is for 2LIS_03_UM.  This will give you an idea of the time-window required for initialization.  We have to have a downtime which is predefined. (We had a down time of 48 hours) Take care not to lock the user that performs the dataloading.  (Ya…this still happens!The whole data loading procedure was done by around 60 hrs.

Check all the relevant objects are transported correctly to PRD.

Step 1:   Lock the users, all users who may do a posting to the stock will have to be locked.

Step 2:   In ECC-PRD, in table TBE11 maintain entry for NDI and BW as active.

Step 3:   Delete the setup tables in LBWG for inventory (Application 03).

Step 4:  Initialize stock using Tcode MCNB. Give the name of run, a future termination date, and 2LIS_03_BX for  transfer structure. F9- execute in background.  In SM 37, check the status of job – RMCBINIT_BW. ( When the status became ‘Finished’, we had around 3.36 L records and it took around 13 minutes).

Step 5:  Fetch these records to BI through infopackage for datasource 2LIS_03_BX.  This infopackage will have  ‘General Initial Status’ as update mode.  Execute the DTP with ‘Initial Non-Cumulative for Non-Cumulative’ extraction mode and fetch the records to the InfoCube IC_C03.  Once successful, compress the request without using the “No Marker Update” (checkbox empty).

Step 6:  This step was started parallel to Step 5 after fetching the records to PSA. Initialize Material movements, Tcode OLI1BW for 2LIS_03_BF.  Give the name of run, a future termination date; select ‘Based on posting date’ give 31.12.9999 in posting date, as it’s possible to make postings with a future date. Execute in background.  In SM 37, check the job status for the job RMCBNEUA.  (We had around 70 million records and it took around 12 hours for the job to finish).

Step 7:   This step was run in parallel to initializing material movements.  Initialize Revaluation in OLIZBW.  Make similar selection as above.  Give company code. Run in background; check in SM37 the status of job RMCBNERP.  This setup table run has to be executed for every company code you have. (We had 5 Company Codes, so 5 times we executed the run selecting one after the other Company Code, Select 1 company code and execute.  When it finishes, select the next company code and execute and so on.  We had around 6 L records and it took around 6.5 hrs)

Step 8: Fetch these records to BI through InfoPackages. (We had Full and then INIT w/o data transfer.  The Full infopackage was scheduled in background.)

Step 9: The users were unlocked after initialization. In theory after filling setup tables we can unlock users as we have used Unserialized V3 update.  Execute DTP and fetch the records to InfoCube.  Compress the request using the “No Marker Update” (checkbox checked).

Step 10: Schedule delta jobs.  In LBWE, in job control, Give Start date as immediate, select periodic job as daily, give print parameter- select the printer, Select Schedule job.  Check in SMQ1.  Schedule delta infopackages.

Issues we faced:

1. The records added for Stock initialization in Inventory cube is almost double than the ‘records transferred’.  This was due to ‘stock in transit’. Such movements really consist of two movements: (1) The goods issue from the ‘stock in transit’ and (2) the goods receipt in the storage location. To reflect this correctly, an additional line for BW is createdRefer SAP Note 415542.

2. While loading Revaluation records to Inventory cube we got an error as ‘Rough Fiscal year variant not processed’. This was rectified by maintaining fiscal year variant in SPRO->SAP Netweaver->Business Intelligence->Settings for BI Content->Retailing-> Set Fiscal Year Variant.  Then reloaded the data to the Cube.

Hope its helpful


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Raman Korrapati
      Raman Korrapati

      Hi Anjali,

      Very useful article. if you add some screens shots it may look more effective.

      Thanks for sharing

      Author's profile photo Anjali P
      Anjali P
      Blog Post Author

      Hi Ram,

      Yes, you have a valid point there...but i guess there are documents already in SDN on this.  These are pointers prepared as already mentioned so that you get the whole idea at a glance and don't miss any points.....

      Thanks again,


      Author's profile photo Raman Korrapati
      Raman Korrapati

      Hi Anjali,

      Yes, documents are there, as my guess those are old version of BW(3.x). if you add pic of bw 7.x versions. that would be more useful. because inventory is bit different process than other extractions part.


      Author's profile photo Craig S
      Craig S

      Can you clarify exactly what production system you are loading?  I thought from the title that this was an article on an initial data load of a regular ERP system.  But it looks like you are extracting records from an ERP system and populating a BW system. 

      Did I miss something?  If not, I would suggest you modify your title to include BW PRD system.  Not just PRD.


      Author's profile photo Anjali P
      Anjali P
      Blog Post Author

      Hi FF,

      Yes you are right..this blog is about extracting records from ECC to BW...thank you for your suggestion...I have changed the title.



      Author's profile photo Stefan Neumann
      Stefan Neumann

      Hello Anjali,

      in Step 8, do you mean the same DataSource as above (2LIS_03_BX) ?

      Thanks and regards

      Stefan Neumann

      Author's profile photo Mohammed Asif Tahsildar
      Mohammed Asif Tahsildar

      Hi Anjali

      Any specific reason why you guys have used Un-serialized V3 as the update mode for inventory in LBWE and NOT Direct Delta or Queued Delta.

      Thanx and Regards

      Mohammed Asif.

      Author's profile photo Former Member
      Former Member

      Nice document Anjali !

      I've few doubts :

      1) If I'm filling setup table for 6 CCs (Step 7 in your case) one after another, The setup table data gets overwrite or append?
      In other words if data is already there in set up table & we try to again fill the setup table (for same application component). Will it overwrite the previous records which are there OR will it append the new records with existing records?
      2) For every datasource we have separate setup table or only one setup tabe?
      3) If we have only one setup table for all 3 the datasources then if BX data is extracted to BW then before fill setup table for BF, we need to first delete the data from setup table?



      Author's profile photo Raman Korrapati
      Raman Korrapati


      Seems like your new to BW.

      1. Set up table is just like a table which holds the data. it won't records any live transactions. its intermediate table . if you load same data again and again, data will be doubled and tripples. So never do that, it leads duplication. Always delete and fill set up tables as per your needs.

      2. For Each LO data source have it own set up table. Please explore mote about LO extraction concept.

      3. No, each data source have their owns et up table.

      Eventhough why need to delete setup table data and refill:

      For ex: some one loaded data for BX and loaded into bw.

      later due some data disturbance at bw side, you may thought to delete and reload the whole data. if you fill setup tables without deletion, your data will be doubled and leads to duplication. So thats why always delete and fil lset up tables. other wise data will mismatch.

      please put some efforts and do google  search about LO extraction, you will get more than required pdf/docs.


      Author's profile photo Mahesh Pakhare
      Mahesh Pakhare

      Hi Anjali,

      Very useful article . 

      Is the same process for BI Version 7.4??

      Thanks for sharing