Professional Documents
Culture Documents
c. Assign process key by tcode BF11 --> set the flag as active for application components
BW, BC-BW & NDI (text: New dimension Integration)
In some scenarios, if this activity is not performed, it creates problems while loading data. If we process with
the loading activity without performing the below settings, records are transferred but no records are added in
the Cube
1. 2.There are 2 ways of extracting Inventory controlling data from SAP-R/3(OLTP) to SAP-BI(OLAP)
a. Using Non-cumulative KFs--> If it is daily extraction then use Non-cumulative KFs method. System is not
allowed to maintain DSO as primary data store but InfoCube allows.
Note: If any Cube maintains a Non-cumulative KF in its structure then it is called Non-cumulative
InfoCube (ex: 0IC_C03).
b. Using Snapshot method (Uses DSO) --> Primary data store is DSO. After that we can load data from
ODS to IC. Detail level of analysis is not possible in SNAPSHOT method.
c. Inventory Controlling Datasources for data extracting into 0IC_C03,
2LIS_03_BX -->Stock Initialization/Material stocks [Maintains Non-Cumulative KFs]
2LIS_03_BF--> Goods Movements [Maintains Cumulative KFs]
2LIS_03_UM-->Revaluations [This is accomplished by creating a price change document, without
physically moving the goods]
Important tables for IC (Inventory Controlling)
MSEG --> Material Segments
BSEG --> Accounting Segments
MARA -->Material Master
MAKT --> Material text
MARC -->Plant Data for Materialetc
2.
h.
It gives now initialization run screen where you can restrict by plant, material and storage location as
shown below.
Note: Termination date is in the future.
1.
1.
Fill setup tables for 2LIS_03_UM --> tcode OLIZBW.You will be asked for the Back Ground Job Print
parameters and give LOCAL as the Output Devices.
7. From BW,
1.
Pull the data for 2LI_03_BX -->its a onetime activity and needs to be done carefully. In the
InfoPackage, choose the upload mode Generate Initial Status
Note: In the InfoCube (0IC_C03), release request with Marker update (No Tick). Marker update is just like
check point--> it will give the snapshot of the stock on a particular date when it was updated. Marker Update
is a special feature available only for Non-cumulative InfoCubes. As we are using Noncumulative key figure
it will take lot of time to calculate the current stock for example at report time. To overcome this we use
Marker update.
1. 8. Pull the data for 2LI_03_BF --> Init Delta without data transfer.
Note:The Marker has no importance for this request since no data was transferred. Perform full load.
Release the request with No Marker Update Tick. If you choose No Marker Update and compress the
reference point is not updated but the requests are moved to zero (Means request no. will become 0). Then
successive Delta loads must always be compressed with No Marker Update Tick.
1.
9. Pull the data for 2LI_03_UM --> Init Delta without data transfer.
Note:The Marker ha s no importance for this request since no data was transferred.Perform full load. Release
the request with No Marker Update Tick.and successive Delta loads must always be compressed with No
Marker Update Tick.
Job scheduling to fill the delta queue,Tcode --> LBWE -->Job control --> Schedule the job. Schedule the
delta update in process chain for both the datasources: 2LIS_03_BF and 2LIS_03_UM.
10. Some important Reports Details,
Stock Ledger report
Valuated stock report
Blocked stock reportetc
Thanks,
RK --> CTS