IBM Support

DCS: How does the system select Shipment Mode (Ship Mode) and SCAC (Carrier) - Proper Setup of 09006 - Ship Mode and SCAC Sel. Rule

Question & Answer


Question

DCS: How does the system select Shipment Mode (Ship Mode) and SCAC (Carrier) - Proper Setup of 09006 - Ship Mode and SCAC Sel. Rule

Answer

 

Problem:
DCS is not signing correct SCAC/ship mode to shippers.

Possible Cause:
SCAC Sel. Rules are not configured properly.

Resolution:
First, it is important to understand that the SHIP MODE is assigned before the SCAC is assigned.  If your shippers are being assigned the wrong ship mode, and there is no rule that links the SCAC to that ship mode, then the correct SCAC will not be assigned.

Here is a quick summary of the usual SCAC selection process:

A. SHIP MODE SELECTION
1) DCS checks the order to see if a ship mode has been predetermined by the host.  If so, this is the ship mode.
2) If not, DCS then checks the order to see if a SCAC has been predetermined.  If so, the default ship mode of this SCAC is selected.
3) If nothing is predetermined, DCS first checks the weight of the shipper against Outbound setup to see if it should be a TL shipment
4) Then, if SHIP MODE has not been selected yet, DCS goes to the selection rules in 09006, and selects a SHIP MODE.
5) If no SHIP MODE is selected, an error will be logged.

B. SCAC SELECTION
5) Once a SHIP MODE has been selected, and provided a SCAC has not been predetermined, DCS goes through the SCAC selection rules in 09006 and selects the highest priority of those fitting the right criteria, including the previously selected SHIP MODE.

More detailed information can be found in solutions 11369 and 11475.

 


When creating a Ship Mode/SCAC Selection Rule, the following fields are MANDATORY:

FROM ZIP CODE
TO ZIP CODE
WEIGHT LIMIT
SHIP MODE
SCAC

The following are not mandatory:

VOLUME LIMIT
BILL TO
PREF SCAC
STATE
NO OF CARTONS
PRIORITY
SCAC SERVICE
DELIVERY CODE

This means that the mandatory fields are ALWAYS used as criteria for selection (Except for SCAC).  Therefore each SCAC Selection Rule is not defined by a rule code, but rather by a combination of the above criteria.

If you want a rule to be irrespective of the zip code, expand the range beyond that of all US zip codes.  Don't forget to consider any "dummy" zip codes you may use on your shippers.  For example, if a shipper's destination is outside the US, it will not have a zip code.  You must use a dummy zip code, so it will be picked up by the SCAC Selection Rules.

DO NOT LEAVE SHIPPER ZIP CODES BLANK IF YOU WANT A SCAC TO BE ASSIGNED TO IT AUTOMATICALLY.  THEY WILL NOT BE PICKED UP BY ANY SCAC SELECTION RULES.  THIS MAY INVOLVE EXTERNAL COOPERATION.

The purpose of the PRIORITY field is to determine which SCAC Selection Rule will be used when a shipper falls under more than one rule.  When this occurs, the rule having the lowest PRIORITY will be applied.

 

 

For example,  let's say you wanted SCACs to be assigned as follows:

A - All parcel shipments should be assigned SCAC Code UPSG.
B - All LTL shippers going to the state of Massachusetts should be assigned FEDG
C - All other LTL shippers should be assigned FEPO
D - All shippers going to zip code 01876 should be assigned DFLT (even if they are parcel or LTL + Massachusetts)
E - All other shippers should be assigned AIRE, unless they are over 1000 lbs
F - All other shippers that are over 1000 lbs should be assigned AIRN

Let's also say the only ship modes you support are PRCL, TL, and LTL, but you know that more may be created in the future.

You would want to create the following codes, starting with the most specific at a low priority.  We will number them for reference (They are not numbered in DCS)

#  FROM ZIP  TO ZIP   WT LMT  VOL LMT  BILL TO  STATE  PRIORITY  SHIP MODE  SCAC
-  --------  ------  -------  -------  -------  -----  --------  ---------  ----
1  ___01876  _01876  9999999  _______  _______  _____  _______1  _____PRCL  DFLT
2  ___01876  _01876  9999999  _______  _______  _____  _______1  _______TL  DFLT
3  ___01876  _01876  9999999  _______  _______  _____  _______1  ______LTL  DFLT
4  _______0  999999  9999999  _______  _______  _____  ______10  _____PRCL  UPSG
5  _______0  999999  9999999  _______  _______  ___MA  ______10  ______LTL  FEDG
6  _______0  999999  9999999  _______  _______  _____  ____1000  ______LTL  FEPO
7  _______0  999999  ___1000  _______  _______  _____  ____1000  _______TL  AIRE
8  _______0  999999  9999999  _______  _______  _____  ____5000  _______TL  AIRN


-Rules 1, 2, and 3 take care of requirement D.  You need a separate rule for each Ship Mode.  Rule 1 must have a lower priority than Rule 4, so it is not overridden.
-Rule 4 takes care of requirement A
-Rule 5 takes care of requirement B - Priority must be higher than Rule 3, otherwise shippers that fall under Rule 3 will be picked up by rule 5
-Rule 6 takes care of requirement C
-Rule 7 takes care of requirement E
-Rule 8 takes care of requirement F - The priority of this rule must be greater than the priority of Rule 7, or it will override any shipments that would otherwise be picked up by Rule 7

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

HTG2129

Document Information

Modified date:
16 June 2018

UID

swg21562787