AI EDI Mapper

In this article: 

• Overview
  • Process Summary
• Accessing the AI EDI Mapper in the Custom Mapping Tool
• Creating an EDI Mapping With the AI EDI Mapper
  • EDI Specifications Files and EDI Sample Files
• Editing the Custom Mapping
• Editing the Flow Configuration Settings
• Viewing Files in the Library
• Attached Files Referenced in the EDI File Types Table

Overview 

The AI EDI Mapper helps you create and configure EDI mappings for your business processes. EDI mappings allow you quickly create the associated mapping, Flow, and library entries within a single window of the Chain.io platform. in one step. 

The AI EDI Mapper currently enables you to create inbound EDI mappings. This means that in the Flow configuration, the EDI file is the source file and data will be converted to another file type of your choosing.

For more information on the custom mappings, refer to the following support articles: 

• Mapping EDI File Files in the Custom Mapping Tool

• Custom Mapping Tool

Process Summary 

1. Navigate to Workspace Settings. 

2. Click Custom Mapping Tool. 

3. Click New Inbound EDI. 

4. Select the EDI document type. 

5. Select the Integration. 

6. Select the Flow type.

7. Upload a specification file. This will be stored in your Integration library. 

8. Upload a sample input file. This will be pre-loaded as the source for your map. 

9. Review the mapping configuration settings. 

10. Click Generate. 

     

Accessing the AI EDI Mapper in the Custom Mapping Tool 

The navigation path to access the AI EDI Mapper is the same as the path for accessing the Custom Mapping Tool. 

1. At the top menu bar, click Workspaces and select the desired Workspace. 

2. At the top right of the screen, click Workspace Settings from the hamburger menu.
3. Navigate to the Developer subsection

1. Click Custom Mapping Tool. 

   The page refreshes to display a list of mappings. If you do not have any mappings, the table will appear blank. 

2. In the upper right area of the page, click the blue New Inbound EDI button.

The page refreshes to display the the AI EDI Mapper. The AI EDI Mapper allows you to build EDI maps by uploading a specification document and a sample input file. These two files will be added to your integration library. The sample will also pre-load into your mapping before you customize your JSONata expression. 

Creating a Mapping with the AI EDI Mapper 

1. Click the EDI Document Type drop-down menu and select the EDI document type that matches your intended EDI input file. 

   This selection represents the Chain.io JSON equivalent of the EDI file you are converting. 

   The options are: 

   • Chain.io 204 EDI
   • Chain.io 300 EDI
   • Chain.io 304 EDI
   • Chain.io 810 EDI
   • Chain.io 850 EDI
   • Chain.io 856 EDI (Standard Shipment)
   • Chain.io 860 EDI
   • Chain.io 888 EDI
   • Chain.io 940 EDI
   • Chain.io 943 EDI
   • Chain.io 945 EDI
   • Chain.io 990 EDI
   • Chain.io EDIFACT EDI IFTMIN

2. Click the Integration drop-down menu and select the Integration type that will be used with the mapping. The list reflects your existing Integrations.

You can also select "Create New Integration" to create a new Integration. The drop-down menu of Integration types is dependent on the EDI document type you selected. If you create a new Integration in the AI EDI Mapper, continue by:

• Entering a new integration name in the New Integration Name field
• Selecting an Integration type from the Integration Type drop-down menu
   

Example

The remaining instructions for this section will be completed using the option of creating a new Integration for the mapping. 

3. Click the Flow Type drop-down menu and select the Flow that will be used in the mapping. 

   The list populates based on the Integration type selected in the previous step.

4. Click the Upload Spec File region to select a file to upload. You can also drag and drop a file into the region. This will be stored in your Integration library. 

EDI Specifications Files and EDI Sample Input Files 

Refer to the EDI File Types table below for the specifications file and sample input file corresponding to your EDI document type. Click the specifications file link or sample input file link from the table to download the document. The file will appear in your Downloads folder and you can upload it to the AI EDI Mapper. During the AI EDI Mapper configuration process, you can use your own sample input file or the one provided in the table. 

The permissible uploaded file extensions are: 

• .pdf

• .txt

• .doc

• .docx

• .edi

   

For each EDI file type, the table provides the: 

• Supported Integration types
  List of Integrations that support the EDI file type.

• Supported Flow types
  List of Flows that support the EDI file type. 

• EDI Specifications File 

• EDI Sample Input File 
  A gray expandable window to view and or copy the sample file code used in the mapping process
   

5. Click the Upload Sample Input File region to select a file to upload. You can also drag and drop a file into the region. This will be pre-loaded as the source for your mapping. 

6. Review the AI EDI Mapper form to ensure all required fields are completed. 

7. At the bottom of the page, click the blue Generate button to create the EDI mapping. 

8. Review the selections on the Confirm EDI Map Generation pop-up window. 
   
   The system pre-selects the following actions to take place from the mapping generation. These two actions can be unselected if desired. 

   • Upload the specification and sample files to Integration library. 

   • Create a Flow using the generated map. 

9. 
   The system always performs the following actions when using the AI EDI Mapper: 

   • Create an EDI mapping for the specified EDI document type. 

   • Create the EDI mapping in the selected Integration. 

10. Click the blue Generate button to confirm the EDI mapping configuration settings. 

The page refreshes to confirm that the EDI mapping was generated successfully. If fields were missing from the EDI Mapper Generation form, the system will prompt you to update them before generating a successful mapping. 

10. Review the information and links on the EDI Mapper confirmation page. View the suggested next steps.

    

11. Keep this browser window open for reference as you progress through the remaining steps to configure the mapping. 

     

Editing the Custom Mapping

1. Under the Edit Map subsection, click the Open in New Tab link to edit the EDI mapping within the Custom Mapping Tool.

2. In the Output panel (3rd column), click the Select a Mapping Target drop-down menu and select the desired output file type for your use case.
   
   Example
   For this example, Booking Response was selected as the mapping target output file type. 

3. Edit the JSONata expression in the JSONata Expression panel (2nd column) to fit your use case.
4. In the upper right of the page, click Save Revision.
5. In the same region, click Deploy as New Version to make the mapping available for use in a Flow. 

Editing the Flow Configuration Settings

1. On the EDI Mapper confirmation page, under the Edit Flow subsection, right click the Edit Flow link to open the link in a new browser window. 

2. Click Edit to the right of the Flow to edit the Flow configuration settings. 
   
   After generating the mapping through the AI EDI Mapper, required subsections of the Flow configuration settings may have red banners. At a minimum, these settings must be configured before executing the Flow. Aside from these red banners, update additional Flow configuration settings as necessary for your use case. 

3. Scroll down to the Source Connection subsection and click the banner to expand.

4. In the Select Connection pop-up window, click the green Add New Connection button to specify a source connection. 

5. Select the appropriate connection type and complete the required fields for your use case.  

Example 
For this example, an email connection was selected. 

6. Click the blue save button to confirm the selection. 

7. Scroll down to Destination File Type subsection and click the banner to expand. 

8. Click Select under the file type that fits your use case. 

Example
For this example, Chain.io Shipment JSON was selected. 

9. Scroll down to the Destination System subsection and click the banner to expand. 

10. Select a Host System from the list of your existing host systems, or click the green Add New Host System button. 

Example
For this example, No Action was selected. 

11. Complete any additional Flow configuration settings required for your use case.  
12. Within the Actions menu on the right side of the page, click Save to save your Flow configuration settings.

13. Within the same menu, click Deploy to implement the configuration.

     

Viewing Files in the Library 

1. On the EDI Mapper confirmation page, under the View the Library subsection, right click the View Library link to open the link in a new browser window. 
   
   The files uploaded during the AI EDI Mapper process are available in the Files subsection. 

2. On the EDI Mapper confirmation page, under the Back to Mappings subsection, click the Close and Go Back to Mappings link to return to the Workspace Maps page.

Attached Files Referenced in the EDI File Types Table

These files are included for the EDI File Types table above to reference.