Keyfigures and aggregation

Hi Gurus,
I have certain doubt regarding "Aggregation".
I know that every key figures has 3 tabs,
1. Data Type / Unit
2. Exception
3. Additional properties.
I have doubt with regard to the tab "Exception".
Please some one clearly explain that?
1. I hope aggregation does not have any effects on the fact table and it affects only the result row of a report? Am i right?
2. I know that we have standard aggregation (min, max and sum) and Exception aggregation based on a characteristic.
why does exception aggregation has (average, counter, first value, last value, etc) whereas standard aggregation has only (min, max and sum)? What is the significance of exception aggregation? Why do we relate it with a characteristic?
3. What are non cumulative key figures? Non-cumulative with non-cumulative change and Non-Cumulative with inflow and outflow?
A clear explanation of the above with some simple scenario is greatly appreciated.
Thanks and regards,
Lakshminarasimhan.N

Hi Lakshminarasimhan.N:
The documents below might help.
"Exception Aggregation in Business Explorer" article by Himanshu Mahajan.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b8ed5b-1025-2d10-b193-839cfdf7362a?quicklink=index&overridelayout=true
"Non-cumulatives / Stock Handling"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31?quicklink=index&overridelayout=true
Regards,
Francisco Milán.

Similar Messages

WebI issue with hierarchy display and aggregation

Trying to wrangle what looks like a defect in WebI's handling of hierarchy display and aggregation. We just completed an update cycle and are running BOBJ 4.1 SP4.
The hierarchy is a standard FM Commitment Item hierarchy in which both the nodes and leaves are Commitment Items (i.e. it uses InfoObject nodes, not text nodes). An example of one of these nodes looks like this in BW:
Cmmt_Item A - Node
    Cmmt_Item B - Leaf
    Cmmt_Item C - Leaf
Let's pretend Commitment Item A has $50 posted to it, B has $20 and C has $30. Analysis for OLAP handles this by adding a virtual leaf line to distinguish postings that are on the parent node like so:
Cmmt_Item A - Node       $100
    Cmmt_Item A - Leaf    $50
    Cmmt_Item B - Leaf    $20
    Cmmt_Item C - Leaf    $30
So you see both the total for the node ($100) and a line for each Commitment Items with KFs posted to them. Our users like this. They can easily see the aggregation and the breakdown.
WebI, on the other hand, will display it like this:
Cmmt_Item A - Node       $150
    Cmmt_Item B - Leaf    $20
    Cmmt_Item C - Leaf    $30
It doesn't create a separate line for the value of the parent node, but it does add it's value into the aggregate. Twice. Modifying the table with the 'avoid duplicate row aggregation' checkbox yields output like this:
Cmmt_Item A - Node       $100
Cmmt_Item A - Node        $50
    Cmmt_Item B - Leaf    $20
    Cmmt_Item C - Leaf    $30
We're about halfway there. While the top row now shows the correct aggregation and it creates a new line to show the distinct amount on the parent node, that new line appears on the same level as the parent. It's no longer clear that there's an aggregate and a breakdown. And attempting to expand or contract a node will now crash the report with one of those 'Error 16' messages.
Has anyone encountered this issue with hierarchies in WebI? This report was built from scratch in 4.1, so I'm not sure if this affects older versions or not. Or if it would affect any hierarchy that uses InfoObject nodes instead of text nodes.

Without a fix, the simplest workaround I can think of would be to restructure the hierarchy. It can't use postable nodes, so Cmmt_Item A - Node from my example would need to be converted into a text node and the postable characteristic added as a child on the same level as the B and C leaves.
This looks like it would affect anyone using hierarchies with postable nodes in a WebI report.
Another oddity in WebI's behavior here - even though the postable nodes show incorrect sums the sum at the root node is correct. So extending my examples from the original post:
Root Node                    $100
    Cmmt_Item A - Node       $150
        Cmmt_Item B - Leaf    $20
        Cmmt_Item C - Leaf    $30

Report with non aggregated and aggregated columns from different facts.

Hi,
We have got requirement as follows,
1) We have two dimension tables, and two fact(Fact1 and Fact2) table in physical.
2) In BMM we have made hierarchies for both dimensions, and are joins both logical fact table.
3)In fact1, we are having three measures of which we have made two as aggregation sum, and one is non aggregated(It contains character).
4)Fact2 have two measures, both are aggregation as sum.
5)Now here the problem arises, we want to make a report with some columns from dim and non aggrgated column from fact1 and and aggregated column fact2
How to resolve the above issue.
Regards,
Ankit

As suggested you really want to move your none-aggregated fact attributes to a logical dimension (using the same physical table as the logical fact). Map this in the BMM layer as a snowflake, Place a hierarchy on this dimension with (at minimum) Total -> Detail levels, then on the other fact table you want to include in the report, set the content level on your other fact measures to the 'Total' level for your new logical Dim and it will allow them to be present in the same report.

What are the major differences between a Access Switch and Aggregation Switch w.r.t Carrier Ethernet domain?

In a Carrier Ethernet domain,Could someone please help me understand what's the basic difference between Access Switch and Aggregation Switch both in terms of s/w and h/w functionalities. MEF deals OAM,CFM, EVC provisioning only at the access edge switches. Do we need to repeat all these at the aggregation level? or is it just used for routing purpose? Do we have a separate Fault Management at the aggregation level?

Duplicate posts. :P
Go here: https://supportforums.cisco.com/discussion/12137156/what-are-major-differences-between-access-switch-and-aggregation-switch-wrt

Upload text file to oracle table with checking and aggregation

Hi Friends,
I am new to ODI. I have encountered a problem which is specific to ODI 11G (11.1.1.6.3) to upload text file to oracle table with checking and aggregation. Would you please teach me how to implement the following requirement in ODI 11G?
Input text file a:
staffCode, staffCat, status, data
input text file b:
staffCodeStart, staffCodeEnd, staffCat
temp output oracle table c:
staffCat, data
output oracle table d:
staffCat, data
order:
a.staffCode, a.staffCat, a.status
filter:
a.status = ‘active’
join:
a left outerjoin b on a.staffCode between b.staffCodeStart and b.staffCodeEnd
insert temp table c:
c.staffCat = if b.staffCat is not null then b.staffCat else a.staffCat
c.data = a.data
insert table d:
if c.staffCat between 99 and 1000 then d.staffCat = c.staffCat, d.data = sum(c.data)
else d.staffCat = c.staffCat, d.data = LAST(c.data)
Any help on fixing this is highly appreciated. Thanks!!
Thanks,
Chris

Dear Santy,
Many thanks for your prompt reply. May I have more information about the LAST or SUM step?
I was successful to create and run the following interfaces p and q
1. Drag text file a to a newly created interface panel p
2. Filter text file a : a.status = ‘active’
3. Lookup text file a to text file b : a.staffCode between b.staffCodeStart and b.staffCodeEnd
4. Drag oracle temp table c to interface panel p
5. Set c.staffCat : CASE WHEN b.staffCat IS NULL THEN a.staffCat ELSE b.staffCat END
6. Set c.data : a.data
7. Drag oracle temp table c to a newly created interface panel q
8. Drag oracle table d to interface panel q
9. Set UK to d.staffCat
10. Set Distinct Rows to table d
11. Set d.staffCat = c.staffCat
12. Set d.data = SUM(c.data)
However, the interface q should be more than that:
If c.staffCat is between 99 and 1000, then d.data = the last record c.data; else d.data = sum(c.data)
Would you please teach me how to do the LAST or SUM steps? Moreover, can interface p and interface q be combined to one interface and do not use the temp table c? Millions thanks!
Regards,
Chris

Use of filters and aggregations based on hierarchy nodes in an update rule

Hello,
I need to calculate some indicators from a ODS (BW 3.5) that contain raw data to another one that will contain indicators. These figures are the results of the use of filters and aggregations based on hierarchy nodes (for example: all sales accounts under a node).
In fact, this is typically a query but I want to store these figures, so I need
I understood I have to use a start routine. I never did that before.
Could you provide me with easy-to-understand-for-newbies examples of:
- filtering data based on the value of an infoobject (value must be empty, for example)
- filtering and aggregation of data based on the appartenance to hierarchy nodes (all sales figures, ....)
- aggregation of the key figures based on different characteristics after filtering of these
Well, I am asking a lot ...
Thank you very much
Thomas

Please go through the following link to learn more on aggregates:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e55aaca6-0301-0010-928e-af44060bda32
Also go through the very detailed documentation:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
Regards,
Mahesh

Transformation logic for char and keyfigure from source keyfigures and flag

Hi All,
   My requirement is populate char and keyfigure values from source keyfigures and flag, which is like transformation of converting the Key Figure based structure to the accounts based structure. I am loading data from the cube1 to cube2,
cube1 structure with sample data:
Plant Furnace ZFurnace ZPlant1 Zplant2 Flag
P01     Blank      0                56        73      P
Blank     F01      335               0           0       F
Target Cube str with sample data
Plant Furnace    FS(Char)   KYF   Flag
P01     Blank         1               56       P
Blank F01            2               335    F
P01      Blank         3               73      P
ZPlant1, ZPlant2 and ZFurnace are the keyfigure tech.names.
FS has master data:
FScode KYF            Flag
1             ZPlant1        P
2             ZFurnace     F
3             Zplant2         P
While loading data from the source cube1 I need to read FS master data and than fill FS code in target cube based on source Flag and Key figure technical names.
I would be greatly appreciate with points if anyone can help me in writing the ABAP logic. The challenging part for me is comparing key figure technical names in cube1 with the FS master data key figure values.
Thanks.
Baba.

Hi All,
   Actually there will be 18 records in FS master data and there will not more than 18 Key figures. Is there any way I can hardcore the values and write small code.
something like:
if KYF = Zplant1.
     WA_FSCODE = '1'.
   WA_EU = source_fields-KYF.
WA_PLant = source_fields-plant.
wa_furnace = source_fields-furnace.
else
    if kyf = zplant2
Please let me know the sample logic with code. I greatly appreciate with points..
Regards
Baba

DP Disaggregation and Aggregation levels

Hi all,
I have a question regarding disaggregation and aggregation levels.
KFu2019s and disaggregation setup:
KF001:
Calculation type: I (not relevant)
Disag. Key Fig.: KF000 (not relevant)
Time-Based Disaggregation: K (not relevant)
Time-Based Disag. Key Figure: (not relevant)
KF002:
Calculation type: I
Disag. Key Fig.: Keyfigure001
Time-Based Disaggregation: P
We are now interested on the KF002. KF002u2019s disaggregation is based on KF001. I am trying to copy KF001 values to KF002 with a macro that is attached to a background job. Macro doesnu2019t do anything else than copy values from KF001 to KF002.
Background job setup:
Selection:
Sales organization: 2000AB
Location: 1000EF
Product: 1 to 2000 (consists 2000 products, including products that do not belong to above location)
Excluded values:
Customer group 1: 2500AB
Aggregation level:
Sales organization
Location
Product
Customer group 1
What I try to accomplish (through background job - mass processing):
I am trying to copy values with above setup so that the most detailed level which is Customer group 2 would have values through disaggregation. I have successfully copied values to product level, location level, sales organization level but the customer group 2 level values are not as KF001u2019s. Values are right in the SUM level, but not disaggregated right to customer group 2 level.
I get right results when I choose Customer group 2 to the aggregation level but this is not something we can do as it causes way too long runtimes. What I am also interested in is that how come the disaggregation does not work properly or does it? How can I get the disaggregation work so that I only have to select the aggregation levels which are defined in the selection and get proper results through disaggregation to customer group 2 level?
Thanks in advance,
Juha

Hello Juha,
You do not need another macro, just make the above change to your original one, and the macro should work.
Your aggregation level in the job should also be OK.
Since you mentioned that the values at detailed level are not the same as key figure 1, it sounds to me that the system did a pro rata disaggregation. Do you have the key figure 2 totally cleared out before copy? Since you're using disaggregation type 'I', it only disaggregates based on another key figure when the key figure value is initial.
So my suggestion is, you can try to change the key figure's disaggregation tyep to 'P' and check if the macro works.
Or if you have to use type 'I', you should add a step in the macro before the copy step, to initialize key figure 2 first.
To initialize a key figure, just put the row in the step, and for the 'Change Mode', select 'Initialization'.
Best Regards,
Ada

Difference between Restricted KeyFigure and Filter

Hi Experts
Could anyone tell me what is the main difference between Restricted Keyfigure and Filter.. Normally in which scenario we will use Restricted Key Figure and when we will use in Filter...
Thanks
Ajay

Restricted Key Figure
In your sales analysis report you have customer,material,sales qty,value for an year..You want to show current month sales one more column.You will create a restritcted key figure based on the current month and show it in the report.You will end up with a report
customer,material,sales qty,value,Current Month Qty,Current Month value.
Filters
The above report you want to show only the current month sales.You will create a filter where the 0CALMONTH = current Month with customer,material,sales qtym,value for the current month only.
Regs
Gopi

OEE Report: KPI formulas and aggregation rules?

Hello,
is there documentation about the formulas and aggregation rules used in the OEE Report? Customers will only trust the KPIs in this report if they can verify them.
Formulas & Aggregation
How are the KPIs calculated?
How are the KPIs aggregated, if a work center or resource type is selected instead of a single resource?
Data & Variables
Which data is used? Where do the variables used in the formulas come from? E.g. which tables and columns or which SQL SELECT statements are used?
There is just very little information about the OEE Report in the online help or in the "SAP ME for Discrete Industries" document. And the MII "OEE Report Action", where obviously all the magic happens, is a black box.
Best Regards,
Martin

Hi Daniele,
Is Saichand correct in assuming that you have SUM setup in the BMM layer? If so, follow Saichand's recommendation.
If you are specifying the aggregation in the Answer Request itself, then try this.
Let's say this is your situation:
SELECT DIMENSION, MEASURE_1
FROM CRITERIA1
UNION ALL
SELECT DIMENSION, MEASURE_2
FROM CRITERIA2
UNION ALL
SELECT DIMENSION, MEASURE_3
FROM CRITERIA3
UNION ALL
SELECT DIMENSION, MEASURE_4
FROM CRITERIA4
Change it to this:
SELECT 'CRITERIA1' CRITERIA, DIMENSION, MEASURE_1 MEASURE
FROM CRITERIA1
UNION ALL
SELECT 'CRITERIA2' CRITERIA, DIMENSION, MEASURE_2 MEASURE
FROM CRITERIA2
UNION ALL
SELECT 'CRITERIA3' CRITERIA, DIMENSION, MEASURE_3 MEASURE
FROM CRITERIA3
UNION ALL
SELECT 'CRITERIA4' CRITERIA, DIMENSION, MEASURE_4 MEASURE
FROM CRITERIA4
Then in the combined criteria, add two new measures:
new_measnure1 = SUM(CASE WHEN CRITERIA in ('CRITIERA1','CRITIERA1') then MEASURE END
new_measnure2 = AVG(CASE WHEN CRITERIA in ('CRITIERA3','CRITIERA4') then MEASURE END
NOTE: The syntax for the new_measure* may need to reference the saw naming convention, ie. saw0 = CRITIERIA, saw1 = DIMENSION, saw2 = MEASURE.
That should work out for you.
Good luck and let me know if this helps.
-Joe

Regenerate filter and aggregation with RSRT2

Hi Everybody,
We have a problem with a planningsequence, Global Support adviced us to regenerate the filter and aggregation. We're familiar with regenerating queries but not with filters and aggregations. Can somebody help me how te regenerate a filter with the transaction RSRT2.
Thanks,
Patrick
Answer Global support:
Regarding the issue,
As from the description in the message, you are using BI-Integrated
Planning. The problem occurs when you execute two planning sequences.
first sequence (FI01PV0069)
second sequence (FI01PV0070)
As per the description , the second sequence (FI01PV0070) is not workingas expected.
For this i would request you to please regenerate the 'filter' and the
'aggregation' which are used for these planning sequence.
You can regenerate the filter in transaction RSRT2.

Hi Patrick,
When you develop the input queries you should be pulling the filters/aggregation levels into the the Queries.
Though the message is to regenerate the Filters/Aggregation Levels.....inturn if you regenerate the Query everything below it gets re-generated.
Try that....you may make thing work.
Regards
Srinivas

Composition and Aggregation

hey guys
I have read the previous posts about composition and aggregation. And here is what i have got.
Composition: life time of objects got to be the same. For example there is a composition between carframe and a car. If the car gets destroyed the carframe woulod also get destroyed.
Aggregation: Life times of the objects are not the same, one oject can live even after the other object has been destroyed.
But i seem to get all these things in theory, but when it comes to coding am not able to translate these theories. To be particular i would want someone to help with me how these relationship can be coded
Thanks
K

Consider the following example :
Car has an engine, chairs, wheel, etc. it is clear
that this is composition, because "Car" is composed
of engine, chairs wheel and so on. but think about
what happens if you want to destroy the car, but
reuse its engine, thing that frequently happen when
you get your car smashed (didn't happen to be thanks
god). Anyway you destroy the car, but it parts stay
alive. so the "composed" objects lifetime can exceed
the "composer" object lifetime.
I think of composition and aggregation in the
following way :
if there is no meaning to the object without its
parts (parts of which it is
composed) then it is composition. if there is any
meaning for the object without its parts (like empty
paragraph (without words) in text, which can be left
empty till the wrighter have something to write in)
well, then it is aggregation.sometimes a car could be smashed and the engine would still be running, junkyard sells tires from wracked cars... all tha, however, has nothing to do with composition or aggration.
composition is a strong form of ownership, a car probablly needs to have an engine, some tirs etc in order to be sold as a car, so the engin, tirs are usually composed as composition. life time of them begins when the car is instantiated and until the instance vanishes. when a car is smashed or totaled, it is merely a state of the car instnace, like a flat tire, the car instnace still exists, so a running engine on a totaled car is ok.
usually if your object has a field referencing an object, that object is a composition, even the creation occurs earlier that the creation of the instance itself, such a case would be a DI: dependency injection. the destruction of an instance is a bit beyond the control of the composing instaance, that however dosnt matter, once the field loses the reference, we can think of it as the end of the life of the composed object. this is a bit different from C++ which allows you to invoke the destructor of the composed object. another difference is that you can have local objects, java objects all live in the heap area, no local objects.

Composition and aggregation implementation

how to write composition and aggregation implementation in java ?
As both of them contains another objects, how do we code to differentiate them ? I'm worried about implementation.
Are they same in implementation-wise but differ in concept-wise ?

user575089 wrote:
how to write composition and aggregation implementation in java ?
As both of them contains another objects, how do we code to differentiate them ? I'm worried about implementation.
Are they same in implementation-wise but differ in concept-wise ?I really think you nailed it and there is nothing more for me to add.

Difference between Compression and Aggregation

Hi,
Can anybody explain the Difference between Compression and Aggregation.Performance wise which is better and explain me in detail.
Thnaks,
Chinna

Hi,
suppose you are having three charecteristics in a cube say X,Y,Z..
Even for the records which are having the same combination of these charecteristics but are loaded with different request they won't get aggregated.
So when you go for compression the records , it deletes the request number, and aggregates the records which are having the same combination of these records.
Coming to the aggregates , if you build a aggregate on the charectaristic say 'X' then it aggregates the records which are having the same value for a particular charecteristic.
ex: say you are having the recrds as
x1, y1 ,z1......(some key figures)
xi, y2,z1,.....
x1,y1,z1,....
x3,y3,z3...
If you compress them, you will get three records.
If you go for aggregates based on the charecteristic 'X' you will get two records.
So aggregates will give more aggregate level of data than compression
regards,
haritha.

What is the Difference between Consolidation and Aggregation

Hi Masters
What is the difference between Consolidation and Aggregation? i think both are same, what is the exact difference in-terms of HFM and Essbase?
regards
Taruni

The differences lies in the mechanism used to calculate and store the value. Dynamic members such as parent accounts or customs, derived views, parent periods, or <Total> members in the value dimension are performed on the fly in the HFM app server's memory without any discrete action on the user or adminisrator's part. These are aggregations in this context, and are distinct from amounts that are calculated and then stored in the HFM database which are either the result of direct data entry (from data loads or journals) or calculated amounts resulting from HFM's rules. "Consolidation" in your question would be one of the stored, calculated amounts in HFM.
--Chris

Keyfigures and aggregation

Similar Messages

Maybe you are looking for