EDI Details

This page will give a rundown of the EDI Process with EDI Standards as well as Ditat standards.

Ditat Supported EDI types

204 - Incoming Load Tenders

• Incoming load tenders will be sent from the EDI Partner and will show on the EDI Process Messages screen.  

  • Once the message is read and processed the load tenders will be added to the Process Load tenders screen. 

  • When a user accepts an original load tender in Ditat, the system will auto-generate the shipment and display the load number on the Process Load Tender screen.

  • Update 204's will not update the loads they are informational for the end-user once accepted they will need to be added to the shipment manually. 

997 - Acknowledge load tenders

• When enabled 997 will be auto-sent from the system when we receive load tenders to tell the EDI Partner we got the message.

• If the EDI partner sends 997 messages, they will show as receipts to show that the messages that were sent were received.

990 - Respond to load tenders

• These are accept or decline messages that are sent to the EDI Partner when the 204 Load Tender is accepted or declined.

• The system will by default also send 990 files to any accepted updates that are sent.  This can be turned off in the mapper for each EDI Partner.

214 - Shipment status messages

• These are updates that are sent from Ditat to the EDI Partner, linked to check calls added in Ditat.

• The different types of messages sent are specified by each EDI Partner and set up on the EDI Partner Profile.

210 - Freight details and invoice

• These are invoices that are sent via EDI to the Partner.  

• These can be viewed or deleted on the Process Freight bills screen.

• The system will auto-import and process all Invoices posted at 4 each morning. Any invoices that have not been sent will be sent at that time.

Documents

• This will allow Invoices or Supporting documents to be uploaded to customers using an EDI connection.

EDI Messages

Messages are always in patterns so they can be read.

Every message will start with an ISA line and end with the IEA line which is the start and stop of the message.

Inside that message, there will be GS to GE that will give details about when and who the message is from on the GS and how many messages were included in the message on the GE line.

Inside that GS-GE there will be ST to SE Loops. These sections will be each message that is being sent.

Separate Partners for Invoicing

Example-

There will need to be multiple EDI Partners for this to work.

Main Partner CH Robinson. 

·         This partner will handle receiving the 204 returning the 990/214 files, No 210’s for this EDI Partner.

There will then be 2 additional EDI Partners one for each invoicing partner.

CH Robinson Invoicing. 

• This Partner will be using a dummy connection in the defaults section so it does not interfere with incoming 204’s.

• On the 210 tab we will Override with the Normal CH Robinson 210 information

Hasbro-CHR Invoicing

• This Partner will be using a dummy connection in the defaults section, so it does not interfere with incoming 204’s.

• On the 210 tab we will Override with the Normal Cass 210 information