HI,
Please find below the information rearding inventory.
The Loading process for Inventory Data sources is slightly different from the other LO Cockpit data sources.
This slight difference results in incorrect stock values after repeated efforts spent in loading Inventory data.
Listed below are the steps that can be followed by developers while they are loading the Inventory data for the first time after the GO-LIVE of BI system or by the support guys who have issues with regards to incorrect stock values. The Steps deal with loading the complete inventory data instead of providing some patch work by doing full repairs.
Brief Background
The Blog assumes that the standard data flow has been used i.e.
2LIS_03_BX -
> 0IC_C03
2LIS_03_BF -
> 0IC_C03
2LIS_03_UM -
> 0IC_C03
2LIS_03_BX - Opening Stock Data Source. The values obtained through this data source is the current status of the inventory
2LIS_03_BF - Daily Inflow and Outflow of stock entries. This data source is responsible for providing the stock received or consumed on a particular date.
2LIS_03_UM - Holds the value of the stock. Since the key figures in this data sources are related to stock value they are of comparatively less importance in most of the systems.
Step by Step Process of loading Inventory data
1. Delete all Data in Cube 0IC_C03.
2. R/3 System Down/User Locking i.e. no Inventory posting in R/3 system
3. Execute program RMBWV303 to clear the extraction queue in R/3 system
4. Delete all initializations from 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to cube 0IC_C03 in BI.
5. Delete setup table contents in R/3 for Application 03 Tcode- LBWG
6. Fill Setup Table for 2LIS_03_BX Tcode u2013 MCNB
7. Fill Setup Table for 2LIS_03_BF for posting date = (current date) u2013 (current date u2013 7) i.e. last 1 week. Tcode u2013 OLI1BW
8. Fill Setup Table for 2LIS_03_UM for posting date = (current date) u2013 (current date u2013 7) i.e. last 1 week. Tcode - OLIZBW
9. Execute infopackage for data transfer for 2LIS_03_BX with update mode Generate initial status
10. Compress Request with marker update in 0IC_C03 Cube in BI(i.e. marker option in cube unticked)
11. Execute init with data transfer for 2LIS_03_BF
12. Compress Request without marker update in 0IC_C03 in BI (i.e. marker option in cube ticked)
13. Execute init with data transfer for 2LIS_03_UM
14. Compress Request without marker update in 0IC_C03 in BI(i.e. marker option in cube ticked)
15. User Locking can now be invoked in R/3 system.
16. Fill Setup table for the rest of the period for 2LIS_03_BF i.e. posting date = (01.01.1900) u2013 (current date - 8).
17. Fill Setup table for the rest of the period for 2LIS_03_UM i.e. posting date = (01.01.1900) u2013 (current date - 8).
18. Load full Repair Request from 2LIS_03_BF to 0IC_C03.
19. Compress Request in cube without marker update i.e. (marker option in Cube ticked)
20. Load full Repair Request from 2LIS_03_UM to 0IC_C03.
21. Compress Request in cube without marker update i.e. (marker option in Cube ticked)
Note: V3 Jobs would be required to be scheduled in R/3 system to move data from Extraction Queue to Delta Queue if not available.
You would observe in the above steps we have first filled setup tables for 2LIS_03_BF and 2LIS_03_UM for last 1 week during the system downtime. This strategy is being used to reduce the downtime required from the customer.
you can find more pdfs and information if you google in.
Regarding KEy field of VBAP table:
VBELN--Sales Document
POSNR---Sales Document Item
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.