Last Value Exception Aggregation

Hi.
I have a KF with excpetion aggregation with Last Value based on CALWEEK. I have to calculate the 'for the month' and the YTD value for this in a query. When I execute the query, the system fetches the last value for the month for 'for the month'. However, it gets the same last value for the YTD as well. How do I change this to get the sum of last value of all the months for the YTD Value. For example, if I am looking in sep 2008, the for the month value should be the last week of Sep 2008 and the YTD should be the sum of all the last values for months Jan -08 to Sep-08.
Cheers
Anand

Hello Vikram
One possible solution I can think of is to use an extra ODS in order to hold your data in an aggregated form that suits you. Unfortunately the exceptional aggregation behaviour does not work outside reporting thus in the transfer rules from your data provider to this new ODS you should add a formula checking whether the new record to be transfered to the ODS has a date newer than the ones already transfered in the ODS. Else it should skip the current record and proceed to the next one.
Another possible solution would be to use the APD and transfer the results of the query you are already playing in an ODS (this way you take advantage of the exceptional aggregation behavior) and by transfering your records to a second ODS you can achieve the aggregation you need.
Assign points if any of the above helped

Similar Messages

KF aggregation/exception aggregation options

Hi
There is one KF that has defined as
1)aggregation option SUM ,
2) Exception aggregation option Last Value
3) aggregation Ref char 0CALDAY.
4)cumulative value radio button s option is on in Cumulative/Noncumulative values option.
These options can be found in KF declaration in the second Tab.
I understand that from the query point of the KF will display last value/given calday. What is the use of aggregation option SUM (option 1 above)? can you give me one example please.
also one more question what is the use of Ncum Value with Ncum Value change?
Thanks
Vennela

Hi,
Here you have specified that aggregation type should be 'last value' for reference characteristic CALDAY. For all other characteristics, it shoule be SUM. That mean if calday is part of query, then KF will have Last value for CALDAY. If calday is not part of query, then it will be summation.
For ex, lets assume that we have calday, cost center as characteristics and head count as keyfigure. When you have both calday and cost center in your query, then it is going to display last value of KF head count in the result, which is practical.
if you have only cost center in your query, then head count value will be sum for that particular cost center. We might have many sales offices in a cost center, so head count will get aggregated for all sales offices under cost center.
Hope this clarifies.
Best Regards,
Rajani

How to determine the "Last Value" in exception aggregation

Hi gurus,
I have a KeyFigure with an exception aggregation -Last value- by time.
I report on a multiprovider ("containing" a infocube and a realtime infocube with BPS-InputLayout). I can correct separate Items with this BPS-Layout. So, at the end I have 2 values for one item.
So, by these facts, my report shows the the last value for the specific KeyFigure, but I expected that both values (the value in the infocube and the correction via BPS)are sumed up.
As this is due to the exception aggregation not the case, I could "overwrite" the normal value in the infocube with the BPS.
But SAP determines the normal value in the Infocube as "Last Value", not the one in the correction cube, which is entered via BPS.
How does SAP determine the "last value" as I can´t see any date...
Thanks in advance!

Thank you for your answer...
I got the soltion by myself.
I thought, Last Value means the last Value, depending on the time, but in my opinion the function last value should be called "Greatest Value".
All figures with the same value for the reference characteristc are aggregated anyway.

Exception aggregation - Last Value

Hi,
We are having requirement where we have a table in non R/3 system for SKU - Customer level closing stocks on particular day are maintained. We want to create a cube for the table in BI. This table contains entries for SKU + Customer for diff days. We want to show the closing stock of last(/latest) day for which Customer+ SKU record exists. To achieve this we have used Calculated Key figure on Closing stock with Exception Aggregation - Last value with ref to Calendar Day.
It woks fine only if I have Customer & SKU both used in query. But we have to show these stocks aggregated on Plant level. (Customer are linked to Plants and it is directly avbl in our cube). In this case aggregation does'nt work.
Lets say following are the closing stocks for SKU- M1 & 3 customers from Plant = 1101
          date-> 1/1/2007 2/1/2007 3/1/2007
Cust1             10                           15
Cust2                            20
Cust3             25
In above case if i have to see closing stock on 3/1/2007 for SKU-M1 @plant 1101 (sum of latest closing stock @ all customer sites under plant 1101), i should get = 60 (152025). But it gives me 15 only.
Could anyone explain how to design a query for this? Or in cube design/uploads it can be managed.
Regards,
Vikram.

Hello Vikram
One possible solution I can think of is to use an extra ODS in order to hold your data in an aggregated form that suits you. Unfortunately the exceptional aggregation behaviour does not work outside reporting thus in the transfer rules from your data provider to this new ODS you should add a formula checking whether the new record to be transfered to the ODS has a date newer than the ones already transfered in the ODS. Else it should skip the current record and proceed to the next one.
Another possible solution would be to use the APD and transfer the results of the query you are already playing in an ODS (this way you take advantage of the exceptional aggregation behavior) and by transfering your records to a second ODS you can achieve the aggregation you need.
Assign points if any of the above helped

First and last exception aggregation

From one of the doc, I got the below info:
For FIR, LAS Exception Aggregation,
If being used for cumulative key figures: Completeness of values with respect to reference characteristic necessary.
If the reference charac being used is non time char. then Sorting is done ascending according to key (internal presentation)
Whatdo the above two points mean?
Thanks
Simmi

hi Simmi,
can please point the doc ?
1st point, with respect to reference characteristic, i think it means which characteristic to be used for reference, normally date (time characteristic);
date----
key figure
01.01.2007---- 10
02.01.2007-----20
10.01.2007-----30
then FIR/first will be 10; and LAS/last = 30
2nd point
if reference characteristic is non time characteristic, e.g zcustomer, then sort is done ascending according to key, e.g
zcustomer-key---description
001----
Simmi
002----
Linggam
003----
Prakash
and we have data
zcustomer------key figure
003----
10
001----
25
002----
70
then consider to FIR/LAS, this will be sorted as
zcustomer------key figure
001----
25
002----
70
003----
10
then FIR is 25 and LAS = 10
hope it's clear for you and help.

Exception aggregation 'Average of all values'

Hi,
What is Exception aggregation 'Average of all values' wrt a reference characteristic. an how do I use it in Bex?
-Simmi

hi,
it determines how the key figure is aggregated in the BEx in relation to the exception characteristic, in your case it's averaged for all values.
another case sample maybe you need to report stock, which should not accumulated, but the last value, then you can choose 'last value', with reference chacarteristic to certain time characteristic.
you may also use it for 'calculated key figure' in BEx to get average value.
http://help.sap.com/saphelp_nw04s/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/6f/56853c08c7aa11e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/9d/76563cc368b60fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm

How to find the value of date char used as exception aggregation reference

Hi BI Gurus,
On a BEx report I need to list three things by material:
1)   the open (not yet delivered) Purchase Order quantities
2)   the PO quantity to be delivered next and
3)   the date that belongs to the next delivery
The model supports these data i.e. for each material I can list all open quantities by Purchase Order / Item / Schedule line and the scheduled delivery dates are also available as a characteristic.
Determining 1) is easy as the drilldown is fixed (materials only) the open quantities get summarized for all PO-s belonging to the materials.
To determine 2) I used a Calculated KF simply including KF 1) =Open PO Qty in the definition and setting Exception Aggregation (first value) with a reference char of the delivery date. This gives back the Open PO Quantity to be delivered first.
My question is about how to determine the 3rd value (actually this is not a KPI but a characteristic value). In other words, for each materials I would need to determine the first among all of the possible delivery date char values of the open PO Items / schedule lines. This is the date the quantity shown in the 2nd KPI will be delivered on.
Does anybody have an idea how to approach this issue?
Thanks for you help in advance,
Attila

Hi Olivier,
Thanks for your suggestion. I got a bit closer with the replacement path formula variable and the CKF. I tried to apply the same logic of KPI 2) but for some reason it did not work. Actually, it delivers the right value but only when 0SCL_DELDAT (Scheduled delivery date) is in the drilldown But what I need is the first delivery date by Material only, and without this 0SCL_DELDAT drilldown.
Any other ideas?
Thanks and bye,
Attila

Exception Aggregation (Average of all values 0) - Non cumulative KF

Hi Experts,
I am using the Exception Aggregation (Average of all values <> 0) on a Non Cumulative KF. Most of the times i am not getting the desired results but some times it gives me the desired result.
my doubt is whether we can use Exception Aggregation on Non cumulatives?????
Thanks for any help
boobal

Hi,
Non-cumulative valuesare 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.
Please check this document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d61b1e95-0501-0010-dfbe-a03970712ef1
Hope this helps.
Regards,
Mona
Edited by: Mona Kapur on Jan 17, 2008 10:45 AM

"last value" in the KF aggregation tab page

can u plz tell me what is the meaning of "last value" in the KF aggregation tab page. also what is use of aggregation reference char. please give explaination with example.
amit

Hi
Last value in KF Aggregation tab is
For example Amount is the Key figure with values 100,200,300,400
if u sekect last value
it will display 400 in the entire amount column..........

Exception Aggregation LAST

Hi all!
We use BCS and in my cube 0FISYEAR, 0FISPER3.
So i need to create KF like amount in the end of the period
I need to create Exception aggregate for my KF ?
Exception Aggregation LAST and Referen. char. 0FISPER3
Right?
Thanks!

Hello Vikram
One possible solution I can think of is to use an extra ODS in order to hold your data in an aggregated form that suits you. Unfortunately the exceptional aggregation behaviour does not work outside reporting thus in the transfer rules from your data provider to this new ODS you should add a formula checking whether the new record to be transfered to the ODS has a date newer than the ones already transfered in the ODS. Else it should skip the current record and proceed to the next one.
Another possible solution would be to use the APD and transfer the results of the query you are already playing in an ODS (this way you take advantage of the exceptional aggregation behavior) and by transfering your records to a second ODS you can achieve the aggregation you need.
Assign points if any of the above helped

Exception Aggregation (Average) displaying incorrect values after EHP1 Upgr

Hi All,
Exception Aggregation (Average) displaying incorrect values after EHP1 Upgrade in our BW system
We have recently upgraded the system to EHP1. After the upgrade some of the queries where we are using Exception Aggregation (Average) started giving the incorrect values.
Eg. We are displaying three Key Figures KF1, KF2 and KF3 (=KF1 %A KF2) against Store Hierarchy. In KF3 we are using Exception Aggregation (Average) on a characteristic 0PLANT.
There are 14 rows against 0PLANT and out of those 2 rows are blank for KF1, so for KF3. When it is calculating the average of these key figures its dividing the total value by 12 instead of 14 which is not correct in our case. Earlier it was dividing the total by 14.
So in this case 'Average' and "Average of all values <>0" are behaving the same way.
Kindly provide some inputs on this.
Best Regards,
Sachin Verma
+44 7506740018

Hi,
Thanks for viewing the thread. And happy to let you know that the issue was resolved.
The solution was:
Two formulas (local) were created, one including the formula variable with replacement path for ZD1, with exception aggregation on ZD1, and the other with formula variable with replacement path for ZD2, with exception aggregation on ZD2. Both these formulas are hidden.
Another formula (local) was created for u2018time takenu2019 = formula with ZD1 u2013 formula with ZD2, with exception aggregation total on u2018ZDOCNOu2019.
For the second instance, when one requires exception aggregation on records that has multiple values for keys, a nesting of formulas can be done displaying only the ones required.
For e.g. a formula with exception aggregation on say characteristic u2018item no.u2019 can be hidden, and included in another formula for exception aggregation on characteristic u2018document no.u2019. This is a typical case where one can achieve calculation before aggregation for a calculated key figure, formula or a counter.
Hope it might help someone, and saves time and effort for a similar issue posted.
Also would like to keep this thread open for exploring better solutions.
Regards,
Vijay

Last value balance

Hello
Infoobject:
- char: number
- keyf: used_value, balanced_value
number | used_value | balanced_value
9444     | 1                   | 30
             | 2                    | 28
              |5                    | 23
9555     | 2                    | 10
             | 5                    | 5
when i drill the caracteristic number the used_value and balanced_value make some sum
its come:
9444 | 8                 | 81
9555 | 7                 | 15
its wrong because I want only LAST VALUE for have my balance, not SUM
the correct would be:
9444 | 5 (?) | 23
9555 | 5 (?) | 5
(?) -> i dont know its make sense.. btw.. i want it make last value for balance_value
i tried to put on balanced_value keyfigure:
-> TYPE/Unit
Type/datatype: Amout
Curruncy : EUR
-> Aggregation
Aggregation: SUM. // another option are max or min.. they are maxium 3 (sum,max,min)
Exception Aggretion: LAST VALUE
Aggregatiom: 0CALDAY
CUmulative/NonComulative:
- Cumulative Val checkd
in another selection (NCUM. value....both) i dont have values to put, when i put f4, so i choose the 1rst one
i dont want to sum/accumulate, just want have last value work drilling, how can i do that?
Regards
Amit
Edited by: Amit Pratapcim on Nov 27, 2009 9:58 PM

Problem Solved.
I created with one characteristic timestamp
concateneted date and time
then exception putted that characteristic

Not showing last value in report

Hello,
I am having a report with new selection and i want the last value in result area and for this i have selected 'Calculated result as Last Value' in properties but it is showing me the summation of all value.so could you please tell me how do i get the value for this.I am using BW3.X.
Thanks & regards,
Anoop Chaturvedi

Hi Anoop,
You need to keep setting as calculate result as ' Last value' or exception aggregation to last value.
As you are in production, to check whether it is working or not in production, run the report in RSRT, go the key figure right click and go to enhanced menu, and then in propeties, and then in kf properties you can settings like calculate result as , no of decimal places, sorting(these options which you design in Query designer), make it as last value under calculate result as and transfer the selection.
This should work and then you make the change in dev and transport.
Regards
vamsi

Constant Selections and Exception Aggregation

Hi,
Can You please tell me
1) what is constant selections?
2) what is Exception Aggregations?
Thanks and Regards.
Naresh.

Hi,
example for the use of standard aggregation and exception aggregation for a key figure is a key figure for the non-cumulative value
with non-cumulative values such as warehouse stock, you want to total up the warehouse stock for various articles and warehouses (standard aggregation), but for the month you want to determine the ending inventory (LAST aggregation) (exception aggregation in regard to the time characteristic Calendar Month)
for more info go through the below link
http://help.sap.com/saphelp_nw04/helpdata/EN/d2/e0173f5ff48443e10000000a114084/content.htm
For constant selection go through the belwo link
http://help.sap.com/saphelp_nw70/helpdata/EN/46/91f0f090ea13e8e10000000a155369/content.htm
Regards,
Marasa.

Exception (Aggregation) in Hierarchy nodes results

Hi All,
We have a requirement to sum all values (as results in hierarchy levels) based on the value of a specific characteristics. example as below is what we want to achieve. Country, Product group, materials are all characteristics and this is viewed as hierarchy in the query. In each material there is a calculation components that will shown the value of Sales Qty, Price/unit and Amount. What we want is to sum up ONLY the Amount value and presented in the hierarchy nodes so that we can see how much sales we did by product group and subsequently by country as whole. If we drill across we will be able to achieve this but we want to drill down as we have the time characteristics and variances at the columns. and no, we do not want user to drill across the calculation components. This query is used in Integrated Planning for planning purposes integrated with BO and that is the structure of the planning layout we want. "Calculation component" is a infoobject that contains 'sales qty', 'price/unit' and 'sales amount' as master data values.
I have tried exception aggregation on calc component infoobject for 'LAST VALUE'. and it did capture only the Sales Amount value as result for node Calc Components. But the other results node State, country and Region also takes LAST VALUE.. which is not what i want. what i want is esseentially summation of all Sales amount for each calculation components by state, country and region.
                                                   Last Year | Variance   | Current Year |   Jan | Feb | Mar |......
Region X                                              200 (sum of all country's sales amount)
->Country A                                          200 (sum of all states' sales amount)
   -> State Y1                                          80 (sum of all components's sales amount)
       ->Calc Components Z1                    30
          - Sales Qty                                   10
          - Price/Unit                                     3
          - Sales Amount                             30
      ->Calc Components Z2                    50
          - Sales Qty                                     5
          - Price/Unit                                   10
          - Sales Amount                             50
   -> State Y2                                        120
       ->Calc Components Z1                   40
          - Sales Qty                                   10
          - Price/Unit                                     4
          - Sales Amount                             40
      ->Calc Components Z2                    80
          - Sales Qty                                   10
          - Price/Unit                                     8
          - Sales Amount                             80
any help would be appreciated...
eddie

Please try the below steps and I hope it should work for you.
Instead of calculated keyfigures,try to use local formula .Because i think sometimes CKF will not give the expected result if you use exception aggregation (not sure though,but i used only local formulas)
1. Create a first local keyfigure (Say F1)for the calculation and use exception aggreagation as 'Average' and reference characteristics as 'PDU'.
2. Create a second keyfigure ( Say F2) using the first keyfigure(F1) and use exception aggregation as 'Average' and reference characteristics as 'Sales Document', if you need the values based on average of the sales documents and hide the first keyfigure(F1)
I consider Sales document is the first level and PDU is the second level ( i mean lowest level) . Because you need to consider these sequencens as well when you design the exception aggregation.
Likewise you can create nested aggregations based on your requirements.
Please do let me know if it works.
Thanks.

Last Value Exception Aggregation

Similar Messages

Maybe you are looking for