Ansicht
Dokumentation

RSETESTD - Delete IDocs

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

This report deletes IDocs without archiving them. It provides the option of also deleting other objects that were created during IDoc generation - objects such as work items, links, RFC entries, and application logs.

Integration

Make an IDoc selection in accordance with the selection criteria given.
If the checkbox 'Test Run' is active, the IDocs and linked objects will be determined in accordance with the selection made, but they will not be deleted.
Using the 'Maximum Number of IDocs' parameter, you can control how many IDocs should be deleted. If you leave this parameter empty, all the IDocs in your selection will be taken into consideration.

Prerequisites

Features

Determining the linked objects is a complex process. Activate the additional functions only if the respective objects are created during IDoc generation and are not already removed from your system by another action.

Selection

Standard Variants

Output

A list with the respective number of selected IDocs and objects will be issued.

Activities

Deleting interface data:
For each individual IDoc, the system determines whether work items exist in accordance with the settings from transactions WE46, WE42, and SWE2. If your selected IDocs are not generated through work items, or if no error work items are incurred during processing, you should deactivate this option. This option is not necessary either if you generally reorganize your work items - for example, using the report RSWWWIDE.

Deleting tRFC entries:
For each outbound IDoc, the system checks whether there are still entries in the RFC layer and whether these are to be deleted. If such entries exist, this generally means that the IDocs have not been transmitted and this points to a general error. The entries can only be deleted if you do not want to transmit them. If you generally monitor or reorganize the RFC queues (transactions SM58, SMQ1), you should deactivate this option.

Deleting application log:
For some message types, such as MATMAS, if there is an error, application logs on the status are generated in addition and, accordingly, a link is provided in the status details. If no link is provided in the status details, no application logs relevant here are created and the option should be deleted. This option is not necessary either if you generally reorganize your application logs - for example, using the report SBAL_DELETE or transaction SLG2.

Deleting links:
During IDoc generation, links are created both for inbound as well as outbound IDocs. If you generally do not require the links, you can suppress their generation using transaction WENOLINKS. This option is not necessary either if you generally reorganize your links - for example, using the reports RSRLDREL, RSRLDREL2.

Commit counter
Due to the quantity of data, the selected data is processed in the form of individual packages. If database terminations occur because of the high volume of data, reduce the counter.

Example

CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3297 Date: 20240520 Time: 131105     sap01-206 ( 73 ms )