When to use ‘Summation’ in a Standard DSO

While loading data to a standard DSO, a key figure can be updated as ‘Overwrite’ or ‘Summation’.

With an overwrite option, the previous value of the key figure which is already there in the active table of the DSO will be overwritten with the new value.

Whereas with the ‘Summation’ option, the values will be summed up in the active table.

capture

If we use cube as target instead of a DSO, the values will be summed up always in the fact table of the cube.

Thus, overwrite functionality is a special feature of a DSO.

However, there are some scenarios where Summation option is needed for a DSO. Below I have elaborated one such scenario.

The GL account data for customers is in below form-

Customer Doc ID Calday Doc Status Posting date Net due date Clearing Date Amount in USD
C1 5678 11/09/2016 O 11/09/2016 12/05/2016 150
C1 5678 11/11/2016 C 11/09/2016 12/05/2016 11/11/2016 -100
C1 5678 11/12/2016 C 11/09/2016 12/05/2016 11/12/2016 -50

Here, the customer C1 has to pay an amount of 150 dollars as on 9th Nov, 2016. The Net due date for the amount is 5th Dec, 2016 after which the Amount will be treated as overdue for dunning.

The same customer has done the partial payment of 100 dollars on 11th Nov. The rest of the amount he pays on 12th Nov. Hence the payment is completely cleared on 12th Nov, 2016.

If this kind of data is loaded to the target DSO, we have to sum up the amount is last column to get the correct amount ignoring the status. Thus for same customer, document no and posting date, amount should be summed up to get the correct open amount.

This will reflect the correct account receivables for the customer on a given calday.