Key figure non-cumulative/ Inflow / Outflow

On the tab page Aggregation of a Key-figure, you are able to choose non-Cumulative values with in- and out-flow. What is the exact function of the in- and out-flow fields?

Hello,
please have a look into the documentation:
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
The inflow / outflow keyfigures is the delta of your non cumulative key figure.
kind reg.
michael

Similar Messages

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

Key Fig Non Cumulative

I have 0GIDATE as KF and want to know which option of Non Cumulative to choose between non *** value with non *** value change or noncum value with in-and out flow? I did go through the forum but could not get an appropriate one for a data kf. Basically the 0GIDATE is used to do calculations between GI and actual GI dates.

hi latha,
i m also using this object as cumulative value.
bhaskar

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

Cumulative key figures

what are non cumulative key figures?

Hi,
Cumulative Key Figure:
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 Comulative key figure:
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/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
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html[/url]
Thanks & Regards
santo

Exception aggregation on Non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Maybe a solution with virtual key figures is an option?
Please help me out!
Best regards, Hans de Klein

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

Count the number of business partners on a non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Would anything with virtual key figures be a solution? Please help me out!
Best regards, Hans de Klein

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

Problem with Non-cumulative key figure.

Hi all,
I am facing the problem with the Non-cumulative Key Figure (Quantity). I have created and loaded data to the non-cumulative InfoCube. <b>This cube is defined by me to test the non-cumulative key figure.</b>
<b>In BEx query the non-cumulative key figure and cumulative key figure (Value change) both display same values, i.e. non-cumulative key figure contains the same values which we have loaded for cumulative value change. Non-cumulative key figure is not calculated based on associated cumulative key figure.</b>
I have done the following while defining the non-cumulative InfoCube:
1. Created a non-cumulative key figure which is associated with a cumulative key figure (value change).
2. Loaded data to non-cumulative InfoCube from flat file.
3. Compressed data in non-cumulative InfoCube after the load.
Note:
1. Validity area is determined by the system based on the minimum and maximum date in data.
2. Validity determining characteristic, 0CALDAY is the default characteristic selected by the system.
Is there any other settings to be done?
Please help me in resolving this issue.
Thanks and regards
Pruthvi R

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

Suppress cumulated key figures for actual data

Hello all,
I have build a query which display monthly actual and forecast order income for an ficsal year. The fiscal year starts in July and end in June
The forecast data were loaded in BW over an flat file for the whole fiscal year. The actual data gets loaded daily from R/3.
When I run the query and select the whole fiscal year and displayed the key figures as "cumulated" in the query properties, I can see all the cumulated forecast values (for 12 months) but the actual order income data just cumulated till the current month (December). For the next months (until June) always the last value from December remains.
I want to provide a line diagram in a Web Application, which shows the forecast and the actual data. Right now the line for the actual data stops to raise at the current period and gets continued as a horizontal line till the end of the fiscal year.
Therefore my question is: Is it possible to suppress values for actual data for the next periods in order to end the actual order income data line in the diagram at the current month.
Any ideas would be great.
Best regards from Munich,
Stefan

The one thing I can think of would require a very messy way of doing things, but it would probably work.
If you created a set of calculated/restricted key figures for each period of the fiscal year (non-cumulated), you could also have a set that cumulates up to each period. Then, in the calculation, you can set the stipulation that if period x is not > 0, then don't sum that particular colum. Then, supress columns that don't have any data in the structure properties. I think you'd end up with 24 columns, 12 hidden, and some that won't display depending on which values exist.

Cumulative Key Figure (Running Total) - how to use in formula?

We have a scenario where I need to use the cumulative value of a Key Figure in a subsequent formula. The Cumulated property setting at the Key Figure level in the query is a Displayed Data Only setting, however, so the cumulated values are not available for use in a formula The individual values are used by BW as opposed to the cumulative values that are displayed in the column.
Ive tried using the Cumulated property at the characteristic level. I am then able to use the displayed cumulative values in a formula. However, I also need to display the individual (not cumulated) Key Figure values in a column. These individual values are no longer available for display if the Cumulated property is set at the Characteristic level.
I thought that the Define Cells functionality could possible be used, but there is only one Structure in the query, so the Define Cells functionality is unavailable. I could not think of a way to use a second structure in the rows, as the rows need to be dynamic (two characteristics, populated based on user input variables).
It may be possible to accomplish this requirement by adding a column using VBA in the SAPBEXonRefresh sub, but use of VBA is not a preferred option, as the query may be run in either the Excel Analyzer or the Web Analyzer.
The infoprovider does not contain a Key Figure field for Cumulative Volumes.
The scenario details:
Rows (Characteristics):
A: Plant (values based on user input variable)
B: Calendar day (values based on user input date variables for start & end dates)
So there is one row for each day within each plant.
Columns (Key Figures):
A: Cumulative Volume at Start of Period (uses user input date variable for start date, and Constant Value property. Hidden column.)
B: Daily Volume (for each day in the period defined by the user input variables for start and end dates)
C: Cumulative Volume at End of Each Day (formula, meant to be equal to the sum of the Cumulative Volume at start of period plus the total so far of the Daily volumes. In other words, equal to the sum of Column A plus the running total of Column B).
Does anyone out there have any more ideas on how to accomplish the required Cumulative Volume computation?

Thanks for your reply Jurgen.
I've created a Global Calculated Key Figure (CKF), and have looked at and tried a number of settings in the Properties of this new CKF.
I have not yet been able to make this work for me.
The "Cumulated" property for a Global CKF is also a display-only property. The displayed running total is not used in any formula containing this CKF, only the individual values are used in the formula.
If I select the 'Enhance' option, where exception aggregation can be done as I think you suggested, I do not see a 'cumulated' option. If I select the 'Summation' option for 'Exception Aggregation', then the 'Reference Characteristic' pull-down is not available.
Is there a different 'Exception Aggregation' option I should be using for running totals at the calendar day level?
Or am I unclear on the concept of your suggestion?
Perhaps you're on a later version of BW that has more Exception Aggregation options? (We're on BW3.5)

Cal & Non-cal Key figure.

Hi Guru's,
Can anyone tell me the what is calculated key figure & non calculated key figure?
what is the difference between them?
Also give me practical example how to create?
Regards,
Bhanu.

Hi,
Calcualted key figure: You can carry out arithmetic, boolean, percent functions on key figures using this.
restricted key figure: You can restrict the values of key figures by restricting it with values of characteristics involved in that query
http://help.sap.com/saphelp_nw04/helpdata/en/f5/ba7be10cee11d289200000e8322f70/frameset.htm
Regards,
Supriya

Non- Cumulative KeyFigures

Hello Forum.
We have a non cumulative key figures with and Inflow keyfigure and an outflow with the aggregartion propery to SUM.
Can you please suggest how to verify the output of the non cumulative keyfigure ?
Is there any way to check the values of this non cumulative keyfigure ?
Thank you in advance .
Regards

Hello,
Possible verification methods are described below.
We recommend verification at plant/material number level (MatNo).
I. Verification of data from the 2LIS_03_BX or 2LIS_40_S278 DataSource
- Execute a corresponding query in BW.
- Use transaction code (TAC) LISTCUBE in BW to select the corresponding MatNo or plant (see Note 629451) and compare the data.
-> If problems occur at this point, there may be a BW technology problem (OLAP processor).
- Now compare the data with R/3 TAC MC.9 and MB5B.
-> If problems occur here, you should also check the PSA contents:
   -> TAC SE16
   -> Table RSTSODS
   -> Selection in the ODSNAME field: "2LIS_03_BX*"
    -> The ODSNAME_TECH field specifies the name of the database table in the PSA - if there are several hits, you can find the corresponding suffix of the source system in the PSA tree.
   -> TAC SE16
   -> PSA database table
   -> Select the data of the corresponding request (you can find this in the InfoCube administration view)
Differences between PSA and InfoCube contents indicate problems in the update (you can use the debugging for the update to check this in more detail).
Differences between PSA and TAC MC.9/MB5B suggest incorrect data extraction. Duplicate or missing stocks indicate technical problems during the data transfer.
I. Verification of data from the 2LIS_03_BF/UM DataSource
- Execute a corresponding query in BW.
- Select the corresponding MatNo or plant in BW using TAC LISTCUBE (see Note 629451) and compare the data.
-> If problems occur at this point, this suggests a BW technology problem (OLAP processor).
- Now compare the data with the R/3 TAC MC.9
- If there is a difference between the stocks, compare the movements, preferably take of note of the month in question and whether it is a receipt or an issue.
- Now compare TAC LISTCUBE in BW with TAC MB5B in R/3, a comparison for exact days should identify incorrect, duplicate or missing documents (select the "Valuated stock" option in TAC MB5B to find records in the BW where the storage location is empty)
- Now check in which format the document number is found in the PSA.
-> In this case also, the reason may be an error in the update or problems in the data extraction.
Consider the logic for determining the transaction keys of receipts/issues (Note 492828).
See these OSS Notes,
SAP Note 745788 Non-cumulative mgmnt in BW: Verifying and correcting data
SAP Note 352344 Process key + reversals in Inventory Management
Thanks
Chandran

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

Key figure non-cumulative/ Inflow / Outflow

Similar Messages

Maybe you are looking for