Complex Aggregation Level

Example: Characteristic product in InfoProvider IP

Let there be an InfoProvider MP, which contains the basis InfoProvider BIP_I and the plan basis InfoCube BIP_P. The actual basis InfoProvider BIP_I contains the characteristics product, product group, version and year, as well as the key figure profit. The plan basis InfoCube BIP_P contains the same objects with the exception of the characteristic, product. An aggregation level ALVL_MP is defined on the InfoProvider IP, containing all characteristics of the InfoProvider.

The following two data records of the underlying basis InfoProvider yield the following data records in InfoProvider IP:

Data record in actual basis InfoProvider BIP_I

Data record in plan basis InfoCube BIP_P

Data records in InfoProvider IP (or ALVL_IP)

The data records in InfoProvider IP are generated from the records of the underlying InfoProvider using a UNION operation. The InfoProvider is always included so as to ensure that the "origin" of the relevant data record is known at the data record level.

If new data records are generated during manual planning or using the planning functions, the system ensure that every record of the InfoProvider can be assigned back to the InfoProviders contained in the InfoProvider uniquely and without loss of information.

The following table shows an example of a data record that could not be assigned.

Example of a record in InfoProvider MP that could not be assigned

The data record belongs to InfoProvider BIP_P. This InfoProvider does not returns a product in the MultiProvider however. This means that P1 is not permitted.

In manual planning, data cells that could lead to this type of record are not input ready. In planning functions, the system ensures that data records like these cannot be saved.