BI Inventory Process in simple way..

BI ECC Inventory Extraction Process

Apple iPad 2 With Wi-Fi 16GB In Black - MC954LL/A (Google Affiliate Ad)

Most of the time when a BI developer thinks of building an Inventory Process, generally we start from BI content and compete the process assuming there are no custom requirements. May be we incorporate a DSO into the Model as Standard Content does not offer this. But as a SAP novice it is difficult to understand the process how an Inventory process built on.

Let us understand the process from Source Point of view and how this gets into BI environment.

Most of the following steps are summarized based on How – to Documentation from SCN.

A purchased Order is raised based on the  Product Demand based on the Procurement Type for the product. When the Vendor supplies the product a Goods Receipt is created against the Purchase Order which in turn called Material Movement Document and PO is updated with receipt quantity. Subsequently Vendor sends a Invoice and this will be verified against the Goods receipt quantity and payment is made to Vendor.

But our concern here is to extract the Inventory Data from ECC to BI.  Before we start the process need to make sure that necessary configuration steps are carried out by ECC IM/FI consultants.

We need to configure certain important initial settings in ECC source system for Inventory management (IM) before extracting the IM datasource into BW system.

1 In the table TBE11 in ECC system make sure the entry "NDI -New Dimension Integration" is set to X(Active) Flag. If this is not SET you can do this by using TCode  BF11 for Applicaiton NDI.

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

3 Activate the determination of the industry sector. To do this go to 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)    None
• b)    Standard Core,
• c)    Retail
• d)    CP Industry.

Generally we choose the default Option  Standard Core but if  the project  you are working  is for Retails then choose Retail.

Let us understand the Data Sources meant for this.

Standard Data sources:

For this SAP has delivered three Data Sources and details are

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. This is useful whenever there is historical data needs to be extracted during Go Live not part of regular Initialization process using Data Source 2LIS_03_BF. First Initialize the data and get the SNAPSHOT Stock Levels at that moment and extract the Stocks.

2.    2LIS_03_BF: This datasource is used to extract historical data and daily Delta loads.

If it is fresh implementation you don’t need to do the above step unless you have initial stocks  posted from Legacy.

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.

Setup of statistical data extract

The following are step by step procedure for statistical data setup for Logistics application component MM (03).

As a precaution delete the entries from Set Up tables using LBWG  or through SBIW.

Step1: Initialize the stock transfer though SBIW---Settings for application specific datasource---Inventory----Stock initialization and enter your options.

 Step 3:  Similarly fill the tables using other data sources from SBIW-Settings for Application-Specific Data Sources (PI)- Logistics-Managing Extract Structures-Initialization-Inventory Management - Perform Setup-Choose Movement first then choose Revaluation later.

 Step 4: Load the opening stock balances to Infocube. In the info package by default in the update tab the option General initial status is selected.

Step 5 Compress the request containing the opening stock which we have loaded from datasource 2LIS_03_BX. Make sure the "No marker update" option is not set before compression.

Step 6 : Load the historical movements of data from datasource 2LIS_03_BF to Cube/DSO based on design, then from the info package  option Init without data transfer

Step 7: After completion of historical data load to cube either directly or through DSO , the DTP requests has to be compressed. choose "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:  Finally do the initialization step for Revaluations if your projects needs this info similarly to the abive.

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.2012

Now we have loaded 2LIS_03_BX Datasource into Infocube with opening balance of 60 units on 01.01.2012

Loaded material movements deltas for Jan 2012=20 units, Feb 2012=10 units & March 2012=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 Jan2012 in the Query results will be 80 units i.e. 60(Opening balance)+ Jan 2012=20 (-) Feb 2012=10 units (-)Mar 2012=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
Google Nexus 7 Black Wi-Fi 32GB Tablet - NEXUS7ASUS1B32 (Google Affiliate Ad)

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.

Let us understand these by taking Standard Infoobject 0TOTALSTCK (Total Stock) which is built on two Key figures 0RECTOTSTCK (Received) and 0ISSTOTSTC (Issued). Here 0TOTALSTCK is defined as non cumulative as we don’t want to sum this value as it is result of difference between Issue and receive stock Quantities.

So while defining Key figures 0RECTOTSTCK (Received) and 0ISSTOTSTC (Issued) , the option will be Cumulative and Aggregation as Summation where as for 0TOTALSTCK the option is non-cumulative value with 0RECTOTSTCK (Received) as inflow and 0ISSTOTSTC (Issued) as Outflow. That means Total stock is difference of Total receipts minus Total issues based on your selection. Remember one thing there is no physical storage of data for this column value  and is populated at Query level only. Even though you add this part of Cube will not visible when you want to see the values using LISTCUBE.