EDI Setup

Several fields are located under TMS Admin → Configuration that control org-wide functionality for EDI transactions.

EDI Settings

See the EDI Setup and Processing documentation for more specific EDI setup information.

1. EDI Enabled

   1. Enables support for sending and receiving EDI transactions.

2. EDI Run Frequency (Minutes)

   1. Determines how often Load Tenders are requested from the EDI VAN via the EDIJob batch process.

3. Display EDI References on Carrier Docs

   1. If checked, display EDI reference numbers on the Carrier and driver tender documents.

4. EDI Freight Charges Code

   1. When set, the field value is passed in outbound EDI 210 transactions.

5. Enable EDI Transaction Logging

   1. When checked, each EDI transaction XML packet is stored with the Load in the EDI Transaction object.

   2. If the Use REST API for EDI field is checked, this field is not available. EDI Transaction records are always created and are handled by the EDI REST fields.

6. EDI Transaction Logging Types

   1. List of EDI transaction types that are logged to the EDI Transaction object.

   2. If the Use REST API for EDI field is checked, these fields are not available. EDI Transaction Logging is handled by the EDI REST fields.

      1. Inbound 204

      2. Inbound 990

      3. Inbound 214

      4. Inbound 210

      5. Inbound 824

      6. Inbound 322

      7. Inbound 410

      8. Outbound 990

      9. Outbound 204

      10. Outbound 210

      11. Outbound 214

      12. Outbound 404

      13. Outbound 998

7. EDI Administrator

   1. Set the user who receives emails in case of EDI issues and errors.

8. EDI Shipment Id Field

   1. The field from the Load object identifies Shipments/Loads in EDI transactions. Usually, the PO Number field is designated as the EDI Shipment ID by the EDI trading partner(s) sending Load Tenders.

9. Enable EDI Overrides

   1. When checked, redirect EDI 210, 214, and 990 transactions to a different EDI Provider or Trading Partner for certain accounts. This functionality overrides the default behavior.

10. EDI Fuel Surcharge Code

    1. When a value is set, this field is passed in outbound EDI 210 transactions.

11. Use REST API for EDI

    1. When checked, the EDI REST architecture is used to receive all EDI transactions from the Partner VAN. Customers who receive EDI transactions are recommended to use this architecture.

    2. When checked, inbound and outbound EDI SOAP transactions are not supported via the EDI job.

    3. With this architecture, customers may have up to 3 different connections to partner VANs (Kleinschmidt, Cleo, and 1 custom EDI).

12. EDI Context User (Kleinschmidt)

    1. The Context User ID to identify and verify Kleinschmidt EDI for REST client credentials flow.

    2. The Context User ID is the API User that is created using the following External Client App instructions.

    3. One Context User is used per VAN/External Client App.

13. EDI Context User (Cleo)

    1. The Context User ID to identify and verify Cleo EDI for REST client credentials flow.

    2. The Context User ID is the API User that is created using the following External Client App instructions.

    3. One Context User is used per VAN/External Client App.

14. EDI Context User (Custom EDI)

    1. The Context User ID to identify and verify custom EDI for REST client credentials flow.

    2. The Context User ID is the API User that is created using the following External Client App instructions.

    3. One Context User is used per VAN/External Client App.

15. EDI 204 Inbound Transaction Exp (Days)

    1. The number of days to retain inbound EDI 204, 404, and 998 transactions before they are deleted by the Data Cleanup job.

16. EDI 990 Inbound Transaction Exp (Days)

    1. The number of days to retain inbound EDI 990 and 824 transactions before they are deleted by the Data Cleanup job.

17. EDI 214 Inbound Transaction Exp (Days)

    1. The number of days to retain inbound EDI 214 and 322 transactions before they are deleted by the Data Cleanup job.

18. EDI 210 Inbound Transaction Exp (Days)

    1. The number of days to retain inbound EDI 210 and 410 transactions before they are deleted by the Data Cleanup job.

19. EDI 204 Outbound Transaction Exp (Days)

    1. The number of days to retain outbound EDI 204, 404, and 998 transactions before they are deleted by the Data Cleanup job.

20. EDI 990 Outbound Transaction Exp (Days)

    1. The number of days to retain outbound EDI 990 and 824 transactions before they are deleted by the Data Cleanup job.

21. EDI 214 Outbound Transaction Exp (Days)

    1. The number of days to retain outbound EDI 214 and 322 transactions before they are deleted by the Data Cleanup job.

22. EDI 210 Outbound Transaction Exp (Days)

    1. The number of days to retain outbound EDI 210 and 410 transactions before they are deleted by the Data Cleanup job.