What is EDI File?
An EDI file is a data file structured using one of the several EDI standards. EDI standards are specific guidelines that govern the content and format of EDI files. EDI file contains structured data stored in a plain text format and is used for transferring business data between multiple organizations.
The primary reason for having these EDI standards is to ensure that businesses can communicate in a” universal language”.
EDI files can be saved by various standards. Here are the common EDI file formats,
- ANSI X12
- EDIFICE (Information Technology)
- EDITRANS (Transportation)
- ETIS (Telecommunications)
Different types of EDI File formats
- Flat file
- Variable file
- Fixed flat file
A flat file is the most common EDI file format during the computer-to-computer exchange of business documents or data.
This type of EDI file potentially contains several sorts of records, such as headlines and retail lines. Headlines indicate what information is held within entire documents. Retail lines comprise commercial documents, such as lines of invoices or orders.
A Variable-Sized Flat File (VFF) is when the data are separated from each other by a particular character such as a semicolon, vertical line, or tabulation. CSV format is the best-known example
The fixed flat file
When each field has a predetermined number of characters, there is no need to separate the data by character. This is called a Fixed Flat File (or FFF). This is the case for one of the two possible formats of Systems, Applications, and Products (SAP) software: iDocs.
A fixed flat file must be accompanied by a complete description containing the position, length, type (digital or alphanumeric), and content of each data field.
The EDI File Structure
The EDI file must contain all the information that you expect to receive from your partner (if the map is inbound) or need to send to your partner (if the map is outbound).
An EDI file is a binary computer file that contains data arranged in units called data elements. Data elements are separated by element terminators, and a group of data elements makes up a data segment. Data segments are separated by segment terminators.
Some elements (known as composite elements) are made up of sub-elements (component elements).
Figure 1a: An example of a data segment (SV1) having four elements. The first element is a composite element with two sub-elements (or component elements) separated by a component element separator, which is ":" (a colon).
Figure 1b: A section of an EDI file with segments ISA, GS, ST, BEG, REF, ITD, DTM, N1, N2, N3, N4
A block of data segments with data that are inter-dependent to each other is called a group or a loop. An example of a loop is the N1 loop, which may hold a company's address information.
Figure 2: An N1 Loop
Figure 2a: A section of an EDI file with three instances of the N1 loop. The first N1 loop consists of segments N1,N2,N3,N4. The second and third instances of the loop consist of segments N1,N3 and N4.
The section of data segments that convey a message is called a Transaction Set or Message. The message itself is sectioned into tables (or areas): the header (or Area 1); the detail (or Area 2); and the summary (or Area 3).
Figure 3a: An X12 Transaction Set structure Figure 3b: A UN/EDIFACT message structure
Transaction Sets (Messages) can be organized by grouping them by their topics or functions. A group of Transaction Sets is called a Functional Group. Functional Groups themselves constitute an interchange. An Interchange is an electronic equivalent of a letter envelope. It contains the destination and sender ID of the EDI message, and the date/time stamp of when it was sent.
Figure 4a: The ASC X12 file structure Figure 4b: The UN/EDIFACT file structure
The Control Segments are the header and trailer segments that mark the start and end of their controlling structure.
• The Header/Trailer control segments of the Interchange are the ISA/IEA in X12, and UNB/UNZ in UN/EDIFACT.
• The Header/Trailer control segments of the Functional Group are the GS/GE in X12, and UNG/UNE in UN/EDIFACT.
• The Header/Trailer control segments of the Transaction Set are the ST/SE in X12, and UNH/UNT in UN/EDIFACT.
Figure 5a: An example of an ASC X12 EDI file Figure 5b: An example of an UN/EDIFACT EDI file
Because EDI files must be processed by computers rather than humans, a standard format must be used so that the computer will be able to read and understand the EDI files. Here is the list of 10 common EDI communication standards
10 Common EDI Communication Standards
- ANSI ASC X12
Benefits of EDI File
- EDI can speed up business cycles
- EDI speeds up the transactions in just few minutes or seconds instead of days or weeks spent on sending manual postal mail or back-and-forth email communications
- Automates paper-based tasks. Frees up your staff time for higher-value tasks and provides them the tools to be more productive
- EDI can quickly process business documents accurately, which will help reduce manual re-entry of orders stock outs and cancellations.
- EDI ensures that all data sent on time and is tracked in real time. Automates application data exchange across supply chain.
- Shortening order processing and delivery helps organizations reduce inventory
- EDI reduces the transaction costs of paper, printing, reproduction, storage, filing, postage and document retrieval, saving businesses 1000’s of dollars.
- Improve supplier relationships. Help do business with multiple trading partners.
- Position yourself for success by automating your processes and improve business efficiency
- EDI ensures order accuracy and elevates strategic decisions
Ready to find out more about Commport EDI Solutions?
Drop us a line today for a free quote!