Transformation Type 
Use
You use the transformation type to control whether a key figure/data field is updated to the InfoProvider.
Features
For InfoCubes:
Depending on the aggregation type you specified in key figure maintenance for this key figure, you have the options Addition or Maximum or Minimum. If you choose one of these options, new values are updated to the InfoCube.
The aggregation type (addition, minimum & maximum) determines 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.
If you choose no transformation, the key figures are not updated to the InfoCube. This means that no data records are written to the InfoCube with the first data transfer, or that data records that already exist will remain in place in spite of subsequent transfers.
For InfoObjects:
Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For DataStore Objects:
Depending on the type of data and the DataSource, you have the options Addition, Minimum, Maximum or Overwrite. If 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. However, it may be useful to change this: For example, the counter data field “# Changes” is filled with a constant 1, but still has to be updated (using addition), even though an after-image only is delivered.
Characteristic 0RECORDMODE is used to pass DataSource indicators (from SAP systems) to the update.
If you are not loading delta requests to the DataStore object, or you are only loading from file DataSources, you do not need characteristic 0RECORDMODE.
Addition:
Addition is possible if the DataSource is enabled for additive delta. Addition 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 so in the chronological order of the data packages and requests. You have to decide the logical order of the update yourself. This means, for example, that orders must be requested before deliveries, otherwise incorrect results may be produced when you overwrite the data. When you update, requests have to be serialized.
No transformation:
If you choose no transformation, the data fields are not updated to the DataStore object. This means that no data records are written to the DataStore object with the first data transfer, or that data records that already exist will remain in place upon subsequent transfers.
Example
You are loading data to a DataStore object. In this example, the order quantity changes after the data is loaded into the BI system. With the second load process, the data is overwritten because it has the same primary key.
First load process
Document No. |
Document Item |
Order Quantity |
Unit of Measure |
100001 |
10 |
200 |
Pieces |
100001 |
20 |
150 |
Pieces |
100002 |
10 |
250 |
kg |
Second load process
Document No. |
Document Item |
Order Quantity |
Unit of Measure |
100001 |
10 |
180 |
Pieces |
100001 |
20 |
165 |
Pieces |