Blank needed for cumulative Key Figure

Hi All,
here's what my BEx report looks like when I run (after 10AM and before 11AM)::
Hour            Qty          CumulativeQty
7AM            10                    10
8AM            20                    30
9AM            15                    45
10AM          13                    58
11AM                                  58
12PM                                  58
But, here's what my BEx report should look like when I run (after 10AM and before 11AM)::
Hour            Qty          CumulativeQty
7AM            10                    10
8AM            20                    30
9AM            15                    45
10AM          13                    58
11AM
12PM
Any suggestions

Try this If.. Else Formula for Cumulative Qty
( Qty KF < > 0 ) * Cumulative Qty KF + ( Qty KF = = 0 ) * 0
Finally set Zero as space in Query global properties.

Similar Messages

Help needed for Virtual Key Figure BADI

I am trying to implement Virtual Key Figures via BADI.
Here is what I have done
Define Method
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 'ZMCOPA_02'.
l_s_chanm-chanm = '0CUSTOMER'.
l_s_chanm-mode = rrke_c_mode-read.
APPEND l_s_chanm TO c_t_chanm.
APPEND 'ZCPRC_FLG' TO c_t_kyfnm.
APPEND 'ZRTNS_PRC' TO c_t_kyfnm.
ENDCASE.
ENDMETHOD. "if_ex_rsr_olap_badi~define
Compute Method
method IF_EX_RSR_OLAP_BADI~COMPUTE.
FIELD-SYMBOLS <fs_ZRTNS_PRC> TYPE ANY.
FIELD-SYMBOLS <fs_ZCPRC_FLG> TYPE ANY.
FIELD-SYMBOLS <fs_0customer> TYPE ANY.
DATA: l_zv_20dv TYPE curr09.
ASSIGN COMPONENT p_kyf_ZRTNS_PRC OF STRUCTURE c_s_data
TO <fs_ZCPRC_FLG>.
ASSIGN COMPONENT p_kyf_ZCPRC_FLG OF STRUCTURE c_s_data
TO <fs_ZCPRC_FLG>.
ASSIGN COMPONENT p_cha_0customer OF STRUCTURE c_s_data
TO <fs_0customer>.
DATA: l_zrtns_prc TYPE /bic/pzcust_prc-/BIC/ZRTNS_PRC.
DATA: lt_zcust_prc TYPE TABLE OF /bic/pzcust_prc.
DATA: ls_zcust_prc TYPE /bic/pzcust_prc.
IF NOT p_cha_0customer IS INITIAL.
<fs_0customer> =
ENDIF.
SELECT SINGLE *
INTO ls_zcust_prc
FROM /bic/pzcust_prc
WHERE /bic/zcust_prc = <fs_0customer>.
IF sy-subrc = 0.
<fs_ZCPRC_FLG> = 1.
<fs_ZRTNS_PRC> = ls_zcust_prc-/BIC/ZRTNS_PRC.
ELSE.
<fs_ZCPRC_FLG> = 0.
<fs_ZRTNS_PRC> = 0.
ENDIF.
endmethod.
I have commented out line in the Compute method because I was getting an error on my SELECT statement. I think the error is due to the fact that <fs_0customer> is not being populated.
In debug mode, p_kyf_ZRTNS_PRC, p_kyf_ZCPRC_FLG and p_cha_0customer all return 0. Shouldn't they have a different value. I have to admit that I don't really understand how ASSIGN COMPONENT works.
I have defined p_kyf_ZRTNS_PRC, p_kyf_ZCPRC_FLG and p_cha_0customer in the Attribute tab.
Any help would be appreciated. I have spent several hours trying to figure out how this works.
Thanks.
Ryan

Check this if it helps:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e051fda8-71a9-2a10-ac9e-8d17414a8c8c

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

Validity table for a Non-Cumulative key figure

Hi,
I need to make changes to a validity table for a Non-Cumulative key figure.
I know initially it is done thru Extras- > Maintain Non-Cumulative value but subsequently how to change the parameters ?
Best Regards,
-Anurag Dev

If you decide later that you require more validity-determining characteristics, you can modify the selection using the report RSDG_CUBE_VALT_MODIFY. In this report, the non-cumulative InfoCube is only changed to the extent that the new validity-determining characteristics are selected and the validity table is reconstructed. The structure of the non-cumulative InfoCube remains the same. You do not have to reload the transaction data for it.

Expression for a cumulated key figures

I would like to make an expression for a cumulated key figure (I set "cumulated" in properties of this KF) in Query Designer 3.5. If I try to make an expression, I'll get an expression for a key figure, and not for a cumulated key figure.
Any ideas? Should I use query view?

Hi,
You may need to think about the Cell Editor concept here.
In of the report I need to take 12 calmonth2 values in the columns starting from a financial year.Here the financial startd from APRIL.
For each coolumn I need to show Average of sales value.Here Average means ,under APril month the value is April's sales value only.But for May ,I need to show like : (sales of April+ sales of May)/2.
Similarly for June: (sales of April+ sales of May+sales of June)/3.
So on ....
Here I used the cell editor concept to get the required out put.
I am take 12 selections in columns for 12 months .
I have taken Sales value 2 times into Rows and hidden the first KF. But in the cell editor: for second row's second cell I have defined a formula like : (second row's First cell+ First row's second cell)/2
Similarly for second row's thrid cell I have defined a formula like :(second row's First cell+ First row's second cell+ First row's third cell)/3.
so on..for other cells of Second row.
With rgds,
Anil Kumar Sharma .P

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.

Intregarted Planning Design for Non-Cumulative Key Figures

Hi,
I have a requirement where i have to design a planning layout for a Invenotry Scenario (Using Non cumulative Key Figures).
What should be the factors i should consider in my design specifically for non cumulative ke figures and how it is different from design for a regular (cumulative) key figure
Thanks
Rashmi.

Thanks for your response. My requirement is to design a retail inventory planning application in which one of the KPI's planned is stock price which is a non cumulative key figure and i am trying to figure out how than can be planned if non-cumulative key figures are not allowed in planning
Thanks
Rashmi.

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

Non Cumulative Key Figure help

Hi All,
I am in need of setting up a non-cumulative key figure in a cube. When I load from my ODS everything is ok, however during a delta process, this field at times gets
summarized when in fact it should be static or in an overwite mode. Can someone provide some advice/comments on how I can set up my key figure field in a basic cube to be static yet be able to be used in a calculation for a query? I do not want to apply any functionality such as aggregation, average etc. In R/3 LIS functionality, you basically set up a characteristic Key Figure, how can this be done in BW ?
Best Regards,
Dennis

Dennis,
Check if you ahve declared the KF properly and also check the query which you use ...
Load data and then compare with the query at the lowest level of data in the ODS. Then you will know if the update rules are correct.
Arun

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)

Is this a candidate for virtual key figure ?

Hello BW Experts,
discount amount = sale amount * disc rate
discount amount is only for the analysis purposes, sale amount comes from the billing document, disc rate is manually maintained in a custom r/3 table (brought to BW as ODS).
Disc rate can change daily. In the Bex report discount amount should be calculated based on the month end disc rate.
wondering different methods to achive the same:
1) make the discount amount as the virtual kf and lookup the month end rate from disc rate ods
2) is it possible to declare the disc amount as the keyfigure with some sort of aggregation / cumulation ?
any suggestions appreciated..
Thanks,
BWer

Hello,
Option 1 is simple and more practical where as option 2 falls under the category of non-cumulative key figures, which is slightly complex to handle.
Option 2 also depends on number of entries in the Info cube, if the data in the Info cube is not huge then 2nd option won't cause any performance issues.
You can also look at other option of creating Global calculated key figures with exception aggregation "Last value" but for this, you need to include discount rate a part of the Info cube.
Hope this helps.
Cheers
Bala

BEx report -two different calculations for a result for one key figure how?

All,
Maybe someone could help me with the following, we have a requirement to setup for one key figure two calculations for result rows. One result (average) for one level, and on a higher level -grand total have a (sum), as for our business it makes sense to do it this way. We have setup average for this KF, we get correct results (see below values 7,5 & 6,5) however for the grand total (across multiple products) so for one level up we need to have a different calculation. How could we achieve this?
Here is an example:
location     product          inventory
AAAA     11111          5
AAAA     11111          5
AAAA     11111          10
AAAA     11111          10
AAAA     Result          7,5      ---> average
AAAA     22222          5
AAAA     22222          6
AAAA     22222          7
AAAA     22222          8
AAAA     Result          6,5       -
> average
AAAA     Result (across products)          14      ---> here I want to have a sum of averages

This could be achieve only IF you upload a hierarchy for product inventory with different levels, wherein each level show subtotals and finally grand total will be shown at the end of the results.

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

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

Blank needed for cumulative Key Figure

Similar Messages

Maybe you are looking for