Non Cumulative Key Figures - Standard Inventory 0TotalStck
The key figure 0TotalStck is non cumulative and is calculated at query runtime, does anyone know a report or function module that would be used to calculate the value? Thanks
Hi Niten,
Not sure what do you meant. Did you need a query where 0totalstck is calculated. If so, then check this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/10/0092fd7bdc7741a26becc772300cbd/frameset.htm
If you wanted to know how non-cumulative KF are calculated then check this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
Hope this helps.
Bye
Dinesh
Similar Messages
-
Snapshot scenario or non cumulative key figure in inventory management
Hi
We are currently using Inventory Management with non-cumulative key figures but we get very high performance problems due to so big number of lines in info cube.
We are analyzing the other scenario with snapshot and I am asking if it would be very realistic to use it to satisfy our requirement: to be able to get inventory management at day level for about 2 000 000 combinations article-site and about 100 000 stock movement lines per day (we are retailer!).
Is there somebody to give me advice about it?
Tanks a lot
AnneBeing 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 -
Purpose of Non Cumulative key figures
Whatu2019s the purpose of Non Cumulative key figures?
Hi....
There is 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
Also Check..........
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Re: Non-Cumulative keyfigure example
Hope this helps.....
Regards,
Debjani........
Edited by: Debjani Mukherjee on Oct 27, 2008 3:46 AM -
Non-Cumulative Key figure with inflow & outflow
I am using some non-cumulative key figure in our inventory cube, however, I could not find the non-cumulative field in E or F table of the cube?
Is there a separate table to hold the reference unit. If so, what is the table name.
Thanks.Hi,
Go to t-code RSDV and enter the tech.name of your cube that has the non-***. key figure and you will see a validity table. This is only thing I know that will make you look at validity table.
The unit for the Non-*** KF will be the same unit as its inflow and outlow parameters' unit.
Thats my 2 cents on the matter.
Reddy -
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. -
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********* -
How to create a non-cumulative key figure & How to make a info cube as so
Hi Experts,
How to create a non-cumulative key figure & How to make an info cube as non-cumulative cube?
Can any one kindly provide me the steps we need to performe?
Thanks in Advance,
RajHi Azael,
In the How to Papers, you will find a Guide on how to take a Sanpshot view of the Stocks(How To Handle Inventory Management Scenarios in BW). Basically if you implement the Guide, you will have another cube called ICSNAP1, which will contain stock quantities /values at the end of each month. You will therefore have to take stock at the end of the last month from that cube and add up the relevant receipts and issues to arrive at the current Stock or Stock as on a particular date.
Hope this helps!
Regards
Sriram -
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 -
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 -
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 -
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. -
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 -
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 -
Bad performance with non-cumulative key figures
Hi All,
I have a cube with 8 non cumulative key figures based on fiscper.
I am not sure how the performance for reporting with non-cumulatives can be improved.
Thanks
KarenPerformance of non cumulative cubes is dependant on the distance between the marker (date of the last compression) and the execution date.
For actual stock, the more you compress the better it is.
Regards,
Fred
Maybe you are looking for
-
Repeated problems - is there any way of saving my projects myself?
I'm sorry to keep filling up the forum with questions, but the more I try moving forward, the more problems I encounter. I am now finding that even simple edits of my work frequently result in the programme crashing, meaning that whatever I have done
-
How do I transfer my iPhone 4S contacts to my MacBook Pro Adress Book?
What I Want: I want to sync my iPhone 4S contacts into the Address Book on my MacBook Pro. Problem: Everything else syncs fine, but my contacts. I have everything under iCloud turned On to sync onto my MacBook Pro, but it doesn't sync the contacts in
-
Scheduling Agreement for Imported Material
Hello Friends I am doing import cycle through scheduling agreement.I maintained all the conditions(custom duty and CVD with custom clearing vendor) in scheduling agreement.Now i am doing first LIV to capture planned delivery cost of bill of entry in
-
OBIEE 11G - Double column (Descriptor Id)
Hello All, I have a problem in implementing Descriptor ID functionality. I have a time dimension, for which i am using Year, Period Name and Period Number. I have placed Period Number as Period Name ID column and in the report i am using the period N
-
Bug in Headstart form template qmstpl65
Found that the CG$CURRENT_RECORD visual attribute is defined w/ a foreground color of BLUE and a background color of BLUE in the qmstpl65.fmb file. Effectively making this BLUE text on BLUE background which won't work if you set the record to utilize