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.

Similar Messages

  • Aggregates for inventory cube

    hello
    Can I use aggreagates for inventory cube (non-cumulative)?
    thanks

    Hi,
    yes, you can suggest the aggregate for non cumulative (inventory cube) but with special care of time char.  You need to include all time char in aggregates.
    also see the help doc for details on how to use aggregates with non cumulative data model.
    Dev

  • Records is not coming in Delta for Inventory Cubes.

    Hi..All
    We are working on BW3.5 SP11 since 01.07.2005.
    We are facing a very serious problem in Inventory management data extraction from R/3 since 24.08.2005.
    Our active data sources of Inventory Mangement are as follow.
         2LIS_03_BF
         2LIS_03_BX
         2LIS_03_UM
    We were regularly getting records through delta as per given schedule after intialisation on 01.07.2005 to till 23.08.2005.
    On 24.08.2005 -- Delta schedule we had find out there are some records that were created in R/3 did not come in BW.
    On 24.08.2005 -- records loaded in PSA was 20550. The same is appering in RSA3(EXTRACTORS) also.
    The Last material document loaded was 4900154552 date 23.08.2005 time 16:56:05 of R/3, but there are many other material documents that were created on the same day but are missing in the extraction.
    On 25.08.2005 delta schedule records are getting 0 (Zero). Not a single record is getting in RSA3 (Extractor).
    on 26.08.2005 situation is still as it is. No record is coming.
    Where as our average records per day is approx. 20000 nos.
    The update mode for inventory is Unserialised V3 update, and the update program in R/3 is running perfectly fine as per schdule with no errors.
    We could not understand why suddenly stop the extraction of records FOR INVENTORY MANAGEMENT. Because rest all
    data sources like Purchasing,Sales and Distribution,Quality Mangement, and PP is working fine on same date.
    We checked the data in extractor checker with giving UPDATE MODE "F"-Transfer all requested data.
    Still it is showing 0 (Zero Records) for data sources 2LIS_03_BF,2LIS_03_UM.
    The situation is still as it is as of now.
    This is very crutial for our business. All inventory reports are showing data which is 3 days old.
    Please give your advice on this issue. And how to get the records in PSA from R/3.
    Regards,
    Navin

    Hi Ravindra,
    Thanks for giving input. The problem got solved.
    There was a problem with QRFC Table. Tcode LBWQ
    Status was wait.
    Thanks for giving feedback.
    Regards,
    Navin

  • Opening stock for inventory cube for april 2011

    Hi all,
    I have loaded the issues and reciepts (material movements from 2li_03_bx) and it is working fine.
    How to obtain the opening balance for 04.2011
    I can see there is on key figure 0valstkvalue which is non cumulative key figure which stores the last value.
    if use the key figure and use an offset based upon the calendar year month i will obtain the closing balance of 03.2011 which is the opening balance of 04.2011.
    but then last month 03.2011 only contains issues and receipts and it doesnt contain the opening balance
    i will given an example
    opening balance 04.2011 ( to be obtained)   
    issues : 120
    receipts : 130
    closing without opening is 10
    month of 03.2011
    issues : 150
    receipts : 200
    closing is 50 without opening
    if i use the ovalstk value key figure i am getting only 50 as closing balance which is wrong as per the user
    can you pls advise how to get the correct opening balance for 04.2011
    thanks

    Hi murali,
    My earlier month thats is 03.2011
    will contain only
    issues and reciepts isnt it . and it doesnt contain opening balance isnt it???
    so only issues - receipts will give the closing balance 
    for eg 03.2011
    issues = 100
    receipts = 120
    closing balance = 20 but the users data is 40 is the closing balance since opening balance is 20 for 03.2011
    Can you pls let me know how to handle it geting closing balance 20 plus adding the opening balance of 03.2011 too
    which gives 40 as closing balance for 03.2011
    thanks

  • Inventory Cube -

    Hi All,
    I have a need for a customized inventory cube, and am planning to use BX, BF and UM extractors into the same cube. I will enhance all the 3 extractors where they have all the characteristics needed for my cube and queries to match my requirements.
    I have the following questions.
    1. Some of my reports will require to report weekly and some monthly and some adhoc or when ever they want to see (like daily). So we will be updating the cube every night. Since it gets loaded every night if I left 'No marker Update' unchecked, but COMPRESS the cube after daily load how the data will be kept in the cube? and the impact on the queries.
    2. How to decide which key figure should be non-cumulative. I have beginning balance, receipts, issues adjustments and turn rate for each week. But I believe except beg balance rest of the key figures can be cumulative.
    If you have done inventory please advice.
    Thanks,
    Alex.

    Alex,
    If I define the amount as non-cumulative (what ever the KYF) and gets calculated during the query run time and based on the time requested in the query (cal week, calmonth etc) the value will be internally calculated and displayed in the query. is this a valid stament?
    --> Yes. That is the advantage of Non-Cumulative keyfigures.
    --> Inventory CUBE: 0IC_C03 contains calday, week, month. Based on user selection it displays balances for day level or week level or monthe level. No need to do any speicific calculation at updaterules or transformation level.
    --> Just do delta's daily and compress with marker update(means no check box).
    Check: [Inventory management: Usage of 2LIS_03_BX datasource |http://sapbwneelam.blogspot.com/2009/03/inventory-management-usage-of-2lis03bx.html]
    [How to Handle Inventory Management Scenarios in BW (NW2004) |http://sapbwneelam.blogspot.com/2008/11/how-to-handle-inventory-management.html]
    Srini

  • Performance query on 0IC_C03 inventory cube

    Hello,
    I am currently facing performance problems on this cube. The query is on material groups so the number of row returned are not to high.
    The cube is compressed. Could aggregates be a solution, or does this not work well on this cube because on the non-cumulative key figure?
    Does anyone have any hints on speeding this cube up? (the only tip I see in the collective note is to always compress)
    Best regards
    Jørgen

    Hi Ruud,
    Once compression with Marker update, latest balances will be created automatically for inventory cube: 0IC_C03.
    Historic moments only required to show stock status for any historic date(eg: 02-01-2008).
    If user not interested to check 3 years old status of stock, old data can be deleted selectively from cube using selective deletion.
    Go through doc: [How Tou2026 Handle Inventory Management Scenarios in BW|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328?overridelayout=true]
    Srini

  • Logical split of inventory cube

    Hi
    I am using the inventory cube 0IC_C03 with non cumulative key figures.
    this cube has grown to over 100 million records after compression.
    I am planning to do a logical split of the cube by time(calendar/month)
    ie 3 cubes - one with last 2 years data, the next for 2-5 years and data and the third rest
    I am currently using a MP on top of 0IC_C03.
    I am not sure how the non cumulative KF will work for inventory balances across 2 or 3 cubes
    Any one done this
    Lawrence

    Hi Lawrence,
    it's long ago, but did you solve your problem. We plan to set up inventory reporting and would like to do a logical split by time as well
    Regards
    Henning

  • How the system know which are Inventory cubes?while compres in ProcessChain

    Hi,Experts
    When I create a Cube compress in ProcessChain ,under the page there is a checkbox called No Maker for Inventory Cube,and I also know the Non-cumulative key figure can not be compress,
    My question is how the system know which are Inventory cubes? and many cube create from ourself.

    Hi,
    I think,
    - in the sap tables there are no information.
    - the program reads the infocube definition and check: is there a non-***. value?
    Sven

  • Selective deletion for Inventory Load

    Hi Guru's
    I have done loading for Inventory cube 0IC_C03 using the 2LIS_03_BF with Delta load and made mistake in last delta load Compression(No Marker Update).. till July 2011 the Data is fine for our report for calculating the TOTAL QUNATITY STOCK..  so we planned to done the selective deletion for August 2011 to till date.. but we cant find the Time Characteristics in selection to done Selective deletion. Please share your valuable ideas...
    Thanks,
    Satish.M.R

    Hi,
    You can delete all the requests from the cube which have been updated from 1st of August onwards.
    Just go to the MANAGE screen of the cube and select all the requests which are loaded from 1st of August onwards and delete all of them.
    Navesh
    Edited by: navsamol on Oct 6, 2011 7:00 AM

  • Inventory Cube Compression - Non-Cumulative

    Dear All
    I have loaded setup tables in R/3
    BX as on date             TAC MCNB1
    BF i.e. Historical         TAC  OLI1BW
    UM                            TAC OLIZBW
    I have loaded the Inventory Cube form all the three Data Sources
    2LIS_03_BX : Initial Status
    2LIS_03_BF : Initialization
    2LIS_03_UM : Initialization
    The queries are <b>fine without compression</b>
    I have compressed the cube
    2LIS_03_BX : with marker update
    2LIS_03_BF : without marker update
    2LIS_03_UM : without marker update
    After compression the data for Stock issues in 24,36,48,60 months is giving vague values i.e.. IT IS ADDING UP ALL THE PREVIOUS VALUES TO SHOW FINAL VALUE
    WHAT ARE THE SETTINGS TO BE MADE FOR COMPRESSION OF NON-CUMULATIVE CUBES ?
    AM I MISSING ANYTHING (STEPS) ?
    Thanks & Regards
    Daniel

    Dear Anil
    I have followed the same procedure
    i.e.
    BX-init: Compression with marker update
    BF-init: Compression without marker update
    UM-init: Compression without marker update
    BF-delta loads: Compression with marker update
    UM-delta loads: Compression with marker update
    But surprisingly the values are not reflecting correctly
    Thanks & Regards
    Daniel

  • 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 Inventory Cube Remodel

    Hello Gurus,
    I've existing inventory cube with non-cumulative key figures with large amount of data. We are using standard non cumulative key figures 0TOTALSTCK, 0ISSTOTSTCK & 0RECTOTSTCK.
    Now I've a new requirement to report issues (0ISSTOTSTCK) & receipts (0RECTOTSTCK) based only on LB. Right now they both are in base UOM. Converting them in LB in query (on the fly) is not an option because of volume / performance of report.
    I'm planning to do this in backend by adding two more key figures for issues & receipts where i'll convert standard ones in LB. I'm not going to touch any of existing non cumulative key figures. But the overall structure (F table) is going to change.
    I'm concerned whether this will work? Any risks? Marker updates?
    Thanks.
    Abhijeet

    Please have a look
    http://sap.seo-gym.com/inventory.pdf

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

  • Noncumulative Cube Copy for Inventory IC where compression is not possible

    Dear All
    We have got Month (0RT_C37) and Week (0RT_C36) Inventory Infocubes. Compression has never been done on any of this cube. The data is fine and result is coming correct but output is very slow. We have done the initialization on this cube on mid of 2008. We have to copy the entire cube to a ZCube and do the compression performed on that Zcube. Our system is BW7.3 SP Level11 and we are going to upgrade to 7.4 .  We tried to move the marker values(RECORDTP=1) to the Zcube with DTP setting (Initial Non-cumulative for Non-cumulative values) which is not happening. But other values with movements we are able to move. The only OSS note found to address this issue is1426533 which is not relevant for us. Is there any workaround for the situation where no compression is ever happened on the cube and the compression is impossible due to some issues, hence we want to copy the entire data to another Zcube and perform the compression there.
    Regards
    Reshoi

    Hi Reshoi,
    There is no DSO for 2LIS_03_BF in Business Content as far as I know. It is possible to create a DSO yourself. Please review SAP Note 581778 - ODS capability of extractors from inventory management and the related SAP Notes carefully if you want to go into this direction.
    Please have a look at the document Re-initialization of the Material Stocks/Movements cube (0IC_C03) with 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM in BW 7.x for contains a step-by-step instruction and lots of valuable information.
    Re. the downtime, there are ways to minimize it. Please see SAP Note 753654 - How can downtime be reduced for setup table update. You can dramatically reduce the downtime to distinguish between closed and open periods. The closed periods can be updated retrospectively.
    Please refer to document How to Handle Inventory Management Scenarios in BW (NW2004) for an evaluation of different Inventory Management scenarios.
    I also would like to recommend you to review SAP Note 419490 - Non-cumulatives: poor query performance for 5 performance tips.
    Last but not least, you might want to have a look at the following SAP Notes:
    SAP Note 436393 - Performance improvement for filling the setup tables;
    SAP Note 602260 - Procedure for reconstructing data for BW.
    Best regards,
    Sander

Maybe you are looking for