Task | 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, the flat file schemas that define the structure of the EDI documents to process are created. Module for EDI uses the flat file schemas for parsing, converting, and validating the structure of an inbound EDI document. |
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 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 a file, or a transmission or batch document might create 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 creating profiles, see Defining Trading Partner Profiles When Using
TRADACOMS 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 When
Using TRADACOMS. For information about the EDITPA variables that affect inbound processing, see Specifying EDITPA Variables that Affect
Inbound Processing When Using TRADACOMS. |