BCS 6.0 Multicube reporting capability

[Former Member]

Hi all,

We are currently desiging a SAP SEM BCS 6.0 solution for our client.

We have two consolidation area's and want to make use of the standard SAP Archiving functionality and let the BCS program build automatically the Virtual cube, Reporting Cube and the Multicube.

However as we don't want two different Multicubes as we want to report from both areas, just one with all 4 cubes below(2 reporting cubes and 2 virtual cubes), we tried to align them in the BCS databasis, so we can use the data from the two consolidation areas in one. This seems not possible.

Has anyone had the same situation with another client and can share their experiences?

Thanks,

Pieter

[Former Member]

Answered.

[Former Member]

Thanks Scotsman, that is helpfull in understanding that this architecture works well for storing the closed periods -> or better requests.

We have now managed to get two reporting cubes and two virtual cubes in one Multiprovider.

We build a query in which we can see data from the two consolidation areas.

I will close this.

Pieter

Edited by: A. Gideonse on Oct 28, 2008 7:01 PM

Edited by: A. Gideonse on Oct 28, 2008 7:22 PM

[Former Member]

Hi Pieter and welcome to SDN!

Two ConsAreas from the same data basis will be based on the same multiprovider. And there will be 2 cubes (not four): the totals one and the virtual counterpart (here I'm not talking about the other cubes that might be build upon these two).

So, what's the problem?

[Former Member]

Thanks for your answer, Eugene.

We want to use the archiving possibility as described in SAP Papers

- How to configure the Delta Load based Multiprovider Scenario

- How to use Delta-Cache and Delta Pair in SEM-BCS

In these papers they add an additional Reporting Cube on top of the Totals cube.

This is automatically done by BCS. The Reporting Cube sits next to the Virtual cube and serves purely for archiving data from the BCS Totals cube.

On top of the Reporting and Virtual cube, they have an automatic created Multicube.

Then on top of this Multicube is then again a Virtual InfoProvider. This last Virtual InfoProvider is then the place where you should build your reports on. The Virtual Infpoprovider helps the Multicube understand to read from the Virtual cube from BCS Total cube.

My questions/problems are:

1. Has anyone used this automatic created BCS archiving possibility from SAP and what are their experiences with this?

2. I want to combine data from two consolidation areas in one Multicube.

For now, we were only able to prototype succesfully a Multicube on top of the Virtual InfoProviders of

the Multiproviders. This seems very illogic and not straightforward. For the reporting landscape only, now all of a sudden we have 11 Infocubes.

Question is, do you know if it is possible (and how?) to add all 4 cubes - so 2 reporting cubes and 2

virtual cubes - into one Multicube and then add the Virtual InfoProvider on top of this again?

Thanks,

Pieter

[Former Member]

Hi Pieter,

I'm afraid, there is still a little misunderstanding between us.

I want to combine data from two consolidation areas in one Multicube.

Are you implying that data of two ConsAreas from the same databasis are sitting in two different transacional/virtual etc. cubes?

That's wrong. One databasis = one (transactional etc.) cube. ConsAreas are subsets of DB. They are all sitting together.

Before going ahead, let's confirm our mutual understanding of the terms, shall we?

[Former Member]

Hi Eugene,

Yes, we have two different databases.

One for Financials.

One for Volumes data which is much more detailed.

There are two different cubes.

Pieter

[Former Member]

Hi A Gideonse,

Yes, we are using the multiprovider scenario, but only half of what you propose;

1 transactional infoprovider (the BCS data basis)

1 virtual infoprovider

1 basic infoprovider (the BCS 'closed periods' cube)

1 multiprovider

The closed periods cube (you call it archiving) should be used to store data of prior periods.

The virtual provider sits on top of the transaction provider

The multiprovider is where you build your reports, sitting on top of the basic and the virtual inforproviders

The advantage of this architecture is that only the data that comes from the basic provider via the virtual provider requires any 'on the fly' calculations (the data in the 'closed periods' cube has already been pre-calculated when loaded).

You can therefore have real-time reporting from BCS, without requiring all report data to be calculated 'on the fly', thereby saving system resources and user time.

I hope this is of some use, please let me know if you have any further questions.