Deleting Replication Objects 

Use

If a BDoc type is no longer meant to be distributed, you have to delete the corresponding replication object.

Data can become inconsistent when replication objects are deleted since there is no information available in the source system (typically a development or test system) about the subscriptions in the target system (typically a productive system).

The replicated data to be deleted cannot be removed automatically since the function modules required for this purpose are also influenced by the delete function.

This means that you must use the Administration Console to delete the corresponding subscriptions in the target system first. Only then may you apply the transport from the source system into the target system.

Prerequisites

You must have selected the object type Replication object in the Object type selection list as well as the relevant replication object.

Procedure

You can delete a replication object by using the Object ® Delete function or the corresponding symbol in the application toolbar, providing that no publications have been assigned to it.

An intelligent or an intelligent dependent replication object can only be deleted if no interlinkage has been defined for this replication object (in table SMOHILTP there should be no entries in the fields RO1 and RO2 for the SHORT_ID of the replication object that is to be deleted). In addition, you may not define any intelligent dependent objects for an intelligent replication object.

Proceed as follows:

...

       1.      First delete the subscriptions in the target system for the affected publication. This means that the data for all the replication objects assigned to the publication is deleted on the mobile clients.

       2.      After realignment has taken place in the target system, check the following:

¡        For replication objects of type unfiltered (bulk):

Check in the look-up table SMOHLUBULK if there is still an entry for the affected publication.To do so, filter table SMOHPUBL using the name of the publication and the current industry indicator, and filter table SMOHLUBULK using the key of table SMOHPUBL for the field OBJ_ID.

¡        For dependent replication objects:

Check if there is still an entry in the look-up table of the higher level replication object. The name of the relevant look-up table can be determined from the SMOHREPOBJ record of the replication object that is intended for deletion. To do so, filter table SMOHREPOBJ for the SHORT_NAME of the replication object and the current industry indicators. The LU_TABLE field of the entry you have determined in SMOHREPOBJ then gives you the character string for which you have to search in the ABAP Dictionary - prefixed by an asterisk (*) - in order to determine the name of the look-up table. If several tables with this character string in the name are found, select the table whose name begins with the character chain "/1CRMG0/" and the industry indicator.

¡        For intelligent and intelligent dependent replication objects:

Check if there is still an entry in the look-up table of the replication object. The name of the relevant look-up table can be determined from the SMOHREPOBJ record of the replication object that is intended for deletion. To do so, filter table SMOHREPOBJ for the SHORT_NAME of the replication object and the current industry indicators. The field LU_TABLE of the entry you have determined in SMOHREPOBJ then gives you the character string for which you have to search - prefixed by an asterisk (*) - in order to determine the name of the look-up table. If several tables with this character string in the name are found, select the table whose name begins with the character chain "/1CRMG0/" and the industry indicator.

This step is not relevant for replication objects of type simple unfiltered or simple intelligent.

       3.      Now check if there is still an entry for the replication object in the extract queue. To do this you have to filter table SMOHMSGQ for the type of the replication object, using QUEUENAME = EXTRACT and MSGTYP = SMOHREPOBJ-SHORTNAME.

This step is not relevant for replication objects of type unfiltered (bulk), simple unfiltered or simple intelligent.

       4.      If the look-up table is empty and there are no more entries in the extract queue, delete the subscription for the affected publication in the source system.

       5.      After realignment has taken place in the source system, carry out the same checks there as you did in the target system.

       6.      If the look-up table is empty and there are no more entries in the extract queue, make the following modifications in the source system.

¡        For replication objects of type unfiltered (bulk) and simple unfiltered:

Delete the publication and then the replication object.

¡        For intelligent and simple intelligent replication objects:

Delete the publication to which the replication object has been assigned, and then the replication object.

If there are intelligent dependent replication objects for this replication object, then these have to be deleted beforehand, while existing dependent replication objects are deleted automatically at the same time.

¡        For dependent and intelligent dependent replication objects:

Delete the publications to which the dependent replication object has been assigned, and then the dependent replication object.

       7.      Now release the transport request into the target system.