DCS-YCS: Error: "YCS Configuration incorrect for <SCAC> carrier"

Resolving The Problem

Solution

A possible cause of this issue is incorrect or missing records in the DCS table CARRIER_API_MAPPING. Check this table for records having CARRIER equal to the Manifest SCAC code of the scanned carton's SCAC. (Manifest SCAC for a given SCAC code is defined in 02016 - Carrier Setup)

You should have one record for each API you will need the ability to invoke. Start by figuring out which existing carrier the new carrier's behavior most closely resembles. If the new SCAC you are configuring behaves like UPS you should have a record for each UPS value below, and if it behaves like FedEx, you should have a record for each FedEx value below, etc.

CARRIER should be equal to the Manifest SCAC defined in 02016.

API_MAP_STRING should be one of the following values:

UPS Values:
CALL_INTRANSIT
CLOSE_MNFST_PRINT_MNFST
CALL_TRACE
CALL_TRACK
CLOSE_MANIFEST
FREIGHT_CHARGES
SHIP_CARTON
TRACKING_NUMBER
VALIDATE_SHIPMENT

FedEx Values:
SHIP_CRTN_SCAN_CRTN
DEL_CRTN
CLOSE_MNFST_PRINT_MNFST

Airborne Values:
SHIP_CRTN_SCAN_CRTN
DEL_CRTN

After you have added these records, be sure to restart the RPC server whrpcd and the YCS server to ensure these changes have taken effect.

For more information, see the topics located in the DCS-YCS Integration Guide under the following topic header:

DCS YCS Integration -> Using DCS-YCS Integration for Other Carriers

Note: The example given in "Carrier Code Setup" topic is an example SCAC code. The value PURL is not hardcoded. You can use any 1-4 character value you choose.