Creating a message ID setup

To create a message ID setup:

  1. Select Transformation Services > Configuration > Message IDs.
  2. Click Create to display the detail view of the Message IDs page.
  3. Specify this header information:
    Effective from Date
    This field defines the start date of the valid period for the configuration.
    When editing, click the Calendar button to select the start date from a calendar.
    Effective to Date
    This field defines the end date of the valid period for the configuration.
    When editing, click the Calendar button to select the end date from a calendar.
    Message Standard
    The message standard defines the format or structure of the message. Examples are ASC X12, UN-EDIFACT, XML, or BOD.
    Message Type
    The message type defines the content of the message. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. The message type depends on the message standard. If no special message type is required for the message ID setup, Default must be selected. For example, in case of UN-EDIFACT messages a special message type definition is not required.
    Remark
    Review or provide a short description that clarifies the purpose of the configuration.
  4. Expand the Note field set and specify a comment on the message ID setup.
  5. Specify this information in the Sender ID Position field set:
    Sender ID – Position 1
    The field defines the first position for a qualifier that identifies the sender in the message file. This is a segment, a record, or a tag and depends on the message standard, for example, UNB, <ShipFromParty>, etc.
    Sender ID – Position 2
    The field defines the second position for a qualifier that identifies the sender in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 3, <PartyIDs>, etc.
    Sender ID – Position 3
    The field defines the third position for a qualifier that identifies the sender in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 1, <ID>, etc.
  6. Specify this information in the Receiver ID Position field set:
    Receiver ID – Position 1
    The field defines the first position for a qualifier that identifies the receiver in the message file. This is a segment, a record, or a tag and depends on the message standard, for example, UNB, <ShipToParty>, etc.
    Receiver ID – Position 2
    The field defines the second position for a qualifier that identifies the receiver in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 3, <PartyIDs>, etc.
    Receiver ID – Position 3
    The field defines the third position for a qualifier that identifies the receiver in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 2, <ID>, etc.
  7. Specify this information in the Additional Sender ID Position field set:

    These additional fields can be used to match data to a partner ID, if two trading partners have the same sender ID and receiver ID.

    Additional Sender ID – Position 1
    The field defines the first position for a qualifier that identifies the additional sender ID in the message file. This is a segment, a record, or a tag and depends on the message standard, for example, UNB, <ShipFromParty>, etc.
    Additional Sender ID – Position 2
    The field defines the second position for a qualifier that identifies the additional sender ID in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 3, <PartyIDs>, etc.
    Additional Sender ID – Position 3
    The field defines the third position for a qualifier that identifies the additional sender ID in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 1, <ID>, etc.
  8. Specify this information in the Additional Receiver ID Position field set:

    These additional fields can be used to match data to a partner ID, if two trading partners have the same sender ID and receiver ID.

    Additional Receiver ID – Position 1
    The field defines the first position for a qualifier that identifies the additional receiver ID in the message file. This is a segment, a record, or a tag and depends on the message standard, for example, UNB, <ShipToParty>, etc.
    Additional Receiver ID – Position 2
    The field defines the second position for a qualifier that identifies the additional receiver ID in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 3, <PartyIDs>, etc.
    Additional Receiver ID – Position 3
    The field defines the third position for a qualifier that identifies the additional receiver ID in the message file. This is a group, an element, or an offset and depends on the message standard, for example, 2, <ID>, etc.
  9. To save the message ID setup, click Save.
    A notification displays that the message ID has been saved successfully.