Description
This program deletes an HCM partner system consistently from HCMCustomizing. It deletes the entries required for communication with thespecified partner system from the tables TN02, TXCOM, TNCI1, TNCO1 andTNCO2.

Precondition
You must have locked the corresponding partner system immediatelybefore executing this program. Program RNCBLD00 must have run onceafter the system has been locked. Only if these conditions aresatisfied can this deletion program function consistently.
Enter the logical name of the system to be deleted.
If messages ready for dispatch to this system exist, an additionalconfirmation prompt informs you of this. You can then cancel theprogram run and transmit these messages (using the program RNCSND01)before proceeding. Note that you have to activate the partner system(momentarily) to be able to do this.
A warning is always issued indicating that the system will be deleted.You have to confirm this message to delete the system.
The system must be entered in the table TN02S for the associatedentries to be deleted from the TXCOM table. If no corresponding entryexists in TN02S, no entries are deleted in TXCOM. However, all of theremaining tables are processed.
Event control entries are always deleted, even if matching entries donot exist in the TN02S system table. You can remove all of the old Thisenables you to remove all of the old entries in the event tables evenif the TN02S entry has been manually deleted beforehand.

Output
Lists the number of records that have been deleted from thecorresponding tables.
If you have select Display deletion log on the selection screen,a list of deleted records is also output. This may be useful if youwant to set up the system again at a later date (for example, OU eventcontrol).