Overview
EDI Locations
From TMS Admin → EDI Locations, enter the EDI identifiers for each EDI trading partner.
There are two types of records in this object:
Trading Partner EDI Identifier records: the Trading Partner and Location fields are identical, and the Trading Partner Id flag is true.
Trading Partner location records: codes for specific locations, by trading partner, are identified.
This table "fills" automatically as EDI 204 Load Tenders are processed (if they contain location codes).
Trading partners for inbound EDI 204 tenders are the customers or customer bill to. Trading partners for outbound EDI 204 tenders are the Carriers.
Several account records can be associated with the same customer trading partner by populating the SCAC field. [Location Code + SCAC] must be unique. This allows for “division-specific” treatment of trading partners.
Location Matching for Inbound 204 Tenders
In order to avoid creating duplicate accounts, the TMS searches existing records to determine location information. There are two scenarios that determine how the TMS matches location information. One, a location code is provided in the XML. And two, when a location code is NOT provided in the XML. This location code is the companyId field in the XML examples provided. See the EDI Specification document for XML examples.
Location Code Provided
When a location code is provided with a Stop, the TMS searches for an EDI Location record that matches the location code in the XML (companyId). The matching EDI location record contains the Trading Partner lookup field. This Trading Partner lookup field must reference the Customer Account on the Load.
If the location code in the XML and the Trading Partner lookup field on the EDI Location record successfully match, several fields are compared:
Account Name
Shipping Street
Shipping City
Shipping State
Shipping Postal Code
Shipping Country
If any of the fields differ, the Account record is updated with the values from the XML.
If the location code in the XML and the Trading Partner lookup field on the EDI Location record do not match, the TMS searches for a matching Account record. The search must exactly match the following fields received in the XML payload:
Account Name
Shipping Street
Shipping City
Shipping State
Shipping Postal Code
A match is found if all 5 fields match an Account record. The TMS then searches for a matching EDI Location. The EDI Location must reference the matching Account AND the Trading Partner lookup field must reference the Customer Account on the Load.
If a matching EDI Location is found, a new Account record is created. A new EDI Location record is created that references the new Account and Location Code. Existing Account and EDI Location records are not changed. In this scenario, multiple Account records can be associated with multiple EDI Locations for the same Trading Partner that all refer to the same Account location with different Location codes.
If a matching EDI Location is NOT found, a new EDI Location record is created for the matched Account record.
When a matching Account record is NOT found, a new Account record is created and a new EDI Location record is created.
Location Code Not Provided
When a location code is not provided with a Stop, the TMS searches for an Account record exactly matching the following fields received in the XML payload:
Account Name
Shipping Street
Shipping City
Shipping State
Shipping Postal Codes
A match is found if all 5 fields match an Account record in the TMS. When matched, that Account is used to create a Stop on the Load. No EDI Location is created.
If no match is found, a new Account record is created. This new Account is used to create a Stop on the Load. No EDI Location is created.