Error Handling and Auditing
PIP 0A1 (Notification of Failure or NoF) is a process control PIP that is used to communicate an exception condition that occurs outside the normal message choreography of the subject PIP.
Typically, PIP 0A1 is invoked when exceptions happen under a specific condition (namely, when the process is in “execution” state at one partner's system and may have possibly reached a “completed” state in the other partner's system) during the execution of any other process.
Execution of PIP 0A1 is shown in the asynchronous and synchronous interaction diagrams (chapter 2.6.8 of the RNIF Core spec) in both single-action and two-action activities.
A failure to complete an interface business activity in compliance with the RNIF 2.0 or RNIF 1.1 core specification can be detected by either of the two parties involved in the interface activity.
In seven different contexts (Calling Types)- the PIP 0A1 is started. The following table describes each Calling Type in detail:
| Calling Type | Initiating PIP or RNIF Process | Failure Reason |
|---|---|---|
| 1 | RNIF_Action (Two or Single Action) | The action process sent a request message on initiator side and is waiting for an acknowledgment. Maximum numbers of retries exceeded or time to perform expired. |
| 2 | PIP3A7_Buyer_Private (Single Action) | During processing, the business message on the responder side of the private process indicates that it cannot process the business message. |
| 3 | RNIF_Action (Two Action) | Time-out during waiting for response message on initiator side. |
| 4 | RNIF_Action (Two Action) | During processing of the response message in the private process on the initiator side, the private process indicates that it cannot process the business process. |
| 5 | RNIF_Two_Action_A sync_Responder (Two Action) | The action process sent a response message and is waiting for an acknowledgment. Maximum numbers of retries is exceeded. |
| 6 | RNIF_Action (Two Action) | Communications error occurred during sending a business message from the initiator to the responder |
| 7 | RNIF_Two_Action_A sync_Responder (Two Action) | Communications error occurred during sending a business message from the responder to the initiator. |
Similar to other RosettaNet business processes, PIP0A1 has an initiator and a responder process. The initiator process is implemented in the BPML module PIP0A1_V02.00. In the current implementation, there is no private process for PIP0A1 on the initiator side. The responder (which has a public and a private part) is implemented in the modules PIP0A1_V02.00_Failure-Report-Administrator and PIP0A1_Failure-Report-Administrator_Private. The RNIF 1.1 equivalent for the modules specified are PIP0A1_1.0.bpml, PIP0A1_1.0_Failure-Report-Administrator.bpml, and PIP0A1_Failure-Report-Administrator_Private.bpml. The initiator creates a PIP0A1 message and sends it. On the responder side, the framework starts the public responder process, which spawns the private process. Within the private process, customized code can be used to handle the error condition adequately.