Error Cases in Private PIPs

These are some RosettaNet cases in which a private process causes an error condition, for example:

• On the Initiator side in a two-action process: the private process is unable to process the response message successfully. In this case, the flag ProcessStatus must be set to false. After passing the ProcessStatus back to the public PIP, a PIP0A1 will be sent to the responder side automatically.
• On the initiator side, a private process is started without PrimaryDocument (that is, no PO Update Notification): in this case public PIP is not started and the FinalPIPStatus is set to Error: Process started without PO Update Notification document.
• On the responder side in a single- or two-action process: the private process is unable to process the request document (for example, no PrimaryDocuments are read from file system). In this case, a PIP0A1 is sent back to the initiator automatically.