Module for EDI 9.12 | Understanding EDI Concepts | Processing Inbound EDI Documents | Initial Processing of the EDI Recognizer
 
Initial Processing of the EDI Recognizer
When you install Module for EDI, the WmEDIforTN package of the module enhances the capabilities of Trading Networks to allow it to recognize and to begin processing EDI documents. The WmEDIforTN package adds an EDI recognizer to Trading Networks.
The following diagram illustrates the initial processing that the EDI recognizer performs on an ANSI X12 document. If you use the TRADACOMS standard, as you view this diagram remember that a reference to an interchange is a reference to a TRADACOMS transmission, a transaction set is a TRADACOMS file, and a group is a TRADACOMS batch.
Step
Description
1
When Trading Networks receives an EDI document, it passes the EDI document to the EDI recognizer. The EDI recognizer parses the inbound EDI document, so subsequent processing can process the following types of documents:
*For ANSI X12 and UN/EDIFACT documents:
*Transaction documents that each contain a single transaction set
*Group documents that contain a single group segment along with its transaction sets
*Interchange documents that contain a single interchange envelope along with its group segments and transaction sets
*For VDA documents:
*Envelope documents that each contain a single VDA message
* For TRADACOMS documents:
*File documents that each contain multiple TRADACOMS messages
*Batch documents that contain a single TRADACOMS batch segment along with its files
*Transmission documents that each contain a single TRADACOMS transmission envelope along with its batch segments and files
When parsing, the EDI recognizer also performs envelope validation and compliance check and places the results in the errors variable in the pipeline.
2
For each interchange segment in the original EDI document, the EDI recognizer determines whether to use standard or non-standard processing for the interchange segment. The type of processing (standard or non-standard) determines which EDI trading partner agreement (EDITPA) the EDI recognizer retrieves to obtain settings that tailor how to process documents from the interchange segment. For more information about EDITPAs, see Creating EDI Trading Partner Agreements.
Note:
Non-standard processing is not applicable with TRADACOMS or VDA documents.
*For standard processing , Module for EDI uses all standard Trading Networks objects for processing. The EDI recognizer obtains profiles for the sender and receiver identified in the interchange header (or TRADACOMS STX segment). Then it retrieves the EDITPA for the sender/receiver pair specified in the interchange header or TRADACOMS STX segment. When you use standard processing, all documents (for example, Transaction, Group, and Interchange) within the interchange segment or TRADACOMS STX segment are processed using the settings you defined for the sender/receiver specified in the interchange header or TRADACOMS STX segment.
*For non-standard processing (which is not applicable for TRADACOMS or VDA documents), Module for EDI uses custom interchange sender/receiver pair information that you must define. This interchange sender/receiver pair information is stored in the Trading Networks database but is not associated with a standard Trading Networks object.
The EDI recognizer uses the interchange sender/receiver pair information to determine the EDI ID qualifiers to use with the senders and receivers on the group headers within the interchange segment. Then for each group in the interchange segment, the EDI recognizer obtains the profiles for the sender and receiver identified in the group header. It then retrieves the EDITPA that corresponds to the sender/receiver specified in the group header. When you use non-standard processing, Transaction and Group documents are processed using the settings you defined for the sender/receiver specified in the group header.
Note:
Non-standard processing is deprecated. If you want to use non-standard processing, however, you must use the WmEDIforTN package home page to define interchange sender/receiver pair information. The EDI recognizer determines whether to perform standard or non-standard processing based on the existence of this interchange sender/receiver pair information. That is, if the sender/receiver pair information exists for the sender/receiver of the interchange segment, the Module for EDI performs non-standard processing. If it does not exist, the module performs standard processing.
3
Performs optional inbound processing based on how you set up Module for EDI. The module can perform:
*Inbound control number validation for control numbers in the:
*Interchange and/or group headers of the inbound ANSI X12 or UN/EDIFACT document
*Envelope headers of the inbound VDA document
*Transmission and/or batch of the inbound TRADACOMS document
Note:
The term control number is used in the EDI standards ANSI X12, UN/EDIFACT, and VDA. It refers to a number in the header of an EDI document that is used for validation and for the ordering of documents exchanged between trading partners. If you use the TRADACOMS EDI standard, the term control number is equivalent to the transmission reference numbers specified in the STX and BAT segments of your TRADACOMS documents. Whether your EDI standard includes control numbers or transmission reference numbers, you define them in Trading Networks in the same way; the only difference is in the terminology. In other words, Trading Networks and Module for EDI use the term control number to mean either control number or transmission reference number.
* Automatic generation of functional acknowledgments (FAs).
*When automatically generating an FA for an ANSI X12 document, Module for EDI generates an FA for each group in the inbound document.
*When automatically generating an FA for a UN/EDIFACT document, the module generates an FA for each interchange in the inbound EDI document. FAs are not applicable to the TRADACOMS or VDA EDI standards.
*Automatic generation of interchange acknowledgments (TA1s) for X12 interchanges.
4
Using the EDITPA that it retrieved, the EDI recognizer determines the types of documents that you want to process using the split option variable within the EDITPA. You can set it to one of the following:
*For ANSI X12 and UN/EDIFACT documents, set it to:
*Transaction split option to have the EDI recognizer submit all Transaction, Group, and Interchange documents to Trading Networks for processing.
*Group split option to have the EDI recognizer submit all Group and Interchange documents to Trading Networks for processing.
*Interchange split option to have the EDI recognizer submit only Interchange documents to Trading Networks for processing. You cannot use this setting when using non-standard processing.
*For TRADACOMS documents, set it to:
*File split option to have the EDI recognizer submit all File, Batch, and Transmission documents to Trading Networks for processing.
*Batch split option to have the EDI recognizer submit all Batch and Transmission documents to Trading Networks for processing.
*Transmission split option to have the EDI recognizer submit only Transmission documents to Trading Networks for processing.
*For VDA documents, the split option is not used. Regardless of the split option setting, the EDI recognizer will submit the VDA envelope containing a single VDA message to Trading Networks for processing.
For information about processing each type of document that results from the split of the interchange segment, see Processing Documents in Trading Networks .
5
If the original EDI document contains multiple interchanges or TRADACOMS transmissions, after splitting documents and sending them for processing, the EDI recognizer can save the entire original EDI document to the Trading Networks database. It determines whether to save the original EDI document based on a setting that you define in the default EDITPA.
For more information, see webMethods Module for EDI Installation and User’s Guide.