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-

CustomerDoc IDCaldayDoc StatusPosting dateNet due dateClearing DateAmount in USD
C1567811/09/2016O11/09/201612/05/2016 150
C1567811/11/2016C11/09/201612/05/201611/11/2016-100
C1567811/12/2016C11/09/201612/05/201611/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.

Comments

Post a Comment

Popular posts from this blog

Sample ABAP program for Updating notepad file data to Internal table and Sending it to Application server

 *--Structure type TYPES: BEGIN OF TY_STD, RONO TYPE C LENGTH 4, NAME1 TYPE C LENGTH 20, GEN TYPE C LENGTH 6, FEES TYPE C LENGTH 10. END OF TY_STD. *--Header line and internal table DATA WKA TYPE TY_STD. DATA INT_TAB TYPE TABLE OF TY_STD. *--Application server files are known as "Datasets" *--here "fname" is the Dataset DATA FNAME TYPE C LENGTH 40 VALUE "StudentsInfo.txt". *--Convert notepad file data into internal table CALL FUNCTION 'GUI_UPLOAD' EXPORTING FILENAME = 'C:Documents and SettingsAdministratorDesktopstudents.txt' HAS FIELD_SEPARATOR = 'X' TABLES DATA_TAB = INT_TAB. *--Sending data to Application Server OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT. LOOP AT INT_TAB INTO WKA. TRANSFER WKA TO FNAME. ENDLOOP. CLOSE DATASET FNAME.
Read more

OPEN SQL EXAMPLES IN ABAP – PART 2

 ******************************************* **displaying Raw Materials and Finished products **only from MARA table. DATA WA TYPE MARA. * **--WHERE clause is for filtering the records SELECT * FROM MARA INTO WA WHERE MTART = 'ROH' OR MTART = 'FERT'. WRITE: / WA-MATNR, WA-MBRSH, WA-MTART, WA-MEINS. ENDSELECT. * **************************************************
Read more

Domains and Data Elements

  Domains A domain provided Technical attributes (type, length and possible values) for a field. The definition of domain in ABAP is same as that in Mathematics. In the world of Mathematics, a domain is defined as the set of input values that are valid for a given function. The same holds true for domains in ABAP. To understand this, let us first see what is the role of domains in ABAP data dictionary. Domains -> Data Elements -> (Structures, DB tables, program references etc.)
Read more