The X12 file is received at the landing zone. The file can contain no more than one ISA segment, with multiple GS groups and multiple ST transactions.
The EDI Accelerator receives the X12 file, validates the X12 file at the ISA level, generates a TA1 message, and sends the TA1 message to the sender based on the input ISA14 element.
If the file passes ISA level validation, the Accelerator splits the X12 file into separate files, for each GS, where each file contains one ISA segment with one GS segment. The GS segment can contain multiple ST segments of the same EDI document, such as transaction type 850.
The Accelerator validates each file with one ISA segment and one GS segment at the GS level. When the "997 Acknowledgment" workflow parameter is enabled (default), the Accelerator creates and sends a 997 message to determine if the file is EDI-X12 compliant. If there is a validation error, an HTML report with error descriptions will be attached to the event.
If the file is EDI-X12 compliant, the Accelerator splits the input into files with one ISA segment, one GS segment and one ST segment. The accelerator then parses the files into Informatica EDI-X12 XML canonical format.
Steps 4-5 are repeated for every GS group contained in the original X12 file.