Non Cumulative KF in ODS

Is it possible to use Non cumulative KF in ODS?
Many thanks
Fabio

Ciao Fabio!
The aggregational behavior of a KF determines whether, and how, key figure values are aggregated in reports using the different characteristics or characteristic values.
In other words, you can use non-*** KF also into an ODS, since a MIN exception (for example) with reference to a DATE object is always possible and performed by the OLAP processor when you run a query!
http://help.sap.com/saphelp_erp2004/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
Hope it helps!
Bye,
Roberto

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.

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

Inventory - Non Cumulative

Hi
I have inventory data coming from legacy syste.
I have the following fields.
Date Mtrl Qty.
As this is coming daily and i would like to keep the history in the ODS as well as cube. How can i make Qty as non cumulative with out Inflow / Out flow.
I should be looking at the reports based on wk, month and qtr.

Thejo,
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 your InfoCube contains a non-cumulative key figure, then a time-based reference characteristic for the exception aggregation of the non-cumulative key figure must exist.
There can be several time characteristics per InfoCube, but only one time reference characteristic. This means, that the time-based reference characteristic is the same for all the non-cumulative key figures of an InfoCube.
This link is very helpful and informative:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
Let me know if this helps.
Pete

Difference between Snapshot scenario and non cumulative scenario

Hi,
Can any one please tell me the difference between snapshot scenario and non cumulative scenario in
inventory management.
Also please give example. I read the pdf " how to handle inventroy management scenarios", but can any one please give some easy to understand examples.
full points guaranteed-

hi,
In Non-cummulative method your stock movements are stored in the cube (inflow and outflow of NC KF) and the Total stock is calculated during query execution. Hence if there are lot of movements in the stock for the period you want to report on, query will take long time to execute.
In case of Snap shot scenario Stock movements are not loaded to cube. you use ODS to load the status of the stock and then from ODS you can load to Cube once in a month. So only summarized data will be availabe in Cube. Reporting will be fast.
Check the below threads
Inventory Management - SnapShot model
snapshot scenario?
SNAP SHOT Scenario in IM

Concept of Non-cumulative KYF

Hi experts,
   We are using some non-cumulative KYFs in our FI customizing cubes. It really brings troubles for the project. Like:
   - Poor query performance
   - No special 0FISCPER value due to setting as 0CALDAY for the base time reference characteristic
   - No useful aggregates could be created as 0CALDAY can't be removed from any aggregate
    As so many troubles show up, I can't help wondering: where is the advantage?
    In our cube, Z1BALANCE is a non-cumulative KYF with inflow (0DEBIT) and outflow (0CREDIT). What is the difference if I set a general KYF Z2BALANCE to replace it and write code in update rules: result = 0DEBIT - 0CREDIT ?
    Would you please explain this in general words and examples instead of bunch of links?
Regards,
Aaron Wang

Hi,
At all this is link will help you understand non-cumulative better.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/b987eb1443534ba78a793f4beed9d5/frameset.htm
Non cumulatives are calculated at the runtime of the that's why query performance is slow.
The option is to compress the cube at regular time interval in case od non- cumulative.This will help in query performance improvement.
I think you can give any time reference in the cube if you want other then 0calday that's you can do at the cube level.
Ya aggregates cannot be created.
you can use non- cumulative as well as cumulative key figure to the same.
depends upon the scenarion which you are working on.
If you data changes frequently then you should use cumulative key figures.
But if it changes non- frequently then should use non- cumulative.
The advantage is it gives you the values with reference to the time there are cartian scenarion which can only be modeled through non - cumulative.
Like inventory where at any point of time you can have just change in the values of the stock.
i.e. always a delta brings in the change in the values of the invenctory.
Inventory va;ues can be maintained in the form of inflows and outflows.That is waht is increasing the stocks and what is decreasing.
Now if you just subtract( inflow- outflow) it will just give you the value at that aprticular time.
This one page documnet explains everything.
In our cube, Z1BALANCE is a non-cumulative KYF with inflow (0DEBIT) and outflow (0CREDIT). What is the difference if I set a general KYF Z2BALANCE to replace it and write code in update rules: result = 0DEBIT - 0CREDIT ?
you can do it through cumulatives also.But that you will have to maintain at the ODS level and then subtract the key figures in the update rules it and maitain it in the cube.
That will get stored with refernce to the time and will work well.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
Hope it helps
Thanks

Non-cumulative Values not showing in Inventory Management Queries

Hi:
Has anyone had a problem with the new version and Non-cumulative key figures not showing up in Bex for Inventory Managemet reports? Specifically, they showed and validated back to ECC for our Development and QA boxes but now in our Regression box they are all showing zeros. Our Cumulative values are all showing correctly still within the Regression box. For example, Total Receipts and Total Issues are correctly poplating values but Total Stock is not.
I have checked and validate that the configuration in the Regression box matches or Dev and QA box.

Found the problem. It had to do with the compression variant in the delta process chain. The compression was set to 'no marker update'. Since we only started receiving measureable deltas in or regression box this is where the incorrect setting showed up. Reinitalized and the deltas are working correctly now.

Aggregates on Non-cumulative InfoCubes, stock key figures, stock, stocks,

Hi..Guru's
Please let me know if anybody has created aggregates on Non-Cumulative Cubes or key figure (i.e. 0IC_C03 Inventory Management.)
I am facing the problem of performance related at the time of execution of query in 0IC_C03.( runtime dump )
I have tried lot on to create aggregate by using proposal from query and other options. But its not working or using that aggr by query.
Can somebody tell me about any sample aggr. which they are using on 0ic_c03.
Or any tool to get better performance to execute query of the said cube.
One more clarification req that what is Move the Marker pointer for stock calculation. I have compressed only two inital data loading req. should I compress the all req in cube (Regularly)
If so there would be any option to get req compress automatically after successfully load in data target.
We are using all three data sources 2lis_03_bx,bf & um for the same.
Regards,
Navin

Hi,
Definately the compression has lot of effect on the quey execution time for Inventory cubes than other cumulated cubes.
So Do compression reqularly, once you feel that the deletion of request is not needed any more.
And ,If the query do not has calday characterstic and need only month characterstic ,use Snap shot Info cube(which is mentioned and procedure is given in How to paper) and divert the month wise(and higher granularity on time characterstic ,like quarter & year) queries to this cube.
And, the percentage of improvement in qury execution time in case of aggregates is less for non cumulated cubes when compared to other normal(cumulated) cubes. But still there is improvement in using aggregates.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Transformation between DS and DSO missing Non-cumulative KYF

Hi SDN,
I installed the business content for CML, and am working with 0CML_DELTA_CAP datasource. I would like to create a transformation between this datasource and DSO 0CML_O03.
By default, when you install the CML business content, the datasources use the 3.x dataflow concept (transfer rules, infosources, and update rules).
I would like to use the 7.x dataflow concept and created a transformation between the 0CML_DELTA_CAP datasource and the 0CML_O03 DSO. In the transformation, it is missing the fields 0CML_B330, 0CML_B340, 0CML_B360, 0CML_B380 in the datatarget. These key figures are non-cumulative with NCum Value change (0CML_B330 uses 0CML_B331 as value change). The value change key figures show up in the transformation, but the non-culmulative key figures do not.
Does anyone have any ideas why the non-cuml. kyf are not showing up in the transformation?
Thanks,

Hi Brendon,
The non- cumulative key figures are not mapped in the transformation. Only the 'Inflow' and 'Outflow' key figures for the non- cumulative key figure are mapped.
You can check the property for the non- *** KF in RSD1, where you would find the corresponding inflow and outflow kf. If both of these are mapped in the transformation, the non- *** kf would calculate the value in the report in which it is included as:
Non-*** KF value = Inflow value - Outflow value.
Hope this helps.
Regards,
Abhishek.

More than Non-cumulative cubes in one MultiProvider

Hi There,
I have got two non cumulative cubes and want to build a MultiProvider on them.
Got information at couple of places on help.sap.com at one place it says MultiProvider can have more than one non-cumulative cubes at other place it says it can't. What is the right suggestion?
Thanks
Vikash

Hi,
From the performance perspective you should not use more than one Non Cumulative Infocube in a Multi Provider. If you user more than one the query will not execute parallel and execute in sequential which leads to delay in query run time.
This is a recommendation from SAP not to use morethan one Non Cumulative Cubes in a MP.
Cheers

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

Error in query due to exc aggregation with non-cumulative KF

Hi All,
when i am trying to execute a query I am getting the following errors.
SAPLRRI2 and form RTIME_FUELLEN_06-01-
Program error in class SAPMSSY1 method: UNCAUGHT _ESCEPTION.
I have calculated KF of non-cumulative KF. If I delete the calculated the query is ok.
I am working on BI 7.Did anybody got this error? any idea?
I have implemented notes 976550 and 991563
Thank you

Hi,
Any one with any suggestions?
Mohammed

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. This cube is defined by me to test the non-cumulative key figure.
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.
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

Non cumulative infocube without BX

Hi Experts,
I need to compress and create aggregates for the inventory cube (Has Non cumulative in/out flow KFs)
We do not use BX as all of the initial stock levels are defined using movements. Does this change anything?
Which way is it as I have seen both answers posted in this forum?
BF-init: Compression without marker update
BF-delta: Compression WITH marker update
OR
BF-init: Compression without marker update
BF-delta: Compression WITHOUT marker update
Thanks,
Chris

If you are not bringing BX, all BF should be compressed with marker update.

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

Non Cumulative KF in ODS

Similar Messages

Maybe you are looking for