b.Service Header Part Message Guideline

b.Service Header Part Message Guideline

The Service Header provides the process context for the message for automated computer processing. Information in this header for Request Purchase Order includes:

Action Identity - used to reference a prior message tracking ID when the current message is a response or reply process

From Role - the Global Partner Classification Code listed in the PIP

To Role

PIP Code – the PIP number

PIP Instance Identifier - the unique identifier for this individual PIP message

Indicator if the message includes an attachment

The table that follows contains service header mapping for the PIP 3A4 based on RNIF V02.00.00, which is included in all 3A4 PO Confirmation messages sent to partners.

i.Service Header Guideline for RNIF 1.1, RNIF 2.0

The cardinality assigned to each Service Header Request indicates if the header request type is mandatory or optional. For example, in a single envelope request, the header must include one BusinessActivityIdentifier. This fact is evidenced by a cardinality value of 1. That same header can optionally include one domain.FreeFormText. This fact is evidenced by a cardinality value of 0..1.

Rows that are shaded grey denote elements not used by Cisco.

A partner includes elements from the table as part of their request to improve the quality of the message exchange service between the partner and Cisco.

Table : Service Header Guideline for RNIF V02.00.00