Computing 2 cummulated key figures

Hi All,
We receive a requirement to develop a report that would able to compute 2 cummulated key figures in BW. I was informed this was not able to be done in the normal BeX query formula as the cummulative values are computed during query execution.
Example:
Usages Loss/Gain %LOSS/GAIN (=SUM(Usages)*100/SUM(Loss/Gain))
is there a way to do this in BeX or must this be done during back-end execution.

Thanks Suman - but i think BeX is not able to handle 2 cummulated key figure values and calculate them in a formula correctly:
The % Tol - is picking up cummulated values from Usages and Daily Gain/Loss - only way i can think of is to store this in the cube.
Usages     % Tol     Daily Gain/Loss
25,713     372             95,666
32,584     -64.52     -133,278
31,302     0.35              37,924
29,915     0.56              362

Similar Messages

Storing Cummulated key figures in cube

Hi,
Can someone share on how to store cumulative key figure ? We have an Inbound and Staging layer that stores the inventory movements quantity. The staging layer contains material document and material item. At the reporting layer we need to be able to use the movement quantity and cummulate them by posting period. can someone share your thoughts on how this is coded with some performance considerations and delta. Is there an easy way to implement this in 3.X ?
I.e.
Material | Plant | Calendar Day | Quantity | Cummulated
A | XYZ | 01.01.2011 | 10 | 10
A | XYZ | 12.01.2011| 5 | 15
B | XYZ | 12.01.2011| 40 | 40
A | BBB | 13.01.2011 | 6 | 6

if youre staging is a dso then you are in luck. you could create a transformaiton routine to read the active dso table, find the key and read all the quantity on it and then store the quanity in the new infoobject result..
it should wok with delta.. unless somebody else comes up with a better idea..
or you could do it in CMOD before you bring it in BW system, makes it run even faster..
if your main object is a structure i could send u some code that help you figure it out..

Cummulative key figures

Hi experts. please explain me what are cummulative KFs and how to use them?
regards
rajesh

Dear Rajesh
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.
Note
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.
Aggregation Behavior of Non- Cumulative Key Figures Locate the document in its SAP Library structure
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/content.htm
The non-cumulative key figures are used in the Inventory cube.
Assign Points if useful
Regards
Venkata Devaraj !!!

Snapshot Inventory Management with Cummulative key figures

Experts,
We are implementing the snapshot model in parallel with the Daily cube. When trying to create the update rules from 2LIS_03_BX, we get a warning message saying 2lis_03_bx is setup for noncummulatives only followed by an error stating that there are no key figures in the cube.
How do we circumvent this issue?
All thoughts appreciated!

Pls go though below link which will help you to implement snapshot Inventory " How to handle Inventory"
https://websmp108.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002121282004E
Regards
Sangita

Problem in using formula when key figure is commulative

Hi all ,
I am problem in generating the report when we use the of cummulative key figure to the formula..
consider the following senerio..
Date      KF1 KF2 KF1(C) Kf2(C) Formula (KF1(C) - KF2(C)
5.10.2005 1   2   1       2      -1 (wrong result)
6.10.2005 3   4   4(1+3) 6      -1
7.10.2005 5   6   9(4+5) 12     -1
System is taking the actual KF1data is subtracted with KF2 data it not taking cummulative data, Actually my requirement i want to subract the cummulative data between two key figure (ie KF1(c)-KF2(c))
My Required Output:
Date      KF1 KF2 KF1(C) Kf2(C) Formula (KF1(C) - KF2(C)
5.10.2005 1   2   1       2            -1 (Correct)
6.10.2005 3   4   4(1+3) 6            -2 (4-6)
7.10.2005 5   6   9(4+5) 12           -3 (9-12)
pls let through the lights on the above issues.
with Regards,
Hari

Hi Murali..
Thanks a lot, now i got a proper output and working fine..
what i did yesterday was i have creted a two key figure as a cummulative key figure ..
and when i try to subtract two cummulative key figure system is subtracting with actual key figure and hence i got wrong result.
Today i did same thing, only diffence is i made the third formula key figure as cummulative ..
With regarsds,
Hari

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

Virtual Key Figures in RSR_OLAP_BADI COMPUTE Method not recalculated

Hi,
Please clarify why is the COMPUTE METHOD of RSR_OLAP_BADI not always
triggered or executed.
For instance, my query is drilled down by customer and
material by default. Upon opening the query and after entering
the appropriate selections, the virtual key figures that I have
used in the query are correct .
However, if i make any change to the query and run it in RSRT, the BADi method COMPUTE is not executed.
Is this really the normal behavior of the said BADI? Why is
it unstable?

Hi Rohit,
I have a similar problem the compute method is not trigerring and i am trying to debug it but it is not breaking at all, although when i generate from rsrt it breaks at a breakpoint of define method however i have defined another break at compute method but not breaking.
I am using the infoobject inside the query but and tried to hard code it for testing in the compute method but doesnt seem to be getting executed.
Please help.
Cheers,
Jad

How to reference Key figure in (BAdI) IF_EX_RSR_OLAP_BADI~COMPUTE method?

Hi,
I am a new bee to the ABAP world.
I am writing a BAdI implementation (Definition name: RSR_OLAP_BADI) for a 'Virtual KeyFigure' named D_TAX1.
I dont know how to set the value for key figure D_TAX1 in BADI implementation COMPUTE method (IF_EX_RSR_OLAP_BADI~COMPUTE).
D_TAX1 is a virttual key figure I had added in DSO.
I want to populate the value in BADI compute method (IF_EX_RSR_OLAP_BADI~COMPUTE).
I haven't written any method implementation for IF_EX_RSR_OLAP_BADI~DEFINE.
Is it mandatory that I need to write some thing there? I haven't declared any attributes either.
I want to set tax amount to the D_TAX1 virtual key figure based on the amount (another key figure in DSO).
I don't know if I need to write this, but the class name in BAdI is: : ZCL_IM_VAL_IMPL.
I really appreciate your help in this matter.
Thank you.
Sekhar

Thank you for your answers.
I have added the following code to the methods DEFINE, INITIALIZE & COMPUTE methods.
method IF_EX_RSR_OLAP_BADI~DEFINE.
DATA: l_s_chanm TYPE rrke_s_chanm,
 l_kyfnm TYPE rsd_kyfnm.
FIELD-SYMBOLS:
 <l_s_chanm> TYPE rrke_s_chanm.
Insert Code
CASE i_s_rkb1d-infocube.
WHEN 'D_DSOIC1'. "DSO name
 l_s_chanm-chanm = 'D_CST1'. "Characteristic
 l_s_chanm-mode = rrke_c_mode-read.
 APPEND l_s_chanm TO c_t_chanm.
 APPEND 'D_TAX1' TO c_t_kyfnm. "D_TAX1 is a newly added Virtual KeyFigure
ENDCASE.
ENDMETHOD. "if_ex_rsr_olap_badi~define
[In the following INITIALIZE method, I didn't change any thing. I used the INITIALIZE method from the CL_EXM_IM_RSR_OLAP_BADI as is]
method IF_EX_RSR_OLAP_BADI~INITIALIZE.
DATA: l_global_name TYPE string.
FIELD-SYMBOLS:
 <l_global> TYPE i,
 <l_s_sfc> TYPE rrkg_s_sfc,
 <l_s_sfk> TYPE rrkg_s_sfk.
there's no need to change this method
Just create attributes for each charactersitic
with name P_CHA_<characteristic> TYPE i.
and constants for each key figure with name
P_KYF_<key figure> TYPE i.
CLASS cl_exm_im_rsr_olap_badi DEFINITION LOAD.
get field postions for characteristics in structure
LOOP AT i_th_sfc ASSIGNING <l_s_sfc>
 WHERE user_exit NE rrke_c_mode-none.
field name in structure is keyreturnnm
name of the global variable
 CONCATENATE 'P_CHA' <l_s_sfc>-chanm
 INTO l_global_name
 SEPARATED BY '_'.
fill the global variable
 UNASSIGN <l_global>.
 ASSIGN (l_global_name) TO <l_global>.
 CHECK <l_global> IS ASSIGNED.
 <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
 i_fieldnm = <l_s_sfc>-keyreturnnm
 i_s_data = i_s_data ).
ENDLOOP.
get field positions for key figures in structure
LOOP AT i_th_sfk ASSIGNING <l_s_sfk>
 WHERE value_returnnm IS NOT INITIAL.
name of the global variable
 CONCATENATE 'P_KYF' <l_s_sfk>-kyfnm
 INTO l_global_name
 SEPARATED BY '_'.
fill the global variable
 UNASSIGN <l_global>.
 ASSIGN (l_global_name) TO <l_global>.
 CHECK <l_global> IS ASSIGNED.
 <l_global> = cl_exm_im_rsr_olap_badi=>get_field_position_d(
 i_fieldnm = <l_s_sfk>-value_returnnm
 i_s_data = i_s_data ).
ENDLOOP.
endmethod.
METHOD if_ex_rsr_olap_badi~compute.
FIELD-SYMBOLS <fs_d_tax1> TYPE ANY.
FIELD-SYMBOLS <fs_d_cst1> TYPE ANY.
ASSIGN COMPONENT p_kyf_d_tax1 OF STRUCTURE c_s_data TO <fs_d_tax1>.
ASSIGN COMPONENT p_cha_d_cst1 OF STRUCTURE c_s_data TO <fs_d_cst1>.
<fs_d_tax1> = 10.
ENDMETHOD.
When I display the virtual key figure D_TAX1 in the query, it is not populated with value 10.
Can you guys please tell me what I need to change?
I haven't written any code in GET_FIELD_POSITION_D (in the example class CL_EXM_IM_RSR_OLAP_BADI, this method is implemented).
I appreciate your suggestions and help.
Thank you,
Sekhar

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*********

Planning using the Non-Cumulative Key figures

HI,
In my reporting requirement for IP, I need to get some actual values from the cube 0IC_C03. The key figues which I required are 0VALSTCKVAL and 0TOTALSTCK, but these 2 are non-culative key figures. When I selected these 2 key figures in my aggregation level, it is throwing an error message as "InfoObject 0VALSTCKVAL(Version A) is not compounded and Aggregation level is inconsitent".
I read in some document that, it is not possible to use non-cumulative keyfigures in ALVL.
I searched in SDN and SERVICE also, but some documents are saying that, in new path level (19) it is possible. Now I using the path level 18 only. In this case how we have to use these non-cumulative keyfigues,, please sugguest me...
Thanks in advance...
Regards
Rajesh

Hi
Non-cummulative keyfigures are not supported fro planning and teh error thrown is correct.Please find the help link which gives what are supported and not supported as part of aggregation levels.
http://help.sap.com/saphelp_nw70/helpdata/EN/43/1c3c7031b70701e10000000a422035/content.htm
Regards, Hyma

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)

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

When creating Key figures

Hi gurus,
When creating Key Figures in Adminstration workbench
in the tabs AGGREGATION and ADDITIONAL PROPERTIES
can somebody kindly explain the below contents and how do they affect and where do they affect, if we select.
AGGREGATION
aggregation----> sum, maximum, minmum
Exception Aggr----> summation
first value
last value
no aggregation (x if more than one record occurs)
no aggregation (x if more than one value occurs)
no aggregation (x if more than one value not= 0 occurs)
standard deviation
summation
var
agg. referen.char
cummulative/non-cumulative values
non *** value with ncum value change
ncum value with in and out flow
i will be very greatfull if somebody can give me some clear explaination and with some examples
thanks and regards
H.B.

hi Dinesh,
thanks for the quick response.
With the info i got ...i am assuming that...
if we set the settings of aggregation when creating key figures they will be displayed in the query results row.
but if we want to have this effect in the data targets then we have to do these settings in the update rules
plz can you tell me where to do these settings and is the affect same as the properties of key figures do in the query results row.
thanks and regards
H.B

Misalignment of key figures in export to excel

Hello Experts,
I have a WAD report with 2 queries (say) Query A and Query B, in this report we are using table interface class for computing the sum of key figures in Query A with Query B and showing in the result row of QueryB
When this report is executed it gives the correct output, but when i export this report to excel, the output of Query B gets mis-aligned.
Please suggest what may be the reason behind this and how should i correct this problem.
We are using MS office Excel 2003.
FYI, for excel export, we're not using the standard feature, rather, using a class : CL_RSR_XLS_HELP_WINDOW_PRINT\
Regards\
Priyanka

OK....!!!!!
just download the Excel file (*.xls) and try open with Word-MS. In the document search by the string that you have mentioned in the question. (Use Ctrl +F).
If you see something like "ABC bla bla ba & instead of &amp , then you have to pass the data through the code I've mentioned.
You can get more details on encoding special characters UTF-8 in Google.com or Sun Websites etc.
You can also encode the & in hexadecimal format to get the desired output.

How to cumulate key figure for whole fiscal year with one time variable?

Hello everybody!
I have a problem creating a query that allows to get cumulated key figure for whole fiscal year (FY), when I actualy type only last period for the FY.
The query itself is very simple:
- I have "Organization" characteristic in "Rows" section
- I have one key figure "Number of invoices" in "Columns"
- I have "Fiscal year variant" 0FISCVARNT defined in "Filter" that has 12 periods within Fiscal year
and then
- in section "Free Characteristics" I have "Fiscal year/period" 0FISCPER.
I want to be able to provide ONE single value when run query, which is last period of a FY (like 012/2003), but then in report see cummulated number of invoices for WHOLE fiscal year.
Will appreciate any help!
Vitaliy

Please see the white paper entitled "How to... Derive a Variable value from another variable 2.x (pdf)".
Regards,
Troy

Computing 2 cummulated key figures

Similar Messages

Maybe you are looking for