Creating a Service 

You must create a new service for the partner using a naming convention as follows

The service should comply to the following definition

Service Name: - “PIP”<PIP Code>”_”<PIP Version>”_”<Partner Role>. For example: PIP3A7_V0202_Buyer where 3A7 is the PIP code, V02.02 is the version and Buyer is the partner’s role.

Variable	Value
<PIP Code>	PIP standard code. Example: PIP3A7
<PIP Version Identifier>	The PIP version The PIP version identifier is found on the front page of the PIP specification and is shorter than the PIP Version. Example: V0202 is the version identifier while V02.02.01 is the PIP version.
<Partner Role>	Value must be taken from the Role Name Column of Partner Role Descriptions table  in the PIP specification corresponding to the currently executing PIP. The role should match the one assumed by the Party for which the service is defined.

This name binding for the service is runtime-relevant. The RNIF 2.0 Adapter determines the partner’s service name and the local service name for an incoming RosettaNet Action Message based on the selected header fields of the RNIF 2.0 protocol service header. The adapter then constructs the name - according to the above mentioned rules as follows:

<PIP Code> := /ServiceHeader/ProcessControl/pipCode.GlobalProcessIndicatorCode

<PIP Version Identifier> := /ServiceHeader/ProcessControl/pipVersion.VersionIdentifier

<Partner Role> := /ServiceHeader/…/MessageControl/fromRole.GlobalPartnerRoleClassificationCode

The service name for the local role would be constructed from

<Local Role> := /ServiceHeader/…/MessageControl/toRole.GlobalPartnerRoleClassificationCode

For more information see, Service