Documentation

How to translate EDI files

Article author
Admin
  • Updated

With Web EDI Translator you can translate EDI files to JSON and from JSON back to EDI. Both editors allow you to modify the contents. 

  1. EDI file to JSON

    Upload a file by clicking on the "Choose EDI file" button. Upon loading the file will be displayed in the EDI Editor to the left. The file is automatically expanded so that each segment is on a new line and is easier to view and edit.

    translate-edi-to-json.png

    You can edit the file, e.g. change the contents of data elements or add segments. The settings menu allows you to configure an explicit model and a custom syntax set.

    When you are ready to translate the EDI file, hit the right-arrow blue button.

    This operation will translate and then validate the EDI file.

  2. JSON to EDI file

    You can generate EDI files by modifying the contents in the JSON Editor to the right. The JSON must be either X12Interchange or EdifactInterchange. The JSON for all EDI transactions must match an existing Transaction Model.

    translate-json-to-edi.png

    When you are ready to generate your EDI file, hit the left-arrow orange button.

    This operation will both translate and validate the JSON.

    The resulting EDI will be expanded with each segment on a new line. You can copy and save it to a file and then edit it to remove all carriage returns, and line feeds.

     

    Configure the EDI delimiters

    • If you need to generate an X12 with non-default separators, set the following items as part of the X12Interchange payload:

      • Segment separator: X12Interchange.SegmentDelimiter
      • Data element separator: X12Interchange.DataElementDelimiter
      • Repetition separator: X12Interchange.ISA.InterchangeControlStandardsIdentifier_11
      • Component data element separator: X12Interchange.ISA.ComponentElementSeparator_16
    • If you need to generate an EDIFACT with non-default separators, add a UNA segment before the UNB.

      When your EDI file contains more than one interchange, only the first interchange is populated in the JSON Editor. If you want to edit/validate any of the remaining interchanges you'll need to manually split the file into multiple files with each interchange in its own file.

Share this:

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.