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

Similar Messages

  • 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 remote cube in Multiprovider

    Hi all,
    I have a situation. We created a multiprovider containing 1 infocube and 1 remote cube. The remote cube contains non cumulative key figure. When we create a query on the multiprovider and check the query, the system gives us a system error message saying "System error in program CL_RSR and form GET_CHANMID-01-". I have tried to find an OSS note, but could find any related notes.
    The problem doesn't occur if the query built on the remote cube or on the multiprovider but without the remote cube. So I think the problem lies on using non cumulative remote cube in a multiprovider.
    Has anyone encounter such a situation? Appreciate any opinion or comments.
    Thank you.
    Regards,
    Anzar

    Anyone?
    I really need your advice on this issue.
    Best regards,
    David

  • Non-Cumulative Info-Cube (0BUS_AREA)

    Hello,
    I have a non-cumulative Info-Cube that as only marked 0PLANT and 0CALDAY in the u201CMaintain Non-Cumulative Valuesu201D.
    When we execute the query, the stocks for the 0PLANT work fine. But, when we do the drill-down by 0BUS_AREA it doesnu2019t work. Is it possible for a cube like this to give this information?
    Can anyone help me with a possible explanation?
    Thank you.
    Joana

    Hello,
    I have a non-cumulative Info-Cube that as only marked 0PLANT and 0CALDAY in the u201CMaintain Non-Cumulative Valuesu201D.
    When we execute the query, the stocks for the 0PLANT work fine. But, when we do the drill-down by 0BUS_AREA it doesnu2019t work. Is it possible for a cube like this to give this information?
    Can anyone help me with a possible explanation?
    Thank you.
    Joana

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

  • 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

  • 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

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

  • 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

  • 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

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

  • How to create a non-cumulative key figure & How to make a info cube as so

    Hi Experts,
    How to create a non-cumulative key figure & How to make an info cube as non-cumulative cube?
    Can any one kindly provide me the steps we need to performe?
    Thanks in Advance,
    Raj

    Hi Azael,
        In the How to Papers, you will find a Guide on how to take a Sanpshot view of the Stocks(How To Handle Inventory Management Scenarios in BW). Basically if you implement the Guide, you will have another cube called ICSNAP1, which will contain stock quantities /values at the end of each month. You will therefore have to take stock at the end of the last month from that cube and add up the relevant receipts and issues to arrive at the current Stock or Stock as on a particular date.
    Hope this helps!
    Regards
    Sriram

  • Inventory - Non Cumulative

    Hi
    I have inventory data coming from legacy syste.
    I have the following fields.
    Date Mtrl Qty.
    As this is coming daily and i would like to keep the history in the ODS as well as cube. How can i make Qty as non cumulative with out Inflow / Out flow.
    I should be looking at the reports based on wk, month and qtr.

    Thejo,
    A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
    If your InfoCube contains a non-cumulative key figure, then a time-based reference characteristic for the exception aggregation of the non-cumulative key figure must exist.
    There can be several time characteristics per InfoCube, but only one time reference characteristic. This means, that the time-based reference characteristic is the same for all the non-cumulative key figures of an InfoCube.
    This link is very helpful and informative:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
    Let me know if this helps.
    Pete

  • How to check in Cube for Non cumulative calculation?

    Hi All/surendra (Inventory Specialist)
      I am now supporting the Inventory cube. I never worked in inventory. I have read all the documents like
    a. How to Inventory
    b. Surendra's Inventory with 3parts
    c. Non cumulative..
    But none of the above docs gave me solution how to go ahead to find or compare with R3 for the first time consultants who is handling Inventory..
    Can you pls help me resolve the following issues?
    1. May I know how actually the NON CUMULATIVE calculation is done for filelds 0VALSTCKVAL and 0VALSTCKQTY  and also other KF's like ISSUE and RECEIPT qty, blocked qty, scrap, stck transit etc as I dont see any mapping done in transformation, if it is not done for Inventory, how it is fetched.??
    2.Also I wanted to know what are the fields used cumulated for the above fields as I dont see any transformation mapping done for Key Figure and understood all Inventory docs that the KF are not visible as they are NON CUMULATIVE KF's.
    3. How to compare the Inventory stock with R3 Material Stocks as when I compare with transaction MC.9, I see the values are totally different?? how and which transactions or tables supposed to be compared? Also we are not 2lis_03_BX in our Inventory. so I am not sure how they loaded the Inventory. Looks I need to redesign, can you tell steps to check and apply if I have initialize to make sure that my data will come correctly??
    Thanks a lot for all you help and efforts in advance.

    The source field for quantities is the field CPQUABU, and for values it is the field CPPVLC.
    Explanation for the routine :-  
    IF ( COMM_STRUCTURE-processkey EQ '000' "Other Receipts
    OR COMM_STRUCTURE-processkey EQ '001' "Goods Receipt / Vendor
    OR COMM_STRUCTURE-processkey EQ '004' "Material Transfer / Receipt
    OR COMM_STRUCTURE-processkey EQ '005' "Stock Adjustment InvD +
    OR COMM_STRUCTURE-processkey EQ '006' "Stock Adjustment Other +
    OR COMM_STRUCTURE-processkey EQ '010' ) "Receipt from Stock Transfer
    AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    only stock in transit is considered
    AND COMM_STRUCTURE-stocktype CA 'FH'
    only movements which are relevant for stock control
    AND COMM_STRUCTURE-stockrelev EQ '1'
    AND COMM_STRUCTURE-cpquabu 0. *
    The above part is used for the KF : 0ISSTRANSST - Issue Quantity: Stock in Transit
    IF ( COMM_STRUCTURE-processkey EQ '100' "Other Issues
    OR COMM_STRUCTURE-processkey EQ '101' "Returns / Vendor
    OR COMM_STRUCTURE-processkey EQ '104' "Material Transfer
    OR COMM_STRUCTURE-processkey EQ '105' "Stock Adjustment InvD
    OR COMM_STRUCTURE-processkey EQ '106' "Stock Adjustment Other
    OR COMM_STRUCTURE-processkey EQ '110' ) "Issues from Stock Transfers
    AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    only movements which are relevant for stock control
    AND COMM_STRUCTURE-stockrelev EQ '1'
    AND COMM_STRUCTURE-cppvlc 0
    see OSS note 630254
    AND ( COMM_STRUCTURE-stockcat IS INITIAL OR
    ( COMM_STRUCTURE-stockcat CA 'EQ' AND
    COMM_STRUCTURE-indspecstk CA 'AM' ) ).
    result value of the routine
    RESULT = COMM_STRUCTURE-cppvlc. *
    This part is used for : 0ISSTOTSTCK - Issue Quantity Total Stock
    Hope this hepls,
    Reg,
    Rahul

  • Validity Table in Non cumulative cube

    Hi Friends,
    What is the use of validity table in Non cumulative cube?
    I have already studied the document 'How to Inventory
    Please can any one explain me with example.
    Thanks & Regards,
    Ramnaresh.P.

    Hi,
    Validity table is created for non-cumulative key values.
    Non cumulative key figures are one which are not possible to cumulate such as head count, inventory amount, these are always in relation to a point in time.
    Regards,
    Shiva.

Maybe you are looking for