• Cluster 0, RosettaNet Support, provides partner interface administrative functionality.
    • PIPs for Segment 0A, Administrative, enables administrative activities.
    • PIPs for Segment 0C, Testing, provides testing activities.
PIP Title Description
0A1 Notification of Failure This PIP provides a mechanism for notification of business activity failures amongst participating partner roles.
0C1 Asynchronous Test Notification This is a single-action process, with asynchronous receipt acknowledgment. Its choreography and controls are similar to PIP3A7.
0C2 Asynchronous Test Request / Confirmation This is a two-action process; receipt acknowledgments and confirmation are asynchronous. Its choreography and controls are similar to PIP3A4 V02.00.
0C3 Synchronous Test Notification This is a single-action process, with synchronous receipt acknowledgment. Its choreography and controls are similar to PIP3A7, except in a synchronous response mode.
0C4 Synchronous Test Query / Response This is a two-action process; the response is synchronous, and no receipt acknowledgments are used. Its choreography and controls are similar to the synchronous mode of PIP2A9.

0A1 Notification of Failure
  This PIP provides a mechanism for notification of business activity failures amongst participating partner roles.
Business Process
0a1

A failure to complete an interface business activity in compliance with the RNIF 2.0 Core Specification can be detected by either of the two parties involved in the interface activity. Some examples are:

  1. The originating party of the business activity times-out when waiting for a specified response for their requesting business document.
  2. The responding party is unable to acknowledge, accept or process the requesting business document.

0C1 Asynchronous Test Notification
  This is a single-action process, with asynchronous receipt acknowledgment. Its choreography and controls are similar to PIP3A7.
Business Process
0c1 image

The general “Asynchronous Notification” Partner Interface Process (PIP) is a simple one-action process. Should this transaction not complete successfully, the requesting partner executes PIP0A1, “Notification of Failure.”

0C2 Asynchronous Test Request / Confirmation
  This is a two-action process; receipt acknowledgments and confirmation are asynchronous. Its choreography and controls are similar to PIP3A4 V02.00.
Business Process
0c2
  1. The general “Request Asynchronous Test” Partner Interface Process (PIP) is two-action process, consisting of a Request by the initiating partner, followed by a related Confirmation by the responding partner.
  2. Should this transaction not complete successfully, the requesting partner executes PIP0A1, “Notification of Failure”.

0C3 Synchronous Test Notification
  This is a single-action process, with synchronous receipt acknowledgment. Its choreography and controls are similar to PIP3A7, except in a synchronous response mode.
Business Process
0c3 image

The general “Synchronous Notification” Partner Interface Process (PIP) is a simple one-action process. Should this transaction not complete successfully, the initiating partner executes PIP 0A1, “Notification of Failure”.

0C4 Synchronous Test Query / Response
  This is a two-action process; the response is synchronous, and no receipt acknowledgments are used. Its choreography and controls are similar to the synchronous mode of PIP2A9.
Business Process
0c4 image

The general “Synchronous Query-Response” Partner Interface Process (PIP) is a two-action process, consisting of a Query by the initiating partner, followed by a related Response by the responding partner.