The EDI X12 format is a standardized format used for electronic data interchange (EDI) to automate and streamline B2B communication. Celigo’s integrator.io platform supports the EDI X12 file type format and provides various tools and features to facilitate the exchange of business documents with trading partners.
Key Features and Processes of EDI X12 in Celigo integrator.io
1. **EDI Workflow (Inbound and Outbound)**
– **Inbound EDI Data**: The platform processes delimited EDI data received from an application based on the import configuration. The data is parsed, validated, and converted to an EDI JSON format, which is then transformed into a document-specific canonical JSON format using Transformation 2.0.
– **Outbound EDI Data**: The platform processes ERP data received from an application based on the export configuration. The ERP data is converted from a canonical format to EDI JSON using mapping rules and then converted to delimited EDI with appropriate validations.
2. **Parsing and Generation**
– Integrator.io includes a built-in EDI parser and file generator to translate EDI documents into supportive file formats. The parser converts EDI information into data that can be mapped to corresponding record types.
3. **EDI Profiles**
– EDI profiles ensure that data complies with EDI standards and specific guidelines set by each trading partner. This involves verifying that all mandatory and optional segments/elements are populated correctly and validating the EDI document against its standards before sending it to the destination.
4. **EDI Validation Rules**
– Centralizing trading partner configurations with EDI profiles reduces configuration time, minimizes errors, and offers a global view of EDI-related validations and values at the header level. This approach allows easy updates for specific trading partner configurations.
5. **Functional Acknowledgement Generation and Reconciliation**
– A functional acknowledgement (EDI transaction 997) is a receipt issued by the receiver in response to a transaction sent by a trading partner. It confirms the integrity and successful delivery of EDI transactions.
6. **Dashboard – EDI Activity**
– The account-level dashboard provides an overview of EDI-specific integration activities, allowing users to view and manage data centrally. The EDI activity tab offers detailed information on all EDI flows and documents.
### EDI X12 File Definition Rules
– **Elements**: Individual items within an EDI document, such as city, state, country, item number, quantity, and price. Elements are separated by delimiter characters.
– **Segments**: Groups of related data elements. Each segment starts with a three-character data identifier and ends with a segment terminator.
– **Loops**: Logical groups of segments that can have sub-loops with other groups of segments. Loops can contain mandatory and optional segments.
– **Relationships**: Dependencies between elements within a segment. Different types of relationships include “one or more,” “if first, then all,” “one or none,” etc.
– **Codelist**: An array of objects holding the possible set of values permitted for a field.
Example of Segment Rule Structure for X12
“`json
{
“maxOccurrence”: 1,
“skipRowSuffix”: true,
“required”: false,
“elements”: [
{
“name”: “BEG”,
“value”: “BEG”
},
{
“name”: “Beginning of a segment”,
“value”: “BEG01”,
“maxLength”: 5,
“minLength”: 1,
“type”: “String”,
“required”: true
}
]
}
“`
Example of Loop Rule Structure for X12
“`json
{
“name”: “PO1”,
“maxOccurrence”: 100000,
“container”: true,
“children”: [
{
“skipRowSuffix”: true,
“required”: true,
“elements”: [
{
“name”: “PO1”,
“value”: “PO1”
},
{
“name”: “Assigned Identification”,
“value”: “PO101”,
“maxLength”: 5,
“minLength”: 1,
“type”: “String”,
“required”: true
}
]
}
]
}
“`
Example of Relationship Rule Structure for X12
“`json
{
“name”: “PO1”,
“required”: false,
“maxOccurrence”: 3,
“container”: true,
“children”: [
{
“skipRowSuffix”: true,
“required”: false,
“elements”: [
{
“name”: “PO1”,
“value”: “PO1”
},
{
“name”: “Entity Identifier Code”,
“value”: “PO101”
},
{
“name”: “Entity Identifier”,
“value”: “PO102”
},
{
“name”: “Currency Code”,
“value”: “PO112”
}
],
“relationship”: [
“C,03,02”,
“P,06,07”
]
}
]
}
“`
Example of Codelist Rule Structure for X12
“`json
{
“name”: “Entity Identifier Code”,
“value”: “BEG01”,
“type”: “String”,
“maxLength”: 5,
“minLength”: 1,
“required”: true,
“enum”: [
“00”,
“01”,
“07”
]
}
“`