Non Cumulative KF in DSO

Hi Experts,
Can any one say why we cant model a DSO with a noncumulative keyfigure.Any reason behind this?
Thanks!
James

Hi James,
Non-cumulative key figures always have summation as standard aggregation (aggregational behavior on the database, for example, upon compression or roll-up of aggregates). but this(Addition)is not possible in DSO.In this we can do only Overwrite functionality.
In query definition and navigation, there is no difference in the way cumulative and non-cumulative key figures are dealt. Cumulative and non-cumulative key figures can be analyzed at the same time in a query.
And you should not use more than one non-cumulative InfoCube (InfoCube with at least one non-cumulative key figure) in MultiProviders, because this could lead to incorrect query results.
The special treatment of non-cumulative key figures is only possible in the InfoCube. DataStore objects do not support this.
Regards,
Neeraja.

Similar Messages

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.

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 urgent

Hi 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

Inventory cube non cumulative KF displaying incorrectly.

Hi
I have created a inventory cube which is a copy of 0IC_C03, fed from a DSO which has the all the Material documents.
I have intitialised using the BX extraxctor to the cube, then loading data from r/3 via the dso. Have MP on top of inventory and revaluation cube.
Due to an error in the code logic i had to drop the cube and reload the data from the BX PSA and subsequently the DSO.
my problem started then, the cumulative key figure have gone haywire ie they the balance display rubbish data. the data loaded into the cube is correct
also if I delete the latest request and reload the request, then the KF display correctly. strange!
I also the same problem for value as i have a revaluation cube. the inventory values are wrong, when i do a list cube from the MP all is ok.
i checked the validity slice rsdv, it is ok.
i also only have 0calday as the non cumulative setting.
Another thing i noticed was if filter the material by one plant then i get the correct value, if i try to display all plants then it all the balances go incorrect.
also if i see the balances by month only the latest month is incorrect.
if you need more info please feel free to ask.
appreciate if some can propose a solution
Lawrence
Edited by: lcoelho on Oct 14, 2011 7:03 PM

Hi Lawrence,
SAP suggests to upload non-cumulatives NEVER from a DSO but from the PSA in parallel to DSO and Cube.
Andreas

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.

Inventory Management (Non-cumulative values)

Dear experts,
I want to extract inventory data from 2LIS_03_BF.
How do I have to configure the Key figures; for example: 0VALSTCKQTY. Is there a need to use Non-cumulative value with in- and outflow as in Content.
Which other possibilities exist?
After InfoObject config. - what are the exact next steps?
Do I load data from the 3 DataSources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM into one DSO first and then into one cube or do I have to split?
I dont want to use the BC data flow.
Thanks for your advice.
Patrick

hi,
Please search the Forum for this, this has been discussed many times.
regards,
Arvind.

How to load init for non cumulative values?

Hi folks,
anyone here, who can tell me how to load initial amounts from DSO to non cumulative values in InfoCubes?
I found only poor documentation about this.
Thanks!

hi Timo
you load initial of load as you do in the normal case only thing you have to keep in mind that before loading opening balance you have to UNCLICK NO MARKER UPDATE from the infocube and compress the request ASAP as it will greatly effect your query performance.
sanjeev

Work around for including Non cumulative cube in an infoset.

Hi Experts,
I have 4 non cumulative infocube in my production, for another reporting purpose I have to use those non-cumulative cubes combining another DSO in an infoset, but the infoset is not allowing me to include non cumulative infocube in it.
The non-cumulative infocube contains 2 non cumulative keyfigures, those keyfigures are needed for my new reporting, to get the infoset logic(inner join) is there any other possible way to get the data ?
Please let me know. your valuable input will be appreciated. Thanks in Advance.

Hi Kalpana,
Try with multiprovider.
Otherway round could be creating DSO and creating transformation from DSO as well as non-cumulative infocubes (full update) and report on newly created DSO.
Hope that helps.
Regards
Mr Kapadia
*Assigning points is the way to say thanks*

BAPI - Issue in fetching non-cumulative KF for Inventory

Hello All,
Would kindly require ur help urgently on the issue mentioned below:
We require the non-cumulative KF '0TOTALSTOCK' in the BW side for further processing. Now we are using BAPI to get the query executed and store the results in a table, so that we can fetch the value from the table.
The issue occuring is, if the Reciept Total Stock and the Issue Total Stock are same which means 0TOTALSTOCK will be '0', this gets stored in the table, but when the the values for Reciept Total Stock and Issue Total Stock are not same, the job for query execution fails giving NO ERROR.
Kindly share ur views on it, since it is critical.
Thank you.
PS: Transaction used for BAPI is RSCRM_BAPI, authorization is not an issue, query contains no formulas, and have performed basic checks with respect to BAPI query execution.
Regards,
Kunal Gandhi

Hi Kunal,
Check this links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b06c3f96-ed4f-2a10-1693-f2c76a39988f
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90886731-21e4-2a10-2ebf-901c2c2b4e3d
Basically, what you do is:
- Define a source: in your case will be a query.
- Define a target: you'll need to create a transactional DSO to save information.
- Connect both: you can simply assign fields if the query is just what you need to download, or you can have routines.
Transaction for creating APD is RSANWB. It's pretty easy and it's a graphical interface, so you should find your way easily.
Hope this helps.
Regards,
Diego

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

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

Issue due to Non Cumulative Keyfigures

Hi All,
I have created a ZCube that gets data from Purchasing and Stocks Cubes. This Zcube has got the Non cumulative Keyfigures 0TOTSTK and 0VALSTCKVAL that are mapped from the Stocks cube in the transformations.
Apart from standard cubes, I have got Transformations from a DSO to the ZCube, I defined these Keyfigures as No transformations.
Data loads are done and data comes into report with an error.
The Validity Interval has the inital value as lowerlimit.
Diagnosis
The initial value has been found as the lower limit of a validity area. This can lead to performance problems and cause queries to terminate, because potentially, non-cumulatives can be reconstructed at any point within the validity interval.
This error occurs if data is loaded to a non-cumulative cube, where the time-reference characteristic is intial (blank).
This error message can also appear when the non-cumulative cube is completely empty.
System Response
Procedure
Check the data in the InfoCube and if there is a request containing data records where the time-reference characteristic is initial (blank), delete this request and reload the request data, with the appropriate time, into the InfoCube.
Is there any chnge to be done in the transformations at DSO level for the non- cumulative keyfigures to overcome this error.
Plz Help.
Thanks in Advance
Regards,
Sudha

Hi all,
Thanks for the Info.
I have mapped all the fields from DSO to cube.Dso doent hold the non cumulative keyfigures.so they are left blank.
I have loade the data to zcube now by deleting the earlier requests. Data is loaded.
I can find entries now in RSDV.
I just have one question to be clarified.. I suspect the issue is with the time Reference char's.
When I do mappping from 0IC_C03 to ZIC_C03 i don't see the mapping for 0CALWEEK, 0CALMONTH, 0CALYEAR. I don't see these fields for doing a mapping though these fields are present in the cube.
Same is the issue wit the DSO also. I dont see the above fields to map in the target.
I don't understand why there are not displayed while creating transfformations though they are in the target.
Please let me know if you understand where I am going wrong.
Sudha

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

UDC infosource set up as Non- Cumulative

Hi, when I click on Update rules going from UD Connect 3.5 infosource to a DSO, I get the following message:
InfoSource ZCSB_REVENUE is only set up for the initial run for non-cumulatives.
Message no. RSAU122
Diagnosis
This InfoSource is specifically set for the initial run of non- cumulatives. Only certain non-cumulative key figures are therefore displayed in the update rules.
If you want to use this InfoSource differently, you have to change the setting in the source system.
I want to change this behavior to a non-cumulative one. I have tried recreating the UDC infosource, but it does not help. Any Suggestions?

Any inputs, please?

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.

Non Cumulative KF in DSO

Similar Messages

Maybe you are looking for