Step | Description |
1 | The module parses an interchange from the EDI document. |
2 | The module determines whether it is to validate control numbers. If the control numbers are: ![]() ![]() ![]() ![]() For more information about validating control numbers, see
Validating Inbound Control Numbers. |
3 | Module for EDI determines whether it is to automatically generate FAs for the sender/receiver pair. If automatic FA Generation is: ![]() ![]() |
4 | ![]() ![]() Note: The FAs are not sent to Trading Networks processing rules at this time. In addition to generating the FAs during this step, Module for EDI also obtains information about: ![]() ![]() ![]() Because Module for EDI has information about the syntax errors and logical errors for transactions, it can also determine the child rejection error status for groups and interchanges. |
5 | Module for EDI determines whether it is to automatically generate TA1s for the sender/receiver pair. If automatic TA1 generation is: ![]() ![]() |
6 | For an ANSI X12 document, the module generates the TA1s for the interchange. Note: The TA1s are not sent to Trading Networks processing rules at this time. |
7 | For ANSI X12 documents, if the interchange contains groups, Module for EDI works with each Group document that was split from the interchange, as follows: 1. The module determines the FA status of each group and then uses this information to determine how to handle the Group document. For more information, see
Determining How
Module for EDI Reports FA Status. ![]() ![]() For more information, see
Defining Actions
Module for EDI Takes Based on FA Status. 2. If the Group document is being processed normally, that is, it has an acceptable FA status, and the splitOption EDITPA variable is defined as Transaction, Module for EDI works with each Transaction document that was split from the group, as follows: a. The module determines the FA status of the transaction and then uses this information to determine how to handle the Transaction document. For more information, see
Defining Actions
Module for EDI Takes Based on FA Status. ![]() ![]() For more information, see
Defining Actions
Module for EDI Takes Based on FA Status. 3. Module for EDI sends all Transaction and Group documents that are processed normally to Trading Networks processing rules. |
8 | For a UN/EDIFACT document, if the splitOption is Transaction, Module for EDI works with each Transaction document that was split from the interchange (that is, transactions that are not within group envelopes). 1. Module for EDI determines the FA status of the Transaction and then uses this information to determine how to handle the Transaction document. ![]() ![]() For more information, see
Defining FA Statuses as Acceptable and
Unacceptable and
Defining Actions
Module for EDI Takes Based on FA Status. 2. If the Transaction document is processed normally, the module sends it to Trading Networks processing rules. |
9 | Module for EDI sends the generated FAs to Trading Networks processing rules. When the FAs are processed through Trading Networks, the EDI recognizer updates the EDITRACKING table for the FAs. Module for EDI uses the EDITRACKING table to track FAs and related groups/transactions for FA reconciliation. For more information about FA reconciliation, see
Reconciling Functional Acknowledgments. |
10 | Module for EDI sends the Interchange document to Trading Networks processing rules. |