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

Similar Messages

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.

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

Trouble with Non Cumulative Key Figures

Hi all of you,
I am working on Non Cumlative Key Figures, (NCKF). I have the data like this
Sales rep S100 visited SHOP S1 on 1st Jan and 10th Aug, and transacted worth 100 and 500
SHOP S2 on 1st Mar and 1st July and transacted worth 200 and 300
SHOP S3 on 3rd Sept. and transacted worth 400
Sales rep S200 visited SHOP S1 on 1st Jan and 1st Aug and transacted worth 100 and 300,
visited SHOP S2 on 1st April and transacted worth 200
I created Non Cumulative Key Figure in the following manners:
In modeling in InfoObjects I double clicked on my key figure BILLAMT and selected the Aggregation tab. I selected Counter (all values) for Exception aggregat. By default Agg. Referen. Char was 0calday. I then activated the info object and went to BEx. Here I took other IOs like Salesrep, Shop NUM and Dt. Of trans in rows and Bill amt in columns and executed the report. I am not getting the output how it should come for NON cumulative key figures.
But when I right click the key figure Bill Amount in BEx in change query mode and select properties. I go to the option Calculate result as and selected the option as Count all values. And in another option Calculate Single Value as I selected the option Count all values. I said OK, saved the query and executed it. Now the output is similar to how it comes for a Non Cumulative Key Figure query but I am unable to understand the output.
Now my doubt is where do we set the properties for Non Cumulative Key Figures? Is it in the Administrator Workbench under Modelling under InfoObjects?
OR
Is it in BEx change query mode by right clicking on the key figure and selecting properties?
Please explain.
Thank you
TR.

As for the setting for Non Cumulative key figures...the default setting is done in the Key Figure properties, where u can define the Exception Aggregation. This property is used as such in the query, but if suppose u are getting the normal aggregation in the query , what you could do is "Create The Key Figure as Global Calculated Key Figure in Bex" and go to properties...click on the Button for aggregation ..select the aggregation and define with respt to 0CALDAY ..here.
Hope this helps.

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
Anne

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

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

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

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? Thanks

Hi,
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

Error while activating cube contains non cumulative key figures

Hi all,
when i am trying to activate a cube which contains non cumulative key figure it is showing out the following error:
DDIC Object TABL /BIC/LZATTR1NON has not been activated
Table /BIC/LZATTR1NON could not be activated
Please let me know if any one come across with such error
Help are appreciated

Before activating an infocube with non-cumulative keyfigures, the system
design forces the user to enter at least once the screen: maintain
non-cumulative values (validity table). If that step has been performed, activation will work fine.
In the meantime, please do this step explicitly, at least once, when
configuring such an infocube, then you should not have any problem.
Please follow the same process while activating the infocube
Goto Infocube ->Goto Change mode->Menu ->Extra-> goto the screen:
maintain non-cumulative values once.
Walter Oliveira.

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
hari

Hi,
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.

Samples of non-cumulative key figure

hi experts,
can u give me samples about:
1> in what scenario should i use the non-***.Value change to create a non-cumulative key figure?
Characteristic            : HEADCOUNT
Aggregation               : (here chose sum?)
Exception Aggregation:(here chose sumation?)
Agg.Reference Char   : (here chose a 0calday?)
N-*** with N-*** Value Change
       Non-***.Value Change: (here what to insert?)
2> in what scenario should i use the inflow/outflow to create a non-cumulative key figure?
Characteristic            : HEADCOUNT
Aggregation               : (here chose sum?)
Exception Aggregation:(here chose sumation?)
Agg.Reference Char   : (here chose a 0calday?)
N-*** with In- and Out-flow
                           Inflow : (here what to insert?)
                           Outflow: (here what to insert?)

hI
1> in what scenario should i use the non-***.Value change to create a non-cumulative key figure?
Characteristic : HEADCOUNT
Aggregation : sum
Exception Aggregation: sumation
Agg.Reference Char : 0calday-----* U CAN GIVE 0CALMONTH too to view head count month wise.*
N-*** with N-*** Value Change
Non-***.Value Change: * If u are maintaining delta value ie if no. of employees joined is 10 and resigned is 6, then delta value is 10-8=2*
in this situation use this type.
2> in what scenario should i use the inflow/outflow to create a non-cumulative key figure?
Characteristic : HEADCOUNT
Aggregation : sum
Exception Aggregation: sumation
Agg.Reference Char : 0calday
N-*** with In- and Out-flow
Inflow : *Inoobject which maintains no of employess joined *
Outflow: *Inoobject which maintains no of employess resigned. *

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

Non-cumulative key figure in Real Estate implementation

Hi all,
    I am implementing Real Estate Module in BW. We are doing analysis on Condition amount ( BKOND).
    The mapped Info Object on BW side is 0COND_AMT, according to standara info sources given by sap ( for e.g in 0RE_3) and it is defined as a Non-cumulative KF with Non cumulkative Change 0COND_CHG.
Can anybody plese explain me the logic behind this. and also source field and table for this 0COND_CHG in R/3 side.

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.

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 help

Hi All,
I am in need of setting up a non-cumulative key figure in a cube. When I load from my ODS everything is ok, however during a delta process, this field at times gets
summarized when in fact it should be static or in an overwite mode. Can someone provide some advice/comments on how I can set up my key figure field in a basic cube to be static yet be able to be used in a calculation for a query? I do not want to apply any functionality such as aggregation, average etc. In R/3 LIS functionality, you basically set up a characteristic Key Figure, how can this be done in BW ?
Best Regards,
Dennis

Dennis,
Check if you ahve declared the KF properly and also check the query which you use ...
Load data and then compare with the query at the lowest level of data in the ODS. Then you will know if the update rules are correct.
Arun

Bad performance with non-cumulative key figures

Similar Messages

Maybe you are looking for