Non-cumulative and time dependence

We are using the Inventory Cube (0IC_C03) and would like to create a historical report that shows over the last months what inventory is active or discontinued. The discontinued flag on 0MATERIAL is only the current status. So if a material is discontinued now, it does not mean that it was discontinued last month.
We investigated using time dependant master data as a navigational attribute. But when reporting with time dependant data you have to specify a key date. This works fine for running the report for a single time period, but we would like to report the changes in multiple time periods.
We also investigated adding the status to 0IC_C03. But since it is non-cumulative I don't think that this would provide correct results. (i.e. if I have 100 in inventory for part A at active status, then the status changes to discontinued, there is no inventory transaction that is created because of the status change. BI will have no idea that the 100 is now discontinued.)
Can anyone recommend a modeling approach that might fit our need? Or do you see any false assumptions I made above?
Thanks,
Chris Robertson

Chris Robertson,
You can achive this using Monthly Snap Shot - Inventory management. Instead of using non-cumulative keyfigures.
[Inventory management with SnapShots and cumulative key figures|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
Hope it Helps
Srini

Similar Messages

Non-Cumulative and BWA

Dear Expert
I have one non-cumulative cube with Inflow and out flow. I compressed that cube and rolled up BWA index. Performance it good but the query still takes much time ( 10- 12 minutes) earlier 30 minutes.
I saw during query running its still accessing Master data infoobject in BW and i have navigation attribute in row of query definition.
Please tell what steps i need to perform to make the query fater, let say within 2 minutes.

Hi Tansu
I have the same kind of problem. In my case, i have the below in rows
Plant_country
Profit Center
Material->display attr ( one display attribute)
Mat_plant-->display attr( one display attribute)
Material_prod_hier
Material_matl_type
Material_division
Mat_plant_mrp_contrl
Mat_plant_0pur_grp
Stor_loc
Stocktype
and whenever I am running the report I see in SM50 /BI0/PMAT_PLANT is being read with report CL_RSDM_READ_MASTER_DATA======CP. for long time ( direct read)
Then another report SAPLRRK0 is taking huge time in reading. But one thing is sure its is reading BWA not the Cube except master data table for MAT_PLANT.
by 30 char object you meant long text /short text?
Dont know what needs to be done to make this particular query faster. Please advise.
Regards
Anindya
Edited by: Anindya Bose on Apr 9, 2011 2:01 AM

Non Cumulative and Cumulative Key Figure

Hi all:
Can anyone clarify difference between Non cumulative KF and Cumulative KF.What is the use of these two and when we go for this.?
Please send me if any docs [email protected]
Rgds
MSK
Note: Points to be reward.

Hi,
Check this Link:
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
take a look to https://websmp105.sap-ag.de/bw -> SAP BW InfoIndex -> Non-cumulatives
here you can find:
Non-Cumulative Values 3.x (pdf)
Also Check this:
Cumilative and non Cumilative
Non cumulitive Key figures
Bye
R.Ravi

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 infocube in Infoset: Inventory

Hi Experts,
I have a requirement to combine a infocube and DSO under Infoset. But the Infocube is non cumulative and is not allowing to add in infoset.
Any solutions for this?
My Infocube is customised and have 3 datasources: 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM
And my DSO contains the alternate UOM with a single datasource: 0MAT_UNIT_ATTR
My Ultimate aim is to bring the alternate UOM.
Please post your suggestions.
Thanks,
Guru

Hi Nirajan,
First of all as I undestood 2LIS_03_BX is the initial upload of stocks, so there is no need of delta load for this datasource, it collects data from MARC, and MARD tables when running the stock setup in R3 and you ahve to load it just one time.
If between delta loads of 2LIS_03_BF you're loading full updates you are dupplicating material movements data, the idea of compression with marker update is that this movements affects to the stock value in the query, it's because of that when you load the delta init you do it without marker update because these movements are contained in the opening stock loaded with 2LIS_03_BX so you dont want to affect the stock calculation.
You can refer to the How to handle Inventory management scenarios in BW for more detail on the topic.
I hope this helps,
Regards,
Carlos.

Archive Stock Cube with non-cumulative nature

Hi All,
I have been trying to archive the Inventory (Stock) Infocube as we have more than couple of hundread million records in the cube and it is taking long time to execute query.
I know how to acrive the regular cubes and DSOs, but I couldn't find any helpful documentation where I can know how to archive the Infocube with non-cumulative nature or containing Marker update.
Can anyone pleaes post the link of document?
BTW, we are using BI7.0 SP15
Thanks,
Dhaval

Hi,
There are two ways of archiving data from a non-cumulative InfoCube - time slot archiving and archiving with selection characteristics.
Time slot archiving (recommended)
As an archiving method, you must choose for a non-cumulative InfoCube, time slot archiving for the time reference characteristic. When you recreate an archiving object for a non-cumulative InfoCube, this characteristic is also suggested by the system.
Only archive non-cumulative changes up to a specific point in the past. This reduces the volume of data in the InfoCube. The marker (= end non-cumulative) remains unchanged.
In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements Only option.
You are only able to archive the marker if you also archive all of the non-cumulative changes. Subsequently, the contents of the non-cumulative InfoCube are archived completely. In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements and End Non-cumulative option.
You must archive the non-cumulative changes (for all times) first, and then archive the marker in a separate archiving run, so that the non-cumulative changes and the marker are stored separately in the archive.
The advantage of time slot archiving is that archiving runs can be carried out periodically using a single variant with a relative time restriction. The alternative archiving method described below does not have this advantage.
Archiving with selection characteristics
In some cases, archiving based only on time slots does not have the required effect of reducing the volume of data in the InfoCube. This is the case, for example, if the non-cumulative bearing objects are subject to high fluctuations, meaning that data is constantly being loaded for new objects and old objects are made obsolete. With time slot archiving, the end non-cumulative remains for all objects until all of the data in the InfoCube is finally archived, even if all the non-cumulative changes for an object have been archived already.
In this case, you want to archive and delete completely any objects that are no longer active in the InfoCube. This means archiving the marker as well. For other objects that are still active, you only need to archive the non-cumulative changes from the past, which means the marker is retained.
When you define the archiving properties for a non-cumulative InfoCube, do not therefore choose the time slot archiving method. Instead, select individually the characteristics that are relevant to restricting archiving runs. The time reference characteristic should also be included in this selection whenever possible.
Using this archiving method, for each archiving run, you need to create selection conditions in a variant. In the variant for the archiving run, in addition to the selection conditions, you can also specify for the selected characteristics whether or not non-cumulative changes and marker data is archived. If you choose to archive marker data, be aware that the time selection contains the maximum value for time.
Please refer to the below link to archive the data for Stock Cube:
http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/c219fe9a46194aa66d55254fdab182/frameset.htm
Hope this helps.
Regards
Tanuj

Regarding Non cumulative options

Hi Friends,
we have two options in aggregate tab while creating key figures.
In that we have two options
1) ncum value with ncum value chage.
2) ncum value with in-and-out-flow.
Please can any one explain above two options clearly.
Thanks in advance,
ramnaresh.

Hi Ram,
A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
A non-cumulative key figure is modeled in BI using the corresponding field for the non-cumulative value change or the corresponding fields for inflows or outflows. You can determine the current non-cumulative or the non-cumulative at a particular point in time. You can do this from the current, end non-cumulative and the non-cumulative changes and/or the inflows and outflows.
Flow/non-cumulative value
You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
Non-cumulative with non-cumulative change
The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
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.
For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, quantity) as the non-cumulative value.
For Additional Information about non cummilative keyfigures plese go through these links:
Non-Cumulatives: [http://help.sap.com/saphelp_nw70/helpdata/EN/8f/da1640dc88e769e10000000a155106/content.htm]
Non-Cumulative Key Figures:[http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a62ebe07211d2acb80000e829fbfe/content.htm]
Modeling Non-Cumulatives with Non-Cumulative Key Figures:[http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a62dee07211d2acb80000e829fbfe/content.htm]
Regards,
Rajkandula

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

Concepts: cumulative / non-cumulative key figures. Differences.

Hi, could you help me to understand cumulative / non-cumulative key figures concepts ? When use it? Differences? Performance?
I appreciate you if you spend few rows without link to massive web documentation.
Thanks in advance!
Bye!
Ferdinando

Have a look at this:
Non Cumulative and Cumulative Key Figure
Hope it helps.
Regards

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

Using Non cumulative key figure in Real time cube

Hi gurus,
I have used non cumulative key figure in a real time cube and when i tried to enter some data using RSINPUT ,it is giving an error and the data is not getting saved.
Can anyone please tell me how to use the Non cumulative key figure in the Real time cube .
Thanks in advance
Regards,
Ravikanth

Hi Ravi,
Please make sure that when you use a non cumulative key figure iun your real time info cube, then choose a time reference characteristic for that key figure.
Then, this time reference characteristic applies for all the non-cumulative values of the InfoCube and must be the u201Csmallestu201D of the time characteristics present in the InfoCube.
For more detaisl, refer to the [http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm]
Thanks & Regards,
Balajee.

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 prasad

Cumulative 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*********

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 figureu2026

Thanks 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

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

Cumulative and non-cumulative for key figure

Hi,
In the aggregation tab, we have the aggregate type SUM, Max or Min.
we also have the comulative/non-cumulative values.
what's the difference between comulative and non-cumulative values? it would be good to have some example for illustration. and does comulative and non-cumulative have any relation with aggregate type?
Many Thanks
Jonathan

Hi,
what's the difference between comulative and non-cumulative values?
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Example: sales revenue, weight, etc.
Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.Example:stock quantities/-values, number of employees, account balances, etc.
Does comulative and non-cumulative have any relation with aggregate type?
Different types of non-cumulative keyfigures.....are....
1.Non-cumulativekey figure = cumulative keyfigure with excep.aggregation
2.Non-cumulativekey figure withassociated singledelta (cumulative)
3.Non-cumulativekey figure withassociated in-andoutflow(cumulative)
check these links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92c0aa90-0201-0010-17b1-bf5b11c71257
hope it helps...
Regards
chandra sekhar
Edited by: chandra sekhar t on Nov 28, 2008 2:18 PM

Non-cumulative and time dependence

Similar Messages

Maybe you are looking for