Aggregation Type
You use the aggregation type to control how a key figure or data field is updated to the InfoProvider.
For InfoCubes:
Depending on the aggregation type you specified in key figure maintenance for this key figure, you have the options Summation, Maximum and Minimum. If you choose one of these options, new values are updated to the InfoCube.
The aggregation type (summation, minimum & maximum) specifies how key figures are updated if the primary keys are the same. For new values, either the total, the minimum, or the maximum for these values is formed.
For InfoObjects:
Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For DataStore Objects:
Depending on the data type and DataSource, you are offered the option Summation, Maximum, Minimum or Overwrite. When you choose one of these options, new values are updated to the DataStore object.
For numerical data fields, the system uses characteristic 0RECORDMODE to propose an update type. If only the after-image is delivered, the system proposes Overwrite. It can be a good idea to change this however: If the counter data field '# Changes' is filled with a constant 1 should be updated by addition although only an after image is delivered.
Characteristic 0RECORDMODE is used to pass DataSource flags (from SAP systems) to the update.
If you are not loading delta requests to the DataStore object, or are only loading from file DataSources, you do not need characteristic 0RECORDMODE.
Summation:
Summation is possible if the DataSource is enabled for an additive delta. Summation is not supported for data types CHAR, DAT, TIMS, CUKY or UNIT.
Overwrite:
Overwrite is possible if the DataSource is delta enabled.
When the system updates data, it does this in the chronological order of the data packages and requests. You have to ensure the logical order of the update yourself. This means for example that orders must be requested before deliveries, otherwise incorrect results can be produced when you overwrite the data. This means that requests have to be serialized when updated.
You are loading data to a DataStore object. In this example, the order quantity changes after the data is loaded into the BW system. With the second load process, the data is overwritten because it has the same primary key.
Document No. |
Document Item |
Order Quantity |
Unit of measure |
|---|---|---|---|
100001 |
10 |
200 |
Pieces |
100001 |
20 |
150 |
Pieces |
100002 |
10 |
250 |
kg |
Document No. |
Document Item |
Order Quantity |
Unit of measure |
|---|---|---|---|
100001 |
10 |
180 |
Pieces |
100001 |
20 |
165 |
Pieces |
For DataStore Objects (advanced):
Depending on the properties of the DataStore object (advanced) in question, you are offered the option Summation, Maximum, Minimum or Overwrite. When you choose one of these options, new values are updated to the DataStore object.
If you have selected the modeling properties Activate Data and All Characteristics are Key, Reporting on Union of Inbound and Active Table, you can choose from the following aggregation types: Summation, Maximum and Minimum.
If you have selected the modeling properties Activate Data and Write Change Log, you can choose from the following aggregation types: Summation, Maximum, Minimum and Overwrite.
If you have not selected any modeling properties, you are not offered any aggregation types at all.