What is Non-Cummulative Cube

Hi..All
1) Can any one explain What is Non-cummulative InfoCube?
2) Why is there a restriction of 16 Dim tables in an Info Cube and 16 key fields in an ODS?
With Regards
Jonn
Due points will be assigned for best answer

Hi Jonn,
1)I do not have idea about any Non-cummulative InfoCube ,but I know that there is concept, kind of cummulative /Non-cummulative Key figures.
please go through,
2) Restriction of 16 Dim tables in an Info Cube and 16 key fields in an ODS is because of the database limitation.
For example like as we know that fact table is having 16 dim IDs which are behaving as composite key as of 16 foreign keys.
Database concept is that ,there is limitation to keep maximum 16 primary keys on one table.
This is limitation of database thats why we have this cube and ODS is having limitation.
Please reward if worth!!
With Regards

Similar Messages

Not able to compress the init request for non cummulative cube

hi sdn
i'm not able to compress request for stock init( for some plants) in non cummulative cube with a marker update the job is cancelled when I see the log it is showing no. of sql lines
and job terminated.
what may be the cause of the problem
ruabne

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.
Hope it helps.
Regards

Cummulative and non cummulative cubes

Hi
what is the difference between cummulative and non cummulative cubes and key figures

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

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

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.

Validity Table in Non cumulative cube

Hi Friends,
What is the use of validity table in Non cumulative cube?
I have already studied the document 'How to Inventory
Please can any one explain me with example.
Thanks & Regards,
Ramnaresh.P.

Hi,
Validity table is created for non-cumulative key values.
Non cumulative key figures are one which are not possible to cumulate such as head count, inventory amount, these are always in relation to a point in time.
Regards,
Shiva.

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

Urgent : Query on Non cumulative cube

Dear BI Experts,
I have a non cumulative cube to help me report Stock Balance. It has stock entries from Jan till June,2006. When I query on the cube to report the balance as of Current Period (July,2006) it doesnot return anything. What I expected is that it would show me current stock balance (from Jan till June,2006) though my selection date is in July where there is new stock update done in July.
I tried compression on the cubes as well but didnot change the result.
Can anybody help.
Kind regards,
priyadarshi

Hi Riccardo,
Thanks for your very useful answer. I have "Company" , "SetOfBooks" , "Material" & "0CALDAY" in my validity table. Here For every combination I see a record in the validity table with "Fixed To Time" set with the last transaction dates for the combination. But I would like to preset the "Fixed To Time" for each record to some value like "31-12-9999" .
Should this be possible & how ?
Regards,
priyadarshi

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

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

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

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

What is Non-Cummulative Cube

Similar Messages

Maybe you are looking for