Creating a message format rule

To create a message format rule:

  1. Select Transformation Services > Configuration > Message Formats.
  2. Click Create to display the detail view of the Message Formats 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 Starts With
    The field defines the starting qualifier of the message. This is a segment, a record, or a tag and depends on the message standard. For example, an UN-EDIFACT or an ODETTE message starts with UNB; an ASC X12 message starts with ISA; a BOD message starts with <?X; and a VDA message starts with 511, 551, 711, etc.
    Remark
    Review or provide a short description that clarifies the purpose of the configuration.
    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.
  4. Expand the Note field set and specify a comment on the message format rule.
  5. Specify this information in the Message Standard field set:
    Check Message Standard In
    The field defines the qualifier in the message file that is used to evaluate the message standard. This is a segment, a record, or a tag and depends on the message standard. For example, in an UN-EDIFACT or ODETTE message the message standard is located in the UNH segment with the qualifiers UN or OD.
    Message Standard – Position 1
    The field defines the first standard position for the qualifier. The standard position is used to evaluate the message standard that is specified in the Check Message Standard In field. This is a group, an element, or an offset and depends on the message standard.
    Message Standard – Position 2
    The field defines the second standard position for the qualifier. The standard position is used to evaluate the message standard that is specified in the Check Message Standard In field. This is a group, an element, or an offset and depends on the message standard.
  6. Specify this information in the Message Type field set:
    Check Message Type In
    The field defines the qualifier in the message file that is used to evaluate the message type. This is a segment, a record, or a tag and depends on the message standard. For example, in an EDIFACT or ODETTE message the message type is located in the UNH segment.
    Message Type – Position 1
    The field defines the first standard position for the qualifier in the message file. The standard position is used to evaluate the message type that is specified in the Check Message Type In field.
    Message Type – Position 2
    The field defines the second standard position for the qualifier in the message file. The standard position is used to evaluate the message type that is specified in the Check Message Type In field.
  7. Specify this information in the Message Version field set:
    Check Message Version In
    The field defines the qualifier in the message file that is used to evaluate the message version. This is a segment, a record, or a tag and depends on the message standard.
    Message Version – Position 1
    The field defines the first standard position for the qualifier in the message file. The standard position is used to evaluate the message version that is specified in the Check Message Version In field. This is a group, an element, or an offset and depends on the message standard.
    Message Version – Position 2
    The field defines the second standard position for the qualifier in the message file. The standard position is used to evaluate the message version that is specified in the Check Message Version In field. This is a group, an element, or an offset and depends on the message standard.
  8. To save the message format rule, click Save.
    A notification displays that the message format has been saved successfully.