Ansicht
Dokumentation

SDRRCLEANUP - Program SDRRCLEANUP

BAL_S_LOG - Application Log: Log header data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

Purpose

You can use this report to anonymize or delete Sales and Distribution (SD) revenue recognition data which became obsolete when your system was upgraded from an SAP ERP release to SAP S/4HANA. As SD revenue recognition is not available in SAP S/4HANA, archiving this data is also not possible using archiving object SD_VBREVlike it was used to in SAP ERP.
This report provides a simplified approach to clean up the obsolete residual data.

Integration

Prerequisites

You have the authorization to delete the sales document types based on which the SD revenue recognition processes were created.

On a technical level, this means that your user profile must include the following authorization:

AUTHORIZATION OBJECT:	V_VBAK_AAT
ACTIVITY:	06
AUART:

Features

This report offers two processing modes, the Data Anonymizationmode and the Data Deletionmode.

Data Anonymization Mode

Using the Data Anonymizationmode, you can delete the customer identifiers stored in the obsolete SD revenue recognition database tables. This may be required to be compliant with the General Data Protection Regulations (GDPR). When this processing mode is used, the sold-to-party (KUNAG) information gets deleted from all selected processes’ control lines and revenue lines. The rest of the SD revenue recognition data remains unchanged in the system.
Impacted database tables: VBREVK, VBREVE,,

Data Deletion Mode

Using the Data Deletionmode, you can permanently delete the obsolete SD revenue recognition database table entries. In SAP S/4HANA, this data is not used by any standard SAP program, so keeping it in the database is a waste of resources.
Impacted database tables: VBREVK, VBREVE, VBREVR, VBREVC

Note: If your SD revenue recognition processes were not migrated to SAP Revenue Accounting&Reporting prior to your upgrade to SAP S/4HANA as explained in SAP Note 2267342, your company may need these database entries for manual reconciliation purposes. In such cases, please make sure you align with your SD, FI, and CO experts before deleting any of this data.

Selection

Selection Parameters

In the Selection Parametersgroup box, you can narrow down the selection of data that is to be processed by this report.
You have the option to restrict the selection of processes based on company code, sold-to partners, sales document type, and archived processes.
When restricting the selection to archived processes, the system only includes processes that no longer exist on database level as sales documents (VBAK) or billing documents (VBRK). Using this parameter, the report can be executed as a follow-up action after finishing the complete archiving of Sales&Distribution processes (archiving objects SD_VBAK, SD_VBRK) to clean up the remaining SD revenue recognition data.,,

Processing Parameters

In the Processing Parametersgroup box, you can further narrow down your selection.
You can restrict the selection of data based on retention days, that is, the number of days which must pass after the latest change in the process to allow the anonymization or deletion of data. The date used for comparison is the creation date of the process’ control lines (VBREVK-ERDAT). (Note: This check is only executed if the number of days is not zero.)
When the Completed Documentsradio button is selected, the status of each control line must be “Completed” to allow the anonymization or deletion.
When the All Documentsradio button is selected, the status of control lines does not matter. Both completed and open processes will be anonymized or deleted, depending on the chosen processing mode. Note that this report processes either all items of a process or none. If an item is invalid due to these checks, its entire document gets skipped.

Technical Parameters

In the Technical Parametersgroup box, you can choose a work package size to avoid memory overflow issues during processing. In each work package, the report processes as many control lines (VBREVK) as defined in the package size. The report then selects the corresponding revenue lines (VBREVE), reference lines (VBREVR), and update lines (VBREVC) to execute further checks and to perform the deletion or anonymization of data on database level. Each package gets updated in the database separately with its own “COMMIT WORK” statement. If the selected package size resulted in a single document being split into multiple packages, the report would dynamically increase the package size to ensure that all items of the document are processed in the same package. Therefore, the actual package sizes during runtime may be slightly bigger than the value of this parameter.

Standard Variants

Output

This report displays the list of messages related to the current program execution in an application log. The output shows you which documents were processed and how many of their database entries were processed. It also shows you which documents were skipped from processing and why. You will also see how many database entries were updated in total. This application log does not get saved into transaction SLG1, it is only available after execution or in the spool in case the report was executed in a background job.

Activities

Example

Scenario 1

Assume you would like to delete all processes’ data which is older than four years.
You would then set the parameters as follows:

Processing Mode:	Data Deletion
Retention Days:	1460 (365 x 4)
Status Check:	All Documents
Test Mode	Unchecked

Leave the default values of all other parameters.

Scenario 2

Assume you would like to anonymize all processes’ data which were archived in SD.
You would then set the parameters as follows:

Processing Mode:	Data Anonymization
Restrict to Archived Processes:	Checked
Status Check:	All Documents
Test Mode:	Unchecked