About DSO Keyfigures

[Former Member]

Dear All,

As we have two options in tranformations for keyfigures in DSO

1. Overwrite and 2. Summation.

Could any one explain me when to go for which, examples will be very helpful. mainly i would like to know about summation.

Thanks

Rupa

[Former Member · Accepted solution]

HI,

For DataStore Objects:

Depending on the type of data and the DataSource, you have the options Summation, Minimum, Maximum 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. However, it may be useful to change this: For example, the counter data field u201C# Changesu201D is filled with a constant 1, but still has to be updated (using addition), even though an after-image only is delivered.

The 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 are only loading from file DataSources, you do not need the 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 so in the chronological order of the data packages and requests. It is your responsibility to ensure the logical order of the update. 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.

Tarak