Non Cumulative KF VS Normal KF with exception aggregation

What is the purpose that is served by "non-cumulative key figures" and is not served by "normal key figures with exception aggregation"?
Inflow and Outflow can also be mapped into a single key figure at update rules level.
Why un-necessary complications like two additional KFs and marker update etc?
Why can't we store actual inventory value on daily basis in a NORMAL key figure with exception aggregation on time?
Also, I heard that data amount will be huge if you don't use non-cumulative key figure. I am not able to understand why?
I HAVE ALREADY GONE THROUGH ALL THE HELP DOCUMENTATION AND ALL THE PREVIOUS THREADS. I DID NOT GET ANSWER TO THESE QUESTIONS.
THANKS IN ADVANCE,
Anup

Anup,
Q1: Why can we not store the actual inventory against the person -
In this case you will end up storing day wise information of stock for the person / material - this will lead to increase of your data volumes depending on the scenario.
Example :
Day Level stock only
Record Structure :
Material | End of day snapshot Stock| date
pipe | 100|20.2.2008
pipe|100|21.02.2008
pipe|100|22.02.2008
pipe|80|23.02.2008
Here you can notice that the material pipe has been sold on 23.03.3008 and no sale has happened previously - however since your extractor will give you end of day stock for all materials you will get 2 additional records
In an opening and closing stock scenario
Opening stock
Marker|
pipe|100|20.02.2008
opening stock|closing stock
pipe|100|100
pipe|100|100
pipe|100|80
Here the values will get overwritten and compared with the marker and calculate that the stock is 80 or 100 depending on the date. I am not able to give a proper example but hope I have addressed it in part.
Also it is a Non *** KF because if you look at stock for pipe over 3 days you will get 300 in the first scenario - this is wrong
and for the next scenario with opening and closing stock
it will ideally be
100 ( your marker) -100100-100100-100+80 = 80
this calculation is done at runtime and gives the right output.
In the other case you can check stock only on a date basis and with the assumption that the stock data is current for that day.
Hope it addresses youor question.
Arun
Day 1:

Similar Messages

Non-cumulative initialization is not possible with historical data

Hi all,
While loading inventory cube.. 0IC_C03 .. after loading 2LIS_03_BX request get sucessful. while compress that request No Marker update. i getting following error msg.
Non-cumulative initialization is not possible with historical data
Regards
siva.

You sure you didn't use BF instead of BX? This messge indicates that you have historical data in your cube whereas BX only loads a fixed state at a specific point in time... Or maybe, did you initialize BX twice in R/3 without deleting the previous init, I don't know if that could cause that error but it's another possibility.

Forumla Variable with Exception Aggregation

Hello,
I've CKF in BEx, in this CKf there is replacement path Formula variable calculating number of documents.
Formula variable is replacing the value of Document number infoobject.
So definition of CKF is -> Replacement path Formula variable *1
Ckf is restricted to summation with Exception aggregation on Document number.
This implementation is working fine but issue is its taking lot of time in query ,like while checking RSRT olap :data transfer(Event ID) is taking lot of time,majority of the query execution time and counter is going somewhere around 100K.
Do you know is there a way we can implement this count in transformation?
Thanks in Advance!

Hi,
Doing SUM in transformation takes a long time as you need to read all the content in target.
So it is better to fine tune the query.
1) Is query running long time for small selections ?
2) Trace the query in RSRT and check where it is taking long time like Data base level , Application level
Thanks
Jagan

Query Problem With Exception Aggregation

Hello,
         I have two I/O 0Customer and 0Cont_Acct and also I have a Infoset made out of both. Here is the problem i am trying to solve,
I want to figure out the customers who has more than five contract accounts associated with each customer number.
Here is the solution I approached....
    1) Created a formula variable counter on the KF # of data records (which is provided in the Infoset automatically ) with exception aggregation total while referencing the contract acct I/O.
   2) Kept my customer # and Contract acct on my rows area.
The results I am getting is less than satisfying. I am expecting   this output below.
Customer #                 Cont Acct                  Total No of Cont.acct
A                                  1001                                1
                                     1002                                1
                                     1003                                1
                                                                              3
B                                  1007                                 1
I would appreciate anybody's help in this. Thanks a lot.
-A

Hi,
We have the same problem and raised an OSS ticket. They replied us with the note 1257455 which offers all ways of improving performance in such cases. I guess there s nothing else to do, but to precalculate this exception aggregated formula in data model via transformations or ABAP.
By the way, cache can not help you in this case since exc. agg. is calculated after cache retrieval.
Hope this helps,
Sunil

Problem with Exceptional Aggregation

Hi Gurus
I have problem with Exceptional Aggregation.I have a cube which as following data
Plant , Fromcostcenter,ToCostcenter, g/l,fiscalyear/period, allocation %,amount
1             101234            102355       888881      001/2006            10       1000
1             101234            102355       888881      002/2006            10       1000
1             101234             102345      888882      001/2006            10       1000
1             101234             102346      888893       001/2006            90      1000
1             101234             102346      888893       002/2006            90      1000
1            101234             102346      888984        001/2006           90       1000
I need summarized report as follows
Fromcostcenter tocostcenter allocation%
101234                   102355         10
101234                   102346          90
But iam getting report as follows
101234   102355 30
101234   102355 270
The allocation% keyfigure should not be accumulated, so for this i specified Exceptional aggregation but not worked.
Any Suggestions,please help me.
Thanks
Raghu

Hi
I am also having same problem. Did you get a solution for your problem? Can you please tell me how did u manage to display 10 and 90 instead of 30 and 270?
I also tried exceptional aggregation if more than one value. but not working.
Thanks

Query issue with exception aggregation

Dear all,
I have to solve the following reporting issue with BEx:
Cube Structure:
Cube A:
Characteristics: Company Code, Article, Distribution Channel, Customer, FiscalYear/Period
Key-Figures: Sales Val., Sales Qty.
Cube B:
Characteristics: Company Code, Article, FiscalYear/Period
Key-Figures: COGS
I simply want to multiply: Sales Qty@COGS = NODIM(Sales Qty) * COGS,
but this calculation should be valid for all characteristics of my cube A, even if I do not have them available in Cube B (like Customer and Distribution Channel). Additionally the calculated totals of my characteristics must be correct so that I can apply in second step a Margin Calculation: Sales Val. - Sales Qty@COGS which is valid on single level, as well as on total level.
I started to setup calculated key-figures
COGS1 = NODIM(Sales Qty) * COGS with Exception aggregation TOTAL by Company Code
COGS2 = COGS1 with Exception Aggregation TOTAL by Article
and this worked fine for both characteristics. If I use COGS2 in my report I get correct figures in a drilldown by Company Code and Article.
I enhanced the calculation by
COGS3 = COGS2 with Exception Aggregation TOTAL by Distribution Channel, but the result in this case is 0. I guess the result is 0, as the characteristic Distribution Channel is not availble in Cube B.
Any ideas how to solve this? Is there probably a different (more elegant) approach, as I fear that having all the exception aggregations my query runtime/ressource consumption will be awful.
Thanks for any idea,
Andreas

Hi,
You should define a new selection for COGS having Constant Selection on DC as defined in following link for PRICE with CUSTOMER.
[http://help.sap.com/saphelp_nw70/helpdata/en/46/91f0f090ea13e8e10000000a155369/content.htm]
and then apply your formulas....
hope it will solve the problem...
Regards.

Query Performance with Exception aggregation

Hello,
My Query Keyfigures has exception aggregation on order line level as per requirement.
Currently cube holds 5M of records, when we run query its running more than 30min.
We cont remove exception aggregation.
Cube is alredy modeled correctly and we dont want to use the cache.
Does anybody can please advice if there is any other better approach to improve query performance with exception agg?
Thanks

Hi,
We have the same problem and raised an OSS ticket. They replied us with the note 1257455 which offers all ways of improving performance in such cases. I guess there s nothing else to do, but to precalculate this exception aggregated formula in data model via transformations or ABAP.
By the way, cache can not help you in this case since exc. agg. is calculated after cache retrieval.
Hope this helps,
Sunil

Problem with exception aggregation

Hi forums,
Can any one help in this issue?
We checked the data in the ECOM cube for the order 63349312 where it is giving 6 records eventhough we are deleting the adjacent duplicates of the order number in the start routine. (Is it like the deletion of adjacent duplicates happen in data packet level instead of happening in the entire cube level? B'cos the same order might present in the different packets.)
    Hence the data is aggregating for the key figure, 'Number of Days' in the ECOM report. But if we check the keyfigure properties in the RSA1, there we selected the Exception Aggregation as 'First Value' and aggregation reference char as 'ZN_CORD' (Order number). Still it is aggregating the number of days value in the report.
Regards,
Charan.

Hi Rohit,
         We are doing same procedure as you mentioned. We assigned order number as refer characteristic to keyfigure No. of days in infi object level. But this operation is not working in report level
      Order number     ZCUDATE                  ZN_GSTRP            ZN_CORDKF     ZN_DAYSKF
        63349312     18.01.2009     01.10.2008     1,000     109
        63349312     18.01.2009     01.10.2008     1,000     109
        63349312     18.01.2009     01.10.2008     1,000     109
        63349312     18.01.2009     01.10.2008     1,000     109
        63349312     18.01.2009     01.10.2008     1,000     109
        63349312     18.01.2009     01.10.2008     1,000     109
I want o/p as
Order number     ZCUDATE                   ZN_GSTRP               ZN_CORDKF     ZN_DAYSKF
        63349312     18.01.2009     01.10.2008     1,000     109
but it is showing as
Order number     ZCUDATE                      ZN_GSTRP     ZN_CORDKF ZN_DAYSKF
        63349312     18.01.2009     01.10.2008     1,000            676

Cumulative and Non Cumulative KF

Hi all,
 What are Cumulative and Non Cumulative KFs. How do we create it and where do we use them?
Thanks in advance,
Sekhar

Hai Sekhar...
Some of the Information Given Below......
Key figures:
1. Cumulative Vaules
2. Non Cumulative Values
Cumulative Values:
 Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period specific Values).
Example:
 Revenue
Non Cumulative Values:
 Non Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
 It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non Cumulative keyfigure with Associated Single Delta:
 If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
 This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
Website Addresses For Non Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/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 it Helps......
BalajeeKannan

Non cumulative KFS

Hi Experts,
can any one pls send some non cumulative KFS, with scenario.
With Thanks&Regards.

Hi Raghav,
Have a look at the help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Go through these.
Re: Types of non-cumulative keyfigures
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
See the following threads
non-cumulatives KF in reporting
Re: use of non cumulative keyfigure
Re: When do we use Non-Cumulative values?
Key figures:
1. Cumulative Vaules
2. Non Cumulative Values
Cumulative Values:
Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period specific Values).
Example:
Revenue
Non Cumulative Values:
Non Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non Cumulative keyfigure with Associated Single Delta:
If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
For Non Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Check this very useful docu.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
Hope this helps.
Regards,
Ravikanth

What is the difference between cumulative and non cumulative keyfigures?

Hi Friends
What is the difference between cumulative and non cumulative keyfigures, when we r using the cumulative and non cumulative
Regards
Ravindra

Hi Ravindra,
Have a look at the help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Go through these.
Re: Types of non-cumulative keyfigures
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
See the following threads
non-cumulatives KF in reporting
Re: use of non cumulative keyfigure
Re: When do we use Non-Cumulative values?
Key figures:
1. Cumulative Vaules
2. Non Cumulative Values
Cumulative Values:
Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period specific Values).
Example:
Revenue
Non Cumulative Values:
Non Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non Cumulative keyfigure with Associated Single Delta:
If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
Website Addresses For Non Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Check this very useful docu.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
****Assign Points If Helpful****
Regards,
Ravikanth

When do we use Non-Cumulative values?

Hi BW Experots?
When do we use Non-Cumulative values?How is it related with exception aggregation
Please tell me .
Thanks in anticipation.

Hi,
Taken from std, doc....
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.
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
Check this out...
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
Pls. assign points if this helps you.. ****
Thanks,
Raj

Non cumulative key figures

Hi
I understand that there are 3 types of non cumulative key figues with these optiones.
1) cumulative KF with exception aggregation
2) with associated single delta(cumulative)
3)with associated IN and Outflow(cumulative)
I know that we use type 3 in inventory. Has any one used option 2 with Non cumulative KF with associated single Delta?
Please let me know the scenario where it is useful?
Thanks
Vennela

Vennela,
It all boils down to the definition of what cumulation is ...
cumulation refers to straightforward addition of key figures along given filter conditions in the query. This is similar to the sum() operator in an SQL query.
However people will need different kind of aggregation at different points in time other than the standard aggregation / cumulation that is used regularly.
Coming to non cumulation :
1) cumulative KF with exception aggregation
This refers to predominantly formulae - for instance - count of all customers whose sales > 0 - but the report is does not have customer in it and the result is expected. This would mean that the calculation essentially happens at a different level as opposed to the actual query and the key figure cannot be simply summed up.
2) with associated single delta(cumulative)
This is somewhat at a higher level of granularity as opposed to case 3 where you look at all movements. An example here would be You have opening stock and then you get only the debits and credits for the day as opposed to getting stock for all movement types.
Somethign like
opening Stock for the day = 100
Outgoing stock = 30
incoming stock = 10
Here movment type information is omitted and instead is consolidated in the source system itself.
3)with associated IN and Outflow(cumulative)
This has been discussed many a time and can be found by searching the forums...

Non-Cumulative keyfigure example

Hi all,
 To test for non-cumulative keyfigures I have modeled a keyfigure noofemployees and below is my model
Infocube has following characteristics, timecharacteristics and keyfigures
Charteristics: Companycode
TimeChar: 0calmonth
Keyfigures: salesrevenue and noofemployees
My infosource has following infoobjects
Companycode,0calday,salesrevenue,nofoemployees
In update rules, I wrote a formulae(0calmonth2) to convert 0calday to 0calmonth.
I want to generate a report to know for every company, its monthly sales and number of employees.
I created numberofemployees as a cumulative keyfigure with exception aggregation as Maximum(to get the maximum number of employees in one month instead of aggregating the values). I don't know if I am doing something wrong, but my keyfigure noofemployees is aggregated for each month.
Please let me know if I created the keyfigure noofemployees correctly.
thanks,
Sabrina.

Hi Sabrina,
A non-cumulative keyfigure can be modeled in BW either using
-a cumulative keyfigure that stores the non-cumulative value changes of the non-cumulative keyfigure or
-Two cumulative keyfigures which represent the inflow and outflow values of the non-cumulative keyfigure.
The keyfigures used to define the non-cumulative keyfigure - keyfigure for non-cumulative value change or keyfigures for inflow and outflow - should themselves be cumulative keyfigures and have the following properties.
 Standard aggregation -> Summation
 Exception aggregation -> Summation
So as per the definition you first create a cumulative Key figure to capture the non-cumulative value changes of the non-cumulative keyfigure.Say ZKF1 and assign following properties:
Aggregation: Summation
Exception Aggregation:Summation.
Now create a Non-cummulative Key Figure say ZKF2 and assign following properties:
Aggregation: Summation
Exception Aggregation:Last Value
Non Cummulative Value Change:ZKF1.
This will give you non-cumulative keyfigures "number of employees" correctly.
Hope this helps.Please grant points if it solves your purpose.
Regards,
Ashish

Non cumulative cube

hi,
i have a problem in changing the fields in validity table.
in cube
i went to extras->maintain non cumulative values
in that along with 0calday i have ticked two more fields.
now i want to remove those fields from validity table.
but if i click on change and went to 'maintain non cumulative values'
it is in display mode.
is there any way to add or remove a field from validity table?

Hi,
I have copied 0IC_C03 to zic_c03 and able to change the settings for 'Maintain non-cumulative values'.
I feel in your case make the update rules inactive and try to change IC then i thnk u will able to change the values for 'Maintain non-cumulative values'.
Hope the information is useful, if yes please provide points.
Regards,
Navi

Non Cumulative KF VS Normal KF with exception aggregation

Similar Messages

Maybe you are looking for