X12 214 - Truckmate

When the Outbound Cloud Monitor receives a flat file, CIC parses it and searches for the matching outbound route. If there is a match, the 214 Flow converts the file to EDI 214 format and sends the file to the Trading Partner Endpoint.

This section explains how to configure the integration for a 214 Flow.

How to Configure the Flow

1. Configure cloudMonitor: Configure OutboundMN cloudMonitor in the package com.cleo._customer_.edi.booster.tmwtruckmate.outbound to poll for the required endpoint.
2. Configure the Outbound Route: The tradingPartnerID field under record P is used to identify the Trading Partner to whom the 214 is to be sent. Update the Outbound Route _TP_214v4010OR (found in com.cleo._customer_.edi.booster.tmwtruckmate.outbound.n214 package) to reflect the matching ID. 
3. Configure the EDI Enveloper: The X12 214 envelope details and the trading partner endpoint to which the X12 214 is to be sent should be configured in _TP_214v4010ENV (found in the trading partner Project/com.cleo._customer_.tmwtruckmate._tp_.outbound.n214.v4010). By default, the Customer name and the TP Name entered in the Wizard property file are added to the sender ID and receiver ID, respectively. If there are any changes to the enveloping details, the object must also be updated accordingly.

How to Run the Flow

1. Before proceeding, ensure that the following Projects have been deployed. If any of these Projects are already deployed and remain unmodified, there is no need to redeploy them. Similarly, if any of these Projects were not checked out to your Workspace, they can be skipped from the deployment process.

1. • com.cleo._customer_.edi
   • com.cleo._customer_.edi.booster.tmwtruckmate
   • com.cleo._customer_.editmwtruckmate
   • com.cleo._customer_.tmwtruckmate._tp_
   • com.cleo.b2bcloud.core
   • com.cleo.b2biaas.clarify
   • com.cleo.cic.cockpit.core
   • com.cleo.cic.cockpit.core.n204
   • com.cleo.cic.cockpit.core.n214
   • com.cleo.cic.cockpit.core.n990
   • com.cleo.cic.cockpit.core.n210
2. Upload the flat file to the endpoint configured in the OutboundBPS and CIC will pick it up.

How to Monitor the Flow

1. Check Auditor log entries. For more information, see Using the CIC Studio Auditor.
2. Verify the following in the CIC Cockpit.
   
   • Message Tiles
   • Jobs
   • Dashboard > Charts

In case of errors:

1. If the processing fails in any of the steps, a ticket is created.

   The Message Tile view shows a corresponding tile with the Issue Flag.
   

   The Job List view shows a corresponding Job with the Issue Flag.
   

2. For details on Outbound EDI validation rules, refer to Validation Rules in the Transformation Settings object.

How to Customize

Here are a few ways you can customize this flow:

Change the filename in OutboundBPS to recognize the transaction

The OutboundBPS residing in the com.cleo._customer_.edi.booster.tmwtruckmate.outbound package is configured to find the transaction type based on filename. A filename containing TMWtruckmate214 is identified as 214 and the corresponding launcher is triggered. If there is a difference in the filename, change it in the String Contains step of OutboundBPS.

Add more details to the X12 214 from the TMW Flat File

The values mapped from flat file to X12 214 are documented in the Integration Design Specification residing in com.cleo._customer_.editmwtruckmate/docs. To add any additional fields, update the ruleset _TP_214v4010RS in the com.cleo._customer_.tmwtruckmate._tp_.outbound.n214.v4010 as required.

Contact Cleo Support if you need any assistance while adding additional rules.

Customizing TMW Flat File Schema

You can customize the TMW truckmate Flat File schema under com.cleo._customer_.edi.booster.tmwtruckmate.inbound.n214 as required.