Confirmation
Use
The UPS represents a cross-system process that accompanies message distribution. This process begins in the source system, then begins in the target system, with the posting of the message of the original packet. The process runs through various
statuses until it ends in the target system with rejected or posted. Notification of these status changes can be sent to the source system, so that the source system can monitor the progress and status of the process. This especially applies to the two final statuses, which also define the process as completed in the source system.A confirmation of the UPS is an independent message of message type UPSRCP, which transfers status changes in the target system back to the source system (in the opposite direction to the distribution direction of the process).
Integration
For each status change in the target system, the settings for the packet type of the ALE distribution unit are read, and a confirmation is sent to the sending system if required. This confirmation is posted to the source system with the relevant ALE distribution unit, thereby updating the status. Except for the two final statuses, this status is for documentation purposes only.
The confirmation for status posted contains the object list of all objects posted using the ALE distribution unit. In the source system, the replication table (see also
Filtering) can be updated for these objects, with status P (posted).Prerequisites
In Customizing for the UPS , under Define Packet Type, you have defined which statuses (in the target system) trigger a confirmation. A confirmation is always sent for the two final statuses.
|
Status |
Key |
Confirmation |
|
Received |
UPRC |
possible |
|
Approved |
UPAP |
possible |
|
Contains errors |
UPER |
possible |
|
Partially posted |
UPIN |
possible |
|
Rejected |
UPRJ |
always |
|
Posted |
UPPO |
always |
Result
The result list contains the IDoc number and the new IDoc status.