2.14. EDI to SAX Event Mapping


When mapping EDI to SAX events, segments are matched in either of these ways:
  • by an exact match on the segment code (segcode).
  • by a regex pattern match on the full segment, where the segcode attribute defines the regex pattern (for instance, segcode="1A\*a.*").
  • required: field, component and sub-component configurations support a "required" attribute, which flags that field, component or sub-component as requiring a value.
  • by default, values are not required (fields, components and sub-components).
  • truncatable: segment, field and component configurations support a "truncatable" attribute. For a segment, this means that parser errors will not be generated when that segment does not specify trailing fields that are not "required" (see "required" attribute above). Likewise for fields/components and components/sub-components.
  • By default, segments, fields, and components are not truncatable.
So, a field, component or a sub-component can be present in a message in one of the following states:
  • present with a value (required="true")
  • present without a value (required="false")
  • absent (required="false" and truncatable="true")
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat