Definition of Non cumulative Key figure and web template
Hi all,
Can anyone define a Non cumulative Key figure and a web template.
Thanks in advance.
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.If the non-cumulatives change infrequently, you should choose non-cumulative management with non-cumulative key figures.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
for webtemplates you can info in the following
http://help.sap.com/saphelp_nw04/helpdata/en/1a/456a3badc1b315e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/b26a3b74a4fc31e10000000a114084/content.htm
Similar Messages
-
How use non cumulative key figure and noncumulative key figure screenshot
how use non cumulative key figure and noncumulative key figure screenshot
Hello,
Please see this docs for Non-Cumulative and Snapshot scenario,
[How to Handle Inventory Management Scenarios in BW (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
[Non-Cumulative Values / Stock Handling|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366]
Thanks
Chandran -
Non cumulative key figure and degenereated dimension?
Hi experts,
can some explain with example what do you mean by non cumulative key fgure? what is the advantage of this key figure?
what is denereated dimension and under what scenarios do we go for degenerated dimension?
will be very helpful if you can explain with an example?
Thanks in advance.Hi,
Please go through the following websites. It should give you a clear understanding about non-cumulative key figures.
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
Hope it helps!
Regards,
Morpheus. -
Non cumulative key figure and fiscal period 13
Hi,
We have defined a non cumulative key figure. In the cube, the non
cumulative characteristic is the fiscal period (0FISCPER).
This non cumulative key figure works fine from period 1 to 12, but
displays nothing for period 13 (and 14, 15, 16).
We want to display the balance for the special periods 13 to 16, Is
there a way to do it?
Thanks,
GabrielHi,
Yes I am sure, there are some amounts posted in period 13. And even if there are no amount posted, there was a balance in period 12, so the balance should stay the same in month 13.
The balance in month 1 of the next year is correct: balance of period 12 + amount posted in periods 12, 13...
Gabriel -
Difference between cumulative and non-cumulative key figures
Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.Hi.............
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
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. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM -
Problem with Non-cumulative key figure.
Hi all,
I am facing the problem with the Non-cumulative Key Figure (Quantity). I have created and loaded data to the non-cumulative InfoCube. <b>This cube is defined by me to test the non-cumulative key figure.</b>
<b>In BEx query the non-cumulative key figure and cumulative key figure (Value change) both display same values, i.e. non-cumulative key figure contains the same values which we have loaded for cumulative value change. Non-cumulative key figure is not calculated based on associated cumulative key figure.</b>
I have done the following while defining the non-cumulative InfoCube:
1. Created a non-cumulative key figure which is associated with a cumulative key figure (value change).
2. Loaded data to non-cumulative InfoCube from flat file.
3. Compressed data in non-cumulative InfoCube after the load.
Note:
1. Validity area is determined by the system based on the minimum and maximum date in data.
2. Validity determining characteristic, 0CALDAY is the default characteristic selected by the system.
Is there any other settings to be done?
Please help me in resolving this issue.
Thanks and regards
Pruthvi RBeing a non-cumulative KF, total stock is automatically takes care of that.
Try putting all the restrictions which you have included for total receipts and total issues, for eg, restrict Total Stock with the movement types used in Receipts as well as Issues.
Check and revert.
Regards
Gajendra -
When do you go for non cumulative key figures?
hi all,
Can anyone explain the significance of non cumulative key figures. and when do we go for non cumulative key figures.
Can anyone explain me with an example.
thanxs in advance
hariHi,
chk these threads:
non cumulative key figures
Cumulative and Non-cumulative Key Figures
also,
There is also an explanation of advantages and disadvantages of using non-cumulative key figures in "How to handle inventory management scenarios in BW" white paper:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20handle%20inventory%20management%20scenarios.pdf
Assign points if this helps!!
Regards,
Dhanya. -
Intregarted Planning Design for Non-Cumulative Key Figures
Hi,
I have a requirement where i have to design a planning layout for a Invenotry Scenario (Using Non cumulative Key Figures).
What should be the factors i should consider in my design specifically for non cumulative ke figures and how it is different from design for a regular (cumulative) key figure
Thanks
Rashmi.Thanks for your response. My requirement is to design a retail inventory planning application in which one of the KPI's planned is stock price which is a non cumulative key figure and i am trying to figure out how than can be planned if non-cumulative key figures are not allowed in planning
Thanks
Rashmi. -
Non Cumulative Key Figures Simple
Please Help me with this.
I have the measurement Amount "0meas_value" non cumulative key figure and
aggregation properties Sum and Last value and other key figure is 0meas_chg
cUMULATIVE KEY FIGURE. aggregation properties Sum and summation. Now my question if I map the field from R3 Datasource (MEASVALUE) to CUMULATIVE key figure 0meas_chg, will it me a mess??? , Since when i try to put "0meas_value" non cumulative key figure in infosource it gives the error that you cannot put the non cumulative keyfigure in infosource. Please tell how can i then map to non cumulative key figure.?? and if I do not map what will be the problem??
<b>Technical name: 0MEAS_VALUE (Non Cumulative)</b>
Use
This key figure contains the measurement amount of a real estate object on a given key date. The key figure is used for analyzing changes to the real estate portfolio.
and
<b>Technical name: 0MEAS_CHG (Cumulative)</b>
Use
This key figure contains the change to a measurement on a given key date. The key figure is used for analyzing changes to the real estate portfolio.
Technical Data
Aggregation
SUM
Exception Aggregation
SUMMATION
Cumulative/Non-Cumulative Value
Cumulative value
Thanks
SoniyaThis kind of issue is difficult to analyze.
Basic approach would be:
1. make sure your BIA revision is the latest.
2. check Tcd: RSDDBIAMON2 and make sure there is no red light
3. rebuild the BIA Index and try again.
Regards,
Patricia -
Integrated Planning and Non-cumulative key figure
Hi
I´m creating an Integrated Planning application and a problem has occurred. The users want to plan on inflow and outflow and at the same time have a row with the total sum in the same layout (they are planning on 0CALMONTH and 0ORGUNIT) This can e.g. be solved through use Web Application Designer with one planning query and one traditional query.
Any way. I have created a non-cumulative key figure with an inflow- and an outflow key figure. The problem is that the non-cumulative key figure starts working first when I change the planning mode from plan status to load status. I could use function modules, to change the status, behind the save button but there are several users who are planning at the same cube at the same time and I don´t want to lock the others from planning.
How to solve this?
- Is it possible to restrict the switching, from plan to load, by setting some kind of filter at the users org.unit? (0ORGUNIT is an authorization object)
- Is it possible to create a process chain and then load the data to another cube for reporting at just this key figure? And also here have a filter at the org.unit
I will gladly get all kind of idea and input to solve this problem. Maybe there is some other way to go than using non-cumulative key figureu2026Thanks for your answers
I have tried different scenarios and I will use a u201Dsave-buttonu201D. In the save-button I use the commands SAVE_DATA and EXECUTE_PROCESS_CHAIN. The command u201CEXECUTE_PROCESS_CHAIN starts a process chain that switches from plan mode to load mode and then back to plan mode again.
One new problem has arisen. The non-cumulative key figure is updating if an existing value (inflow- or outflow) is changed. But if an input is made to an empty cell, without value, nothing happen when I press on the start-button. BUT if I refresh the browser the non-cumulative value is updated!!!
Is there any command in WAD that refresh the whole page? If so I can include it in my start-button.
If not, any sugestion on how to solve the problem?
Best regards
Mikael -
Non cumulative key figure is not getting filled based on inflow and outflow
hi,
i have a non cumulative key figure which is having inflow and outflow.
i have these three info objects in dso.
as i know non *** key figure is calculated based on inflow and outflow.
i am getting values for inflow and outflow so non *** should be calculated based on this values.
<b>but the collumn is blank in the dso</b>
in that non *** keyfigure i have added two info objects in inflow and outflow.
is there any other setting i nedd to do?
please sugest me.
its urgentHi Venkat,
Have you followed the process right. First Filling the Initial Stocks and then Inflow and Out Flow and then Delta. If you follow the process correctly then you can able to view the Data in the Reporting Level.
For Initial Stocks the Marker Should be set. For Inflow and Outflow the Marker should not be set.
Hope This Helps,
Regards,
rik -
Cumulative key figure and non cumulative key figure
Hi BW Expertz
Could any one give me the clarification about cumulative and non cumulative key figures .Why we go for cumulative key figure and non cumulative key figure.If any docs could u just mail to the following [email protected]
Thanx In advance
Best regards
sankar prasadCumulative values are those key figures (KF) that are cumulated using all characteristics, thus also using time.
Ex: Sales revenue, Quantity....
Non-cumulative values are those key figures that are measured in relation to a period in time; they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so called exception aggregation.
Ex: Number of employees, Inventory, Stock prices, Account balance,.....
AGGREGATION TAB
Non cumulatives are evaluated by non-cummulative values. Non-cummulative values are special key figures that are different from other key figures (cummulative values) in data transfers and saving as well as in aggregational behaviour. These are measured in relation to a period in time; that is to say, they cannot be meaningfully cumulated over time. Non-cumulative value are summaraized over-time using exception aggregation.
Non-cumulative values such as 'number of employess' are cumulated using characteristics such as 'cost center'. It does not make any sense, however, to cumulate the number of employees using different periods. The result at the end of any particular period would be the sum total of number of employees for each posting during the period. This would of course be wrong.
Instead, the aggregation of the KF can be defined as exception aggregation wherein an additional references characteristics is utilized to tell BW which value to use during the period, in this case, 0CALMONTH is used, in the above example, to indicate that only the last value of 0HEADCOUNT, updated by costcenter, is to be taken for any calender year and month.
Cummulative vs Non-Cumulatives
The purpose of non-cumulatives is to optimize the data transfer in BW, the data retention and the database access. The data transfer from OLTP to BW is minimized and only the meaningful data is saved and processed.
It is recommended that you use non-cumulative values for areas that dont change frequently such as warehouse stock or number of employees.
Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it for storing the non-cumulative or for inflows or outflows.
Non-cumulative values are stored with special KF that differ in terms of data transfers and aggregational behaviour.
Features of NON-Cumulative Values Transfering and Saving Data:
- NC values are mapped uisng one KF for NC changes or two KF for inflows and outflows.
-NC are transferred in an initialization run and the change runs that follow (initialization can also be omitted here)
- A non-cumulative value always has a time-related exception aggegation.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
with Example
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
/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 Useful********* -
Multicube with Cumulative and Non Cumulative Key Figures
Is there any problems if I build a Multicube which consists of InfoProviders which have non-cumulative key figures (Inventory cube) and those which do not
In the query I will be summing the key figure for example Stock Quantity across the InfoProviders? ThanksHi,
There is no problem if you do that only thing is when you assign key figures in the multiprovidesr you have to be careful in deciding the infoprovider from which the key figure comes.
Hope this helps
Assign points if useful
Regards,
venkat -
Planning on Non-Cumulative Key Figure
Hello,
is it possible to plan data on a non-cumulative Key Figure?
SAP_ABA 701 0005 SAPKA70105 Cross-Application Component
SAP_BASIS 701 0005 SAPKB70105 SAP Basis Component
PI_BASIS 701 0005 SAPK-70105INPIBASIS Basis Plug-In
ST-PI 2008_1_700 0001 SAPKITLRD1 SAP Solution Tools Plug-In
SAP_BW 701 0005 SAPKW70105 SAP Business Warehouse
BI_CONT 704 0003 SAPK-70403INBICONT Business Intelligence Content
ST-A/PI 01L_BCO700 0000 - Servicetools for other App./Netweaver 04
We implemented also the How-to Paper Copy and Paste in the Web Template but it isn't working in a proper way. UnderPrerequistes in the How-to Paper I found IE 7.0 and Clipboard. But I was informed that we have an higher Level.
Thank you in advance for your help.
Kind Regards
DorisNot possible.Please find the help link for more details.
http://help.sap.com/saphelp_nw70/helpdata/EN/43/1c3c7031b70701e10000000a422035/content.htm
Regards, Hyma -
Regarding Non-Cumulated Key figures
Dear All,
I wanted to create Multiprovider which includes infocube having Non-cumulative key figures .When I am including that Non-cumulative key figure in the Multiprovider , I am getting an error "Inconsistencies were found when checking MultiProvider ZMULTIPTP"
detail fo this error is
Define the characteristics of the validity table for non-cumulatives
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.Hello,
See this Validity table for non-cumulatives in a self defined cube
Thanks
Chandran
Maybe you are looking for
-
Transaction Type is not updated to FAGLFLEXT
Hi, When entering asset acquisition, user will use posting key:70 and transaction type 100 and enter the asset. This is updated in the BSEG. In the FAGLFLEXT table there is column transaction type, it is not updated.. Pl.sugesst how to rectify the ab
-
After i install window 8.1, i can't see window icon in my start up disk, i see only mac icon 10.10, but i can see both mac and win icon in my window boot camp control. i want to see window icon in my mac Yosemite 10.10.2,system preference, start up d
-
How to add new line wrapping rule?
Hi all, I have a question about line wrapping condition of Java editor of JDeveloper. JDev has some predefined rules for it and I can change them from preference. But can I add a new rule? I'd like to place conditional operators such as "&&" or "||"
-
Using leopard as alarm with internet radio?
It would be really great if I could use the Mac I'm about to get as an alarm - waking up to radio4. Would that be doable? I know you can set the OS to fire up at a certain time, but can you have it automatically play a stream online without having to
-
Post Author: DAndre10 CA Forum: General I'm using the following function to determine a person's age: round(({calcdata.dob},{calcdata.dodec})/360,3) I am rounding the result to three decimal places, but does anyone know of any other rounding features