Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.0 to 6.3.3 [Release 6 to 6.3]
Information in this document applies to any platform.
In OTM, the following property is set so that SMC's Carrier Connect can be used
glog.RatingEngine.Rateware.NewAPI = true
It is found that even for SMC Rates that are not configured with a Rate Service that uses Carrier Connect (i.e. have Rate Service Type of EXTERNALTRANSITDAYS), that the SCAC Code is still being sent to SMC resulting in the following exception:
"Invalid SCAC (Carrier Code) / Carrier Type Code."
Since this rate is not expected to use Carrier Connect, the SCAC Code is not expected to be sent to SMC.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms