Delete X12 transaction sets in error if not used

If you do not use a transaction that causes an analysis error, delete both occurrences of it, that way, when you analyze your schema, you do not get the errors. Deleting causes the analysis to run faster. You can delete the entire transaction set category under the Inbound category and the entire transaction set category under the Outbound category.

In addition, delete the Funct'lGroups, under Inbound and Outbound, that contain the deleted transaction. Then, analyze the schema again.

For example, the #838 transaction set in the ansi3030 schema causes an analysis error. If you are using ANSI version 3030, and you are not using the #838, you can delete the entire #838 category for the transaction set under Inbound and under Outbound.

Also, delete the Funct'lGroup type #838, under Inbound and under Outbound.

For information on customizing your own EDI type tree, see the Create industry subsets documentation.

If you do use a transaction set that causes an analysis error, refer to the explanation of the errors that follow. Then, determine how you want to fix it.