Description
Report RKADELIT deletes those posting rows from tables COEP and COEPLin the current system that were created in this system and whose copieswere sent via ALE. If during this process all posting rows for onedocument are deleted, the document header is also deleted from tableCOBK.
You need to call up this report, because automatic deletion is notpossible. When you archive in the system in which the document wascreated, the posting rows sent via ALE are not archived. They remain inthe sending system. When you archive in the receiving system, thesystem archives only those rows that also exist in this system - theyare only copies.

Procedure

• Specify the controlling area from which the ALE posting rows are to be
deleted.

• Enter a To-posting date and/or To-entry date to limit the number of
posting rows to be deleted.

• The system considers for deletion only the posting rows that were
posted (entered) before the To-posting date (To-entry date).

• Select "Test run" if you want to execute the deletion in a test mode.

"Test run" is the standard setting.

• Execute the program.

Precondition
You are using ALE.
Deletion should take place when


• the posting row copies have arrived in the receiving system,


• you no longer wish to display these posting rows in the target system.

Output
The system outputs the following:


• General processing information (User who started the report, start
time, start date, and so on),

• Statistics to show the number of documents with ALE posting rows (total
number of records read) and the number of deleted documents (totalnumber of records deleted) for table COBK.

• Statistics for tables COEP and COEPL to show how many records were
selected for deletion (total number of records read) and how manyrecords were actually deleted (total number of records deleted).
In the test mode this last figure is always zero.