The first and the foremost the BW consultants has to get a high level understanding of process flow in Inventory management. They are prescribed as follows;
- The Purchase Requisition is sent by the inventory department to the Purchasing department of an organisation.
- The Request for Quotation(RFQ)- The Purchasing Department will ask the vendors/Suppliers to give the quotation for the requested materials.
- The Quotation is then sent by vendors/suppliers to the Inventory department.
- Now, the Purchase order is created in the ECC system in T.Code ME21N based on all the relevant parameters of a quotation sent by vendors to Inventory department. Vendors are selected from whom the material has to be obtained. Finally,the company gives the purchase order to the selected Vendor/Suppliers.
- Creation of goods receipt- The Vendor sends the goods to the requested company with goods receipt. In ECC system the goods receipts is achieved using the T.code MIGO.
- Invoice verification : The Invoice verification is done based on goods receipt.
- Payment to Vendors : Finally the Payment is made to the Vendor based on invoice verification. This is where the integration of FI with MM happens using account determination in ECC source system.
We need to configure certain important initial settings in ECC source system for Inventory management(IM) before extracting the IM datasource into BW system.
Following are the some of the important source system settings in ECC needs to be carried out before extracting/initialization the data sources. They are as follows;
Settings 1 In the table TBE11 in ECC system make sure the entry “NDI -New Dimension Integration” is set to X(Active) Flag.
Settings 2 Go to T. Code – BF11 from ECC and set the indicator to active for the business warehouse application entry. Also, this is client specific settings, entry may needs to be transported to the production
Settings 3 Activate the determination of the industry sector.To do this goto SBIW from ECC —Settings for application specific datasource—-Logistics—Determine industry settings.
The above settings is required to define if data should be transferred to SAP BW. Now, we have the list of radio buttons to choose. They are
a) standard Core,
b) Retail and
c) CP. We always go by the option Standard radio button. But in case if the project which you are working deals with Retail, then we will have to choose the Reatil radio button.
We are now ready to pull the very three important inventory data sources in BW. They are as follows;
There are 3 SAP delivered standard transactional data sources of inventory management in BW.They are as follows;
1. 2LIS_03_BX: This datasource is always needed to carry out the initialization of the stocks. This datasource is used to extract opening balances on granular level of either Plant or material. The T .Code in ECC source system is MCNB. The job run for the datasource 2LIS_03_BX is not very time-intensive because the system does not read the individual documents from the very large MSEG table and instead, it access the smaller tables MARC, MARD and so on.
2. 2LIS_03_BF: This datasource is used to extract historical data. This is used to extract the material movements into the BW system which is MCMSEG structure.
3. 2LIS_03_UM: This datasource is only needed if revaluations are carried out in ECC source systems . This data source is helpful if adjustment in material prices is done time to time in ECC source system.
All the current stock balance will be from dataSource 2LIS_03_BX in the setup table MC03BX0SETUP.
All the historical material documents with dataSource 2LIS_03_BF in the setup table MC03BF0SETUP.
Postings done after the set up are found in extraction queue/central table. They are transferred into the BW using the delta queue. RSA7
Setup of statistical data extract
The following are step by step procedure for statistical data setup for Logistics application component MM (03)
Step1: Initialize the stock transfer. Go to the T.code MCNB or we can go to SBIW—Settings for application specific datasource—Inventory—-Stock initialization
Note: As similar to other application, we need to delete the set up table in LBWG, if we data target already contains the movement data.
Step 2: Restrict by plant, material and storage location. The termination date should be in future
Step 3: Similarly, perform setup for material movements (to be extracted using the dataSource 2LIS_03_BF, Report RMCBNEUA, transaction OLI1BW) for revaluations (DataSource 2LIS_03_UM, Report RMCBNERP, transaction OLIZBW
Step 4: Load the opening stock balances to Infocube. In the infopackage by default in the update tab the option General initial status is selected
Step 5 Now, we should compress the request containing the opening stock which we have loaded from datasource 2LIS_03_BX. In the relevant Infocube, we should make sure the “No marker update” option is not set
Step 6 : If we want to load the historical movements of data from datasource 2LIS_03_BF, then from the infopackage choose update tab and select Init without data transfer
Step 7: After completion of historical data load , The loaded data request has to be compressed. We should make sure that “No marker update“ indicator is set. The reason to set this checkbox is that the historical material movements are already contained in the opening stock
Step 8: After successful Initialization set up is done, we are now ready to set the job ticking regularly (Hourly/Weekly/Monthly). We can use the program RMBWV303 to write data from the extraction queue to the delta queue (or) simply we can go to LBWE— Go to Job control & give start date and time and set the print parameters and schedule the job from job control tab
3. Marker=(Reference point) Concept in IM
Why do we need the Marker/No marker update in Infocube?
Marker is used to reduce the time for fetching the non-cumulative key figures while reporting so that query will report the correct stock balances as same as ECC.
Marker updates do not summarize the data. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record. In the absence of marker update, the data will be added up and will not provide the correct values as compared to ECC.
There are two marker concepts in Infocube.
a) Marker update in Infocube: The Marker update in Infocube is used when we load the records pertaining to the opening stock balance/or the stock present at the time of implementation. In such situation, we will unselect option No marker update( uncheck no marker update) in Infocube so that the value of current stock quantity is stored in the marker.
E.g. Take a look at below scenarios, assume the Current date: 31.03.2011
Now we have loaded 2LIS_03_BX Datasource into Infocube with opening balance of 60 units on 01.01.2011
I have loaded the material movements deltas for Jan 2011=20 units, Feb 2011=10 units & March 2011=10 units in Infocube. I have compressed with marker update for Jan 2011 and Feb 2011 in Infocube. Now, my Infocube will have marker value of 90 units. I have not compressed the marker value for Mar 2011.
Now, My stock balance at end of Jan2011 in the Query results will be 80 units i.e. 60(Opening balance)+ Jan 2011=20 (-) Feb 2011=10 units (-)Mar 2011=10.
Non-Cumulative Key figure
As name suggests a “Non-Cumulative key figure” is a Non Aggregating field which will not be cumulative depending on some characteristic values, instead it is considered with reference to time characteristics.
The non cumulative key figures are used in inventory management or banking application where users are interested to know the stock or Account balance information as of date.
Let’s take an example of revenue on day 1 = 1000 $, on day 2 it is 2000$, and day 3 it is 3000$. So the total revenue for 3 days is 6000$. But if the stock of a particular product on day 1 is 50 unit, on day 2 it is 60 unit and day 3 it is 70 unit, This does not signify the stock for last 3 days is 180 units .The business Users will be interested in knowing the stock available on each day and not the cumulative value for all 3 days put together.
Aggregation Behavior of Non- Cumulative Key Figures
The aggregation behavior determines whether, and how, key figure values are aggregated in reports using the different characteristics or characteristic values. For most of the scenarios for the non-cumulative key figure relating to the time characteristic, the first value (FIRST aggregation), the last value (LAST aggregation) or the average is often taken for calculation.
Example: Let’s see the difference between the FIRST aggregation and the LAST aggregation. The aggregated value for CALDAY 02.02.02, then the non-cumulative with the FIRST aggregation is 90.The non-cumulative with the LAST aggregation will be 110, which is the non-cumulative from 90 plus the receipts of 20
Cumulative Key figure: Cumulative value sales revenue, for example, it makes sense to cumulate the individual sales revenues using different periods, and using characteristics such as Products and customers.
Example of the cumulative key figures:
Sales volume (cumulative value): Sales volume 01/20 + sales volume 01/21 + sales volume 01/22 gives the total sales volume for these three days.
Detailed example for Non cumulative KFY
Let’s consider a scenario which will help to understand the use of Non-Cumulative Key figures. In a manufacturing industry we need to provide stock Balances on a particular day/date done by the customer.
That is, Stock balance = (Stock Balance on previous day + Issued stock– Stock returned) on current day.
Now, let us go step by step process of creating a Non cumulative Key figure with the above scenario to arrive at stock balance.
Step 1: Creating Cumulative Key Figure
1.1 First we will create two cumulative Key figure 0RECTOTSTCK(Stock returned) and 0ISSTOTSTCK(Stock issued) where = 0ISSTOTSTCK =Outflow and 0RECTOTSTCK= inflow with aggregation as SUM and exception aggregation as Summation.
1.2 Second we will create a non cumulative Key figure as 0TOTALSTCK(Total stock balance) and select option Non *** Value with In/Outflow as shown below, where 0ISSTOTSTCK =Outflow and 0RECTOTSTCK = inflow
Step 2: Creating Non-Cumulative InfoCube
2.1 Now we will create a infoCube say for example with technical name as YNONC_CUB and include non-Cumulative key figure in it. Remember we have created a non cumulative key figure as 0TOTALSTCK(see point 1.2) above.
After we include the non cumulative 0TOTALSTCK into the key figure folder, automatically the keyfigure inflow 0RECTOTSTCK and outflow 0ISSTOTSTCK will get added automatically into key figure folder of Infocube.
2.2 Include the time characteristics 0CALDAY for exceptional aggregation and maintain the validity table.
Set the validity table in Infocube
3. In order to set up the validity table for Infocube YNONC_CUB, go to extras—-maintain non cumulative values and choose the required characteristics infoobject along with time characteristics 0Calday as validity reference characteristics.
4. Create a transformation and DTP between the Infocube YNONC_CUB and the datasource Y_INVTY_TRAINING.
5. Now, load the data from DTP. This DTP will load the data from the datasource Y_INVTY_TRAINING to Infocube YNONC_CUB.
6 Create a Bex query on top of Infocube Y_NONC_CUB.
7. Reconcile the data in Bex query with SAP ECC data for opening balance and closing balance using the T .code MB5B in SAP ECC .