Using Conventions for Communication Component Names

If you are using the RNIF adapter, there is a convention for naming the communication component that the communication channel is assigned to.

1. Create a communication component in Integration Directory.
2. Adhere to the following convention when naming the communication component:

   Name: PIP<PIP Code>_<PIP Version>_<PartnerRole>

   • <PIP Code>: PIP standard code

     Example: PIP3A7

   • <PIP Version>: PIP version

     Enter the value of the PIP version identifier from the title page of the PIP specification document. Omit the period.

     Example: The PIP version identifier in the specification document is V02.02. Enter V0202.

   • <PartnerRole>:

     Take the value from the Role Name Column of Partner Role Descriptions table in the PIP specification for the currently executed PIP.

     The partner role must match the role assumed by the partner for which the communication component is defined.

Assigning a name to the communication component is runtime-relevant. The RNIF adapter determines the name of the communication component of the partner and the current name of the communication component for an inbound RosettaNet action message that is based on the selected header fields of the RNIF 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/ProcessControl/MessageControl/fromRole.GlobalPartnerRoleClassificationCode

The name of the communication component for the local role would have the following form:

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

The communication component is called PIP3A7_V0202_Buyer. 3A7 is the PIP code, V02.02 is the version, and the partner has the role Buyer.