Step | Description |
1 | Define the TN document types for the EDI documents that you want to process. For instructions, see Defining TN EDI Document Types. When you define the TN document types for EDI documents, Module for EDI creates the flat file schemas that define the structure of the EDI documents. Module for EDI uses the flat file schemas for parsing, converting, and validating the structure of inbound EDI documents. |
2 | Optional. Create the flat file schema that defines the structure of an internal-format document. Use Designer to create the flat file schema. For more information about creating a flat file schema, see the Flat File Schema Developer’s Guide. Note: You use the flat file schema created in this step if the service that you create to process an Interchange, Group, or Transaction document creates an internal-format document. Module for EDI provides a service that you can invoke to create the internal-format document based on the flat file schema. |
3 | Define profiles for the senders and receivers in the inbound EDI document. For more information about how to create profiles, see Defining Trading Partner Profiles and the webMethods Trading Networks Administrator’s Guide for your release. |
4 | Define the default EDITPA and optionally, the partner-specific EDITPAs for the sender/receiver pairs in the EDI document. For more information about creating EDITPAs, see Defining EDI Trading Partner
Agreements. For information about the EDITPA variables that affect inbound processing, see Specifying EDITPA Variables that Affect
Inbound Processing. |
5 |  When using non-standard processing, you must also define the interchange sender/receiver pair information. For instructions, see Defining Interchange-Level Sender/Receiver
Pair Information in Using
Module for EDI Decoupled from
Trading Networks . For more information about the difference between standard and non-standard processing, see webMethods Module for EDI Concepts Guide . |