NON CUMMULATIVE KEYFIGURE

hi everybody & kalpana,
i need brief notes regarding Non-Cumulative keyfigure.start routines & update routines.
plz help me in this issue.

Hi
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.
How you model the folder for non-cumulatives in the BI system depends on your scenario. According to how often non-cumulatives change and the total number of objects for which you want to calculate non-cumulatives, you should choose one of the following two options:
Non-Cumulative Management with Non-Cumulative Key Figures:
If the non-cumulatives change infrequently, you should choose non-cumulative management with non-cumulative key figures.
If you use non-cumulative key figures, an absolute non-cumulative value (the marker) and all non-cumulative value changes are saved in the fact table of the InfoCube. In this way, the retention and volume of data in the data load process is optimized. A data record is then only loaded to the InfoCube if a non-cumulative changes because of a transaction. Non-cumulatives can then be evaluated at any time in queries, using non-cumulative key figures.
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
If you previously worked with the ABAP form routines of the update rules and transfer rules, you have to familiarize yourself with the differences in working with routines in the transformation.
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
example
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm
end routine
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/c3963dfbde4dede10000000a422035/frameset.htm

Similar Messages

Non-Cummulative KeyFigures Usage at Aggregation Level in IP

Dear Team,
I am getting following error while selecting Non-Cummulative Keyfigure at Aggregation Level in IP
InfoObject 0CFMF0902 (version A) is not compounded
Aggregation level ZCFMAG1 is inconsistent.
I have selected the Key Figure which is using by this Key Figure and also selected the Unit Loc Currency , eventhough I am getting the above error.
If anybody aware of this problem or if there is any alternative way to use Non-Cummulative Key Figure , kindly reply to this.
Best Regards,
SG.

SAP Note 1323302
We cannot use Non-Cummulative Key Figure at Aggregation Level in IP.
I have to get opening balance in each month without using Non-Cummulative Key Figure and I have to use that for futher calculation in FOX. Can anybody give me idea how can i get it.
Best Regards,
SG
Edited by: SG on Dec 29, 2009 2:55 PM
Edited by: SG on Dec 29, 2009 2:57 PM

Non-cummulative KF wih NCum value change

hi,
Could anyone tell me the difference between the types of non-cummulative keyfigures
Non-cummulative value wih ncum value change &
Non-cummulative value with in and out flow
Kindly give me an example for the first one, I am pretty ok with the inflow n outflow type.
Regards,
sujai

Hi
A noncumulative value is a non-aggregating key figure, on the level of one or more objects, that is always displayed in relation to time. Examples of noncumulative values include head count, account balance, and material inventory. These are noncumulative in respect to time..
For example, you cannot add inventory for this month and inventory for next month to get total inventory.
There are two ways to manage these kinds of key figures. One option is to load the balance every night. The other, a more complicated and powerful solution, connects normal key figures to track the delta changes in the balance key figure. In the inventory example, this might be a key figure called Inventory Movements or two separate key figures called Inventory Adds and Inventory Subtracts. These key figures would be added to the initial balance key figure at query runtime to determine the balance in any
specific time period.............
Now .........Total sale of the Month will be a Cumulative Keyfigure.....
Non-cummulative value wih ncum value change
The key figure is a non-cumulative value. An additional key figure belongs to this key figure, which displays the non-cumulative value change.
Only those values for selected times (markered curves) are saved for the non-cumulative value. The values for the other times are calculated on the basis of a markered curve and the non-cumulative value changes in between.
Non-cummulative value with in and out flow
The key figure is a non-cumulative value. Two additional key figures belong to this key figure, which display the in- and outflow of the non-cumulative value.
Only those values for selected times (markered curves) are saved for the non-cumulative value. The values of the remaining times are calculated on the basis of the value in a markered curve, and the non-cumulative value inflows and outflows inbetween.
Santosh

Cummulative and non cummulative

Hi all,
Can we add cummulative and non cummulative keyfigure and send that result to datatarget.
Is it possible to do addition non-cummulative and cummulative
Regards
Narendra

Hi reddy,.
Yes, you can.
Cumulative KF at query level are same as non cumulative.
Cheers
Raj

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

Cummulative and non cummulative cubes

Hi
what is the difference between cummulative and non cummulative cubes and key figures

hi
check this...
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
also see the thread for example,
Non-Cumulative keyfigure example
cubes which have cummulative key figures are cummulative cubes.
hope it helpss..
cheers..
Message was edited by:
tarun bafna

Non- Cumulative KeyFigures

Hello Forum.
We have a non cumulative key figures with and Inflow keyfigure and an outflow with the aggregartion propery to SUM.
Can you please suggest how to verify the output of the non cumulative keyfigure ?
Is there any way to check the values of this non cumulative keyfigure ?
Thank you in advance .
Regards

Hello,
Possible verification methods are described below.
We recommend verification at plant/material number level (MatNo).
I. Verification of data from the 2LIS_03_BX or 2LIS_40_S278 DataSource
- Execute a corresponding query in BW.
- Use transaction code (TAC) LISTCUBE in BW to select the corresponding MatNo or plant (see Note 629451) and compare the data.
-> If problems occur at this point, there may be a BW technology problem (OLAP processor).
- Now compare the data with R/3 TAC MC.9 and MB5B.
-> If problems occur here, you should also check the PSA contents:
   -> TAC SE16
   -> Table RSTSODS
   -> Selection in the ODSNAME field: "2LIS_03_BX*"
    -> The ODSNAME_TECH field specifies the name of the database table in the PSA - if there are several hits, you can find the corresponding suffix of the source system in the PSA tree.
   -> TAC SE16
   -> PSA database table
   -> Select the data of the corresponding request (you can find this in the InfoCube administration view)
Differences between PSA and InfoCube contents indicate problems in the update (you can use the debugging for the update to check this in more detail).
Differences between PSA and TAC MC.9/MB5B suggest incorrect data extraction. Duplicate or missing stocks indicate technical problems during the data transfer.
I. Verification of data from the 2LIS_03_BF/UM DataSource
- Execute a corresponding query in BW.
- Select the corresponding MatNo or plant in BW using TAC LISTCUBE (see Note 629451) and compare the data.
-> If problems occur at this point, this suggests a BW technology problem (OLAP processor).
- Now compare the data with the R/3 TAC MC.9
- If there is a difference between the stocks, compare the movements, preferably take of note of the month in question and whether it is a receipt or an issue.
- Now compare TAC LISTCUBE in BW with TAC MB5B in R/3, a comparison for exact days should identify incorrect, duplicate or missing documents (select the "Valuated stock" option in TAC MB5B to find records in the BW where the storage location is empty)
- Now check in which format the document number is found in the PSA.
-> In this case also, the reason may be an error in the update or problems in the data extraction.
Consider the logic for determining the transaction keys of receipts/issues (Note 492828).
See these OSS Notes,
SAP Note 745788 Non-cumulative mgmnt in BW: Verifying and correcting data
SAP Note 352344 Process key + reversals in Inventory Management
Thanks
Chandran

Non-cumulative keyfigures in virutual multi providers in BI-7.

Is it possible to use non-cumulative keyfigures in virutual multi providers in BI-7? The Non-cumulative KFs are working in the cube. But when we create a virutual MP that contains this cube. They all are showing zero. Is this supported at all? Is there a note that we need to apply? Please help! This is BI-7.
Thanks.

Hi,
Do not use more than one InfoCube with non-cumulative key figures in a MultiProvider since this may result in incorrect numbers in the query.
Refer to SAP Note 690475 on SAP Support Portal.
Refer
http://help.sap.com/saphelp_nw04s/helpdata/en/43/5617d903f03e2be10000000a1553f6/frameset.htm
Thanks,
JituK

Cumulative and Non Cumulative Keyfigures

Hi,
What are Cumulative and Non Cumulative Keyfigures..? and
what is the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
Can you please tell eloborately?
Regards
Naresh.

Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,

Non Cumulative keyfigure

Hello Gurus,
what customisation should i have to do if i have to use non-cumulative keyfigure in cube.
What is the validity table for non-cumulative keyfigure of non-cumulative cube.
hope to have details..
Regards,
BPNR

BPNR
You just need to do check mark in your cube under keyfigur tab detail View.
Hope this helps
Thanks
Sat
Check this link if it helps
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm

Issue due to Non Cumulative Keyfigures

Hi All,
I have created a ZCube that gets data from Purchasing and Stocks Cubes. This Zcube has got the Non cumulative Keyfigures 0TOTSTK and 0VALSTCKVAL that are mapped from the Stocks cube in the transformations.
Apart from standard cubes, I have got Transformations from a DSO to the ZCube, I defined these Keyfigures as No transformations.
Data loads are done and data comes into report with an error.
The Validity Interval has the inital value as lowerlimit.
Diagnosis
The initial value has been found as the lower limit of a validity area. This can lead to performance problems and cause queries to terminate, because potentially, non-cumulatives can be reconstructed at any point within the validity interval.
This error occurs if data is loaded to a non-cumulative cube, where the time-reference characteristic is intial (blank).
This error message can also appear when the non-cumulative cube is completely empty.
System Response
Procedure
Check the data in the InfoCube and if there is a request containing data records where the time-reference characteristic is initial (blank), delete this request and reload the request data, with the appropriate time, into the InfoCube.
Is there any chnge to be done in the transformations at DSO level for the non- cumulative keyfigures to overcome this error.
Plz Help.
Thanks in Advance
Regards,
Sudha

Hi all,
Thanks for the Info.
I have mapped all the fields from DSO to cube.Dso doent hold the non cumulative keyfigures.so they are left blank.
I have loade the data to zcube now by deleting the earlier requests. Data is loaded.
I can find entries now in RSDV.
I just have one question to be clarified.. I suspect the issue is with the time Reference char's.
When I do mappping from 0IC_C03 to ZIC_C03 i don't see the mapping for 0CALWEEK, 0CALMONTH, 0CALYEAR. I don't see these fields for doing a mapping though these fields are present in the cube.
Same is the issue wit the DSO also. I dont see the above fields to map in the target.
I don't understand why there are not displayed while creating transfformations though they are in the target.
Please let me know if you understand where I am going wrong.
Sudha

What is Non-Cummulative Cube

Hi..All
1) Can any one explain What is Non-cummulative InfoCube?
2) Why is there a restriction of 16 Dim tables in an Info Cube and 16 key fields in an ODS?
With Regards
Jonn
Due points will be assigned for best answer

Hi Jonn,
1)I do not have idea about any Non-cummulative InfoCube ,but I know that there is concept, kind of cummulative /Non-cummulative Key figures.
please go through,
2) Restriction of 16 Dim tables in an Info Cube and 16 key fields in an ODS is because of the database limitation.
For example like as we know that fact table is having 16 dim IDs which are behaving as composite key as of 16 foreign keys.
Database concept is that ,there is limitation to keep maximum 16 primary keys on one table.
This is limitation of database thats why we have this cube and ODS is having limitation.
Please reward if worth!!
With Regards

Not able to compress the init request for non cummulative cube

hi sdn
i'm not able to compress request for stock init( for some plants) in non cummulative cube with a marker update the job is cancelled when I see the log it is showing no. of sql lines
and job terminated.
what may be the cause of the problem
ruabne

You need to restrict the number of the request that you are going to compress for every job. Try also to enlarge TableSpace, in particular the temporary TableSpace, that you can subsequently reduce.
Consider that any other job, like query from user or other uploads, reduce the speedof the compression.
Hope it helps.
Regards

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

How does Non-cumulative KeyFigure Works ?

Hi, experts !
What's the difference between the non-cumulative values of summation and of last value?
And how does non-cumulative value with in-flow and out-flow works?
Does anyone have relative documents?
Plz post a copy to my e-mail: [email protected]
Thank you very much !!!
Looking forwards !

Hi, Can you also send me the doc. My Id is [email protected]
Thanks,
Sam

NON CUMMULATIVE KEYFIGURE

Similar Messages

Maybe you are looking for