X12 (Document Type)
Introduction: You can find a description of this phase in section Phase 2 (Introduction). See especially subsection
When Does the Parser Start a New Record?
X12 is an EDI data transmission standard used mainly in the United States. The main difference to EDIFACT, which is mainly used in Europe, is the different structure of the message, but technically the same principles apply.
The source structures for the different message types are available as templates.
(1) If this checkbox is set, the input fields are checked against their format templates during parsing. If a value violates the format template of the field or exceeds the field length, an error is created. If an error occurs, the profile job will not be aborted immediately in phase 2, but at the end of phase 2 or after 50 errors. Attention: The use of format checking puts a strain on performance and should only be used if absolutely necessary.
(2) Specifies whether to check the number of repetitions (of fields and nodes) in the source structure.
(3) See comments in next section.
(4) Incoming files can be checked with semantic rules. See section Semantic Check .
Comments on X12 Parser
An X12 file may only contain one message type, since the profile only allows for one source structure to be defined. But the format would allow for different message types in one file.
The checkbox (3) can be used to split one X12 file into individual messages. A job is created for each message. The restriction to one message type still applies if the messages in the profile are to be parsed into the source structure.
The parser is only implemented for the X12 version 005030.
See also section X12 Input File Check.
Creating X12 Output Files
If you want to generate an X12 output file, have a look at the sections X12CreationUnit and Integration Units. See also section Content Settings - Details .