Rational Developer for System z, Version 7.6

EDIFACT

This topic presents a high level structure of an EDIFACT message.
In the following diagram:
  • The backtick character is an actual delimiter in the data stream.
  • Curled brackets { } are used to indicate groupings, but are not actually part of the datastream.
Interchange
{
   Service String Advice (UNA)
   Interchange Header (UNB)
   `
   Functional Groups or only Messages
   {
      Functional group header - UNG
      `
         Message_01
         {
            Message Header -- UNH
            `
               Data Segment 01
               {
                  Tag {Code:Value}
                  Simple Data Element {Value}
                  Composite Data Element
                  {
                     Component Data Element {Value}
                     :
                     Component Data Element {Value}
                  }   
                  `
               }
               Data Segment 02
               Data Segment 03
               Message Trailer -- UNT
            `
         }
         Message_02
         Message_03
         Functional Group Trailer UNE
      `
   }
   Interchange Trailer UNZ
   `
}

You can model the top level interchange of an EDIFACT message by setting the following properties for the complex type on which the message is based:

Composition = Sequence
Content Validation = Closed
Tag Data Separator = <EDIFACT_TAGDATA_SEP>
Data Element Separation = Tagged Delimited
Delimiter = <EDIFACT_CS>

Within an EDIFACT message, you can define the delimiters to be used in the message itself using the optional Service String Advice element. To enable this element to be recognized as an EDIFACT Service String, you must set the element property Interpret Element Value to EDIFACT Service String. You must also set the delimiter values to the mnemonic values that are defaulted when you set the Message Standard property to EDIFACT.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)