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

Similar Messages

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

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

Aggregation level doesnt support non-cumulative kf

hello
IP planer generates an error "Infoobject 0AMOUNT (version A) is not compunded" when I include non-cumulative kf into aggregation level of infoprovider.
KF ZAMOUNT is non-cumulative and depends on 0AMOUNT. Both kf are active.
I need non-cumulative kf just for informative purposes, i dont want to plan with this kf.
Does anyone know is it possible to use non-cumulative kf in aggregation level of multicube?

Hi,
no non-kumulative key figures are not supported in aggregation levels.
But one can use a MultiProvider on the cube with the non-cumulative key figure. Create an aggregation level for the objects you want to plan and use this aggregation level also in the MultiProvider. Then you can integrate the 'plan objects' and the non-cumulative key figure in a query defined on the MultiProvider.
Regards,
Gregor

How can u do aggregation level in keyfigure give detail steps

how can u do aggregation level in keyfigure give detail steps

HI Deba,
PLz check here.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
Regards,
Vijay.

Empty Aggregation Level - Need user to put in entries when none exist

Hi, I have an aggregation level for Version, Material Family, and a Key Figure. The Cube has no data planned at this level when the user 1st starts to work with their version.
I am trying to find a way to get the user to be able to input a Key Figure Value for some Material Families.
I would either like the users to see a list of Material Families and input the Key Figure Next to the Material Family
or
I would like the user to input a Material Familly and the associated Key Figure for each family value they have. Thus creating entries for the Material Family Values they would like to run a planning function on.
I have been able to create a query that shows a list of Material Families and an input enabled Key Figure Field. When I put the value in and Save the Value gets saved to "Unassigned" Material Family even though I put the Key Figure Value next to a displayed Material Family.
I have also been able to create a query that does not show the Families but has an input record. The same thing seems to happen. I input a family value and key figure value, save, and it gets saved to "Unassigned".
I have tried working with Characteristic Relationships, but it doesn seem to work when I'm just working with 1 characteristic like Material Family. Here's an example of my issue: Link:[http://i27.tinypic.com/n1a1wn.png|http://i27.tinypic.com/n1a1wn.png]
Am I going about this in the right Way
Is there a way to have the user add data where there is none?
It seems I have such a simple scenario.

Hi, Thanks for following up. I simply need to have users input the Key Figure Values for a single "Family" Characteristic. I am simply trying to create "Family" Records for which no planning data exists and it is totally eluding me. The Aggregation Level only has Family, Version, InfoProvider. Version and InfoProvider are in the filter.
I have successfully created an input enabled query and also added a input line at the bottom. If I input input a value next to a Family or if I input a new family and save the data the values just end up in the unassigned family. To get the families to show up in the query I have the Family Characteristic Advance settings (in query settings) set to Master Data
Please take a look at the below link for an example.
Please let me know what I have to do so users or myself can create Family records in my aggregation level!
Link: [http://i25.tinypic.com/1qmz5w.png|http://i25.tinypic.com/1qmz5w.png]

ASO Build Rule - "Level Usage for Aggregation"

When Building ASO (9.3.1) Dimensions via Rules, we wish to set the “Level Usage for Aggregation” of a member in the data file.
You can set a Rule Field Property to Aggregate Level Usage, though it not clear what value should be inserted in the Data File to specify one of the four options below for a member
•     Consider All Levels
•     Do Not Aggregate
•     Consolidate Top Level Only
•     Never Aggregate to Intermediate Levels
Inserting the full name does not work and we cannot find any reference to the Aggregate Level Usage property in the Dbag.
Can anyone advise on the correct property value’s required.
Much Apreciated.

From the DBAG here are you options for dimension builds with ASO applications
% Express as a percentage of the current total in a consolidation (applies only to members of a dynamic
hierarchy)
* Multiply by the current total in a consolidation (applies only to members of a dynamic hierarchy)
+ Add to the current total in a consolidation (applies only to members of a dynamic hierarchy)
- Subtract from the current total in a consolidation (applies only to members of a dynamic hierarchy)
/ Divide by the current total in a consolidation (applies only to members of a dynamic hierarchy)
~ Exclude from the consolidation (applies only to members of a dynamic hierarchy or members beneath Label Only members in a stored hierarchy)
O Tag as label only
N Never allow data sharing
C Set member as top of a stored hierarchy (applies to dimension member or generation 2 member)
D Set member as top of a dynamic hierarchy (applies to dimension member or generation 2 member)
H Set dimension member as multiple hierarchies enabled (applies to dimension member only)
Brian Chow

Non-Cumulative keyfigure example

Hi all,
      To test for non-cumulative keyfigures I have modeled a keyfigure noofemployees and below is my model
<b>Infocube has following characteristics, timecharacteristics and keyfigures</b>
Charteristics: Companycode
TimeChar: 0calmonth
Keyfigures: salesrevenue and noofemployees
<b>My infosource has following infoobjects</b>
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

Keyfigure fixing at aggregate level

HI,
I am using APO V4,
1. I am planning to fix my keyfigure only at aggregate level, My keyfigure is open at all levels like plant or material group or material, i can enter the data at any point manually. but when come to keyfigure fixing, i want to fix the keyfigure only at aggregate level, i mean if the keyfigure is at material level i need fix, any other level it should not allow me to fix.
I was thinking for a drill down macro, but my keyfigure should open at all levels irrespective of keyfigure fixing, is it manageable any how that keyfigure can only be fixed at material level?
2. this is a different issue from above, i have fixed the keyfigure for a month, after that i had run a copy macro to the fixed key figure, but the fixed values are overwritten once the copy job is completed, and when i check in the planning book, it is visible as fixed agian. do i need to have any macro specific setting for this during the copy macro?
Thanks in Advance
ARUN R Y

Hi Gurus,
I am having some problems with Key Figure Fix.
The business requirement:
Some fields must be kept fixed and locked during the interactive planning performed in tc /SAPAPO/SDP94.
What was done in order to do it:
We created macros using standard features in order to fix and block some cells in accordance with the business requirements. The first macro disaggregates the planning to the last level available for collaboration. Another macro using FIX_CALC and ROW_INPUT functionalities fixes and locks some cells (3 levels). After these activities the planning view is aggregated and it will be ready for collaboration.
These macros run automatically every time that the user open an specific planning view.
The problem:
After the aggregation when the disaggregated level is called again all cells have been showed fixed and locked. If we perform the fix and lock manually the system run correctly, i.e., only the cells fixed and locked are kept in this status after an aggregating and disaggregating processes.
Step-by-step
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro FIX_CALC in aggregated level. The first attribute set with ROW ATRIBUTES, the second attribute set with VALUES. FIX_CALC (Cota de Vendas; Cota de Vendas). With this setting, the aggregated line will be fixed.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro FIX_CALC in level 1. The first attribute set with ROW ATRIBUTES, the second attribute set with VALUES. FIX_CALC (Cota de Vendas; Cota de Vendas). With this setting, the level 1 line will be fixed.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro ROW_INPUT in aggregated level. Cota de vendas = ROW_INPUT ( 0 ). With this setting, the aggregated line will be locked.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro ROW_INPUT in level 1. Cota de vendas = ROW_INPUT ( 0 ). With this setting, the level 1 line will be locked.
u2022 Now, go to in /SAPAPO/SDP94.
u2022 Disaggregated the planning view.
u2022 Run the FIX_CALC and ROW_INPUT macros.
u2022 Aggregated the planning view.
u2022 Disaggregated the planning view again. You can see the problem.
Thanks,

Problem with Non Cumilative key figs at report level.

Hi Gurus,
I got an issue with the below keyfigures when I tried to display them in the report Stock Overview.
0TOTALSTCK
0VALSTCKVAL
0QMSTOCK
0TRANSSTOCK
0BLOCKEDSTK
0CNSSTCKQTY
These keyfigs are non-cumulative keyfigures. I wonder why these keyfigures show nothing at report level. The cube is IC_C03 which has the datasources 2lis_03_BX, 2LIS_03_BF and 2LIS_03_UM.
Please help.
Regards,
Sasi

Did you initialize the inventory properly?
Check if inflow and outflow exists in cube for the values you are trying to execute the report

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

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,

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

Aggregation level and planning filter question

Hi,
I have below questions on aggregation levels and planning fitlers.
Scenario: An Aggregation level is built on a multiprovider( Actual Cub1(5 chars, 4 keyfig), Actual Cube2(8 chars, 6 key fig), and Real Time Cube3(8 chars and 3 keyfig)). A FOX copy function has to be built on this aggregation level in which data from cube1 will be copied to cube 3.
1. Does an Aggregation level need to have all chars and keyfigures from cube 1 and cube 3? or it should have structure of Cube 3 only as data will be written to cube 3?
- what are the standard design considerations for defining aggregation level?
2. In planning filter, both cube1 and cube3 are to be restricted or only cube3?
Is it necessary that only target planning cube is to be resricted? In that case how function will get the source data from cube1?
- what are the standard design considerations for defining planning filter?
Please provide some info on this...
any document on design consderations for planning object will be great.
Thanks,
Pundari.

Please go thru the following link u will find step by step procedure for IP:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0568315-7727-2d10-d4ba-88ab69e16577?quicklink=index&overridelayout=true
Please provide ur valuable points if it is helpful:)
Regards,
Prasad.

Non-Cummulative KeyFigures Usage at Aggregation Level in IP

Similar Messages

Maybe you are looking for