Cumulative key figure and non cumulative key figure

Hi BW Expertz
Could any one give me the clarification about cumulative and non cumulative key figures .Why we go for cumulative key figure and non cumulative key figure.If any docs could u just mail to the following [email protected]
Thanx In advance
Best regards
sankar prasad

Cumulative values are those key figures (KF) that are cumulated using all characteristics, thus also using time.
Ex: Sales revenue, Quantity....
Non-cumulative values are those key figures that are measured in relation to a period in time; they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so called exception aggregation.
Ex: Number of employees, Inventory, Stock prices, Account balance,.....
AGGREGATION TAB
Non cumulatives are evaluated by non-cummulative values. Non-cummulative values are special key figures that are different from other key figures (cummulative values) in data transfers and saving as well as in aggregational behaviour. These are measured in relation to a period in time; that is to say, they cannot be meaningfully cumulated over time. Non-cumulative value are summaraized over-time using exception aggregation.
Non-cumulative values such as 'number of employess' are cumulated using characteristics such as 'cost center'. It does not make any sense, however, to cumulate the number of employees using different periods. The result at the end of any particular period would be the sum total of number of employees for each posting during the period. This would of course be wrong.
Instead, the aggregation of the KF can be defined as exception aggregation wherein an additional references characteristics is utilized to tell BW which value to use during the period, in this case, 0CALMONTH is used, in the above example, to indicate that only the last value of 0HEADCOUNT, updated by costcenter, is to be taken for any calender year and month.
Cummulative vs Non-Cumulatives
The purpose of non-cumulatives is to optimize the data transfer in BW, the data retention and the database access. The data transfer from OLTP to BW is minimized and only the meaningful data is saved and processed.
It is recommended that you use non-cumulative values for areas that dont change frequently such as warehouse stock or number of employees.
Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it for storing the non-cumulative or for inflows or outflows.
Non-cumulative values are stored with special KF that differ in terms of data transfers and aggregational behaviour.
Features of NON-Cumulative Values Transfering and Saving Data:
- NC values are mapped uisng one KF for NC changes or two KF for inflows and outflows.
-NC are transferred in an initialization run and the change runs that follow (initialization can also be omitted here)
- A non-cumulative value always has a time-related exception aggegation.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
with Example
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
****Assign Points If Useful*********

Similar Messages

  • What is cumulative key figure and non cumulative key figure?

    Hi Experts,
    can anyone clarify me about KEY FIGURES in detail with an example for each topic like
    1.Aggregation Tab in Key Figure InfoObject
    2.Cummulative
    3.Non Cummulative/Cummulative Values
    4.Non Cummulative( Inflow & Outflow )
    I think it would be better understandable with if explained with example
    Thanks,
    Venu Gopal.K

    HI ,
    Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
    Example: sales revenue, weight, etc.
    Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.
    Example: stock quantities/-values, number of employees, account balances, etc.
    refer the below document for a detailed study
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366?quicklink=index&overridelayout=true
    Regards,
    Sathya

  • Cumulated Keyfigure and Non-Cumulated Keyfigure

    Hi Guy`s,
    Can we load Cumulative Key Figure and Non-Cumulative Key Figures in the Inventory InfoCube? Please explain with Scenario Urgent client requirement.
    thanks in advance,
    Venkat.

    Hi,
    Check the following link.
    How To…Handle Inventory Management Scenarios in BW
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20handle%20inventory%20management%20scenarios.pdf
    Cheers
    Pagudala

  • Cumulative and non-cumulative for key figure

    Hi,
    In the aggregation tab, we have the aggregate type SUM, Max or Min.
    we also have the comulative/non-cumulative values.
    what's the difference between comulative and non-cumulative values? it would be good to have some example for illustration. and does comulative and non-cumulative have any relation with aggregate type?
    Many Thanks
    Jonathan

    Hi,
    what's the difference between comulative and non-cumulative values?
    Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
    Example: sales revenue, weight, etc.
    Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.Example:stock quantities/-values, number of employees, account balances, etc.
    Does comulative and non-cumulative have any relation with aggregate type?
    Different types of non-cumulative keyfigures.....are....
    1.Non-cumulativekey figure = cumulative keyfigure with excep.aggregation
    2.Non-cumulativekey figure withassociated singledelta (cumulative)
    3.Non-cumulativekey figure withassociated in-andoutflow(cumulative)
    check these links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92c0aa90-0201-0010-17b1-bf5b11c71257
    hope it helps...
    Regards
    chandra sekhar
    Edited by: chandra  sekhar t on Nov 28, 2008 2:18 PM

  • Difference between cumulative and non-cumulative key figures

    Hi,
    What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

    Hi.............
    Basically the key figures are of two types cumulative and non cumulative.
    Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
    but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
    Now
    1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
    2)NCum. value with NCUM value change:
    In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
    Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
    In this case you will this option and use the key figure here in the space provided.
    3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
    you use one key figure for the inflow and one key figure for the outflow.
    The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
    net value of stocks( inflow- outflow).
    Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
    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. here the aggregation of key figure is based on the another info object
    There are two different ways to define non-cumulative key figures:
    • Non-cumulative key figure with non-cumulative changes:
    Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
    • Non-cumulative key figure with inflows and outflows
    There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
    Features of non-cummulative key figures
    A non-aggregating key Figure.
    Records are not summarized for Reporting
    Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
    Examples: Head Count, Account balance, Material stock
    consider simple senario
    Date Net Stock Quantity Sales Revenue
    01.02.2005 40 1000
    02.02.2005 50 2000
    03.02.2005 25 3000
    this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
    if stock quantity taken as a cummulative key figure
    Date NET STOCK QUANTITY SALES REVENUE
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 100 6000
    in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
    if stock quantity taken as non-cummulative key figure
    Date Net Stock Quantity (LAST) Sales Revenue
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 20 6000
    Hope this helps you..............
    Regards,
    Debjani................
    Edited by: Debjani  Mukherjee on Sep 15, 2008 7:22 AM

  • Adding Cumulative and Non Cumulative Key Figure

    Hi All,
    Can we add Cumulative and Non Cumulative KF in a query and display the resuly.
    regards,
    Jeet

    Yes, you can.
    Cumulative KF at query level are same as non cumulative.
    Hope it helps.
    regards

  • Cumulative and Non-cumulative KFs

    Guys,
             so I am confused about cumulative/Non-cumulative keyfigures.  I read what it says about them on help.sap.com
    Flow/non-cumulative value
    You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
    Non-cumulative with non-cumulative change
    The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
    Non-Cumulative with inflow and outflow
    The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
    For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, and quantity) as the non-cumulative value."
    and also checked a few threads on sdn but still a little confused about their purpose.
    Can someone tell me when do we use which one?
    Thanks,
    RG.

    Hi Ram,
    Cummulative & Non Cummulative Key Figures :
    Basically the key figures are of two types cumulative and non cumulative.
    Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
    but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
    Now
    1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
    2)NCum. value with NCUM value change:
    In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
    Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
    In this case you will this option and use the key figure here in the space provided.
    3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
    you use one key figure for the inflow and one key figure for the outflow.
    The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
    net value of stocks( inflow- outflow).
    Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
    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. here the aggregation of key figure is based on the another info object
    There are two different ways to define non-cumulative key figures:
    u2022 Non-cumulative key figure with non-cumulative changes:
    Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
    u2022 Non-cumulative key figure with inflows and outflows
    There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
    Features of non-cummulative key figures
    A non-aggregating key Figure.
    Records are not summarized for Reporting
    Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
    Examples: Head Count, Account balance, Material stock
    consider simple senario
    Date Net Stock Quantity Sales Revenue
    01.02.2005 40 1000
    02.02.2005 50 2000
    03.02.2005 25 3000
    this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
    if stock quantity taken as a cummulative key figure
    Date NET STOCK QUANTITY SALES REVENUE
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 100 6000
    in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
    if stock quantity taken as non-cummulative key figure
    Date Net Stock Quantity (LAST) Sales Revenue
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 20 6000
    Hope it helps you.
    Thanks & Regards,
    SD

  • Cumulative and Non Cumulative Keyfigures

    Hi,
    What are Cumulative and Non Cumulative Keyfigures..? and
    what is   the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
    Can you please tell  eloborately?
    Regards
    Naresh.

    Hi,
    Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
    Non-cumulative values are those key figures that are measured in relation to a period in time;  Non-cumulative values are summarized over time using so-called exception aggregation.
    In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
    After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
    In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated  for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
    Regards,

  • Cumulative and Non Cumulative KF

    Hi all,
               What are Cumulative and Non Cumulative KFs. How do we create it and where do we use them?
    Thanks in advance,
    Sekhar

    Hai <b>Sekhar</b>...
    Some of the Information Given Below......
    <b>Key figures:</b>  
    1.     Cumulative Vaules
    2.     Non – Cumulative Values
    <b>Cumulative Values</b>:
              Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period – specific Values).
    Example:
              Revenue
    <b>Non – Cumulative Values:</b>
              Non – Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
    <b>Cumulative Keyfigures With Exception Aggregation</b>:
              It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
    <b>Non – Cumulative keyfigure with Associated Single Delta:</b> 
                           If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
    KF1 (initial) STOCK (non-***.) = 100
    KF2 flow = -30
    KF2 flow = 70
    KF1 (final) STOCK (non-***.) = 140
    <b>Non-cumulative key figure with associated in and outflow:</b>
                             This is the case of 2LIS_03_BF KF stocks fields.
    Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
    You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
    KF1 (initial) STOCK (non-***.) = 100
    KF2 (out))flow = 30
    KF3 (in)flow = 70
    KF1 (final) STOCK (non-***.) = 140
    <b>Website Addresses For Non – Cumulative KeyFigures:</b>
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html 
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
    Re: Non-Cumulative keyfigure example   
    Re: Types of non-cumulative keyfigures 
    /community [original link is broken]
    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    /community [original link is broken]?forumID=131&threadID=29557&messageID=273049
    /community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
    <i><b>Assign Points If it Helps......</b></i>
    <u><b>BalajeeKannan</b></u>

  • Cumulative and non cumulative

    Hi All,
    What is the exact deff between cumulative and non cumulative?
    give me a simple sceneriao it would be very helpful...?
    thanks
    kiran

    HI ,
    Cumulative : Normal Key figures are cumulative
    Example : Say Key figure X  has on 15th you have Qty 20 & oon 16th you have Qty 10
    So when you run the report you can see the value for X Kf as Qty 30.
    So,here the values are cumulated
    Non -Cumulative :  Derivative of the two cumulative key figures showing in the New key figure is Non -Cumulative
    Example: Non - Cumulative KF is Qty total stock
    Qty total stock is the derivative of Qty Reciept Stock & Qty Issued Stock
    Date        Qty   Receipt stock                        Qty  Issue Stock                            Qty  Total Stock 
    15th   |            20                    |                                   10          |               =                    10
    16th         |     10 + 15 =25             |                            02              |          =                     23
    Hope you can understand
    Regards
    Hari

  • What is the difference between cumulative and non cumulative keyfigures?

    Hi Friends
    What is the difference between cumulative and non cumulative keyfigures, when we r using  the cumulative and non cumulative
    Regards
    Ravindra

    Hi Ravindra,
    Have a look at the help:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
    Go through these.
    Re: Types of non-cumulative keyfigures
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
    See the following threads
    non-cumulatives KF in reporting
    Re: use of non cumulative keyfigure
    Re: When do we use Non-Cumulative values?
    Key figures:
    1. Cumulative Vaules
    2. Non – Cumulative Values
    Cumulative Values:
    Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period – specific Values).
    Example:
    Revenue
    Non – Cumulative Values:
    Non – Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
    Cumulative Keyfigures With Exception Aggregation:
    It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
    Non – Cumulative keyfigure with Associated Single Delta:
    If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
    KF1 (initial) STOCK (non-***.) = 100
    KF2 flow = -30
    KF2 flow = 70
    KF1 (final) STOCK (non-***.) = 140
    Non-cumulative key figure with associated in and outflow:
    This is the case of 2LIS_03_BF KF stocks fields.
    Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
    You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
    KF1 (initial) STOCK (non-***.) = 100
    KF2 (out))flow = 30
    KF3 (in)flow = 70
    KF1 (final) STOCK (non-***.) = 140
    Website Addresses For Non – Cumulative KeyFigures:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
    Re: Non-Cumulative keyfigure example
    Re: Types of non-cumulative keyfigures
    /community [original link is broken]
    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    /community [original link is broken]?forumID=131&threadID=29557&messageID=273049
    /community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
    Check this very useful docu.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
    ****Assign Points If Helpful****
    Regards,
    Ravikanth

  • Key fields and non-key field of condition table

    Hello Gurus,
          what is key fields and non-key field of condition table?
    thanks very much!

    Key field
    Each condition table contains keys that can be used for creating dependent condition records.
    for example let take condition type PR00.
    PR00 uses access sequence PR02 .
    Access sequence PR02 has following tables associated with it namely 304, 305 & 306
    When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
    In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
    Non key field
    For example take condition table 144 - sales deal basic data.
    Table 144 is associated with access sequence PBUD.
    If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
    So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
    Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

  • Difference between Snapshot scenario and non cumulative scenario

    Hi,
    Can any one please tell me the difference between snapshot scenario and non cumulative scenario in
    inventory management.
    Also please give example. I read the pdf " how to handle inventroy management scenarios", but can any one please give some easy to understand examples.
    full points guaranteed-

    hi,
    In Non-cummulative method your stock movements are stored in the cube (inflow and outflow of NC KF) and the Total stock is calculated during query execution. Hence if there are lot of movements in the stock for the period you want to report on, query will take long time to execute.
    In case of Snap shot scenario Stock movements are not loaded to cube. you use ODS to load the status of the stock and then from ODS you can load to Cube once in a month. So only summarized data will be availabe in Cube. Reporting will be fast.
    Check the below threads
    Inventory Management - SnapShot model
    snapshot scenario?
    SNAP SHOT Scenario in IM

  • Integrated Planning and Non-cumulative key figure

    Hi
    I´m creating an Integrated Planning application and a problem has occurred. The users want to plan on inflow and outflow and at the same time have a row with the total sum in the same layout (they are planning on 0CALMONTH and 0ORGUNIT) This can e.g. be solved through use Web Application Designer with one planning query and one traditional query.
    Any way. I have created a non-cumulative key figure with an inflow- and an outflow key figure. The problem is that the non-cumulative key figure starts working first when I change the planning mode from plan status to load status. I could use function modules, to change the status, behind the save button but there are several users who are planning at the same cube at the same time and I don´t want to lock the others from planning.
    How to solve this?
    - Is it possible to restrict the switching, from plan to load, by setting some kind of filter at the users org.unit? (0ORGUNIT is an authorization object)
    - Is it possible to create a process chain and then load the data to another cube for reporting at just this key figure? And also here have a filter at the org.unit
    I will gladly get all kind of idea and input to solve this problem. Maybe there is some other way to go than using non-cumulative key figureu2026

    Thanks for your answers
    I have tried different scenarios and I will use a u201Dsave-buttonu201D. In the save-button I use the commands SAVE_DATA and EXECUTE_PROCESS_CHAIN. The command u201CEXECUTE_PROCESS_CHAIN starts a process chain that switches from plan mode to load mode and then back to plan mode again.
    One new problem has arisen. The non-cumulative key figure is updating if an existing value (inflow- or outflow) is changed. But if an input is made to an empty cell, without value, nothing happen when I press on the start-button. BUT if I refresh the browser the non-cumulative value is updated!!!
    Is there any command in WAD that refresh the whole page? If so I can include it in my start-button.
    If not, any sugestion on how to solve the problem?
    Best regards
    Mikael

  • Multicube with Cumulative and Non Cumulative Key Figures

    Is there any problems if I build a Multicube which consists of InfoProviders which have non-cumulative key figures (Inventory cube) and those which do not
    In the query I will be summing the key figure for example Stock Quantity across the InfoProviders? Thanks

    Hi,
    There is no problem if you do that only thing is when you assign key figures in the multiprovidesr you have to be careful in deciding the infoprovider from which the key figure comes.
    Hope this helps
    Assign points if useful
    Regards,
    venkat

Maybe you are looking for