The following properties are used for EDI.
The syntax rules are specified at the segment level to define the valid combinations of required elements for that segment. They are exactly the X12 syntax rule specifications, where each rule is separated by a semicolon (;). Even though the syntax rule specifications are defined by X12, they are usable for both EDIFACT and X12 EDI.
Used only for EDI elements, this defines the sequence number, in the form nn of this element. Generally this will match the sequence number that is included in the name of the element. This is used only for validating the element data against the EDI syntax rules.
Defines the type of EDI element represented by this element. The possible values are:
None - This is not an EDI element.
Transaction - The root element of a transaction, this defines the transaction. The name of this element is the name of the EDI transaction. For example 832 or PRICAT.
Segment - Defines an EDI segment. The name of this element is the segment and must be less than or equal to three characters. For example DTM.
Element - Defines an EDI element. The name of this element is the name of the enclosing segment and is followed by the two digit sequence number of the within the segment. For example DTM02.
Composite - Defines an EDI composite. If the parent of the composite is an EDI segment, the name of the composite follows the same convention as that for an EDI element. If the parent of the composite is an EDI element, the name of the composite is the name of the element followed by a hyphen and a two digit sequence number. For example SEG05-01.
Loop - Defines an EDI loop. The name of this element must start with Loop-.
Code Value Part - Used when a code value has two parts to it. One element defines each of the parts of the code value.