Type trees

For each custom X12 version, a Master Type Tree must be created that follows specific rules so that the EDI Wizard can generate the x12mail and x12user type trees. These rules are as follows:

• The overall organization of the Type Tree must conform to the organization of the X12 Type Trees contained in the IBM WebSphere Transformation Extender Packs for EDI (See the X12 type trees documentation.)
• Under Inbound/Outbound Partner Funct'lGroup ANSI EDI the name of the custom group must be F followed by the custom version (excluding the leading zeroes). For example, to support 004010VICS the name of the group would be F4010VICS. Characters in the version name not supported by the Type Designer should be removed, for example, for R2/8 the name of the group would be FR28.
• The component rule for the GS segment inside the custom group has to have the LEFT function removed and the literal must be the complete version string as it appears in the GS Segment. For example, for 4010VICS the component rule must read: VersionReleaseIndustryIDCd Element:$ = "004010VICS"
• Under ANSI EDI the category that contains the transactions for the custom group must be V followed by the custom version (excluding the leading zeroes). For example, to support 004010VICS the name of the category would be V4010VICS. Characters in the version name not supported by the Type Designer should be removed, for example, for R2/8 the name of the category would be VR28.

Any changes to the transactions, segments, and/or elements inside the custom category will be picked up by the EDI Wizard and included in the resulting x12mail and x12user trees.

Versions that contain characters not supported (R2/8) must be manually added to the x12mail and x12user trees.