Order Release to Consol Shipment Match Based on Reference Number Qualifier and Value
This feature allows you to specify a Reference Number Qualifier that will be used in Consol Shipment Planning (actions and bulk planning) to match your Order Releases to Consol Shipments where there exists a match for the selected Reference Number Qualifier and its Value. The Order Release Consol matching feature is available with all Consol Types.
To configure this feature, you will need to specify the Reference Number Qualifier that will be used for matching. The Planning Parameter CONSOL SHIPMENT MATCHING REFNUM QUALIFIER is used to identify the Reference Number Qualifier to use.
Parameter - CONSOL SHIPMENT MATCHING REFNUM QUALIFIER
Below are the setup steps followed by a series of examples to show how the CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and Value are used to determine what Consol Shipments are and are not considered based on the different options for setting, or not setting, the CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and Value on the available Consol Shipments.
The first step for using this feature involves selecting (or creating) the Shipment and Order Release Reference Number Qualifier to use. The chosen Reference Number Qualifier will be the value entered in the Planning Parameter CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and will be the Reference Number Qualifier assigned to the Order Releases and Consol Shipments. Note, since Reference Number Qualifiers are actually defined and managed by object (in this case Order Release and Shipment ) the Reference Number Qualifiers selected must be configured in the same Domain. In this example, the Order Release and Shipment Reference Number Qualifier "CONSOL_MATCH" was created in the "OOTB" Domain. Note that the value specified for the Planning Parameter CONSOL SHIPMENT MATCHING REFNUM QUALIFIER is the GID for Reference Number Qualifier, in this case OOTB.CONSOL_MATCH.
CONSOL SHIPMENT MATCHING REFNUM QUALIFIER - Parameter Setup
While you are setting up the Parameters - you will also need to make sure/change the Order Routing Method to Network Routing v Cost Based routing.
In summary, the Parameter setup changes required are shown below.
Parameter Overrides Required
To demonstrate the usage of the feature, multiple Ground Consol Shipment options have been created. One Shipment Consol option is with Carrier01 and another is for Carrier02. The two Consol Shipments are identical - with the one exception being that the Carrier02 option is more expensive than the Carrier01 option. Without the configuring the CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and value - the order release will be planned on to the Carrier01 Ground Consol - Carrier01 is the least expensive option.
Demonstration 1 the Order Release and Consol Shipment 25133 - for Service Provider Carrier02 will both have a matching CONSOLSHIPMENT MATCHING REFNUM QUALIFIER and Value. Consol Shipment 25132 - for Service Provider Carrier01 will have a matching CONSOLSHIPMENT MATCHING REFNUM QUALIFIER but the Value will not match.
Below is the Order Release that will be used in the example. The CONSOLSHIPMENT MATCHING REFNUM QUALIFIER
Order Release With Configured Reference Number and Value
Below is Consol Shipment 25133 - for Service Provider Carrier02 with the matching Reference Number Qualifier and Value CONSOL_MATCH WK41.
Carrier02 Consol Shipment 25133 With Qualifier and Value
Below is Consol Shipment 25132 - for Service Provider Carrier01 with the matching Reference Number Qualifier, but a different Value CONSOL_MATCH WK42.
Carrier01 Consol Shipment With Different Reference Number Qualifier Value
With this setup, running the action Build Buy Shipment On Primary Leg Show Consol Options will only bring back the Carrier02 Consol Shipment Option - as shown below. The Order Release - below - has also been configured with the same Reference Number Qualifier and Value as the Consol Shipment for Carrier02.
Build Buy Shipment On Primary Leg Show Consol Options
In this case - only one option is provided - the Consol Shipment (25133) option with the matching Reference Number Qualifier and Value CONSOL_MATCH WK41.
Consol Shipment Option with the Matching Reference Number Qualifier and Value CONSOL_MATCH WK41
The same setup, with Bulk Planning results in having Order Release assigned to the matching Consol Shipment 25133 - as shown below.
Bulk Plan
Below is the Bulk Plan result, the Order Release is assigned to the matching (and more expensive) Consol Shipment for Service Provider Carrier02.
Bulk Plan Result
In the scenario below, the Reference Number Qualifier and Value for Consol Shipment 25132 - for Service Provider Carrier01 is removed. In this setup, both Consol Shipment 25133 with the matching Reference Number Qualifier and Value and Consol Shipment 25132, with no CONSOLSHIPMENT MATCHING REFNUM QUALIFIER specified will be candidate Consols for the Order Release.
Consol Shipment 25132 - Service Provider Carrier01 - No CONSOLSHIPMENT MATCHING REFNUM QUALIFIER
In this setup, both Shipment Consols will be considered - as shown below after running the action Build Buy Shipment On Primary Leg Show Consol Options.
Build Buy Shipment On Primary Leg Show Consol Options - One Shipment Consol With Qualifier Value One Without
The result, as expected, when running Bulk Plan - with both options available results in the selection of the less expensive Consol Shipment option - Consol Shipment 25132 - Service Provider Carrier01 as shown below.
Bulk Plan Results
Changing the Value for the Reference Number Qualifier to a non-matching value will limit the available Consol Shipments to the 25132 Consol shipment, which is the Consol Shipment without the CONSOLSHIPMENT MATCHING REFNUM QUALIFIER specified.
Order Release No Matching Value for Qualifier - Only No Qualifier Consol Shipment Valid
Removing the CONSOLSHIPMENT MATCHING REFNUM QUALIFIER from the Order Release allows for both Consol Shipments 25132 without the Qualifier and Value and 25133 with the Qualifier and Value to be considered.
Order Release No Qualifier
You Order Release can specify multiple options for matching to a Consol Shipment. In the example below, the Order Release has two options for matching to a Consol Shipment - CONSOL_MATCH WK41 or CONSOL_MATCH WK42. The Consol Shipment 25132 has been modified to have the Reference Number and Value- CONSOL_MATCH WK42.
Order Release Multiple Match Options
With this setup, running the action Build Buy Shipment On Primary Leg Show Consol Options brings back both options since both Shipment Consol options - for WK41 or WK42 - are a match.
Multiple Match Options
Business Benefit
Provides a way to match your order releases to the desired Consol Shipment.
Steps to Enable
-
You will need to select or create the Shipment and Order Release Reference Number Qualifier to use. The selected Reference Number Qualifier will be the value entered in the Planning Parameter CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and will be the Reference Number Qualifier assigned to the Order Releases and Consol Shipments. Since Reference Number Qualifiers are defined and managed by object (in this case Order Release and Shipment ) the Reference Number Qualifiers to be used for Order Release and Consol Shipments must be configured in the same Domain.
-
You will need to specify the Reference Number Qualifier you want to use in the Planning Parameter CONSOL SHIPMENT MATCHING REFNUM QUALIFIER. This parameter identifies the Reference Number Qualifier that the logic will use. Note that value entered is the GID i.e., Domain.Reference Number Qualifier ID.
-
You will need to make sure your Domain Default Parameter Set includes the CONSOL SHIPMENT MATCHING REFNUM QUALIFIER and has Order Routing set to Network Routing. The same is true for the Parameter Set you intend to use in Bulk Planning - if it's different.
-
Finally you will need to add the Reference Number Qualifier and Value to the appropriate/desired Consol Shipments and Order Releases.
Tips And Considerations
Make sure the Reference Number Qualifier IDs for your Shipment Reference Number Qualifier and your Order Release Reference Number Qualifier are the same and are created in the same Domain.