Tallan's Technology Blog

Tallan's Top Technologists Share Their Thoughts on Today's Technology Challenges

Dell Boomi X12 Trading Partner Feature Overview

Mike Agnew

The Dell Boomi AtomSphere provides users with the ability to create and configure trading partners for EDI transactions. Users can create trading partners to be used with the X12 Interchange format.

The X12 Interchange Format is a standard used for the sending and receiving of EDI files, it allows us to define different pieces of information about the file and communicate information about what is expected of the file between the respective trading partners. It uses the ISA and GS segment definition headers within sent EDI messages to set this information.

This post will cover how to create a basic X12 Trading Partner and the different configuration options available for them.

First we can create our trading partner by creating a new component and selecting “Trading Partner”, we can configure items such as the name and whether or not this is our company or a trading partner we’re communicating with, we also want to make sure that “X12” is selected as the Standard:

1

 

Click “Create” and it will take us to the configuration window for our trading partner:

2

 

In the Basic Options and Configuration tab, we can set the Identifier for the trading partner:

3

 

When we expand “Basic X12 Options” we will see a number of settings that correspond to how our EDI File should be read:

  • Functional Acknowledgement Options – Tells us whether a functional acknowledgment will be generated.
  • Document Envelope Options – Specifies how transaction sets will be grouped within the outbound interchange, there are three possible configurations for this:
    • Group By Interchange – Single interchange is made and can have one or more functional group.
    • Group By Functional Group – All sets of the same message type are grouped together.
    • Group By Transaction Set – Each transaction set has its own interchange.
  • Element Delimiter – Allows us to set the delimiter used between elements within the segments

4

  • Segment Termination Character – Used to set the character which denotes the end of a segment. (i.e. ~)
  • Filter Functional Acknowledgements – If checked, inbound interchanges will not pass 997 acknowledgments.

5

 

Next up is the ISA Identification Options which allows us to set options around how our EDI file’s ISA segments are configured, this will determine what is displayed within the ISA headers when our files are passed through the trading partner:

6

1. Authorization Information Qualifier – Sets the Authorization Information qualifier which corresponds to ISA01, this categorizes the Authorization Information ID:

7

2. Authorization Information ID – Sets the Authorization Information ID, if the qualifier is set to zero, this value would be set to nothing and appear as ten empty spaces in the file. This field corresponds to ISA02:

8

3. Security Information Qualifier – Sets the Security Information qualifier which corresponds to ISA03, this categorizes the Security Information ID:

9

4. Security Information ID – Sets the Security Information ID, if the qualifier is set to zero, this value would be set to nothing and appear as ten empty spaces in the file. This field corresponds to ISA04:

10

5. Interchange ID Qualifier – The field that this represents depends on whether file is inbound or outbound. If it’s outbound it represents ISA05 and categorizes ISA06’s Interchange ID, if inbound, it corresponds to ISA07 and categorizes ISA08’s Interchange ID:

11

6. Interchange ID – Corresponds to ISA06 is outbound, and ISA08 if inbound, this is typically set to the same value as GS02/GS03 which is also defines here within the GS Version/Control Options. If outbound it is called the Sender ID, inbound it is the Receiver ID:

12

ISA Version/Control options lets us setup the intended values for ISA11-16 we can select items such as which X12 standard we are using, what environment we’re working in, and our component separators:

13

1. Interchange Standard ID – Corresponds to ISA11, for control standards before 4020 this sets the code for the agency that controls the standard (U, TDCC, UCS), otherwise this sets the repetition separator which splits repeating occurrences of simple data elements:

14

2. Interchange Version – Corresponds to ISA12 and sets the Version Number of the control we are using, this relies on a specific format, for example if control version is 4010 this would be set to 00401:

15

3. Interchange Acknowledgment Requested – Corresponds to ISA14, if unchecked the value should be “0” and the send is not requesting any acknowledgment, if checked, the value is “1” and an acknowledgement that the ISA was received is requested:

16

4. Test Indicator – Corresponds to ISA15, allows us to specify whether this interchange is for testing or production, defined by a “T” or a “P”, respectively:

17

5. Component Separator – Corresponds to ISA16, this is lets us define the separator to be used for data sub-element components, commonly this is set to “:” or “>”:

18

The final X12Specific setting is for GS Version and Control Options. The correspond to the next line in the file, the GS segment:

19

 

1. Application Code – Corresponds to GS02 for outbound, indicating the send, and GS03 for inbound identifying the receiver:

20

2. Responsible Agency Code – Corresponds to GS07 and specifies which agency has control over the standard for the type of document being set. “T” for the Transportation Data Coordinating Committee and “X” for the Accredited Standards Committee:

21

3. GS Version – Corresponds to GS08 and defines the Version/Release/Industry Identifier code, which defines the standard for the type of document being set, should be prefixed with “00”:

22

Trading partners also contain settings for other, non-interchange specific settings that allow us to define what kinds of EDI file types we can take it, where they should go, and different types of meta-data attached to the file, these settings include:

  • Contact Info
  • Communication (FTP, SFTP, Disk, ect…)
  • Document Types (834, 810, ect…)
  • Archiving (Where to archive files)
  • Where Used (Lists processes where referenced)

 

Dell Boomi AtomSphere

The Dell Boomi AtomSphere integration platform is a shared-everything, multi-tenant platform that supports cloud-to-cloud, SaaS-to-SaaS, cloud-to-on-premises, on-premises-to-on-premises and B2B integration. Boomi AtomSphere supports real-time integration and elastically scales to meet high-volume needs in mobile, batch (ETL) and EDI environments. Easily accessed via a browser, it delivers an impressive range of integration, master data management (MDM) and platform extension capabilities.

Tallan Integration Solutions for Dell Boomi
Tallan is a certified Dell Boomi Partner specializing in iPaaS platform integrations. We specialize in Integrations using EDI and Dell Boomi as the iPaaS platform of choice. Leverage Tallan’s vast integration experience for your AtomSphere platform needs.  Our certified architects and developers provide the expertise, best practices, and guidance to deliver a successful integration solution.

We hope this guide will help you in your use of AtomSphere. If you have any questions or comments, or need assistance with any Integrations or development questions, please contact us at integrations@tallan.com.

 

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

\\\