Key Figure Summation in Result Row with Cumulation Ticked

Hi,
I have a Bex question regarding the summation rows.
I need a Year To Date amount and a Period To Date amount in the report. However, there is no Year To Date key figure available in the cube. So in order to calculate YTD, I'm using the PTD key figure and have Cumulated box ticked mark in Bex.
All looks fine across columns per Vendor. But the results row for the Cumulative Balance is always equal to the results row for Period Balances. I believe this is because the same key figure is used, and it is only reading the amounts in the cube - not the ones calculated on the fly.
Does anyone know how to correct the results row for a cumulated key figure?
Regards,
Rhonnie

You have to create two restricted KF; one is PTD restricted to period; the second is PTD restricted in a period range from 01.yyyy to current period.
Hope it helps.
Regards

Similar Messages

Subtraction of two key figures normalized to result not working as expected

Hello SAP Community!
I am having problems with getting the right result from a subtraction of two KFs which are "normalized to results" which means the KFs really have values expressed as percentages. The substraction that should be performed is of two percentages (e.g.: 87.298% - 85.527% = 1.77%) but my report prints out the result as "number of units" instead (e.g.: 87.298% - 85.527% = 71,514.00 EA). The two normalized KFs actually "point" to two stock KFs, hence the "number of units".
In order to explain the problem I am facing please analyze below text:
1) Let's assume I have below data:
LOAD MONTH PLANT MATERIAL HORIZON MONTH FORECAST UNITS
200805 PLANT-A MAT-1 200805 510,235.00
200805 PLANT-B MAT-1 200805 74,240.00
200805 PLANT-A MAT-1 200806 438,721.00
200805 PLANT-B MAT-1 200806 74,240.00
200805 PLANT-A MAT-1 200807 356,981.00
200805 PLANT-B MAT-1 200807 74,240.00
200806 PLANT-A MAT-1 200805 0.00
200806 PLANT-B MAT-1 200805 0.00
200806 PLANT-A MAT-1 200806 510,235.00
200806 PLANT-B MAT-1 200806 74,240.00
200806 PLANT-A MAT-1 200807 438,721.00
200806 PLANT-B MAT-1 200807 74,240.00
2) Then, assume I have a comparison report, restricted by load month for two months May and June 2008 (filter restricted by two month variables) with FORECAST units spread accross columns for whole horizon (two months also in this case).
Material Plant 2008/06 2008/07
===================================================================
MAT1 PLANT-A
 Base Units (May 2008) 438,721.00 356,981.00
 Comparison Units (June 2008) 510,235.00 438,721.00
 PLANT-B
 Base Units (May 2008) 74,240.00 74,240.00
 Comparison Units (June 2008) 74,240.00 74,240.00
 TOTALS Base Units 512,961.00 431,221.00
 Comparison Units 584,475.00 512,961.00
3) Now, let's suppose we want to know the proportions (%) of Base vs Comparison units, so
we normalize forecats to results an we get the below report:
Material Plant 2008/06 2008/07
===================================================================
MAT1 PLANT-A
 Base Units (May 2008) 438,721.00 356,981.00
 Base Units % (May 2008) 85.527% 85.527%
 Comparison Units (June 2008) 510,235.00 438,721.00
 Comparison Units %(Jun 2008) 87.298% 82.784%
 PLANT-B
 Base Units (May 2008) 74,240.00 74,240.00
 Base Units % (May 2008) 14.473% 15.702%
 Comparison Units (June 2008) 74,240.00 74,240.00
 Comparison Units %(Jun 2008) 12.702% 17.216%
 TOTALS Base Units 512,961.00 431,221.00
 Comparison Units 584,475.00 512,961.00
4) Finally, let's suppose we want to know the deltas (differences) of Base vs Comparison
units, for both number of units and %. The report now look as below:
Material Plant 2008/06 2008/07
===================================================================
MAT1 PLANT-A
 Base Units (May 2008) 438,721.00 356,981.00
 Base Units % (May 2008) 85.527% 85.527%
 Comparison Units (June 2008) 510,235.00 438,721.00
 Comparison Units %(Jun 2008) 87.298% 82.784%
 Delta base vs. comp. units % 1.77% 2.74%
 Delta base vs. comp. units 71,514.00 81,740.00
 PLANT-B
 Base Units (May 2008) 74,240.00 74,240.00
 Base Units % (May 2008) 14.473% 15.702%
 Comparison Units (June 2008) 74,240.00 74,240.00
 Comparison Units %(Jun 2008) 12.702% 17.216%
 Delta base vs. comp. units % -1.77% -2.74%
 Delta base vs. comp. units 0.00 0.00
 TOTALS Base Units 512,961.00 431,221.00
 Comparison Units 584,475.00 512,961.00
5) PROBLEM:
In my report, the "Delta base vs. comp. units %" is not working as expected and
calculates number of units just as "Delta base vs. comp. units" does instead of calculating the % difference.
So my report looks as follows:
Material Plant 2008/06 2008/07
===================================================================
MAT1 PLANT-A
 Base Units (May 2008) 438,721.00 356,981.00
 Base Units % (May 2008) 85.527% 85.527%
 Comparison Units (June 2008) 510,235.00 438,721.00
 Comparison Units %(Jun 2008) 87.298% 82.784%
 Delta base vs. comp. units % 71,514.00 81,740.00 <<<WRONG!!
 Delta base vs. comp. units 71,514.00 81,740.00
 PLANT-B
 Base Units (May 2008) 74,240.00 74,240.00
 Base Units % (May 2008) 14.473% 15.702%
 Comparison Units (June 2008) 74,240.00 74,240.00
 Comparison Units %(Jun 2008) 12.702% 17.216%
 Delta base vs. comp. units % 0.00 0.00
 Delta base vs. comp. units 0.00 0.00
 TOTALS Base Units 512,961.00 431,221.00
 Comparison Units 584,475.00 512,961.00
The formulas are:
a) Delta base vs. comp. units %
Delta base vs. comp. units % = Comparison Units % - Base Units %
b) Delta base vs. comp. units
Delta base vs. comp. units = Comparison Units - Base Units
The KFs
- Comparison Units %
- Base Units %
Are RESTRICTED key figures (restricted to Base and comparison month variables) which
are setup as:
1) Calculate Result As: Summation of Rounded Values
2) Calculate Single Value as: Normalization of result
3) Calculate Along the Rows
The KFs
- Delta base vs. comp. units %
- Delta base vs. comp. units
are FORMULAS setup to:
1) Calculate Result As: Nothing defined
2) Calculate Single Value as: Nothing defined
3) Calculate Along the Rows: user default direction (grayed out)
Thanks for the time taken to read in detail all of this. Long text but necessary to understand what the problem is.
Any help is highly appreciated.
Thank you.
Mario

Hi,
The subraction will be carried out before doing the normalization of your KF's. So, it is displaying "number of units". Create a calculated keyfigure and subtract the KF's and in the properties of this calculated keyfigure, change the enhancement as "After Aggregation".
I hope this will solve your issue.
Regards,
S P.

Key figure summation

Hi All
I searched SDN forums and could not find a solution for the same.
I have added a keyfigure as display attribute in 0costcenter masterdata. The same is available as display attribute in headcount cube (0papa_c02) via 0mast_cctr. Now at the reporting level, the values for the key figure is not summing up at the node level for costcenter hierarchy as a normal functionality of display attribute. It works fine for normal key figures.
So as a solution, I added this keyfigure in the headcount cube and populated the same via a routine from 0costcenter masterdata. The values are populating perfactly fine in the headcount cube. But the problem is that, as the headcount cube has multiple entries for the same costcenter, the values for the key figure is getting aggregated at the reporting level. I even tried using exception aggregation and non cumulative key figures to get the non aggregated value. But I am unable to solve this.
Could you please guide me how can I acheive this. I know I can achieve this if I use an ods. But this will affect the whole design. Plaese suggest.
Cheers
Chanda

Hi Jacob
I created one calculated key figure which contains the real key figure from the cube. When I press Ok, it will get saved. The only thing I could see is the properties of the calculated key figure/ key figure. Where I can see count all values <>0 in calculate result as.
I could not find below at the query level. Are you talking about the aggregation tab in the infoobject maintainance in BW side?
"on the next screen in bottom left corner, there is a button (I think it will say "Expand" if you log on in english). Click that one and now you get to set the aggregation behaviour. Set the exception aggregation to 'count all values 0' and the reference char to the costcenter (I think your mst. costcenter in this case)"
Cheers
Chanda

Impact of Delta Records on Key Figure Summation in DSO

Hi experts,
I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
E.g.
source DSO
doc_id (key) | doc_pos | type | amount
4711 | 1 | A | 100 USD
4711 | 2 | B | 20 USD
target DSO
doc_id (key) | amount
4711 | 120 USD
If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
4711 | 1 | C | 100 USD
This will lead to incorrect amount:
target DSO
doc_id (key) | amount
4711 | 220 USD
How can I handle this situation?
Thanks in advance.
Regards,
Meng

Hi..
I believe one document number and document Item will have only one type.
Like 4711 1 should have only one type ( A / B / C).
If the above assumption is true then just remove Doc Type from Key field of source DSO.
Then From Source to Target Change Log table can handle this.
Regards
Anindya

Key Figure value in Cube showing with extra zeros

Loaded data into the cube. When I display the result
Key figure values are showing with 2 extra zeroes and Quantity value shaowing with 3 extra zeroes.
Original value
Price, Quantity, Sales Rev
2     1     2
3     2     6
When display value from cube
Price, Quantity, Sales Rev
2,00     1,000     2,00
3,00     2,000     6,00
Why zero is showing? How can I display the original value? In PSA, values are showing correctly.
Thanks,

Hi,
These are the zeroes after the decimal places. this is the property of the key figure.
In your report you can change the display value. In the display properties of the Key figure under the number of decimal places make it as 0. This will remove the zeroes.
Hope it helps.
Regards,
Gaurav
Edited by: Gaurav Kothari on Oct 16, 2008 10:35 AM

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

Key Figure Summation in DSO

Hi,
I am loading data from Cube to DSO.
In cube i have fields with 2 records below as example
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
In DSO all these f1's fields are key fields as per requirement. And when i load now i get in DSO as
f1=1 f2=2 f3=3 f4=4 and key figure k1=2
I do not want k1=2 but i want k1=1 in DSO and not sure why this is getting summed up even though i have selected overwrite in Transfer rules.
I have checked mapping and cube data. All are fine.
I just want to avoid this and do not know what to do.
A routine or formula or something else?
Please help.

Hi,
Check your DSO Design
Keep f1 ,f2, f3, f4, are in KeyFileds of DSO and Keep key figure k1 in DataFields of DSO.
Here I'm assuming that F1 to F4 are Charecteristics.And only K1 is Keyfigure. If this is the case then I hope it will work if you follw the above design.
Thanks
Reddy

Key figure display in planning book with respect to Time bucket profile

Hi,
I am loading a key figure to planning area from the info cube for the current month. When I review the key figure in planning book with monthly time bucket profile it shows 85 for the current month. In the same planning book with weekly bucket profile, it shows 55 from the current week and future weeks and the remaining 30 goes into the past weeks of the current month.
How to make the total quantity 85 to show in the current and future weeks only.
thanks and regards
Murugesan

Hi Murugesan,
Within the Planning Area, the data is stored at the lowest level granularity that you maintain in storage bucket profile. Then during display, system will decide what data to show depending on what kind of time bucket profile you use in the planning view, and the time based disaggregation that you maintain for Key Figure.
In this below case, what time characteristic do you have in cube? Is it date, week or month?
If it's date, check how much KF data is maintained on the dates which belong to week which has days both in this month/last month e.g. if I talk about Dec 2011, how much data is stored 1,2,3 & 4 th of Dec, 2011.
This data would appear in Dec in monthly view, but in week, it would appear in the week starting 28th November.
If data is maintained in cube in weeks, then you need to calculate how time based disaggregation would show it to you in months.
If it's months, then you would need to find out how much data would go to the days in the past week of the month.
The time based disaggregation may be causing you some issues, but in that case, I would not expect 30 out of 85 to go in the past week, unless you have data in cube in days.
Data shown in weekly view for week starting 28th Nov should ideally be a small proportion of 85, unless you are using a time stream/fiscal year variant, due to which most of December is in holidays. The only other exception I can think of is that you have data in teh days mentioned above.
It would be best to help the business understand this disaggregation logic, rather than thinking of manipulating the data to shift to a later week.
If this logic doesn't explain your situation, then please provide the date/week/month at which you have data in cube, and what quantity.
Thanks - Pawan

Key figure summation for KF IN different cube of a MP

Hi,
   I need to design a report on a Multiprovider. MP is based on two Cube Cube1 and Cube2.
   Cube 1 has field item and key figure total quatity. Cube 2 has field item and key figure quatity1.
   I need a report which will show
                  Item quantity1 Total quantity   Percentage
Percentage = (quantity1/total quantity)*100.
I am surprised that percentage is X, though other two KF has value.
Is it the case that it is not possible to make summation, subtraction or any opeartion between two KF in different cube.
Could you please guide how to create percentage between two KF in different cube in a MP.
Regards
Deep

Hey Deep,
First confirm me what I understand... First you created a Mp which contains both KFs... Total quantity and Quantity one then in BEx query designer you created report in which you created a formula named "Percentage" and formula was (quantity1/totalquantity)*100... and in analyzer you are getting X instead of values. Then first try to check the properties of Formula (Percentage) in BEx query designer if decimal places etc are implemented and correct and second check if analyzer is reading these values as CHAR or Keyfigures and that you can check if there is a green arrow on left corner of each cell on both column's individual cells. If the green arrow kinda symbol is present there then it means that analyzer is not reading the values as CHAR thats why it is not doing any operation on both columns. Check these and let me know.

Floating point key figure does not clear completely with delete function

When executing a planning layout and/or a planning function, a floating
point key figure with a residual amount attempts to be deleted but does
not truly delete. The residual value remains.
We wrote an OSS note and below is the response and this was few months before.
Yes, unfortunately this is the effect of both the system design and the
database aggregation. So one has to live with these effects or you can
use other data types as packed numbers instead (type amount with data
type curr, here addition and deletion is always exact with the technicaltechnical decimals).
Since we have already configured and the data is stored in database, not sure if there is a way to convert to Packed numbers as well.
Did any one experience the same issue and is there a solution ?
Regards,
Kumar

Hi Kumar,
yes, I had the same experience once.
We did not find any better solution than use a "normal" key figure instead of the floating point.
regards
Cornelia

DSO - Key figure summation

Hi Experts.
I have a question on how BW is thinking when updating DSOs.
If I mark the keyfigures in the DSO to summarize, what will then be the effect.
If I compare to a SQL sentence I will sum the keyfigures for sure.
But will i Group by all the others info-object, or only the info-objects that are in the key area of the DSO.
Thank you in advance !

Husby,
In your update rule you will specify Addition or Overwrite. This will play the major role in how the data is summed up or not. Again this summarization will happen only for the key figures.
So if the keys match it will do the sum or not based on the condition set.
Hope this helps.
Alex(Arthur Samson)

Substraction of two key figures normalized to results not working as expect

Hi All,
I am having problems with getting the right result from a subtraction of two KFs which are "normalized to results" which means the KFs really have values expressed as percentages. The substraction that should be performed is of two percentages (e.g.: 87.298% - 85.527% = 1.77%) but my report prints out the result as "number of units" instead (e.g.: 87.298% - 85.527% = 71,514.00 EA). The two normalized KFs actually "point" to two stock KFs, hence the "number of units".
Thanks & Regards,
Venkat Vanarasi.

Hi,
The subraction will be carried out before doing the normalization of your KF's. So, it is displaying "number of units". Create a calculated keyfigure and subtract the KF's and in the properties of this calculated keyfigure, change the enhancement as "After Aggregation".
I hope this will solve your issue.
Regards,
S P.

Key Figure's Result Summation and SUMGT

Goal: I need to capture the reports Results for KF1 and KF2 to use it in the same report for further calculations. However, the report should include into Results calculations only the records that have KF1 or KF2 with values greater than 0.
Potential Solution: Create a Formula that uses Function SUMGT (or SUMCT, SUMRT) on the desired key figures and use conditions at the query level.
KF1 Property:     Calculate Result As SUMMATION
KF2 Property:     Calculate Result As SUMMATION
Report with No Conditions:
Year      KF1     SUMGTKF1     KF2     SUMGTKF2
2001     10        70                         10        90
2002     20        70                         20        90
2003     0          70                         30        90
2004     40        70                         30        90
Result   70        70                         90        90
Report with Conditions:
KF1 > 0
or
KF2 > 0
Year     KF1     SUMGTKF1     KF2     SUMGTKF2
2001    10         70                        10         90
2002    20         70                        20         90
2004    40         70                        30         90
Result 70         70                        60         90
Problem: When Conditions apply the SUMGT (as well as SUMCT and SUMRT) do not take them into consideration and includes in its calculations the excluded records as well.
Questions:
1. How can I make SUMGT (or any of the other tow) return a result that take into consideration the specified conditions? For KF2 the Result should be 60 and NOT 90.
2. Is there any other way I can capture the Results for KF1 and KF2 when the above specified conditions are implemented?

I think No of repair days is a characteristic..
What you can do is create a formula variable with user input. User will enter no of repair days in it.
Now create a variable on no of repair days of type customer exit.
In the exit read the value of the formula variable and assign it to that variable.
Restrict your key figure no of completed orders with that variable...

BEx Broadcaster Send button - No Broadcast Wizard with Key Figures in Rows

Working in BI 7.0 SP 16, we are having an issue with BEx Broadcaster. For a typical horizontal query (key figures in columns), the send button in BEx on the Portal works properly and returns the Broadcasting Wizard. However, when using a query in a vertical format (key figures in rows), the window opended by the send button displays the "spinning wheel" and never procceds on to the Broadcasting Wizard.
I have checked for SAP notes related to BEx Broadcaster and was not able to find anything relevant.
The same query was tested with the key figures in columns and in rows. The Broadcast Wizard comes up when the key figures are in columns, but not in rows. Since it was tested both ways with the same query, I am assuming that the issue is related to the orientation (horizontal vs. vertical).
Has anyone else run into this issue? Is there a known limitation, or a patch available? Does anyone have a BI system with a query you could flip the key figures from columns to rows and give it a try?
thanks,
-Shawn

Shawn,
I'm having my own issues with BEx Broadcaster in the Portal, but from BEx Query Designer - Query - Publish - BEx Broadcaster, the BEx Broadcaster Wizard is available in both cases (Key figures in columns and key figures in rows).
Kim

Drilldown on structure with hierarchy display shows additional result rows

Hi all,
difficult problem to explain, but I'll try:
- a structure for the rows axis
- the structure contains hierarchical elements
- each leaf node in the structure is defined as a characteristic C, restricted to certain values from a hierarchy
- additionally characteristic C is on the rows axis below the hierarchy (for detailed drilldown)
- for the row axis, "display as hierarchy" is selected (initial drilldown until structure only)
- on the columns some key figures
- zero suppression set to active for rows
So in Query Designer it looks like this:
1) Structure S
---> Subnode S1
> Element 1 (Characteristic C restricted to value V1 and V2 from hierarchy H)
---> Subnode S2
> Element 2 (Characteristic C restricted to value V3 and V4 from hierarchy H)
2) Characteristic C
Now what happens at runtime:
1. The user opens Subnode S1 and sees 1 row with cumulated values for V1 and V2
2. The user drills down further to Characteristic C
3. He sees 2 result rows below "Element 1": row 1 with value V1, row 2 with value V2
All fine.
4. Now the user opens subnode S2 and drills down to Characteristic C.
5. => The user gets 4 result rows for "Element 2":
    - one row with value V3 (as expected)
    - one row with value V4 (as expected)
    - one row with V1 and empty values (empty values OK, but complete row not expected!)
    - one row with V2 and empty values (empty values OK, but complete row not expected!)
So, apparently the OLAP processor has some issues when mixing structures with restricted elements, hierarchies and drill downs
Note: this is exactly the same behaviour as the last poster in this thread noticed:
[Re: Adding Hierarchy to Structure|Re: Adding Hierarchy to Structure]
Does anyone know about workarounds / solutions?
Hendrik
Edited by: HMaeder on Feb 25, 2010 5:31 PM

Advice from SAP so far is to go to BI Frontend SP11, which should solve the problem.
Edited by: HMaeder on Mar 17, 2010 10:04 AM

Key Figure Summation in Result Row with Cumulation Ticked

Similar Messages

Maybe you are looking for