Show TOC

Simple Aggregation LevelLocate this document in the navigation structure

Use

The following example demonstrates how the system works when a key figure value is changed (manually or automatically).

Assuming there is an basic InfoProvider suitable for planning with the characteristics product, product group, version and year, along with the key figure revenue. The aggregation level ALVL includes the same objects with the exception of the characteristic, product.

Product

Product Group

Version

Year

Sales

P1

PG1

V1

2005

10

P2

PG1

V1

2005

20

P3

PG2

V1

2005

42

The key figure revenue includes the database aggregation SUM. Therefore, we get the following result when the transaction data for the aggregation level ALVL is read from the database without restriction:

Product Group

Version

Year

Sales

PG1

V1

2005

30

PG2

V1

2005

42

If the revenue is changed from 30 to 40 and is saved as a new value, the system writes a new record with the difference of the key figure value to the basic InfoProvider:

Product

Product Group

Version

Year

Sales

#

PG1

V1

2005

10

In this type of delta records, all characteristics of the basic InfoProvider, that are not included in the aggregation level, are assigned the initial value (not assigned: #). (Here we assume that no derivations were used. For more information on this concept, see Characteristic Relationships).