Show TOC

Procedure documentationDeleting Publications

 

You can delete publications when they are no longer needed for data distribution.

Data can become inconsistent when publications are deleted, since there is no information available in the source system (typically a development system 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 can the transport be imported from the source system into the target system.

Prerequisites

You have selected the object type Publication in the selection list Object Type.

Procedure

You can delete a publication by using the Start of the navigation path Object Next navigation step Delete End of the navigation path function or the corresponding icon in the application toolbar, providing that no subscriptions have been assigned to it.

To delete a publication, proceed as follows:

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

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

    • For publications of type Bulk:

      Check in the look-up table SMOHLUBULK whether 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 intelligent publications:

      Check that the look-up table of the corresponding replication object no longer contains an entry. 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 indicator. The LU_TABLE field 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 the ABAP Dictionary, to determine the name of the look-up table. If several tables are found with this character string in the name, select the table whose name begins with the character chain /1CRMG0/ and the industry indicator.

      Note Note

      This step is not relevant for publications of type Simple Bulk or Simple Intelligent.

      End of the note.
  3. Now check whether 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.

    Note Note

    This step is not relevant for publications of type Bulk, Simple Bulk, or Simple Intelligent.

    End of the note.
  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 in the target system.

  6. When the look-up table is empty and there are no more entries in the extract queue, delete the publication in the source system.

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