Types in EDI schemas

The type names in EDI schemas are consistent with the terminology used in the EDI standards.

The root of each schema is called EDI. Each schema has an ANSI or EDIFACT category, an Interchange category, and a Transmission category.

You can combine versions and standards by selecting one schema and copying or merging other versions or standards to it. You can create a schema, which includes separate definitions for each of your trading partners by customizing a schema for one partner and then copying or merging types with definitions of other partners.

An EDI version schema includes the entire data dictionary for that particular version and the transmission and interchange objects common to all versions.

The type names of data elements are abbreviated versions of the element descriptions. For example, the name of the type that defines the data element Account Type Code is Acc'tTypeCd. If you find these or other names inappropriate for your use, rename the type - every reference to that type is renamed for you automatically. For a list of abbreviations that are used in EDI schemas and their corresponding full name, see "EDI schema abbreviations."

The data objects of a particular standard are located under a category with the version name, for example, V3050 in the ansi3050 schema. The names of particular elements, segments, transaction sets, and messages do not change from schema to schema unless the standard, itself, has changed. This naming convention makes it easier to migrate from one version to the next, if the standard does not change.