Defining TN EDI Document Types
For Trading Networks to recognize EDI documents, you must define a TN EDI document type for each corresponding EDI transaction set or TRADACOMS file (of a specific standard and version) that you will exchange. For example, if you plan to exchange 850s (purchase orders), 855s (purchase order acknowledgments), and 997s (functional acknowledgments), you would define the three TN EDI document types corresponding to a specific version and standard of each transaction set. Or, if you plan to exchange three TRADACOMS File document types, you would define those three TN EDI document types corresponding to a specific version and standard of each file.
When you define a TN EDI document type,
Module for EDI automatically creates a flat file schema for the same EDI transaction set or TRADACOMS file.
Trading Networks stores flat file schemas in the EDIFFSchema folder in the WmEDIforTN package, using the naming conventions described in
Flat File Schema Namespace Conventions for
Non-TRADACOMS Standards or
Flat File Schema Namespace Conventions When
Using TRADACOMS.
Note: In a clustered environment, you can optionally deploy the EDIFFSchema folder in all the nodes so that the installed document types are available across the cluster.
If you have set the tn.docType.EnableLogDocumentType property to true, Trading Networks logs the details of the new document type in the activity log. For more information about setting Trading Networks configuration properties, see the webMethods Trading Networks Administrator’s Guide for your release.
Note: You might need to customize flat file schemas for your specific validation needs. For example, you might want to validate fewer constraints, or modify the valid values.
For information about how to work with flat files schemas, see Flat File Schema Developer’s Guide.
These are the following three high-level steps for defining TN EDI document types:
Note: You must have administrator privileges and data permission to define and manage document types in Trading Networks. For information about defining data permissions and role-based access, see the webMethods Trading Networks Administrator’s Guide for your release.