Why we need to unload non-cumulative

Dear all,
why we need to unload non-cumulative cube. what are the step needed?
Thanks
V.G.VG

Hi,
Non-cumulative key figures are not summarized: examples are head count, inventory amount;
These are always in relation to a point in time; for example we will ask how many employees we had as of last quarter. We don't add up the head count.
Steps to load non-cumulative cube:
1. Initialize opening balance in R/3 (S278).
2. Activate extract structure MC03BF0 for datasource 2LIS_03_BF.
3. Setup historical material document in R/3.
4. Load opening balance using data source 2LIS_40_S278.
5. Load historical movements and compress without market update.
6. Setup V3 update.
7. Load delta using 2LIS_03_BF.

Similar Messages

What are the steps to unload non cumulative cubes

Dear friends,
can any one of you let me know, What are the steps to unload non cumulative cubes.
Thanks in Advance.
Chandan Kumar

Hi,
what do you mean by unload? Do you want to delete the whole cube or just special requests.
You should delete the requests from the top until this request where you get wrong data.
Or press on the trash bin at the top if you want to delete the whole cube.
Regards,
Juergen

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.

Loading non cumulative values

hi,
Why do we require two separate infosources for loading the initial non cumulative value and the subsequent non cumulative changes?
Regards
Deepti

Hi Deepti,
Basically you can omit the first step of initialization with one infosource and just you can use only infosource to laod full data as two infoaources are seldom used.
But basically first infosource is for initialization(One value for a combination of caharcteristica) and the second one brings the change after wards).
But this funcionality you can achieve through one infosource also no need for another one.
Even an int and full repair request will do the same thing and subsequent delta's will pick the changes
More information you can find on this link.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/02/9a6a22244411d5b2e30050da4c74dc/content.htm
Assign points if helpful
Thanks

Non-cumulative cubes require 0CALDAY in Netweaver 2004s?

Dear all,
I just noticed, that under NW2004s you are not able anymore to activate a cube (containing non-cumulative data, like stock data) that does not contain 0CALDAY as a time characteristics.
So far our stock cube is only based on 0CALMON and I have not planned to change this. It worked for many years and I really do not need 0CALDAY in there...
Does someone know, why this has changed and whether I can do anything against it? Is there some kind of documentation or information regarding this change?
Thanks,
Andreas

Hi,
this happesn becuase non-cumulative aggreagte based on key date( ie.e values of the key figures till that date value) and if there is no key date given in the query then they take 0CALDAY as defualt key date.
Now in some cases the two cubes may be able to show the correct data becasue of aggregation happening on that level may bring the correct result but in some cases the date could be different and thats why the values are not macthing
Thats why it is not allowed to use more then one non-cumulative in a multicube.
Thanks
Ajeet

Cumulative and Non Cumulative Keyfigures

Hi,
What are Cumulative and Non Cumulative Keyfigures..? and
what is the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
Can you please tell eloborately?
Regards
Naresh.

Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,

Non-cumulative value Parameters EFFECT

Hi,
I am customizing the 0IC_C03 inventory cube to get to the reports we need. But the query performance is extremly slow. We do not have BI Acceleratior, but aggregates are build for my query. So I duplicated the cube and removed 0MATERIAL from the non-cumulative parameter value for the cube, and have only 0CALDAY and 0PLANT. When I run the same query it runs way faster than before. All I did was remove the 0MATERIAL as one of the possible parameters.
I would like to know the role of these parameters and the effect of not having 0MATERIAL as one of the parameter value.
Anyone know why the performance difference?
Also looking at the /BIC/ZL* cube with 0MATERIAL, the record counts are as high the material count. Now after removing the same table has lot less records.
Could anyone explain about this?
Thanks,
Arthur.

Hi,
The basic purpose of Non-cumulatives is to get the values for them depending upon the Time Characterestics alone and not on any other characterestics. As far as I know you cant use 0MATERIAL as the aggregation reference Char.

Unserrialized delta for non cumulative keyfigure

Hello Friends ,
Why the update mode is unserillized delta at the time of non cumulative KF extraction ?
Regards,

Hi..
As per my knowledge there is no such rule........
There are three Update modes :
V1 - Synchronous update{DIRECT DELTA}
V2 - Asynchronous update{QUEUED DELTA}
V3 - Batch asynchronous update{UNSERIALIZED V3 UPDATE}
V1 >> Synchronous Update Method When we use this type of update method after the first successfully entered the signal comes back as the first record is entered successfully. Then only the next record will enters into the file. If the first record fails, then there is no further process. Even though the first record enters into the file successfully, the 2nd record will wait until the signal comes back. So here a performance is decreases. One more point is that there is no background process for V1 update method.
V2 >> Asynchronous Update Method When we use this type of method there no need to the signal comes back to enter the second record. It automatically the 2nd record will enters into the file. If there is any in the first record, it will not wait until it is corrected; the 2nd record enters into the file. Here the first drawback is over comes here. But the 2nd one is there i.e. here also there no background process.
V3 >> is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (eg in LBWE definitions) to process these. This is again to optimize performance.
Check this link :
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
Hope this helps you.....
Regards,
Debjani.......

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.

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.

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 Inventory cube to snapshot Inventory cube scenario

We currently have a non-cumulative Inventory cube in production system and the stock values match to ECC data. Now we want to build a snapshot cube (to improve query performance) and the question is can we use the current cube (non-cumulative) as data source for the new snapshot cube or do we need to load it from ECC? Is there any special handling needed if it is loaded from current cube?
Thanks!

Hi,
You can use the existing cube, but make sure that you have implemented the OSS Note 1426533 before doing this.
Regards,
Raghavendra.

Inventory management: non-cumulatives VS. snapshots

In the How to Handle Inventory Management Scenarios in BW, I read that (p. 2):
- Inventory management with non-cumulative key figures is better when "90 percent of all materials were moved 1 time in the month";
- Inventory management with SnapShots is better when "90 percent of all materials were moved 1 time in the month".
I think the second sentence is not correct. But what can be the right number of movements to be considered?
Thanks a lot,
Davide

Hi Ajay,
so my next question is:
Besides the time granularity needed (daily-level vs. monthly-level), is there a threshold for the number of movements, that could be used to choose one of the two models?
I mean, if materials are moved on average e.g. less than 10 times per month, the non-cumulative architecture could be best one. While if there are more than 10 times per month, the snapshot architecture could be more appealing. In this example, 10 movements per month is the threshold.
Cheers, Davide

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.

Why we need to unload non-cumulative

Similar Messages

Maybe you are looking for