Corrections in the UPS (SAP Library - PLM Product Data Replication)

Corrections in the UPS

Use

The distribution of objects in a UPS is asynchronous. For this reason, the processing using the UPS and the UPS in the source system must set up the object lists required in the target system independently, to allow a correct, consistent status of all objects. This object list can contain errors due to technical or organizational problems. For this reason, you can use a correction packet to change the object list of the distribution unit, and thereby correct the distribution process.

Prerequisites

In Customizing for the UPS, you can define whether corrections in the source or target system are allowed for a packet type.

Authorization object B_UPS for the UPS also allows you to define user-specific authorizations for creating correction packets (UPSMODE = 'C').

Features

When the current packet of a distribution unit is released, the object list is fixed. It can only be changed by a correction packet. If Customizing settings allow, a correction packet can be created.

Like the original packet, the correction packet goes through the statuses of the UPS.

Correction packets allow the following changes to the UPS object list:

Change	Description
Insert	A new object (status) is included in the object list. This makes it a relevant part of the distribution unit. When the packet is distributed, a message is set up for this object. As for all other objects in the unit, the object must be posted successfully to the target system before the distribution process is complete.
Update ('UPD')	An object already sent is to be distributed again. If there were problems in message processing for distribution, you may need to replace a message. When the packet is distributed, a new message is set up for this object. It must be posted successfully to the target system before the distribution process is complete. The existing message is no longer relevant to the subsequent posting process. It is set to obsolete (IDoc status ‘67’).
Delete ('DEL')	An object already sent is to be deleted. The object is no longer relevant to the successful completion of the distribution process. For this reason, it is deleted from the object list. When the correction packet is distributed, a message is set up for the object. The existing message is no longer relevant to the subsequent posting process. It is set to obsolete (IDoc status ‘67’).

In addition to a correction created by the source system, you can make local corrections in the target system. You can only delete objects from the object list that are not relevant for the target system. The source system is not informed. If a correction is sent from the source system to the target system, the correction is posted after all corrections so far – including local corrections.

Note

When you update or delete an object from the object list, it may occur that the relevant message has already been posted in the target system. The correction then has no further effect. The message remains posted and the changes to the database remain.

In conjunction with the replication table (see also Filtering), conflicts may occur if there are local corrections in the target system. If the distribution status for filtering is set to S (sent), an object is not sent again, even if the object has been deleted by a local correction. So the object will still be missing from the target system in a subsequent distribution, which may lead to inconsistencies.

If a correction packet from the source system is posted to the target system, and the distribution unit has already been posted or rejected, the corresponding message is set to obsolete (IDoc status ‘68’) and can no longer be posted. So the correction is too late.