Skip to Content
Author's profile photo ashok nannuri

Inventory Modeling in SAP BW4/HANA

Inventory Management Process:

This process allows users to manage all the Materials/items purchased, manufactured, sold, or kept in stock.

For each Material/item, users enter the data relevant for a particular area in the system. This data is used automatically by the system for purchasing, sales, production, inventory management, accounting and etc.

It provides optimum support for business. Helps create orders, delivery notes, and outgoing invoices, automatically calculating prices, sales units, and gross profit.

Enables complete control over stock quantities at all times and lets users analyze the financial aspects of stockholding at the same time. Allows users to control production on the basis of the items that are used for production and on the basis of the finished product and any by-products created.

Inventory Data Flow in ECC and BW4/HANA


Inventory Data Sources: –

2LIS_03_BX – Stock Initialization for Inventory Management
This structure is used to extract the stock data from MM Inventory Management for initialization to a BW system.

Replicate the 2LIS_03_BX in SAP HANA studio as shown below.
Datasources  ODP-SAP Extractors RK3CL800 SAP-R/3MM
Right Click on MM —- > Click Replicate
Find required datasource as shown below and select next and then finish


As per data flow below, Install the Infosource – /IMO/MMIM_IS00 and ADSO from Business content using RSA1 transaction from BW4 HANA system.

Once Infosource and ADSO installed in BWHANA System, this will be available in HANA Studio in below path


We have all 3 layers to create the dataflow.
First we will create an info area in HANA studio. Right click on any user - New  Click Create Info area  give description and Finsih.
Now we are ready to create dataflow — > Right click on Info Area click on New  Dataflow

Create the dataflow as shown below.
Datasource – 2LIS_03_BX datasource which we replicated earlier.
Infosource – /IMO/MMIM_IS00 which we installed from Business content.
ADSO – /IMO/D_MMIM01 which we installed from Business Content.

Dataflow diagram which needs to be created as per below


ADSO – /IMO/D_MMIM01 setting needs to check as below
General modeling properties of an advanced DSO with non-cumulative key figures


Make sure to check the Inventory check-box. Alternatively, Template “Inventory” can be chosen to auto select the required properties.

Transformations and DTP
Create Transformation between infosource and ADSO shown below, this will open a GUI from HANA studio, where you can perform mapping and add business logic in start/end routine. Then activate.
Right Click on ADSO – /IMO/D_MMIM01 —Create Transformation.

This will open a GUI in BW4HANA as below, perform the code logic if required then activate


Data Transfer process
Right Click on ADSO – /IMO/D_MMIM01 - DTP’s  Create DTP  With the removal of PSAs and InfoPackages in BW/4HANA, DTPs are used for the initial load into advanced DSOs.  To load data from 2LIS_03_BX, which is a onetime load, it is imperative to select the Extraction Mode as “Initial Non-Cumulative for Non-Cumulative Values” in the DTP.

So the reference table which needs to be checked for 2LIS_03_BX datasource is shown below. Table name – /BIH/AD_MMI015

Datasource – 2LIS_03_BF

The inventory model has split inventory corporate memory into two DSO’s, regular and historic

Normal — /IMO/CMMMIM02

Historical — /IMO/CMMMIMH1



After creating according to dataflow diagram, flow should like below


Historical dataload

To load historical movements i.e. those stock changes that occurred before the initialization.
Load the DTP from 2LIS_03_BF to /IMO/CMMMIMH1 with Full according to your selection criteria.

Now when we loading data from corportate memory to EDW ADSO, we need to select below check box to update stock.

Composite provider

(/IMO/V_MMIM01) Install Composite provider from business content and use below ADSO’s in HANA studio. This Composite Provider enables you to evaluate stock quantities, stock values and material movements from SAP ERP Central Component (SAP ECC).

Assigned Tags

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


      Nice blog.

      I have few questions on this.

      1. Does infopackages are removed for good?
      2. How does historical transactions and marker updates are being handled in BW4/HANA



      Author's profile photo ashok nannuri
      ashok nannuri
      Blog Post Author

      Thanks Nagendra.

      Yes there is no Infopack concept in BW4/HANA.

      All the historic transactions has been pushed down to DTP level. Once we select the check box mentioned in above blog saying that Extract from Archive, for Full loads from BF, this won't update any balances, so no compression and marker update required.

      Author's profile photo Nagendra babu
      Nagendra babu



      Author's profile photo Parth Kulkarni
      Parth Kulkarni

      Hi Ashok,

      Very helpful. I have a question.

      How does corporate memory helps us in entire data flow instead of storing data multiple times?

      Author's profile photo ashok nannuri
      ashok nannuri
      Blog Post Author

      Hi Parth,

      Data modeling is now more leaned towards LSA++.

      The corporate memory contains the complete history of the loaded data.

      This displays an intermediate layer. The data is posted to other DataStore objects (advanced) that serve as architected data marts. It is filled separately from the update in the architected data marts.



      Author's profile photo Radha Krishna Reddy Gaddam
      Radha Krishna Reddy Gaddam

      Hi Ashok,


      Very interesting blog on Inventory Management in SAP BW4/HANA.

      How to differentiate the cumulative and Non cumulative and initial stock balances in ADSo ?





      Radha Krishna Reddy

      Author's profile photo ashok nannuri
      ashok nannuri
      Blog Post Author

      Thanks Radha Krishna.

      1. You need to select Inventory selection check box in ADSO settings to add Non cumulative keyfigures.
      2. For advanced DSOs, reference points contain the initialization records.Reference points are updated whenever a request with delta movements is activated. In other words, reference points are the stock values of the initialization plus/minus those of all activated requests with delta movements.
      3. So, is it like stock initialization data can’t be seen in movement DSO and it will always be present in the reference table only and BW will consider the reference table.
      Author's profile photo VENKATA S KOSARAJU

      Interesting blog

      Author's profile photo Rukmambara Ananthula
      Rukmambara Ananthula

      Very useful. Thanks