Basics of Inbound and Outbound Data Transformation Flows

Building inbound and outbound data transformation flows in the CIC Studio follow basic patterns that are comprised of interconnected Objects, sequenced in a way that receives, processes, transforms, and outputs data in a particular sequence.  For the purpose of this article, the patterns are broken down as such:

• Inbound EDI Pattern
• Outbound EDI Pattern
• Basic non-EDI Pattern

Note: The following patterns apply where both applications are file-based; patterns differ when a Web Service, Database, or CIC Connector are being used to access applications. 

Inbound EDI Pattern

This diagram presents a common integration pattern for an inbound EDI process, in which an 810 document is transformed to a Flat File.

For the routing and processing stage, it is the source data that will be inspected to determine:

• who it is from
• what it is

Knowing the who (your trading partner) as well as the what (the type of document) allows the integration engine to direct the data to the proper Business Process you’ve created that will both transform and send the transformation results according to your design. 

Video:  Check out this Community video that demonstrates inbound EDI data processing.

Outbound EDI Pattern

For outbound, this diagram presents a common integration pattern for an outbound EDI process, in which a Flat File 810 document is transformed into an 810 document.

Video:  Check out this Community video that demonstrates outbound EDI data processing.

Application-to-Application (Non-EDI) Pattern

This diagram presents a basic integration pattern for an Application-to-Application (non-EDI) process. Note: A Data Analysis Ruleset is used in this scenario; depending on the use case, you may not require this.

Video:  Check out this Community video that demonstrates non-EDI data processing.