Skip to Content

SAP BW4HANA 1.0 SPS9 Inventory Management Implementation

Hi Experts,

We are implementing Inventory Management as per the standard SAP Content on SAP BW4HANA 1.0 SPS 9

-Completed the Initial loads for all target ADSO as per guidelines in the SAP Link provided below for BW4HANA

-In Stock overview report (STD SAP report) “Quantity Total Stock” are showing exactly twice the quantity when executing the report, I can observer that it is because both Delta Movements (/IMO/CMMMIM01 -> ADSO /IMO/D_MMIM01) and Historical Movements ADSO (ADSO /IMO/CMMMIMH1 -> ADSO /IMO/D_MMIM01) are being loaded to Target ADSO D_MMIM01 with DTP settings (uncheck the historical Transactions for delta) for all delta loads

Can you please suggest if these two ADSO i.e, Delta Movements and historical movements should be loaded to target if yes are we missing any settings in DTP/ADSO for delta loads to get the correct output in report.

Other way is that should we load Historical Movements ADSO (ADSO /IMO/CMMMIMH1 -> ADSO /IMO/D_MMIM01) for the first time, and for delta’s only the Delta Movements (/IMO/CMMMIM01 -> ADSO /IMO/D_MMIM01) ADSO should be loading part of daily loads.

The query applies for Revaluations flow as well. Please suggest


Mahesh Kumar. A

im-mm-flow.png (102.2 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on May 21, 2019 at 01:21 PM

    Hi Mahesh,

    totally correct, DTP into the 'delta' staging DSOs /IMO/CMMIM01 for movements and /IMO/CMMIM02 for revaluations should be done with setting "Delta init without data".

    For the issue

    1) "DTP flowing from /IMO/CMMMIM01 to /IMO/D_MMIM01 (...) is automatically getting checked even though it is unchecked manually". What exactly did you do? Activating of DTP, closing and reopening, and the option was checked again automatically? Did you close Eclipse in the interim or was it potentially caused by cache problem?

    If the problem persists raising a Support ticket with screenshots or screencam might be the way to go.

    2) After load is finished it takes around 5 minutes that the report is reflecting the updated numbers: It might be worth to check the runtime properties of the composite provider and/or query, e.g. 'query cache'.

    All the best,


    Update: Below some pics trying to visualize the data load procedure, hope it helps...

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 16, 2019 at 02:15 PM

    Hi Mahesh,

    the movement data from the extractor 2LIS_03_BF (same for 2LIS_03_UM) should be only loaded ones.

    The historical movements, that is the data coming from the setup table, should be loaded with FULL into the staging DSO /IMO/CMMMIMH1 only. From there, one time load with flag "Historical Transactions" into the EDW Core Layer DSO's.

    The later delta movements, that are the movements captured after the stock initialization took place, should be loaded into the staging DSO /IMO/CMMMIM01. From there load the data as 'normal' ongoing deltas into the EDW Core Layer DSOs.

    One more possible reason for the issue you mentioned (but happens quite often...): Twice the stock amount might also appear in the stock report, when the stock initialization (OLI1BW & OLIZBW) was carried out twice without deleting the setup tables in the interim.

    Hope it helps to fix your issue,


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 21, 2019 at 12:21 PM

    Hi Andreas,

    Thanks for your quick response.

    Similar steps were considered during Inventory data loads and I would like to add some additional points

    -As informed, post one time load with flag "Historical Transactions" into the EDW Core Layer DSO's(/IMO/D_MMIM01) is done, the later loads i.e., from /IMO/CMMMIM01 to /IMO/D_MMIM01 should be loaded with ‘perform delta initialization without data transfer’ and then later movements will follow with normal ongoing deltas into the EDW Core layer DSO’s from the same flow, if this is not considered than Data would be loaded twice to the Integrated Layer /IMO/D_MMIM01.

    The same can be considered for Revaluations flow as well, correct me here please.

    Also two other issues in this flow were observed:

    -The delta DTP flowing from /IMO/CMMMIM01 to /IMO/D_MMIM01 having ‘Historical Transaction’ option in update tab is getting automatically modified to with a check box even though it is unchecked manually

    -The other issue is that after loads are completed to /IMO/D_MMIM01 in the report “Stock Overview” report, one of the key figure “Quantity Total Stock” (based on Inflow and outflow calculation) is having slight delay in providing the output in reports (around 5 mins) including RSRT as well. Is this the Normal behavior.

    Let me know if you have came across this else I will raise it with SAP Support if required.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 17 at 08:11 PM

    Does data initialization(First time full Loads) need downtime with BW7.5 using above process flow?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.