MultiCube 

Definition

A MultiCube is a superior InfoCube that combines data from several BasicCubes/RemoteCubes, and brings it together into one context. The MultiCube itself does not contain any data; its data comes exclusively from the BasicCubes it is based on.

Use

A MultiCube allows reporting to take place using more than one BasicCube or RemoteCube. A MultiCube usually consists of more than one BasicCube, but it can also be a 1 to 1 relationship.

 

You have a BasicCube with actual data for a logically closed business area, and an equivalent BasicCube with plan data. You can combine the two BasicCubes into one MultiCube so that you can compare the actual data with the planned data of a query.

Structure

Integration

MultiCubes only exist as a logical definition. The data is still saved in the BasicCubes it is based on. A query generated from a MultiCube is divided into several queries using the BasicCubes in question, which can be worked on in parallel.

In a MultiCube, every characteristic in every BasicCube involved should correspond to one characteristic or navigation attribute (as long as these are available).

If there is ambiguity, you must tell the system (by selection), which InfoCube it is that you want to assign the MultiCube characteristic to.

 

A MultiCube contains the characteristic 0COUNTRY. A BasicCube contains the characteristic 0COUNTRY, as well as the navigation attribute 0CUSTOMER_0COUNTRY. In this case, select exactly one of these InfoObjects.

Select a key figure, contained in a MultiCube, from at least one of the BasicCubes involved. In general, exactly one of the BasicCubes provides the key figure. However, there are cases where it is better for the user to select from more than one BasicCube.

If the key figure is 0SALES, redundantly stored in more than one BasicCube (that is, contained completely in all value combinations of the characteristics), then it is a good idea to select from exactly one of the BasicCubes involved (otherwise, the multiply existing value would be incorrectly added in the MultiCube).

However, if 0SALES is in a BasicCube, for example, as an actual value, saved in another plan value, so that there is no overlapping in the data records (in other words: Sales is divided disjunctively between several BasicCubes), then it makes sense to make a selection from several BasicCubes.