Translation, Enveloping, and Data Formats (EDI, XML, Flat File)
Domain 4 tests translation and enveloping across EDI, XML, and flat files. You must know how a source document is parsed, mapped, validated, and wrapped, and where acknowledgments are produced.
Translation
- Map Editor: source-to-target maps with standard and extended rules; extended rules handle complex conditions and loops.
- EDI: X12 and EDIFACT transactions, qualifiers, control numbers, and acknowledgments (TA1, 997/999, CONTRL).
- XML: XSD validation and XSLT transforms; namespaces are a common failure point.
- Flat file: positional or delimited layouts defined by rules; fixed-width fields need exact offsets.
Enveloping
Envelope services add or strip ISA/GS/ST (X12) or UNB/UNH (EDIFACT) segments. Control numbers must be unique per sender/receiver pair and must reconcile with acknowledgments. Outbound envelopes must match the partner's expected version and qualifiers.
Worked example
An inbound 850 fails translation. Check the ISA sender/receiver qualifiers and IDs against the partner profile, confirm the GS version matches the map, verify the ST transaction set is supported, and inspect the 997 status. Reasoning: a parse failure is usually envelope or delimiter related, not a map rule.
Traps
- Assuming a map validates business data; it transforms, it does not enforce all partner rules.
- Reusing control numbers, which breaks acknowledgment reconciliation.
- Ignoring delimiters declared in the ISA.
- Forgetting that 997 acknowledges receipt, not business acceptance.