Cumulative and non cumulative cube

what is the diff bet
*** and non *** cube.
please suggest me
i will assign points

Hi Vishal,
Please go through this link.
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
Regards,
Praveen

Similar Messages

Cummulative and non cummulative cubes

Hi
what is the difference between cummulative and non cummulative <b>cubes and key</b> <b>figures</b>

hi
check this...
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
also see the thread for example,
Non-Cumulative keyfigure example
cubes which have cummulative key figures are cummulative cubes.
hope it helpss..
cheers..
Message was edited by:
tarun bafna

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

Query for Future period on a non cumulative cube

Hi Colleagues,
I have a non cumulative cube. It has data till June,2006. When I query on the cube to report the balance with period as "July,2006" it doesnot return anything. What I expected is that it would show me the balance value as of June,2006 which is the last period for which there is data.
Am I missing anything ?
Regards,
priyadarshi

If you filter by jul06 and there is no data in cube, no matches with selection happens. You need to select any data to apply calculation of balance, try to select a range of months, with an offset.
Maybe if you put the month in free characteristics instead in filter section ir worked.

Activation error on Multi Provider which has Non-cumulative Cube

Hi,
My company has upgraded the BI 7.0 from 3.5.
It is working fine so far.
But I met the below message and could not activate it when I generate the multi provider which has Non-cumulative Cube.
Define the characteristics of the validity table for non-cumulatives (Message no. R7846)
And then I checked the Single cube but Single cube has no error.
I think this is program error and searched the notes in OSS but could not find.
Does any expert know this issue?
Thank you.

Hi lee,
validity slice tables need to be defined for cubes using non cumulative key figures.
In this we need to specify the characteristic combination on which this table has be maintained.
The maintanence can be done from cube change mode, menu bar extras--> maintain non cumulative values.
This table constantly gets updated with validity dates as we upload data.
An report on this can be seen in tcode RSDV.
Naveen.A

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

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*

Validity slice is not correct for non-cumulative cube

Hello Expert,
There are two non-cumulative cube, say cube1 and cube2. Cube2 has only one more dimension of PLANT than Cube1.
Cube2 is copied from cube1 and change the char of validity.
Cube1 & cube2 use the same fill data source. That is, first load with opening balance and second with delta.
char of validity for cube1: calendar day & material
char of validity for cube2: calendar day & plant.
The query based on cube1 works well. To say cube2, the validity slice(in TXN RSDV or TBL /BIC/TCUBE2) is not correct. There is only one record which contains BLANK plant.
There are plants in F table.
I tried the following steps to recovery the validity slice, however, it made no sense.
1) PGM RSDG_CUBE_VALT_MODIFY to rebuild the validity slice structure
2) FM RSDV_VALID_RECREATE with I_REBUILD_FROM_FACT = 'X' to create validity slice from fact table.
Would you please suggest?
Thanks
XY

Hi XY,
For sure, running the RSDV_VALID_RECREATE function module in SE37 will recreate the validity table. And you can use the parameter "X" in the parameter I_REBUILD_FROM_FACT if the entire fact table should be read.
Also, to change the validity slice manually in tcode RSDV you should:
- overwrite the column 'To mode' with a 'F', which mean Fixed
- & then the 'Fixed to time' with your new value.
There is a program which allows you to modify it: Program > RSDG_CUBE_VALT_MODIFY
At
Nadja Xavier

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,

To load non cumulative cube initialize opening balance in R/3. explain?

To load non-cumulative cube i have to initialize opening balance in R/3(S278). please elaborate and what is S278 means is it LIS datasource please explain?
Thank you,
York

Dear all,
The data source 0EC_PCA_1 doesn't consider the opening balances i believe, can any experts help me solve this problem.
Regards,
M.M
Edited by: Magesh Magesh on Jun 26, 2009 2:55 PM

Compress non-cumulative cube

Hi Gurus! I'm working on a retail project. I've created an infocube based on 0RT_C36 to keep the stock movements. It is a non-cumulative cube.
After the load of the initialization data (2lis_03_bx) the compression with the option "no marker update" unchecked runs fine. The process compress about 300.000 records in a few minutes.
But after the load of historical movements, the initialization of 2lis_03_bf, the compression with the option "no marker update" checked runs for more than 10 hours. There are 400.000 records loaded in the fact table (F table). I've checked in ST22, ST21 and no errors or dumps appear. In SM50 the process was running and the number of inserted records was 250.000. After that the basis gay kill the compression...
Is it normal? Is there anything I can check to speed up the process?
Thanks!

Hi Federico,
This a common problem.
You can find also another message in this Forum section with the same problem.
You need to restrict the number of the request that you are going to compress for every job. Try also to enlarge TableSpace, in particular the temporary TableSpace, that you can subsequently reduce.
Consider that any other job, like query from user or other uploads, reduce the speedof the compression.
Ciao.
Riccardo.

Loading non Cumulative cube

Hi BW Experts,
How can I upload non cumulative cube's ?

Hi Hoyer,
Are requesting for steps ?
Then :-
1) Iniatialize opening balance in R/3 (S278)
2) Activate extract structure MC03BF0 for data source 2LIS_03_BF
3) Setup historical material documents in R/3
4)Load opening balance using data source 2LIS_40_S278
5)Load historical movements and compress without marker update
6)Setup V3 Update
7)Load deltas using 2LIS_03_BF
TQ
Kumar

How can I extract non-cumulative cube data to another cubes ?

Dear Expert,
         I copied inventory cube 0ic_c03 to a new cube : ZIC_C03 , then I loaded the data of 0ic_c03 to the new cube ZIC_C03 .
the loading was sucessful, but the result of report of the ZIC_C03 was not correct. After looking into the problem, I found out
the new cube can successfully extract data related with "Goods movement" & "Revaluation", yet the extract of "Open Balance" does not seems to work.
         I have read through Note:375098, in which I could not find (InfoObject 0RECORDTP) in my start routine as mentioned in the solution
,and the note was not mentioned valid for BW 3.5 release.
         How can I extract non-cumulative cube data to another cubes correctly in BW3.5 release SP20?
   Thanks !

Hi,
Check Routines in Update rules wether same code is wrriten in new cube
cheers,
Satya

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

Can I use return table in non-cumulative cubes upd rules?

hi,
Is it possible to use return table in non-cumulative cubes upd rules?
What I mean is:
In non-cumulative cubes I need to use Automatic Time Conversion for time chars and when I use return table I have to map fields from comm structure to return table.
I am designing stock cube (with granularity on storage bin and quant level) where material movement data is took from Transfer Order docs. Data for source and target storage bin are in one document item, so I have to split each record.
Regadrs,
Andrzej
ps. Maybe somebody has some technical documentation on Automatic Time Conversion?

Hello Andrez,
May be this code will be useful for you.
*data decleration
data: num type i,
      num1(2) type c,
*variable for fiscper
      lv_fiscper type RSFISCPER,
*variable for the calendar month
      lv_calmonth type RSCALMONTH,
*variable for the period
      lv_period type T009B-POPER,
*variable for the fiscal year
      lv_year type T009B-BDATJ,
*variable to find out the calendar quarter
      lv_month TYPE RSCALMONTH,
      lv_calquarter type RSFO_CALQUARTER.
*ICUBE_VALUES contain data for cube.Put these value into RESULT_TABLE
RESULT_TABLE = ICUBE_VALUES.
*add 12 times entry into result_table for 12 months
do 12 times.
append RESULT_TABLE.
enddo.
*processing for the split the value into 12 periods
loop at RESULT_TABLE.
num = num + 1.
num1 = num.
*divide the value by 12 for each month
RESULT_TABLE-/BIC/ISMPLNRV = COMM_STRUCTURE-/BIC/ISMPLNRV / 12.
RESULT_TABLE-CRM_CURREN = COMM_STRUCTURE-CRM_CURREN.
case strlen( num1 ).
WHEN 1.
concatenate RESULT_TABLE-fiscyear '00' num1 into lv_fiscper.
RESULT_TABLE-fiscper = lv_fiscper.
WHEN 2.
concatenate RESULT_TABLE-fiscyear '0' num1 into lv_fiscper.
RESULT_TABLE-fiscper = lv_fiscper.
endcase.
lv_period = lv_fiscper+4(3).
lv_year = lv_fiscper(4).
*find out the calendar month from the period and year
CALL METHOD CL_RSAR_FUNCTION=>FISCPER_CALMONTH
EXPORTING
    I_FISCPER = lv_PERIOD
    I_FISCVRNT = 'Z9'
    I_YEAR     = LV_YEAR
   I_CASE     = 0
IMPORTING
    E_CALMONTH = lv_calmonth
RESULT_TABLE-CALMONTH = lv_calmonth.
*find out the calendar quarter from the fiscper
concatenate lv_fiscper0(4) lv_fiscper5(2) into lv_month.
*find out the calendar quarter
if not lv_month is initial.
    CALL METHOD CL_RSAR_FUNCTION=>MONTH_QUARTER
      EXPORTING
        I_MONTH   = lv_month
      IMPORTING
        E_QUARTER = lv_calquarter.
    if sy-subrc <> 0.
      lv_calquarter = '00000'.
    endif.
else.
    lv_calquarter = '00000'.
endif.
RESULT_TABLE-CALQUARTER = lv_calquarter.
modify RESULT_TABLE.
endloop.
Regards
Gopal

Cumulative and non cumulative cube

Similar Messages

Maybe you are looking for