The Kleinschmidt integration provides the ability to send and receive customer and Carrier Tenders with EDI Transaction processors (type of API).
The following EDI transactions are supported:
API Provider | EDI 204 Support | EDI 990 Support | EDI 214 Support | EDI 210 Support |
|---|---|---|---|---|
Kleinschmidt | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound |
Cleo | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound |
Custom EDI | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound | Inbound/Outbound |
For more specific EDI setup, see this article.
Setup
Enter Credentials
Enable the Kleinschmidt integration by:
Navigating to TMS Admin,
Select Credentials.
Select the Global Services tab,
Find Kleinschmidt in the list and open the card.
Check the Enabled checkbox.
Enter the User ID and Password 1 into the text fields.
Click the Save button when finished.
Valid credentials are required from a Kleinschmidt subscription. See examples in the table below.
User ID | Password 1 | Password 2 | Customer Number |
|---|---|---|---|
Required | Required |
When using the Kleinschmidt EDI, make sure any unused EDI integrations are NOT enabled.
Remote Site Settings
Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Kleinschmidt integration URL are up to date.
Click the Setup gear icon in the top right corner.
From the drop-down, click Setup.
In the Quick Find Toolbar type Remote Site Settings and click the link.
From the list of remote sites find Kleinschmidt and click the Edit link.
Update the Remote Site URL to match the Service URL below:
Service URL: https://www.sub.kleinschmidt.com/
Text Service URL: https://www.sub.kleinschmidt.com/test/
TMS Admin
Configuration
See EDI Setup for specific settings under TMS Admin, Configuration to use EDI transactions.
EDI Error Codes
This table contains a list of EDI error codes/messages and steps to resolve the issue or detailed information.
Error Code/Message | Quick Description |
|---|---|
Arugment 1 cannot be null(rtms)218 | A required field is not populated |
EDI failure: Stop number is invalide. Cannot be zero. | The <dropoffStopNum> CANNOT be set at zero. There must be a matching Stop number passed in the transaction. |
First exception on row 0; first error: STRING_TOO_LONG | STRING_TOO_LONG occurs due to populating a field with more characters than its max length. |
Unable to tunnel through proxy: 'HTTP/1.1 503 Service Unavailable”(rtms)34 | 'HTTP/1.1 503 Service Unavailable”(rtms)34' means that the EDI web service was down during the time of the callout to it. |
Read timed out(rtms) 35 | The Kleinschmidt transaction is timing out. As long as the EDI queue is still in place, the Loads will be picked up the next time the job runs. |
Troubleshooting
EDI Failure: Stop number is invalid. Cannot be zero.
Issue
Kleinschmidt EDI tender fails due to zero being passed as a Stop number. Stop number cannot be zero.
Resolution
The <dropOffStopNum> CANNOT be set at zero. There must be a matching Stop number passed from Kleinschmidt.
<pickupStopNum>2</pickupStopNum>
<dropoffStopNum>0</dropoffStopNum>
<itemNum>12432</itemNum>
Insert failed. First exception on row 0; fist error: STRING_TOO_LONG, Transaction Payload: data value too large.
Issue
The STRING_TOO_LONG error occurs due to populating a field with more characters than the maximum length. For example, if a field length is set to 255 characters and attempt to insert 300 characters, this exception is thrown.
Resolution
This error is due to duplicate reference numbers sent from Kleinschmidt. Resolve this issue by contacting the Kleinschmidt team at motor@kleinschmidt.com and request they remove the duplicate fields from the XML transaction.
