SAP Message SMOE_MESSAGE246 - Deassignment of subscriptions can cause inconsistencies

&CAUSE&
You are using the Administration Console to deassign a site from asubscription or a subscription from a site, or to delete asubscription.
The type of the related publication is simple intelligent (sync),simple intelligent (msg) or simple bulk (msg). As a consequence,changes (insert, update, delete) of a BDoc instance are sent to a siteonly if the site has been assigned the corresponding subscription. Theassignment or deassignment of such subscriptions will not trigger asynchronization of the site database.
Example:
Your site Back-End is of sitetype R/3. It has been assigned asubscription for a BDoc type. The type of the publication is simplebulk (msg). The creation of a business object (for example, businesspartner) with identifier 111111 ensures that this business object willbe sent to site Back-End.
After deassigning the subscription in the Administration Console allchanges in business object 111111 will not be sent to the siteBack-End. In addition, a newly created business object withidentifier 222222 will also not be sent to site Back-End.
As you reassign the subscription, the following inconsistencies occur:

  • Business object 111111 has not been synchronized in the R/3 back-end.

  • Business object 222222 is not available in the R/3 back-end.

    • Procedure
    If the subscription you have selected for deassignment is stillrequired for your site, you can just leave the edit mode withoutsaving. If you are deleting a subscription or you are using theIndirect Assignment of Subscriptions, you can still cancel thedeletion.
    If the subscription is no longer needed, it can be deassigned. If asubscription was deassigned by mistake, it has to be reassigned and allBDoc instances sent in the meantime have to be resent to ensureconsistency. The resending has to be triggered from the applicationthat changed the BDoc instances.
    If a subscription has to be deleted in order to use another publicationor for changing the type of the replication object, you should ensurethat during the period while the subscription is missing no BDocinstances can be changed or sent. To ensure this, lock the applicationresponsible for the object or stop the corresponding queues andactivate them again after assigning the new subscription.