EDI · EDIFACT
EDI mapping that shows you where the error is.
Convert, map and validate EDIFACT messages. Every error names the segment and its position, and goes to the error path with an alert.
UNH+1+ORDERS:D:96B'
BGM+220+4711+9'
DTM+137:20261026:102'
<BGM>
<e2>4711</e2>
</BGM>
{ "BGM": {
"doc": "4711"
} }
Capabilities
Four tools in one connector.
CONVERSION
EDI ⇄ XML ⇄ JSON
Both ways. Plus a readable copy with one segment per line.
MAPPING
Field by field, by path
Point BGM.1 or NAD.1.0@1 at the target column.
MANIPULATION
Field formatting
EDIFACT dates (102, 203, 303), decimals, truncation, padding, UNOA/UNOB.
VALIDATION
Three levels
Syntax, envelope structure and your own business rules.
Validation
Every message goes through three filters.
LEVEL 1
Syntax
Separators, escapes and character set. Can the message be read?
LEVEL 2
Structure
An UNB envelope, every UNH closed by its UNT, every segment in a valid position.
LEVEL 3
Business rules
Required, max length, numeric, pattern and allowed values — per field.
Standards
From order to invoice.
EDIFACT, X12, EANCOM, TRADACOMS, HL7 and more — EDIFACT in every directory version.
IATA PADIS
Aviation
Coming soon EDI is included in Enterprise.
Bring a real message. We'll validate it with you in the demo.