Overview
Blue Yonder
Access tokens to Blue Yonder are granted through OAuth 2.0 Client Credentials grant type. The User Id represents the Client ID and Password 1 represents the Client Secret.
The Blue Yonder credentials are used only for returning rates to the Blue Yonder system. All other actions are performed by the REST based classes in the TMS.
The EDI Tenders checkbox under the Blue Yonder credentials should be enabled if the tenders to Blue Yonder loads will be done via EDI instead of through Blue Yonder. Enabling the field will automatically populate relevant EDI fields on Blue Yonder loads.
Additional Configuration
The following should be configured before using Blue Yonder:
Customer Blue Yonder Ids should be populated on the Blue Yonder Id field on the customers’ transportation profiles. This will link the Blue Yonder customer to the account in the TMS otherwise an error will be throw.
The Blue Yonder Code and Blue Yonder Mode should be set for each equipment type in the TMS. The Blue Yonder Code will link the Blue Yonder equipment type code to the equipment type in the TMS and the Blue Yonder Mode will set the corresponding mode on the load.
An API accessorial with the API Provider as Blue Yonder should be created for each accessorial Blue Yonder can provide. If Blue Yonder includes an accessorial and an API accessorial is not found, the system default with be used.
If customer tendering is done through EDI instead of through Blue Yonder:
The EDI Tenders should be checked under the Blue Yonder credentials.
EDI locations should be created for the relevant Blue Yonder customers.
From TMS Admin, Configuration, confirm that the box for Blue Yonder is checked.