The following example demonstrates how the system works when a key figure value is changed (manually or automatically).
Assuming there is an InfoCube IC 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.
Fact Table of the InfoCube IC
Product | Product Group | Version | Year | Revenue |
P1 | PG1 | V1 | 2005 | 10 |
P2 | PG1 | V1 | 2005 | 20 |
P3 | PG2 | V1 | 2005 | 42 |
The key figure revenue includes the database aggregation SUM. Accordingly, we get the following result when the transaction data for the aggregation level ALVL is read from the database without restriction:
Aggregation Level ALVL (Key Figure Aggregated on the Database Level)
Product Group | Version | Year | Revenue |
PG1 | V1 | 2005 | 30 |
PG2 | V1 | 2005 | 42 |
If you have changed the revenue 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 fact table of the InfoCube IC:
Delta Record in the Fact Table of the InfoCube IC
Product | Product Group | Version | Year | Revenue |
# | PG1 | V1 | 2005 | 10 |
In this type of delta records, all characteristics of the InfoCube that are not included in the aggregation level get the initial value (not assigned: #). (Here we are assuming that no derivations were used. For more information on this concept,
No comments:
Post a Comment