cancel
Showing results for 
Search instead for 
Did you mean: 

Customer evaluations F.30 – Dynamic selections ignored in DSO (RFDRRE05).

AntonFarenyk
Contributor
0 Kudos

Dear members of ERP Financials space,

I would like to ask your opinion on the following issue.

We set-up standard Customer evaluations(configured in OBDF, created by F.29 and display F.30). In evaluation view we use standard program RFDRRSEL to select the data. In a variant for this program we want to use Dynamic selections to restrict data selected for evaluations. When we run evaluations through background job scheduled via F.29, in DSO (Days of Sales Outstanding) analysis using method 2 we want, for example, only particular document type and posting date to be considered for average sales figure calculation. Expected behavior of standard program RFDRRE05 would be to take only selected line items from customer accounts for average sales. However, this is not what program RFDRRE05 does. It instead takes total sales figures by period from KNC1 (see ABAP program RFDRRE05).

Meanwhile in the note 39883 we could read quote «In a background job, report RFDRRGEN (customers) is executed. This job in turn executes the data provision report RFDRRSEL of level 1), which selects the data limited in the respective variant. The selected data is now passed on to the level 2) reports RFDRRE01, RFDRRE02, and so on, which create and store the evaluations according to the characteristics defined in report variants on level 3)»

Indeed first 4 of 6 standard evaluations work exactly as described in OSS 39883. Meaning that Due date analysis(RFDRRE01), Payment history (RFDRRE02), Currency analysis(RFDRRE03) and Overdue items (RFDRRE04) are all take into account selections (Dynamic and usual) from RFDRRSEL. But DSO analysis (RFDRRE05) ignores Dynamic selections and even sales during current month if the key date is not the last day of month.

In fact STANDARD program RFDRRE05 fails to accurately calculate DSO, other than at the end of the month for complete periods.

So to your opinion is this a bug or bad design or normal behavior of a standard SAP program?

Best regards,

Anton

Accepted Solutions (1)

Accepted Solutions (1)

AntonFarenyk
Contributor
0 Kudos

After a month of animated discussions with SAP Support & Development support we cloned RFDRRE05 and made it work as it should.

Answers (0)