...
1.
...
This document outlines the guidelines for the Document of EDI Implementation FAQ.
...
EDI Standards and Format
Q1. What are the different EDI standards and how do they differ?
The most common EDI standards are ANSI X12 and EDIFACT. ANSI X12 is primarily used in North America, while EDIFACT is used internationally. Each standard specifies how business documents should be formatted and structured, though they cater to different regional and industry-specific requirements.
...
ANSI X12: Widely used in North America for various industries such as retail, healthcare, and transportation.
EDIFACT: Commonly used in Europe European and international transactions.
HL7: Used predominantly in the healthcare industry for exchanging medical information.
EANCOM: A subset of EDIFACT, used mainly in the retail industry.
...
Interchange Control Header and Trailer: Delimiters that mark the start and end of an EDI file.
Functional Group Header and Trailer: Group-related transaction sets.
Transaction Set Header and Trailer: Enclose individual transactions.
Segments and Elements: Each transaction set is composed of segments (lines of data), which are further divided into elements (individual pieces of data).
...
Invoice Number: Unique identifier for the invoice.
Invoice Date: Date The date when the invoice is issued.
Purchase Order Number: Reference to the purchase order.
Item Details: Description, quantity, unit price, and total price of the goods/services.
Payment Terms: Terms of payment, including due date and discounts.
Shipping Details: Information about the shipping method and delivery.
...
Q20. EDI - No such file or directory.
Error:
We began receiving these errors in the Kernel log, and we cannot figure out why:
...
The directory that Adeptia is writing to has too many directories
Solution:
Free up necessary space on the hard drive
...
Q22. Data too long for column GS_SEGMENT
Error:
The Adeptia Suite 5.3 with MySQL as a log database.
The EDI Inbound with source file has a GS Segment’s length > 64
...
The GS_Segment column within the log database has a character limit of 64.
Solution:
Run the attached alter script on the log database. The transaction should be completed successfully.
...