Overview

Trading Manager uses the x12mail Type Tree to validate X12 transactions, and Partner Manager Structure Records to identify segment and data element errors if the transaction fails validation by x12mail.

If a custom X12 version is a subset of an ANSI X12 version (for example, 4010VICS is a subset of 4010) Trading Manager will first attempt to use Type Tree and/or structure definitions for the specific subset. If these structure definitions are not found, Trading Manager will use the Type Tree and/or structure definitions for the related ANSI X12 version as long as there also are trade links specified for the functional group ids used in the custom X12 version that are using the ANSI X12 versions. When implementing custom X12 versions, create an x12mail Type Tree that includes all of the custom X12 versions to be processed.

You can bypass creating structure records but you should define acknowledgments (997s) to report on the group or transaction level only.