Inbound EDI documents adhere to widely accepted standards, which allows them to be handled in a uniform, predictable fashion. They have standard "envelope" information that indicates who the document has come from and to whom it is intended. Because the envelope information has been standardized, CIC can provide services that examine the envelope, determine who it is from, what kind of document is within, and then direct it to one or more Business Processes that handle the integration activity.
This typical pipeline would be designed to process EDI documents (850) received from your trading partners, and generate Flat File (FF) outputs. Note too that a Functional Acknowledgment (997) is generated as part of this integration. (if enabled, the generation of the FA happens first; if we accept their document then the remaining process will complete).
Note on diagram key: The colors represented in the key refer to different Projects in which the resources are created. Note the use of Core.
Among the many design resources used in this pipeline, the following are specifically made to work with inbound EDI integrations.
- Inbound EDI Routes associate an EDI document's "envelope" information with a corresponding Business Process. When an EDI document is received, CIC will parse the EDI envelope segments, search the Inbound EDI Routes for one or more that match the envelope information and then call all the Business Processes that are attached to the Inbound EDI Route.
Inbound EDI Business Processes are designed to transform source data (provided to it) to a target format, and then send those results to the target. It is executed for each EDI message (ST-SE) to be processed. It must be created using the Inbound EDI Business Process template so that it inherits tasks and parameters specially designed to process inbound EDI data.