The inbound process converts an EDI-X12 formatted document to an XML document.
In a basic message flow, inbound processing consists of the following components and steps. For an illustration of the components available in the construction of a message flow, see Using a Channel to Construct a Message Flow. You will define the components in the configuration instructions in Sample Configuration for Inbound Processing: EDI to XML.
Inlet
The preparser ensures that the document is converted to a structurally correct EDI XML document. The transformation templates that are provided in the Ebix are used to transform the structure of the document.
The iWay Integration Solution for EDI supports one preparser (EDIX12SplitterPreParser), which is described in Preparsers.
Validation
The inbound EDI document is validated for structure and content. The published EDI standards and user implementation guides define element types (for example, numeric, alpha, or date) and describe business rules to apply for validation.
For example, here is a typical date segment in an inbound EDI document:
DTM*001*20080701
The value in DTM01 ("001") is validated against an allowed code list. The value in DTM02 ("20080701") is validated as a properly formatted date.
In addition, the following business rule is applied: DTM02 is required if DTM01 is present (if there is a qualifier, there must be data).
Route
For details on available services, see the iWay Service Manager User's Guide.
Outlets
Outlets define how messages leave a channel at the end of a process. In our basic example, two outlets are configured in the route and one outlet is configured in the channel.
iWay Software |