Non cumulative remote cube in Multiprovider

Hi all,
I have a situation. We created a multiprovider containing 1 infocube and 1 remote cube. The remote cube contains non cumulative key figure. When we create a query on the multiprovider and check the query, the system gives us a system error message saying "System error in program CL_RSR and form GET_CHANMID-01-". I have tried to find an OSS note, but could find any related notes.
The problem doesn't occur if the query built on the remote cube or on the multiprovider but without the remote cube. So I think the problem lies on using non cumulative remote cube in a multiprovider.
Has anyone encounter such a situation? Appreciate any opinion or comments.
Thank you.
Regards,
Anzar

Anyone?
I really need your advice on this issue.
Best regards,
David

Similar Messages

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.

Non-Cumulative Info-Cube (0BUS_AREA)

Hello,
I have a non-cumulative Info-Cube that as only marked 0PLANT and 0CALDAY in the u201CMaintain Non-Cumulative Valuesu201D.
When we execute the query, the stocks for the 0PLANT work fine. But, when we do the drill-down by 0BUS_AREA it doesnu2019t work. Is it possible for a cube like this to give this information?
Can anyone help me with a possible explanation?
Thank you.
Joana

Hello,
I have a non-cumulative Info-Cube that as only marked 0PLANT and 0CALDAY in the u201CMaintain Non-Cumulative Valuesu201D.
When we execute the query, the stocks for the 0PLANT work fine. But, when we do the drill-down by 0BUS_AREA it doesnu2019t work. Is it possible for a cube like this to give this information?
Can anyone help me with a possible explanation?
Thank you.
Joana

Non Cumulative Inventory Cube Remodel

Hello Gurus,
I've existing inventory cube with non-cumulative key figures with large amount of data. We are using standard non cumulative key figures 0TOTALSTCK, 0ISSTOTSTCK & 0RECTOTSTCK.
Now I've a new requirement to report issues (0ISSTOTSTCK) & receipts (0RECTOTSTCK) based only on LB. Right now they both are in base UOM. Converting them in LB in query (on the fly) is not an option because of volume / performance of report.
I'm planning to do this in backend by adding two more key figures for issues & receipts where i'll convert standard ones in LB. I'm not going to touch any of existing non cumulative key figures. But the overall structure (F table) is going to change.
I'm concerned whether this will work? Any risks? Marker updates?
Thanks.
Abhijeet

Please have a look
http://sap.seo-gym.com/inventory.pdf

How to create the General Remote Cube

Hi Experts,
pl help me to tell the steps for the HOw to Create Remote Cube.
is the mandatory for assign the 3rd party source system.
Thanks
Herald

HI,
Remote cubes(Virtual infocubes) will be used to export up-to-date data directly from a planning area.
A). we can create Virtual infocubes three types in BW.
1.SAP remote cube -- for other modules like CRM etc
2.Non SAP remote cube -- for other databases
3.with services -- for a particular functional module
B). we can create three types Virtual infocubes in BI.
a).Virtual infocubes for Direct Access
b). with SOurce system
c). Based on Funtion Module.
The above types are same(BW and BI).
You can create by RSA1> Select Infoprovider> Select Info area> Create the Infocube> Select Virtual infocubes.
Regards,
Suman.

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

Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?

A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
(1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
(2) The query runtime can be affected by the calculation of the non-cumulative.
(3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
(4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) , Issue Stock Quantity(0ISSTOTSTCK)
, Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03 business content cube. Your honest suggestions and comment are greatly appreciated!

Hello Marc,
Thanks for the reply.
I work for Dongxin, and would like to add couple of points to the original question...
Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
We would like to confirm if there would be any long term issues doing so.
To optimize the performance we are planning to create aggregates at plant level.
Couple of other points we took into consideration for using cumulative keyfigures are:
1. Parallel processes possible if non-cumulative keyfigures are not used.
2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
Once again, thanks for your input on this issue.
Thanks
Dharma.

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*

Building an aggregate on non-cumulative cube

Hi all,
My Question is very specific, kindly review the scenario below :
1) we have non-cumulative cube which was loaded with
a) Data from BX - initial stock - compressed in the cube with marker update
b) History load - compressed in the cube with "No Marker update"
c) Deltas - compressed in the cube with "with marker update'
I wish to now create an aggregate. Will the Intial-fill program generate the markers correctly in the aggregate?? i think i read an OSS note - which i cannot locate any longer - that it is not possible & markers may not be accurate on the aggregate
Arvind

Note 1116174 - MultiProvider on non-cumulative cube
It solved my problem
Regards,
Vikram.

Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

Hello all.
I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures. I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
Steps I followed:
1. Ran initialization of beginning balance with 2LIS_03_BX
2. Ran the historical job with 2LIS_03_BF
3. Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
4. Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
Now, to this point, everything was fine. Quantities were as expected. Dollar values were as expected. The problem occurs once I load deltas:
5. Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
Query example:
MATERIALA:
Initial Stock Balance = 1000 EA
Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
Now, I have the record in BW showing the stock issue of 150. However, the non-cumulative key figure within the query still shows 1000. And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance. It is like it is not recognizing the updates.
Any help would be appreciated.
Thanks,
Brent

Hi!
Here is what helped in my case, very similar to your:
In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

Inventory Cube Compression - Non-Cumulative

Dear All
I have loaded setup tables in R/3
BX as on date             TAC MCNB1
BF i.e. Historical         TAC OLI1BW
UM                            TAC OLIZBW
I have loaded the Inventory Cube form all the three Data Sources
2LIS_03_BX : Initial Status
2LIS_03_BF : Initialization
2LIS_03_UM : Initialization
The queries are <b>fine without compression</b>
I have compressed the cube
2LIS_03_BX : with marker update
2LIS_03_BF : without marker update
2LIS_03_UM : without marker update
After compression the data for Stock issues in 24,36,48,60 months is giving vague values i.e.. IT IS ADDING UP ALL THE PREVIOUS VALUES TO SHOW FINAL VALUE
WHAT ARE THE SETTINGS TO BE MADE FOR COMPRESSION OF NON-CUMULATIVE CUBES ?
AM I MISSING ANYTHING (STEPS) ?
Thanks & Regards
Daniel

Dear Anil
I have followed the same procedure
i.e.
BX-init: Compression with marker update
BF-init: Compression without marker update
UM-init: Compression without marker update
BF-delta loads: Compression with marker update
UM-delta loads: Compression with marker update
But surprisingly the values are not reflecting correctly
Thanks & Regards
Daniel

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

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.

Using Non cumulative key figure in Real time cube

Hi gurus,
I have used non cumulative key figure in a real time cube and when i tried to enter some data using RSINPUT ,it is giving an error and the data is not getting saved.
Can anyone please tell me how to use the Non cumulative key figure in the Real time cube .
Thanks in advance
Regards,
Ravikanth

Hi Ravi,
Please make sure that when you use a non cumulative key figure iun your real time info cube, then choose a time reference characteristic for that key figure.
Then, this time reference characteristic applies for all the non-cumulative values of the InfoCube and must be the u201Csmallestu201D of the time characteristics present in the InfoCube.
For more detaisl, refer to the [http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm]
Thanks & Regards,
Balajee.

How to create a non-cumulative key figure & How to make a info cube as so

Hi Experts,
How to create a non-cumulative key figure & How to make an info cube as non-cumulative cube?
Can any one kindly provide me the steps we need to performe?
Thanks in Advance,
Raj

Hi Azael,
In the How to Papers, you will find a Guide on how to take a Sanpshot view of the Stocks(How To Handle Inventory Management Scenarios in BW). Basically if you implement the Guide, you will have another cube called ICSNAP1, which will contain stock quantities /values at the end of each month. You will therefore have to take stock at the end of the last month from that cube and add up the relevant receipts and issues to arrive at the current Stock or Stock as on a particular date.
Hope this helps!
Regards
Sriram

Non cumulative remote cube in Multiprovider

Similar Messages

Maybe you are looking for