EDI Data Validation
X12 and EDIFACT are widely used for electronic data interchange (EDI). Validating X12 or EDIFACT data ensures that the exchanged messages conform to the syntax and rules defined by the standards.
Schema Level Checking
Schema Level checking is the process of validating EDI documents against predefined schemas or standards to ensure appropriate structure and data type.
...
Segment Delimiters and Control Structures: EDI standards specify delimiters e.g. segment terminator, and element separator used to separate different parts of the EDI document. So the syntax checking verifies that delimiters are correctly used and positioned as per standard.
Segment and Element Order: Each EDI transaction set (e.g., Purchase Order, Invoice) has a predefined sequence of segments and elements. Syntax checking ensures that segments appear in the correct order and that elements within segments are properly sequenced.
E.g.
Segment Separator, Field Separator, Composite Separator, Sub Composite Separator etc.
...
Product Codes: Identifiers used to specify goods or services traded between partners (e.g., GTIN for Global Trade Item Number).
Currency Codes: Standard codes representing currencies used in financial transactions (e.g., USD for US Dollar, EUR for Euro).
Country Codes: Two-letter or three-letter codes representing countries or regions (e.g., ISO 3166 codes like the US for the United States, CA for Canada).
Units of Measure: Codes specifying units of measurement (e.g., EA for Each, LB for Pound, KG for Kilogram).
Custom Codes: Industry-specific or partner-specific codes that are defined and agreed upon between trading partners.
E.g. if a field is supposed to contain a specific code for a country, ensure the code used in the message is valid.
...
Control Structures: EDI documents include control segments or segments with defined roles (like segment headers) that ensure data type rules across the entire document set.
Segment Level Validation: Each segment within an EDI document has defined rules for the type and format of data it contains. Validation occurs at both the segment level (ensuring each segment adheres to its format requirements) and the data element level (ensuring individual data elements within segments conform to their specified formats).
E.g. if a field is supposed to contain a string value, ensure the value used in the message is valid.
...
Segment Length: Each segment within an EDI document has predefined lengths for its data elements. EDI checks that the length of each segment does not exceed the maximum specified length.
Data Element Length: Within each segment, individual data elements (e.g., fields like customer ID, product code, etc.) have specific maximum lengths defined in the EDI standard. Length validation ensures that the data elements do not exceed these maximum lengths.
Composite Data Elements: Some data elements in EDI consist of sub-elements (components) with specific lengths. Length validation also applies to these composite data structures to ensure all components adhere to their defined lengths.
E.g The ‘customer name’ field (e.g., N1 segment) has a maximum length of 50 characters. If the fields exceed their specified maximum lengths during transmission, the EDI software would flag it as an error.
...
Transaction Set Enveloping: Each EDI transaction set begins with an envelope segment (like ISA/IEA in ANSI X12) and ends with a corresponding terminator segment. Segment sequence validation includes checking that these envelope segments are present and correctly positioned.
Segment Order: Within the transaction set, specific segments must appear in a predefined order. For example, in an EDI purchase order (ANSI X12 850), the segment sequence typically includes segments such as BGN (Beginning Segment), CUR (Currency), N1 (Name), PO1 (Item Detail), CTT (Transaction Totals), and SE (Transaction Set Trailer).
Looping Structures: Some segments in EDI documents can occur multiple times in a loop structure. Segment sequence validation ensures that segments within loops are repeated according to the defined rules and do not violate loop limits or constraints.
f.) Segment Occurrence Validation
...
Min/Max Occurrences: Each segment within an EDI transaction set has predefined minimum and maximum occurrence requirements. For example, a purchase order (EDI 850) may require at least one BGN (Beginning Segment) and exactly one SE (Transaction Set Trailer).
Looping Structures: Some segments in EDI documents can occur multiple times within specified loops. e.g., the N1 (Name) segment in an invoice (EDI 810) may repeat to identify different parties involved in the transaction. Segment occurrence validation ensures that segments within loops comply with defined loop limits and constraints.
Envelope Segments: Segment occurrence validation also includes checking the presence and correct usage of envelope segments (like ISA/IEA in ANSI X12) that encapsulate the entire transaction set.
E.g. The transaction set must begin with a BGN (Beginning Segment) and end with an SE (Transaction Set Trailer), each occurring exactly once.
...
Debugging Debugging Steps
If the issue is related to Inbound File processing, cross-verify if the relationship has all values defined as per the Input EDI file.
Check that the Partner ID and Host ID defined in Trading Partner are similar to the file.
Check the Kernel Application.log file for a detailed error description. (https://support.adeptia.com/entries/21796646-Application-logs-location)
Try using the "Skip Compliance Check" option while defining the relationship. If it works after checking this option, then your file may have some issues.
Check if your Inbound file is valid or not by validating it in third-party EDI software or Can also validate through EDI Schema.
If an issue occurs while Outbound File Processing, then check if you have applied Filters on ISA, GS, ST, SE, GE, and IEA.
...
EDI Related tool
EDI (Electronic Data Interchange) tools facilitate the exchange of business documents and data between companies in a standardized electronic format. Here are some notable EDI tools and a brief guide on how to use them:
EdinationEdiNation:
Edination EdiNation is an online tool for validating EDI files. It supports various EDI standards and provides a simple interface for quick validations.
...
Access the Tool:
Upload and Validate:
Upload your EDI file through the website's interface.
Run the validation process to check for errors and compliance issues.
Review the validation results and correct any identified issues.
...
EDIValidator:
EDIValidator is a simple online Validation tool specifically for validating X12 messages.
...
Access the Tool:
Visit the https://www.edivalidation.com/app
Upload and Validate:
Sign up on the EDIValidator website.
Upload your EDI file through the website's interface
Run the validation process to check for errors and compliance issues.
Review the validation results and correct any identified issues.
...
EDI Notepad:
EDI Notepad supports multiple EDI standards and versions, ensuring that documents are validated against the correct specifications.
...
See the validation result.
...
Compliance Check:
In EDI transactions there is an option in the transaction configuration, this will enable you to do the inbound validation on runtime.
...