Non cumulative with non cumulative value change

hi,
can any one tell the concept of non cumulative with non cumulative value change with an example with numbers,i am bit confused .
like we have for non *** inflow and outflow- stocks inflow and outflow so non *** is based on inflow and inflow.
in the same way any example for above concept

Hi Venkat,
If I under stand your question correctly you wish to have an example of where non cumulative values are used and you have given the value of stock? If so here is an example with figures
So you would do an initial load loading the opening balances of Stock.
Say material number 12345 = 100 units
After that, only movements will be posted so Stock will either increase or decrease depending on what image is posted via the change log.
So there will be a purchase of material 12345 for 50 units so now the balance of material is 150.
But then you could use or sell 70 units of material 12345 so you stock value would be 80 units
I hope this makes sense and this is an example that you are after if not please let me know and I'm happy to help
Regards
Ben
PS assign points if useful

Similar Messages

Non cumulative with non-cumulative change

Hi Experts,
I have a Question !, As i know that i can create Non-Cumulative Figure By Means Of two ways:-
1. Non cumulative with non-cumulative change and
2. Non Cumulative with Inflow and Outflow.
the second one is very clear but i am not very clear about 1st option i.e What Non-Cumulative Value changes is? and how it calculates the non-cumulative Value.
If u have an Idea please share your knowledge...
Ragards
Prakash

The 1st option is for key figures like headcount or similar, which you would like to store as a total figure in a cube instead of a DSO in a scenario where you are using a multiprovider on this together with other non-cumulative cubes.
The SAP help below explains this quite well
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
Best,
Ralf

Using an event structure to reset a boolean control with ring menu value change

I am trying to get two boolean buttons to reset when the value of a ring menu changes. For this I am using an event structure set to execute with a ring value change. However I have other code that needs to be executing while the event structure waits for the value change. I place my event structure inside the while loop the buttons reset as expected but my other code does not run (except at the moment of value change). If I place it outside the loop the rest of the code functions as expected but the buttons do not reset. Any help you can offer is much appreciated.
Solved!
Go to Solution.
Attachments:
event structure reset.vi ‏11 KB

try this
Attachments:
event structure reset_edit.vi ‏14 KB

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

Cumulative and Non-cumulative KFs

Guys,
so I am confused about cumulative/Non-cumulative keyfigures. I read what it says about them on help.sap.com
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 with inflow and outflow
The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
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, and quantity) as the non-cumulative value."
and also checked a few threads on sdn but still a little confused about their purpose.
Can someone tell me when do we use which one?
Thanks,
RG.

Hi Ram,
Cummulative & Non Cummulative Key Figures :
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:
u2022 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.
u2022 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 it helps you.
Thanks & Regards,
SD

How to tackle the dataflow problem when Value Change event always triggers after another GUI event

We know that Value change event always triggers after another GUI event. Eg, the user modifies string control, the user clicks on a boolean control. Then event boolean clicked is triggered before event string control value change.
Now suppose somehow the GUI event that must happen to subsequently trigger the Value change event can potentially affect the data that Value change event is supposed to work on. How can we tackle this problem ?
For example, in a mockup application that the grand purpose is to have user entered values in a textbox logged to a file (no missing information is accepted, and there is a boolean to determine how the information is logged).
There are 2 controls, boolean A when clicked (mouse down) will load random number in text box B. Text box B is designed with event structure VALUE change which saves whatever values user enters into text box B to a log file.
There are 3 problems when instead of clicking anywhere on the front panel after modifying text box B, the user ends up clicking on boolean control A.
1. Event mouse down on Boolean control A will execute first, modifying text box B content before the user entered values in B get saved.
2. The value of boolean A can potentially affect how textbox B is loggged.
3. The value of boolean A affects how the file is logged and this is indeterminate. Somehow when running this VI with no Highlighting, the textbox B Value change event executes -before- boolean A value is updated (F to T). When running this VI with Highlighting, the boolean A value is updated (F to T) (because we click on it) -before- textbox B value change event occurs. Why is it like this ?
Now the situation I made up seems non-sense, but I believe it resembles one way or another a problem that you might run into. How would you solve this problem elegantly ?

You can set the string control to "update while typing".
Are you sure appending the log to itself is reasonable? Wouldn't it grow without bounds if the users keeps entering strings or pressing the ingore button?
Why isn't the "constant" a diagram constant instead of a control. Is the user allowed to change it?
To reset just write empty strings or a false to local variables of the controls (renit to defaults" seems a bit heavy handed).
All you probably need is a single event case for "ignore:value change" and "String" value changed", no need for the local variable..
Also add a stop button and an event for it.
You don't need the timeout event.

KF creation - Non-cumulative value with NCUM value change - option

What is the use above option in the KF creation?
Thanks

Hi,
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.
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 loading 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.
Pls chk this links;
http://sap.seo-gym.com/inventory.pdf
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Reagrds
CSM Reddy

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 R

Being 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

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

Problems with Non-cumulative Cube

Dear All,
I have a cube with non-cumulative key figures. An DSO supply data for that cube.
The query on that cube will gets wrong results sometimes. But after removing all the data from that cube and uploading again from the DSO, the query presents the right result.
Is there anybody knows why and how to fix it?
Thanks.
Bolun

Hi
Non-cumulative Cubes to be defined correctly with Inflow and Outflow because it depends on Which option you choose depends on how you want to evaluate the non-cumulative key figure, and also the Marker Update you are dealing with.
The key figures for non-cumulative value change or for inflows and outflows are normal cumulative key figures that have u2018summationu2019 both as aggregation and exception aggregation. Generally, Non-cumulative key figures always have summation as standard aggregation.
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Hope it helps and clear

"initial non-cumulative for non-cumulative values" is not available in DTP (0AFMM_C02)

Hi Experts,
We are working for BI implementation for AFS Industry,
when we are working on AFS specific inventory cube 0AFMM_C02 , we are facing stock mismatch problem
for AFS Stock initialization we are using the data source 2LIS_AF_STOCK_INITALIZATION instead of 2LIS_03_BX, this data source is specificly designed for AFS
when we are extracting the data using 2LIS_AF_STOCK_INITALIZATION for stock initialization and
2LIS_03_BF data source to load the Moments.
we compressed cube with Marker update for 2LIS_AF_STOCK_INITALIZATION data load(by deselecting the No marker update check box)
we compressed cube with No Marker update for 2LIS_03_BF historical data load(by selecting the No marker update check box)
we compressed cube with Marker update for 2LIS_03_BF Delta data load(by deselecting the No marker update check box)
Now we are facing stock mistach problem, we found reason for this
"initial non-cumulative for non-cumulative values" option is not available in DTP only Delta & Full options are available
and infopackage of 2LIS_AF_STOCK_INITALIZATION data source also has "Full update" instead of "Generate Intial Status"
Please let us know how can we get the "initial non-cumulative for non-cumulative values" option in the DTP level.
Regards,
Chandra

Hi Chandrakumar,
We are facing the same problem, how do you solve it?
Regards,

BPS: Planning with Non-Cumulative KF

Hi All,
i'm trying to implement Headcount Planning and to do this i'm thinking to use a non-cumulative KF (Headcount) with delta cumulative KF (Hiring and Dismissal).
The user should plan the delta cumulative KF.
I would like to know if this is possible in BPS 'cause i have read that it's "better" not to use non-cumulative KF in BPS.
Thanks in advance

Very Thanks Marc,
so you say me that i cannot plan on the cumulative KF associated to the Non-Cumulative one, example:
1) ZHEADCNC -> Non-Cumulative KF with INFLOW and OUTFLOW:
1a)ZHEADCAS -> Cumulative KF for INFLOW
1b)ZHEADCCS -> Cumulative KF for OUTFLOW
Is it not possible to plan on 1a) and 1b) and get the exact value on the non-cumulative KF?
The question is that the user should plan the headcount variation and not the "headcount stock" on a defined cluster.
I appreciate any hints

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
Karen

Performance 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

InfoProvider with non-cumulative key figures

what does infoprovider with non-cumulative key figures...
noncumulative key figures..
looking for reply

it's property of the KF... nothing do with Cubes or ODS.
Name itself telling non-Cumulative KF. We can't cumulate this KF. Suppose take the Case Sales Amount and No of Employees. Sales Amount can be cumulated over Time. But No Employees can't be cumulated. Same is the Case with Stock as well.
Nagesh Ganisetti.

Error when activating Cube with Non-cumulative KF

Hi all,
I'm trying to re-activate an InfoCube but now with non-cumulative KF and I'm getting the error message "Object YYYYY could not be activated".
Please help!
Best regards,
Thiago Modro

hi,
have you included the neccessary time characteristics
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Ramesh

Non cumulative with non cumulative value change

Similar Messages

Maybe you are looking for