EDI and Dell Boomi – Part 2
In our last post we were able to import an EDI Profile using Dell Boomi’s built in tools and we learned a little bit about how Boomi processes EDI. This time we will be modifying our 810 profile with some custom fields that our “business” requires.
From last time, the file we’re working with for this sample looks like this:
ST*810*1004~ BIG*20101204*217224*20101204*P792940~ REF*DP*099~ REF*IA*99999~ N1*ST**92*123~ ITD*01*3***0**60~ IT1*1*4*EA*8.60**UP*999999330023~ IT1*2*2*EA*15.00**UP*999999330115~ IT1*3*2*EA*7.30**UP*999999330146~ IT1*4*4*EA*17.20**UP*999999330184~ IT1*5*8*EA*4.30**UP*999999330320~ IT1*6*4*EA*4.30**UP*999999330337~ IT1*7*6*EA*1.50**UP*999999330634~ IT1*8*6*EA*1.50**UP*999999330641~ TDS*21740~ CAD*****GTCT**BM*99999~ CTT*8~ SE*18*1004~ GE*1*1320~
We already have a profile that can handle the input of this file, but let’s say one of our department heads just notified us they would like to keep track of the type of truck the order an invoice was for was driven on.
We’ll say that information in our file will look something like this:
Let’s add this segment below our N1 Loop in the Header Loop, we’ll say that this information is static for an entire invoice so it makes sense to put it here:
To add a new segment below this loop click on the blue arrow to the left of “Header Loop” and select “Add Child Segment”:
This creates a new empty segment at the bottom of the Header Loop section. It should be just labeled “segment” at the moment. To start changing the settings, click on the segment and we’ll get a form on the right where we can start defining our new segment:
Let’s go over the different options:
- Segment ID – This is what we set to match our file, so in our case we will have this set to “TR”
- Name- This allows us to be able to tell what segment we’re looking at without having to know all of the segment IDs, so we’ll set this to “Truck Information”
- Mandatory – This allows us to set whether or not the given segment is required. For our example we’ll say that it is required so we will check the box.
- Max Use – Allows us to set how many times this segment can appear, in our case we only want it to appear once so it should stay set to “1”.
- Repeat Action – We can change this to define what happens if we start seeing repeats, we’ll just leave this as N/A.
- Looping Option – Can be set to either Unique or Occurrence, we’ll be just leaving it to unique.
Here’s what we should have now:
Next we want to add in our elements. If we look at our sample segment, we can see we have three elements in our segment:
Creating elements in Boomi is pretty similar to creating segments. Click the blue arrow to the left of our “TR” segment, and select “Add Multiple Child Elements”, then in the box that pops up, enter “3” and click OK:
Now we have three new elements under our new segment:
Let’s start setting up our elements. Select your first element, and change the “Data Name” field to something more logical, in our case we’ll be calling it “TR01”. In our case TR01 will represent an ID for the truck. This means we will need this field to be mandatory, so we want to check of the “Mandatory” box. For now we won’t change anymore settings, but it should be known you can really fine tune each element and its constraints.
Below are the settings used for the three elements:
Now we’ve created our new “TR –Truck Information” segment for our file.
So next let’s say we want to extract the information about the truck used for the invoice and store it in an XML document. So we’ll create an XML Profile that we can map our EDI data to. For our purposes something simple is fine:
Next we’ll want to create our map from EDI to XML. Set the source profile as our EDI Profile, and the destination as our XML profile. Then simply map the appropriate values:
We can test our work by creating a new process, inserting our file, and running it through a map shape using our new map. What we should get is some simple XML output with an invoice number and our truck information.
Here is the file we’ll be inserting:
ST*810*1004~ BIG*20101204*217224*20101204*P792940~ REF*DP*099~ REF*IA*99999~ N1*ST**92*123~ ITD*01*3***0**60~ TR*123456*2006*ajk-123~ IT1*1*4*EA*8.60**UP*999999330023~ IT1*2*2*EA*15.00**UP*999999330115~ IT1*3*2*EA*7.30**UP*999999330146~ IT1*4*4*EA*17.20**UP*999999330184~ IT1*5*8*EA*4.30**UP*999999330320~ IT1*6*4*EA*4.30**UP*999999330337~ IT1*7*6*EA*1.50**UP*999999330634~ IT1*8*6*EA*1.50**UP*999999330641~ TDS*21740~ CAD*****GTCT**BM*99999~ CTT*8~ SE*19*1004~ GE*1*1320~
For our process we just did a static message shape with our file inserted into it, this goes into our map, which goes out to a disk connector we setup:
We run our process and we’ll get our output file:
As you can see we extracted the information from our EDI file successfully and our newly added segment worked perfect!
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 is a certified Dell Boomi Partner specializing in iPaaS platform integrations. 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.