Add a messaging ID

You can add a messaging ID to a partner or to a community.

Add a messaging ID to a partner

  1. In the B2Bi user interface, select Partners > Manage partners.
  2. The interface displays the Partners page.
  3. From the list of available partners, click the name of the partner for which you want to add a messaging ID.
  4. The interface opens the Summary page for the selected partner.
  5. Every partner must have at least one messaging ID in order to be able to trade messages with other partners or communities. If you have not already created a messaging ID for the current partner, the following command is displayed: This partner has no default Messaging ID. Add a Messaging ID. You can either use this command to go directly to the messaging ID screen, or continue this procedure.
  6. On a partner Summary page click Messaging IDs in the navigation graphic at the top of the page to open the Messaging IDs page.
  7. This page displays a list of the messaging IDs that have been created for the currently-selected partner.
  8. Click Add a Messaging ID.
  9. Enter a name for the messaging ID. This is the name that identifies the messaging ID in the user interface.
  10. In the Messaging standard box, select the standard for this ID. For each standard, you must complete additional fields on this page. See Messaging ID fields for specific standards.
  11. When the required fields are compete, click Finish.

Add a messaging ID to a community

  1. In the B2Bi user interface, select Trading configuration> Manage trading configuration.
  2. The interface displays the Communities page.
  3. From the list of available communities, click the name of the community for which you want to add a messaging ID.
  4. The interface opens the Summary page for the selected community.
  5. On a the Summary page click Messaging IDs in the navigation graphic at the top of the page, to open the Messaging IDs page.
  6. This page displays a list of the messaging IDs that have been created for the currently selected community.
  7. Click Add a Messaging ID.
  8. Enter a name for the messaging ID. This is the name that identifies the messaging ID in the user interface.
  9. In the Messaging standard box, select the standard for this ID. For each standard, you must complete additional fields on this page. See Messaging ID fields for specific standards.
  10. When the required fields are compete, click Finish.

Messaging ID fields for specific standards

EDIFACT

  • Syntax group – The appropriate syntax to use for messages.
  • Interchange partner ID – The interchange sender's identification (S002 0004) or the interchange recipient's identification (S003 0010)
  • Identification code qualifier – The interchange sender's partner identification code qualifier (S002 0007) or the interchange recipient's partner identification code qualifier (S003 0007)
  • Interchange internal identification – The interchange sender's address for reverse routing (S002 0008) or the recipient's routing address (S003 0014)
  • Interchange internal sub-identification – The interchange sender's interchange sender internal sub-identification (S002 0042) or the recipient's interchange recipient internal sub-identification (S003 0046)

HL7V2

  • Application namespace ID – One of three elements that, together, uniquely identify the sending (HD 00003) or receiving (HD 00005) application.
  • Application universal ID – One of three elements that, together, uniquely identify the sending (HD 00003) or receiving (HD 00005) application.
  • Application universal ID type – One of three elements that, together, uniquely identify the sending (HD 00003) or receiving (HD 00005) application.
  • Facility namespace ID – One of three elements that, together, uniquely identify the sending (HD 00004) or receiving (HD 00006) facility.
  • Facility universal ID – One of three elements that, together, uniquely identify the sending (HD 00004) or receiving (HD 00006) facility.
  • Facility universal ID type – One of three elements that, together, uniquely identify the sending (HD 00004) or receiving (HD 00006) facility.

IDOC

  • Partner number – The partner number of the sender (SNDPRN) or the receiver (RCVPRN)
  • Partner port – The port of the sender (SNDPOR) or the receiver (RCVPOR)
  • Partner type – The partner type of the sender (SNDPRT) or the receiver (RCVPRT)

Inhouse

  • Identification – For an outbound message, enter the sender’s ID. For an inbound message, enter the receiver’s ID.
Note   Do not use the colon character (:) within the text of a messaging identifier field or in detectors because it can cause agreement identification issues.

NACHA

  • NACHA Identifier – Position 04-13 (Immediate Destination) or 14-23 (Immediate Origin) of the NACHA file header record.
  • NACHA Name – Position 41-63 (Immediate Destination Name) or 64-86 (Immediate Origin Name) of the NACHA file header record.

TRADACOMS

  • Transmission code – An EAN location number (GLN) identifying the transmission sender (FROM code) or the transmission receiver (UNTO code). The interchange parties can agree upon the code. The value must be 14 or fewer alphanumeric characters.
  • Transmission name – Identifies in plain language the transmission sender (FROM name) or the transmission receiver (UNTO name). The interchange parties can agree upon the name. This value must be 35 or fewer alphanumeric characters.

VDA

  • Partner code – For an outbound message, enter the sender’s ID. For an inbound message, enter the receiver’s ID.

X12

  • Used for interchange and group level processing – (Default) Select this option to enable the handling of complete X12 messages (including ISA headers). Then, specify the following:
    • Interchange ID qualifier – The qualifier for designating the system or method of information code structure used to designate the sender ID element being qualified (ISA05). Or, the qualifier for designating the system or method of information code structure to designate the receiver ID element being qualified (ISA07). These are Interchange envelope parameters.
    • Interchange ID – The information code published by the sender for other parties to use as the receiver ID to route data to them (ISA06). Or, the information code published by the receiver of the data (ISA08). When you are sending, the sender uses this as its sending ID. Other parties sending to you use this as a receiving ID route data to them. These are Interchange envelope parameters.
    • Application ID – A code identifying the sender (GS02) or the receiver (GS03) of the message. The trading partners agree upon the codes to use. This is a functional group parameter.
  • Used for group level processing – Select this option to enable the handling of X12 messages without ISA headers. Then, specify the following:
    • Application ID – A code identifying the sender (GS02) or the receiver (GS03) of the message. The trading partners agree upon the codes to use. This is a functional group parameter.

XML

  • Identification – For an outbound message, enter the sender’s ID. For an inbound message, enter the receiver’s ID.

Related Links