Inventory management: non-cumulatives VS. snapshots

In the How to <i>Handle Inventory Management Scenarios in BW</i>, I read that (p. 2):
- Inventory management with non-cumulative key figures is better when <i>"90 percent of all materials were moved 1 time in the month"</i>;
- Inventory management with SnapShots is better when <i>"90 percent of all materials were moved 1 time in the month"</i>.
I think the second sentence is not correct. But what can be the right number of movements to be considered?
Thanks a lot,
Davide

Hi Ajay,
so my next question is:
Besides the time granularity needed (daily-level vs. monthly-level), is there a threshold for the number of movements, that could be used to choose one of the two models?
I mean, if materials are moved on average e.g. less than 10 times per month, the non-cumulative architecture could be best one. While if there are more than 10 times per month, the snapshot architecture could be more appealing. In this example, 10 movements per month is the threshold.
Cheers, Davide

Similar Messages

  • Inventory Management (Non-cumulative values)

    Dear experts,
    I want to extract inventory data from 2LIS_03_BF.
    How do I have to configure the Key figures; for example: 0VALSTCKQTY. Is there a need to use Non-cumulative value with in- and outflow as in Content.
    Which other possibilities exist?
    After InfoObject config. - what are the exact next steps?
    Do I load data from the 3 DataSources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM into one DSO first and then into one cube or do I have to split?
    I dont want to use the BC data flow.
    Thanks for your advice.
    Patrick

    hi,
    Please search the Forum for this, this has been discussed many times.
    regards,
    Arvind.

  • Inventory Management Non Cumulative Please Help

    Hello BW Gurus.  My current client needs to report on average inventory for the last 12 months, but the material movements cube will only allow me to report on the average inventory for the last day of the current month. Can someone give me some pointers to help me figure out a solution. Also, will I be able to create an ods layer even though the cube has noncumulative key figures?

    Hi,
    I dont know the exact answer to your question. But see if this doc helps you..( hope you dont have it already)
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0ea8a990-0201-0010-2796-fa9ae8691203
    assign points if useful ***
    Thanks,
    Raj

  • Inventory cube non cumulative KF displaying incorrectly.

    Hi
    I have created a inventory cube which is a copy of 0IC_C03, fed from a DSO which has the all the Material documents.
    I have intitialised using the BX extraxctor to the cube, then loading data from r/3 via the dso. Have MP on top of inventory and revaluation cube.
    Due to an error in the code logic i had to drop the cube and reload the data from the BX PSA and subsequently the DSO.
    my problem started then, the cumulative key figure have gone haywire ie they the balance display rubbish data. the data loaded into the cube is correct
    also if I delete the latest request and reload the request, then the  KF display correctly. strange!
    I also the same problem for value as i have a revaluation cube. the inventory values are wrong, when i do a list cube from the MP all is ok.
    i checked the validity slice rsdv, it is ok.
    i also only have 0calday as the non cumulative setting.
    Another thing i noticed was if filter the material by one plant then i get the correct value, if i try to display all plants then it all the balances go incorrect.
    also if i see the balances by month only the latest month is incorrect.
    if you need more info please feel free to ask.
    appreciate if some can propose a solution
    Lawrence
    Edited by: lcoelho on Oct 14, 2011 7:03 PM

    Hi Lawrence,
    SAP suggests to upload non-cumulatives NEVER from a DSO but from the PSA in parallel to DSO and Cube.
    Andreas

  • Non-cumulative Inflow and Outflow explanation

    Hello Everyone,
    We are just implementing Inventory reporting in BW and cannot understand query results.  We have searched the forums and documenation, but cannot find an answer.
    We have a Non-*** Key Figure that we have defined an Inflow and Outflow for (in the aggregation tab).  Can someone please explain in detail how this Non-*** will be calculated with Inflow and Outflow.
    The Non-*** has Aggregation of SUM and exception of LAST
    Here are our results (and the Inflow and Outflow KF's are ***)
    We have a test query showing the KF for Inflow, KF for Outflow and KF for the Non-*** value.
    The Inflow KF shows 26320
    The Outflow KF shows 12428
    The Non-*** KF (with the 2 above Inflow/Outflow) shows 66002
    We thought this Non-*** would be calculated as Inflow (minus) Outflow.  So the total of the Non-*** we were expecting 13892.
    How does this Non-*** work with Inflow/Outflow?  We can't find anything on this.
    Thanks so much,
    CM

    Hi CM,
    this has been discussed so many number of times in SDN.. and please search the forum on the same..
    Also for ur ref:
    non-cumulative key figures
    Inventory management: non-cumulatives VS. snapshots
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    http://help.sap.com/saphelp_nw70/helpdata/EN/7e/96cc373de44040e10000009b38f8cf/frameset.htm
    How to implent inventory cube 0IC_C03  with Transformation & DTPs
    Thanks
    Assign points if this helps

  • Inventory management snapshot model using Datamart Interface

    Hi,
    We have implemented Inventory management NON-CUMULATIVE scenario.
    Now for reporting needs we are adding snapshot model and trying to use datamart interface to fill up snapshot cube.
    But how to get value of KF say "ZTOTALST" becuase NON-*** cube has only changes stored as "0RECTOTSTCK" and "0ISSTOTSTK". If anyone has implemented or has any ideas on using snapshot model  with datamart interface , please help .
    regards,
    Daljit Boparai

    Try out with this
    http://help.sap.com/bp_biv335/BI_EN/index.htm
    Regards
    Kumar

  • Indication of documents about Inventory management in BW

    H
    I've got this excellent document "How to handle inventory management scenarios in BW". Very clear, easy to understand.
    I'd like to go into more details about 2LIS_03_BX (initialization of the current stock), compression of requests and marker update.
    Does anyone have indication of other documents that deal with these subjects?
    Thanks in advance
    César Menezes

    Hi Cesar:
    Please refer to the documentation below:
    "10 important points to consider while working with inventory management", blog by Ranjit Rout.
    /people/ranjit.rout/blog/2009/06/14/10-important-points-to-consider-while-working-with-inventory-management
    "Non-cumulatives / Stock Handling"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31?quicklink=index&overridelayout=true
    "BI Inventory Management- Data Loading", paper by Gaurav Kanungo.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906b837a-0d54-2c10-08b8-bde70337547e?quicklink=index&overridelayout=true
    "Inventory Management (0IC_C03) Part - 1", paper by Surendra Kumar Reddy Koduru.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60101663-3cb7-2c10-3687-8d1e0ef51b0d?quicklink=index&overridelayout=true
    "Inventory Management (0IC_C03) Part - 2", paper by Surendra Kumar Reddy Koduru.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0783925-f4be-2c10-9c89-ffa108f72547?quicklink=index&overridelayout=true
    "Inventory Management (0IC_C03) Part - 3", paper by Surendra Kumar Reddy Koduru.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e00860a4-350f-2d10-29a0-fc09681a8bae?quicklink=index&overridelayout=true
    "Inventory Management in SAP BW", article by Harishraju Govindaraju.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9054ac59-aac4-2d10-3d9b-df98c52b4f31?quicklink=index&overridelayout=true
    "Loading to the Inventory Cube 0IC_C03", blog by Akshay Chonkar.
    /people/akshay.chonkar2/blog/2010/05/19/loading-to-the-inventory-cube-0icc03
    "Insights into Cube compression", blog by Arun Varadarajan.
    /people/arun.varadarajan/blog/2008/08/19/insights-into-cube-compression
    SAP Note 643687 - "Compressing non-cumulative InfoCubes"
    SAP Note 745788 - "Non-cumulative mgmnt in BW: Verifying and correcting data"
    SAP Note 1548125 - "Interesting facts about Inventory Cubes"
    Regards,
    Francisco Milán.
    Edited by: Francisco Milan on May 7, 2011 12:08 PM

  • Loading to Inventory Management Snapshot ODS and Cube

    I am trying to develop an Inventory data model and have already created and loaded to the Inventory Management (0IC_C03) cube.
    I have now created a Snap Shot ODS and Snap Shot cube, is there a way that I can load to these objects without having to do a re-init? Thanks

    Hello Niten,
    There is no need to do re-init, you can load the data into non-cumulative and snapshot targets in parallel. Through sam infopackage with which you are loading to 0IC_C03, load to snapshot targets also.
    Regards,
    Praveen

  • How  use non cumulative key figure and noncumulative key figure screenshot

    how  use non cumulative key figure and noncumulative key figure screenshot

    Hello,
    Please see this docs for Non-Cumulative and Snapshot scenario,
    [How to Handle Inventory Management Scenarios in BW (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
    [Non-Cumulative Values / Stock Handling|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366]
    Thanks
    Chandran

  • About archiving BW Inventory Management cubes

    Hi everyone!
    I would like to know what a marker in Inventory Management (BW) is. This question comes from the following: I need to archive a IM cube, and it presents the following option:
    Stocks:
    Only transactions
    Transactions and Markers
    I don't know what a marker is, so I'm kinda lost here...
    Any help would be greatly appreciated (and rewarded, ofc!).
    Best Regards,
    Luís.

    Hi,
    Marker is fairly simple, you will get the details also on help.sap.com with more detailed explanation.
    In a brief here is what i can tell you :
    1. The marker is set on a specific date and the value of the inventory KF( NON CUMULATIVE KF) the value on that particular date is stored in the cube.
    2. Since Inventory is working on the non cumulative method the difference is calculated since DAY 1. but with Marker the difference is calculated from the day of marker.
    Hence it helps in retrieving faster results.
    Let me know if you want more information.
    Regards,
    Den

  • Snapshot scenario or non cumulative key figure  in inventory management

    Hi
    We are currently using Inventory Management with non-cumulative key figures but we get very high performance problems due to so big number of lines in info cube.
    We are analyzing the other scenario with snapshot and I am asking if it would be very realistic to use it to satisfy our requirement: to be able to get inventory management at day level for about 2 000 000 combinations article-site and about 100  000 stock movement lines per day (we are retailer!).
    Is there somebody to give me advice about it?
    Tanks a lot
    Anne

    Being a non-cumulative KF, total stock is automatically takes care of that.
    Try putting all the restrictions which you have included for total receipts and total issues, for eg,  restrict Total Stock with the movement types used in Receipts as well as Issues.
    Check and revert.
    Regards
    Gajendra

  • Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

    Hello all.
    I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures.  I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
    Steps I followed:
    1.  Ran initialization of beginning balance with 2LIS_03_BX
    2.  Ran the historical job with 2LIS_03_BF
    3.  Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
    4.  Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
    Now, to this point, everything was fine.  Quantities were as expected.  Dollar values were as expected.  The problem occurs once I load deltas:
    5.  Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
    Query example:
    MATERIALA: 
    Initial Stock Balance = 1000 EA
    Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
    Now, I have the record in BW showing the stock issue of 150.  However, the non-cumulative key figure within the query still shows 1000.  And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance.  It is like it is not recognizing the updates.
    Any help would be appreciated.
    Thanks,
    Brent

    Hi!
    Here is what helped in my case, very similar to your:
    In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

  • Non-cumulative Inventory cube to snapshot Inventory cube scenario

    We currently have a non-cumulative Inventory cube in production system and the stock values match to ECC data. Now we want to build a snapshot cube (to improve query performance) and the question is can we use the current cube (non-cumulative) as data source for the new snapshot cube or do we need to load it from ECC? Is there any special handling needed if it is loaded from current cube?
    Thanks!

    Hi,
      You can use the existing cube, but make sure that you have implemented the OSS Note 1426533 before doing this.
    Regards,
    Raghavendra.

  • Non-cumulative Values not showing in Inventory Management Queries

    Hi:
    Has anyone had a problem with the new version and Non-cumulative key figures not showing up in Bex for Inventory Managemet reports? Specifically, they showed and validated back to ECC for our Development and QA boxes but now in our Regression box they are all showing zeros. Our Cumulative values are all showing correctly still within the Regression box. For example, Total Receipts and Total Issues are correctly poplating values but Total Stock is not.
    I have checked and validate that the configuration in the Regression box matches or Dev and QA box.

    Found the problem.  It had to do with the compression variant in the delta process chain.  The compression was set to 'no marker update'.  Since we only started receiving measureable deltas in or regression box this is where the incorrect setting showed up.  Reinitalized and the deltas are working correctly now.

  • Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?

    A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the  standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
    (1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
    (2) The query runtime can be affected by the calculation of the non-cumulative.
    (3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
    (4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
    Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) ,  Issue Stock Quantity(0ISSTOTSTCK)
    , Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
    In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
    To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03  business content cube. Your honest suggestions and comment are greatly appreciated!

    Hello Marc,
    Thanks for the reply.
    I work for Dongxin, and would like to add couple of points to the original question...
    Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
    So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
    Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
    We would like to confirm if there would be any long term issues doing so.
    To optimize the performance we are planning to create aggregates at plant level.
    Couple of other points we took into consideration for using cumulative keyfigures are:
    1. Parallel processes possible if non-cumulative keyfigures are not used.
    2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
    So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
    We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
    Once again, thanks for your input on this issue.
    Thanks
    Dharma.

Maybe you are looking for