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

Similar Messages

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

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

Combining cumulative and non cumulative Key fig in same report with Quarter

Hi there,
could someone please help with the following,
I need to define a query, with a Keyfig called Amount (cumulative) coming from Controlling Cube, and HR Head count(non cumulative) from HR cube. Need to display Quarters in columns, Amt and Head Count in Rows. User might want to expand quarters and should be able to see the amount/Head count values for each of Fiscperiods. Up to this point, I had my definitions made, everything seems good.
problem here is, structure defined for quarters is basically a formula that sum up each fiscperiods, so it is working for fine for the amount, but for head count, it should not sum up each period values, rather need to average.....How can I achieve this?
Any help is greatly appreciated.

Thanks for your help.
My scenario kinda take an hr to explain, difficult to put it here on the thread.
to keep it simple, I need Head Count as LAST value with respective to calmonth, but need to have average with respective to Quarter. where I have defined the quarter as formula (mth1Variable Value Type + Mth1Variable Value type + mth2variable value type + mth2variable value type .....etc). So I could not set the aggregation as average in the formula. Rather I used cell definitions.
Thanks Again

Modelling a non-cumulative key figure.

Hi All,
   I have a requirement like given below. I feel a non-cumulative key fig serves my purpose. But i m not geting exactly how to model it.Pls give u r suggestions onnhow to do it?
   i got chars C1,T1 and key figures K1,K2.
C1 IS A CUSTOM CHAR.
T1 IS A 0CALDAY TIME CHAR.
K1 IS A CUMULATIVE KEYFIG( NORMAL KEYFIG).
K2 IS ALSO NORMAL KEYFIG. ITS VALUE IS CONSTATNT FOR ENTIRE MONTH.
e.g Data.
C1   T1   K1   K2 ( constant value for jan). K3
X1   Y1   10    100                                  100-10=90.
X2   Y1   30    100                                   90-30=60.
X3   Y2   20    100                                   60-20 = 40.
C1   T1   K1   K2 ( constant value for FEB). K3
X1   Y1   10    200                                  200-10=190.
X2   Y1   30    200                                  190-30=160.
X3   Y2   20    200                                  160-20 =140.
According to above logic i need to derive K3.
My plan is that make k3 as non-cumulative w.r.t K2.
my doubts r
1) How to laod that initial value ( 100,200).
2) As Initial value changes for each month, how to model this? i.e for january it is 100. so for january my initial value is 100. then for February it is 200. so for feb my initial value is 200. How to model these?
3) Is this approach is correct or is there any other way to do this?
Points will be assigned to useful answers.
Thanks in advance.
Regards,
Ramana.

Hi Gurus,
   I m waiting Egerly for u r replies.
Regards,
Ramana.

Cumulative key figs in MM(LO-Inventory)

Hi Frnds
Can anybody tell me, wht are the Cumulative and Non Cumulative Key Figs in MM(LO-Inventory).Plzz name those.
Thanks & Regards
Prabhakar

To respond to your latest question....
You may already know this, so bear with me...
Non-cumulatives have an "incoming" and "outgoing" reference. Meaning, for a the record to be stored it takes an "addition" and "subtraction" to calculate the value. Generally, you either initialize this value with an "addition" (the value can be positive or negative). This initialization can either be the first record you insert or a "generate initial status". After that first record/status, all values after that are generally (depending on marker update) added or subtracted from this value to make up the non-cumulative value.
Take for instance the KF:
0VALSTCKVAL - Value of valuated stock
Inflow(+):
0RECVS_VAL - Value received into valuated stock
Outflow(-):
0ISSVS_VAL - Value issued from valuated stock
In the infocube, you will want the 0VALSTCKVAL, 0RECVS_VAL and 0ISSVS_VAL.
0RECVS_VAL and 0ISSVS_VAL are normal KF's and can be used anywhere, they are not non-cumulative. But, they make up the + and - of the key figure of 0VALSTCKVAL.
Now, the KF 0VALSTCKVAL can not be updated directly, once you add it to the infocube, it can only be updated by updating the key figures of 0RECVS_VAL and 0ISSVS_VAL. (They system doesn't let you even try to update 0VALSTCKVAL directly). Thus, the value is controlled by the additions-inflows (receipts) and subtractions-outflows (issues). You can see this behavior in the update from 2LIS_03_BF/UM to 0IC_C03.
Now, to set an initial status, you just need to update the "inflow" of each Non-cumulative KF. You can see this behavior in the 2LIS_03_BX update to 0IC_C03.
You can also see this behavior if you look what SAP is doing during compression and building of aggregates. You will see some SQL that looks similiar to this.
...SUM( 0RECVS_VAL - 0ISSVS_VAL )
...SUM( 0RECVS_QTY - 0ISSVS_QTY ) "(Not sure if these are real
Now, non-cumulatives in ODS objects or anything other than an infocube are useless as they do not have a cooresponding validity table to store the updated pointer.
I will not go into the pointer logic, but there is a document out there for non-cumulative you will want to look at to make more sense of this pointer logic.
I hope this is what you were looking for...
/smw
Message was edited by: Steve Wilson
Message was edited by: Steve Wilson

Aggregates on Non-cumulative InfoCubes, stock key figures, stock, stocks,

Hi..Guru's
Please let me know if anybody has created aggregates on Non-Cumulative Cubes or key figure (i.e. 0IC_C03 Inventory Management.)
I am facing the problem of performance related at the time of execution of query in 0IC_C03.( runtime dump )
I have tried lot on to create aggregate by using proposal from query and other options. But its not working or using that aggr by query.
Can somebody tell me about any sample aggr. which they are using on 0ic_c03.
Or any tool to get better performance to execute query of the said cube.
One more clarification req that what is Move the Marker pointer for stock calculation. I have compressed only two inital data loading req. should I compress the all req in cube (Regularly)
If so there would be any option to get req compress automatically after successfully load in data target.
We are using all three data sources 2lis_03_bx,bf & um for the same.
Regards,
Navin

Hi,
Definately the compression has lot of effect on the quey execution time for Inventory cubes than other cumulated cubes.
So Do compression reqularly, once you feel that the deletion of request is not needed any more.
And ,If the query do not has calday characterstic and need only month characterstic ,use Snap shot Info cube(which is mentioned and procedure is given in How to paper) and divert the month wise(and higher granularity on time characterstic ,like quarter & year) queries to this cube.
And, the percentage of improvement in qury execution time in case of aggregates is less for non cumulated cubes when compared to other normal(cumulated) cubes. But still there is improvement in using aggregates.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Purpose of Non Cumulative key figures

Whatu2019s the purpose of Non Cumulative key figures?

Hi....
There is an explanation of advantages and disadvantages of using non-cumulative key figures in "How to handle inventory management scenarios in BW" white paper:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20handle%20inventory%20management%20scenarios.pdf
Also Check..........
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Re: Non-Cumulative keyfigure example
Hope this helps.....
Regards,
Debjani........
Edited by: Debjani Mukherjee on Oct 27, 2008 3:46 AM

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. This cube is defined by me to test the non-cumulative key figure.
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.
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

Non-Cumulative Key figure with inflow & outflow

I am using some non-cumulative key figure in our inventory cube, however, I could not find the non-cumulative field in E or F table of the cube?
Is there a separate table to hold the reference unit. If so, what is the table name.
Thanks.

Hi,
Go to t-code RSDV and enter the tech.name of your cube that has the non-***. key figure and you will see a validity table. This is only thing I know that will make you look at validity table.
The unit for the Non-*** KF will be the same unit as its inflow and outlow parameters' unit.
Thats my 2 cents on the matter.
Reddy

Non cumulative key figure is not getting filled based on inflow and outflow

hi,
i have a non cumulative key figure which is having inflow and outflow.
i have these three info objects in dso.
as i know non *** key figure is calculated based on inflow and outflow.
i am getting values for inflow and outflow so non *** should be calculated based on this values.
but the collumn is blank in the dso
in that non *** keyfigure i have added two info objects in inflow and outflow.
is there any other setting i nedd to do?
please sugest me.
its urgent

Hi Venkat,
Have you followed the process right. First Filling the Initial Stocks and then Inflow and Out Flow and then Delta. If you follow the process correctly then you can able to view the Data in the Reporting Level.
For Initial Stocks the Marker Should be set. For Inflow and Outflow the Marker should not be set.
Hope This Helps,
Regards,
rik

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

Bad performance with non-cumulative key figures

Hi All,
I have a cube with 8 non cumulative key figures based on fiscper.
I am not sure how the performance for reporting with non-cumulatives can be improved.
Thanks
Karen

Performance of non cumulative cubes is dependant on the distance between the marker (date of the last compression) and the execution date.
For actual stock, the more you compress the better it is.
Regards,
Fred

When do you go for non cumulative key figures?

hi all,
Can anyone explain the significance of non cumulative key figures. and when do we go for non cumulative key figures.
Can anyone explain me with an example.
thanxs in advance
hari

Hi,
chk these threads:
non cumulative key figures
Cumulative and Non-cumulative Key Figures
also,
There is also an explanation of advantages and disadvantages of using non-cumulative key figures in "How to handle inventory management scenarios in BW" white paper:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20handle%20inventory%20management%20scenarios.pdf
Assign points if this helps!!
Regards,
Dhanya.

Trouble with Non Cumulative Key Figures

Hi all of you,
I am working on Non Cumlative Key Figures, (NCKF). I have the data like this
Sales rep S100 visited SHOP S1 on 1st Jan and 10th Aug, and transacted worth 100 and 500
SHOP S2 on 1st Mar and 1st July and transacted worth 200 and 300
SHOP S3 on 3rd Sept. and transacted worth 400
Sales rep S200 visited SHOP S1 on 1st Jan and 1st Aug and transacted worth 100 and 300,
visited SHOP S2 on 1st April and transacted worth 200
I created Non Cumulative Key Figure in the following manners:
In modeling in InfoObjects I double clicked on my key figure BILLAMT and selected the Aggregation tab. I selected Counter (all values) for Exception aggregat. By default Agg. Referen. Char was 0calday. I then activated the info object and went to BEx. Here I took other IOs like Salesrep, Shop NUM and Dt. Of trans in rows and Bill amt in columns and executed the report. I am not getting the output how it should come for NON cumulative key figures.
But when I right click the key figure Bill Amount in BEx in change query mode and select properties. I go to the option Calculate result as and selected the option as Count all values. And in another option Calculate Single Value as I selected the option Count all values. I said OK, saved the query and executed it. Now the output is similar to how it comes for a Non Cumulative Key Figure query but I am unable to understand the output.
Now my doubt is where do we set the properties for Non Cumulative Key Figures? Is it in the Administrator Workbench under Modelling under InfoObjects?
OR
Is it in BEx change query mode by right clicking on the key figure and selecting properties?
Please explain.
Thank you
TR.

As for the setting for Non Cumulative key figures...the default setting is done in the Key Figure properties, where u can define the Exception Aggregation. This property is used as such in the query, but if suppose u are getting the normal aggregation in the query , what you could do is "Create The Key Figure as Global Calculated Key Figure in Bex" and go to properties...click on the Button for aggregation ..select the aggregation and define with respt to 0CALDAY ..here.
Hope this helps.

Key Fig Non Cumulative

Similar Messages

Maybe you are looking for