When a transaction with your trading partner expires or times out, a PIP 0A1 Notification of Failure can be initiated. To initiate NOF, add the invocation of NOF on timeout in your process model. PIP 0A1 is designed to communicate between trading partners when errors occur at the various stages of processing. This informs both trading partners that a problem occurred and where to look for the issue. To illustrate how a Notification of Failure works, the following example explains what happens when there is a failed conversation.

Acting as the initiator, you send your initial request to your partner and receive a Receipt Acknowledgement (ACK). The conversation waits for a Response document from your trading partner, but none arrives. If no response is received within the specified timeout time, the conversation in your enterprise expires.

When a conversation expires in your enterprise, your system will initiate the PIP 0A1, as defined in your process model, to notify your trading partner that you never received a response and there may be a problem in the trading partner’s system.

RosettaNet Module sends a PIP 0A1 Notification of Failure using the alternate delivery settings defined in the Trading Partner profile. This alternate delivery method is used instead of the preferred delivery method whenever there is a communication failure, for example, when your partner’s Web server is down. If no alternate delivery method is defined in the trading partner’s profile, RosettaNet Module uses the preferred delivery method. If you did not specify a preferred delivery method, an error occurs.