List of Parameters

Parameter sets are accessed via:

Shipment Management > Power Data > General > Parameter Sets
Master Data > Power Data > General > Parameter Sets

Following are the parameter settings defined in the DEFAULT Parameter Set stored in the Public domain.

There are additional multi-stop parameters and continuous move parameters on the Logic Configuration page.

See also Bulk Plan Cost Based Routing.

BUILD SECONDARY CHARGE SHIPMENTS AUTOMATICALLY

Brokerage and Forwarding

Controls whether secondary charge shipments are automatically built when building shipments.

BUILD SHIPMENT CALC TRANSIT TIME ON EACH LEG

Shipment Planning

When this parameter is set to TRUE, if the shipment options have the same cost, the option with the shorter service ti me will be selected.

This functionality only applies to shipments that are created from Create Direct Shipment action.

BUILD SHIP ON PRIMARY LEG OBEY REUSE EQUIP ON LEG

Shipment Planning

20C

When this parameter is set to true and if consol shipment is not unitized then OTM assigns equipment based on the re-use equipment assignment setting on itinerary leg and create order movements that share the same shipment ship unit.

By default, this parameter is set to false.

Note: This parameter is applicable only for consol shipments that are not unitized.

BULK PLAN LOGISTICS GUIDE ID

Bulk Plan

Select a Logistics Guide ID. Based on the ID passed into the bulk plan through this parameter, the cost data from the logistics guide aggregate data will be retrieved.

BULK PLAN ORDER MOVEMENTS BY LEG CLASSIFICATION

Multi-tier

6.2

If parameter is false (default), bulk plan order movements by original leg GID (pre 6.2 logic) and also by leg depending upon the value of the ALLOW DIFF ORIG LEG GID OMS CONSOLIDATE parameter. The groups are then sorted by the original leg position value (actually, the absolute value), and then planned. Groups with a negative original leg position (occur prior to the primary leg), will be planned as late as possible in order to minimize the time gap between the primary leg shipments are prior leg shipments.

If set to true, OTM will bulk plan order movements by leg classification based on the Leg Classification ID on the Order Movement manager. The groups are then sorted by the sequencing factor on the leg classification (actually, the absolute value), and then planned. This gives you a large measure of control over which order movements are grouped together for consolidation. Groups with a negative sequencing factor (occur prior to the primary leg), will be planned as late as possible in order to minimize the time gap between the primary leg shipments are prior leg shipments.

If true, the parameter ALLOW DIFF ORIG LEG GID OMS CONSOLIDATE will be ignored.

BULK PLAN VIEW LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Bulk Plan Results. Default is BULK PLAN VIEW WORKBENCH.

BUNDLE MAX NUM OF DAYS

Order Management

6.2

This specifies the maximum number of days the order release/order movement dates can be apart of each other in an order bundle. The order date is the date specified in the property glog.business.consolidatation.bulkplan.orderSortByDateType. It defaults to zero days (0D), which means no restriction and is backward compatible.

BY DAY RATE SERVICES USE EARLY PICKUP TIME

Service Time

This allows pickups to occur at the start of the rate service calendar, instead of the end. Default is false, so OTM uses the end time of the rate service calendar day for the pickup.

When set to true, the "By Day" rate service types (including Day Duration, Distance Duration, and External Transit Days rate services) will perform their pickup activity at the earliest possible time of day.

This replaces the property glog.business.rate.rateservice.ByDayUseEarlyPickupTime.

CALCULATE VAT ON VOUCHER

Settlement

This parameter determines how VAT is calculated on a voucher. This parameter has three possible options:

False: does not calculate the VAT for a voucher.

BY_APPROVAL_PERCENT - builds the voucher invoice line VAT amounts from the invoice line item VAT amounts and voucher VAT analysis from the VAT analysis based on the percentage of the invoice amount that was approved.

If there is a difference between the invoice total amount and the approved amount, then for each VAT code on the VAT analysis, the percentage difference is multiplied by the VAT amounts to re-determine the VAT for the voucher.

For voucher VAT analysis - voucherVATTaxAmount = ((Approved Amount/ Invoice Net Amount) * (invoiceVatAnalysis.taxAmount))

For Voucher Invoice Line VAT amounts - voucherInvLineVATTaxAmount = ((Approved Amount/ Invoice Net Amount) * (InvoiceLineItemVAT.vatAmount))

If the parameter value is set to BY_APPROVAL_PERCENT, the VAT amounts will be calculated for a voucher only if the VAT is calculated on the corresponding invoice of the voucher.

BY_LINE_ITEM - if this is set and the invoice was approved/adjusted by line, then the VAT engine is used to determine the correct VAT rates, VAT codes and VAT amounts.

voucherVATTaxAmount = ((Approved Amount) * (VATRate from VATEngine/100)).

If this parameter is set to BY_LINE_ITEM and the invoice is not approved/adjusted by line (glog.invoice.approveByLine = false), then the voucher VAT is calculated by setting the CALCULATE VAT ON VOUCHER parameter value to BY_APPROVAL_PERCENT.

If the invoice is not approved by line and only partial invoice amount is approved, then only the Voucher VAT Analysis amounts are calculated. In this scenario, the system doesn't calculate the Voucher VAT amounts at the line level as it is not possible to determine how much amount is approved from each invoice line item.

CARRIER CAPACITY WEIGHTING FACTOR

Service Provider Assignment

Note: See parameter Plan Shipments with Carrier Commitment. While, this parameter still works, the other is generally better.

The purpose of this parameter is to provide intelligence behind the selection of carriers for a set of shipments across all shipments. For example, Carrier_1 has a resource capacity limit of 1 so one of the 2 shipments is assigned to Carrier_2.

	Carrier_1	Carrier_2	Carrier_3	Cost Difference (Carrier_2 minus Carrier_1)	Cost Difference (Carrier_3 minus Carrier_2)
Shipment_A	$500	$600	$1000	$100	$400
Shipment_B	$100	$500	$700	$400	$200
Total Cost	$600	$1100	$1700

Option 1:

Shipment_A      Carrier_1:   $500
Shipment_B      Carrier_2:   $500
Total:                       $1000

Option 2: (Least Cost option)

Shipment_A Carrier_2: $600

Shipment_B Carrier_1: $100

Total: $700

Option 2 is the best option since it is least cost. The purpose of this parameter is to get the least total cost across all shipments.

The value of the parameter ranges between 0 and 1. The higher the value, the more significant the first choice carrier is during carrier assignment. The lower the value, the more significant the second choice carrier is during carrier assignment.

Weighted Rank is calculated as follows ( CCWF = Carrier Capacity Weighting Factor): ( CCWF X Cost Difference between Carrier_2 and Carrier_1) + ((1 CCWF) X Cost Difference Between Carrier_3 and Carrier_2)

Note: The system does not consider carriers that are infeasible due to service time or capacity constraints and only considers feasible options.

The following examples use the data in the tables above:

Example 1:

CCWF = 0.7

The weighted rank of Shipment_A = (0.7 X 100) + (0.3 X 400) = 190

The weighted rank of Shipment_B = (0.7 X 400) + (0.3 X 200) = 340

In this example, Shipment_B has a higher weighted rank so it will be assigned a carrier first.

Example 2:

CCWF = 0.3

The weighted rank of Shipment_A = (0.3 X 100) + (0.7 X 400) = 310

The weighted rank of Shipment_B = (0.3 X 400) + (0.7 X 200) = 260

In this example, Shipment_A has a higher Weighted Rank so it will be assigned a carrier first. Oracle Transportation Management sorts all shipments by their weighted ranking and then assigns a carrier one by one.

Exception:

If a shipment specifies an Equipment Group or Service Provider, they will be assigned a carrier resource first.

Rules & Considerations:

1. If there are less than three carrier options for a given shipment, the following rules apply to the rank calculation:

If shipment has one option: rank = MAX rank.
If shipment has 2 options: rank = (option 2 option 1) + MAX/2
If shipment has 3 or more options: rank = (factor) * (option2 option1) + (1 - factor) * (option 3 option 2)

* This assumption assures that shipments with 1 option will always have preference over shipments with 2 options, and that shipments with 2 options will always have preference over shipments with 3 options. If there is a situation where many shipments have two or three options, you can set the factor to 1 so that all shipments are evaluated based on the first two carriers.

If shipment rank is equal, then priority will be given to the cheaper option.

2. The algorithm only uses options that are still feasible when performing this sorting. It should not be using options that have previously been deemed infeasible due to service time or capacity constraints.

For the CARRIER CAPACITY WEIGHTING FACTOR to be used by the rating engine, the Rerate All Shipments After Bulk Plan parameter must be set to true. If set to false, then the CARRIER CAPACITY WEIGHTING FACTOR is NOT used in assigning capacity to shipments during rating.

CARRIER RESOURCE REASSIGNMENT TYPE

Service Provider Assignment

This parameter specifies what happens at the end of the bulk plan process when capacity reaches its limit.

If set to 0, then when the assigned equipment resources are used up, it will re-assign the shipment to the next best available equipment resource. If none are found, then the shipment fails.

If set to 1, then when the assigned equipment resources are used up, it will re-assign the shipment to the next best available equipment resource. If none are found, then it will re-plan the shipment.

If set to 2, then when the assigned equipment resources are used up, it will re-plan the shipment.

CHARTER VOYAGE ARRIVE DATE CHANGE THRESHOLD

Service Time

Specifies the threshold when the arrival date change will impact the next order movements. If you change the arrival date on a charter voyage and the change is within this tolerance then the next order movement will not be adjusted.

CHARTER VOYAGE DEPART DATE CHANGE THRESHOLD

Service Time

Specifies the threshold when the departure date change will impact the previous order movements. If you change the departure date on a charter voyage and the change is within this tolerance then the previous order movement will not be adjusted.

CHECK DRIVER CALENDAR FOR SHIPMENT START ONLY

Fleet Management

23C

This parameter allows you to check a driver calendar against an entire shipment, instead of only checking the start time of the shipment.
Setting the parameter value to False will invoke the functionality whereby the assignment of a shipment to a driver is feasible if the entire duration of the shipment falls within a driver calendar window.
Setting the value to True will mean that the assignment of a shipment to a driver is feasible if the start time of the shipment falls within an open window on the driver calendar even if the shipment end falls outside the driver calendar window.

Default: True

CHECK EQUIPMENT CAPACITY IN REFERENCE UNITS

Bulk Plan

Must be set to TRUE in order for the planning logic to consider Equipment Reference Units.

This parameter should be set to TRUE in all parameter sets.

By default, this parameter is set to FALSE.

CHECK LOCATION CAPACITY

Location Capacity

If this parameter is False, the location capacity constraints are ignored during planning.

CHECK STOP SPECIAL SERVICE IN EQUIPMENT PACKING

Container Optimization

19B

When this parameter is false, the equipment packing will not happen for combination equipment when it is multistop shipments and packing for single equipment remains unchanged.

If the parameter is set to true, the equipment packing for LIFO (last-in-first-out) shipments into combination equipment is invoked. For more details see the Combination Equipment Group for Multistop Shipments section in the Combination Equipment Group.

The default value is false.

CHECK TEMP CONTROL COMPATIBILITY IN BUNDLING

Order Management

6.4.2

Determines if temperature control compatibility on a commodity should be checked during order bundling. The check will be done during container optimization regardless of this setting.

This replaced the property glog.business.consolidation.bulkplan.performTempControlCompatibilityCheckInOrderBundling.
The default is FALSE: do not check in order bundling.

Note: Do not change this parameter unless directed by Support.

CHOOSE EARLIEST FEASIBLE GROUND SCHEDULE

Service Time

19B

This parameter provides flexibility to plan order releases into earliest or latest ground schedule shipments using as late as possible logic. The default is true, so OTM will use the earliest available ground schedule.

CHOOSE ITINERARY BY NUM OF ORDERS

Bulk Plan

If this parameter is set to Y, when Oracle Transportation Management selects the best itinerary during planning, it uses the number of order bundles mapped to this itinerary. Otherwise, Oracle Transportation Management uses the max weight that mapped to this itinerary.

CM AUTO CREATE

Continuous Moves

6.3.3

Set to TRUE to have Oracle Transportation Management automatically look for continuous move opportunities at then end of the bulk plan process.

CM MAX SEARCH DISTANCE

Continuous Moves

6.3.3

Maximum amount of distance between two shipments when the Find and Create Continuous Move business action is searching for potential continuous move shipments. The distance is measured from the last stop of the first shipment to the first stop of the second shipment.

CM MAX SEARCH DURATION

Continuous Moves

6.3.3

Maximum amount of time between two shipments when the Find and Create Continuous Move business action is searching for potential continuous move shipments. The time is measured from the first shipment end time to the second shipment start time.

CM MODE

Continuous Moves

6.3.3

The transportation mode of the continuous move eligible shipments.

CM REDRIVE

Continuous Moves

6.3.3

When set to TRUE, shipments will be recalculated in order to find more continuous move eligible shipments. It will check the latest start time of the next shipment and calculate whether it is equal to or later than the end time of the first shipment plus the drive time.

CO2 EMISSION GRAM PER MILE

FTI Parameters

6.1

Used for tracking carbon dioxide emissions on the green dashboard.

Changes to this parameter are not considered until the server restarts. *

COLLECT SERVICE PROVIDER RESULTS

Bulk Plan

When set to TRUE, bulk plan result metrics are collected by service provider and by mode.

COMPUTE SHIPMENT TIME WINDOW

Service Time

If this is set to true, Oracle Transportation Management drives the shipments twice to get the Earliest Start and the Latest Start.

If this is false, Oracle Transportation Management drives the shipments once and looks to the HOLD AS LATE AS POSSIBLE parameter to determine how to calculate the time window.

To have flexible time windows on multi-stop shipments, you also need to set the property glog.business.consolidation.multistop.computeShipmentTimeWindowsInMultistop to true.

Note: This only applies to build shipment action and when bulk planning a single leg. For other actions, the earliest and latest start times are not computed, only the best start time.

CONNECT SHIPMENT GRAPHS FOR SPLIT ORDERS

Bulk Plan

If set, then during bulk plan process if order releases are split into multiple shipments, the system goes through all the graphs and combines the ones that share the same order releases into one graph. Then it can be saved as one transactional unit.

This replaces the property glog.business.consolidation.bulkplan.connectShipmentGraphsByOrder to provide more flexibility. For example, you can set it for running Load Configuration and not set it for Bulk Plan.

CONSIDER CARRIER CAPACITIES DURING MULTISTOP

Multistop

6.3

This controls the multi-stop behavior with respect to capacities. Set this to true if you want carrier capacity limits to be considered by multi-stop logic. When multi-stop logic considers carrier capacity limits, it will take care not to create too many large shipments when the availability of large equipment is limited.

When set to true, the multi-stop logic configuration parameter "Multistop Cost Saving Check Type" will automatically be internally set to a value of “4.Calculate cost for all paired shipments”. This is required to allow equipment evaluation to occur during multi-stop which is required to evaluate carrier capacities.

This functionality is enabled only when Network Routing is used (when ORDER ROUTING METHOD is set to Network Routing).

The default is false (off).

CONSIDER THIRD PARTY SHIPMENTS FOR ASSIGNMENT

Fleet Management

6.2.2

When set to True, you can use non-fleet shipments when assigning drivers to shipments, and shipments to drivers. Additionally the Optimize Driver Assignment action would also consider non-fleet shipments when this parameter is set to True.

Default: False

CONSIDER VOYAGE SCHEDULES IN CONTAINER OPT

Container Optimization

6.2.1

Determines if container optimization uses voyage schedules. This must be set to TRUE in order for container optimization to use voyage schedules. The default is FALSE.

CONSOL SHIPMENT MATCHING REFNUM QUALIFIER

Shipment Planning

24A

When you define a value for this planning parameter, planning process matches the value of this reference number qualifier of an order release with the value of the same reference number qualifier of consol shipments. If the reference number value of the order release and shipment match, the shipment is considered as valid shipment, and this order is planned for the primary leg.

For example, if the order release OR1 has the reference number qualifier "CONSOL BOOKING REFNUM" with value as "ABC", planning process identifies the consol shipments with reference number qualifier "CONSOL BOOKING REFNUM" having value as "ABC". When the reference number value of the order release and shipments match, these shipments are considered as valid primary leg consol shipments, and the order is planned for primary leg.

CONTINUOUS MOVES CONFIG ID

Continuous Moves

6.3.3

Identifies the continuous moves configuration in use. Default = Continuous Moves Default

CONSOL BOOKED VALUES UPDATED IMMEDIATELY

Shipment Planning

This parameter is used in conjunction with the Shipment action "Book to Buy Consol - Show Options". If set to True, the consol's booked weight and volume will be updated when a shipment's weight and volume are recalculated The default is False.

CONTAINER OPT CONFIG ID

Container Optimization

Use the desired Container Opt Configuration ID you set up in Power Data so the planning logic correctly optimizes containers during loading.

If container optimization related logic parameters are defined both here and in LOGIC CONFIG SET ID parameter; CONTAINER OPT CONFIG ID will overwrite that defined by LOGIC CONFIG SET ID. This is the reverse of 6.2.

CONTAINER OPT SEARCHING WINDOW DAYS

Container Optimization

5.5 CU3

When checking carrier resource limit and usage, this parameter controls the number of days to search for available resources. The default is 3.

COPY SHIPMENT GROUP RULE FLEX FIELDS AUTOMATICALLY

Shipment Planning

6.3.5

Indicates if flex fields defined on the Shipment Group Rule are to be copied onto the Shipment Group automatically. If so, the values are copied automatically to the ship_group table (not the ship_group_d table). This allows you to copy values that are defined on the rule to the appropriate flex field on the Shipment Group table.

The flex fields added to the ship_group_d table can be manually populated. This is useful when the shipment group is modeling a business document, such as like manifest or FCR (Forwarder's Cargo Receipt), and you need to override a field at this level before printing the document but you do not want to change the underlying database entries.

See Shipment Group Rule Details in Bulk Planning.

CR AGGREGATOR IGNORE COMMODITY

Cooperative Route Planning and Execution

When this parameter is true, the CR Aggregator will not aggregate shipments by commodity, and thus will produce lane volume aggregates that do not have any equipment group profile. This can be used when you do not want to separate shipment aggregations by commodity and equipment group profile.

CR AGGREGATOR INCLUDE OUTLIERS FOR CONFIDENCE

Cooperative Route Planning and Execution

When this parameter is true, the CR Aggregator will include outlier lane volume aggregates when computing the CR Forecast statistical data including the confidence factors. However, the outlier lane volume aggregates will still not be included in the computation of the forecasted volume for the CR Forecasts.

CR SOLVER LOOP END RADIUS

Cooperative Route Planning and Execution

This distance is used by the CR Solver to determine when a CR Route should end. If the CR Solver creates a CR Route where a CR Forecast ends within this distance of the start of the first CR Forecast of the route, then the route cannot continue beyond that point (except to return to a depot location if any).

CR SOLVER MUST RETURN TO START

Cooperative Route Planning and Execution

When this parameter is true, if no depot location is specified, the CR Solver will create only CR Routes that return to the start location of the route. (If depot locations are specified, then the CR Solver will end at a depot location as usual.)

CREATE INTEGER AWARDS

Sourcing

5.5 CU4

Indicator variable that describes whether the awards are solved as continuous or as integers.
0: Continuous values. Awards can be fractions but are rounded to 0.
1: Solved as continuous values but reported as integers with a value of 1 or larger.
2: Solved as integers with a value of 1 or larger.

Example of option 1: The solver might find that giving a carrier 11.45% of a lane is the best but it is easier to work with whole numbers so instead the solver will award only integer percentages.

CREATE LOCATION ASSET INVENTORY IN LOCATION DOMAIN

Fleet

6.3.4

Determines where the location asset inventory is created. When the parameter is the default value of false, the location asset inventory will be created in the current domain of the user. If the parameter value is true the location asset inventory will be created in the domain of the location.

CREATE NEW BILL FOR STANDARD APPROVED ADJUST

Settlement

6.2

If this parameter is set to TRUE, then when you run the Bill Adjusted Cost action from a shipment, any changes to the bill will be placed on a new bill if the original invoice was already approved. Default = false.

Note: This is no longer used and will be removed in a future version.

CREATE NEW INVOICE FOR STANDARD APPROVED ADJUST

Settlement

If this parameter is set to TRUE, then when you run the Invoice Adjusted Cost action from a shipment, any changes to the invoice will be placed on a new invoice if the original invoice was already approved. Default = false.

Note: If the glog.invoice.adjustments.createNewInvoiceForAdjustments property is true, then this parameter is ignored and the system checks if the existing invoice is already approved. If approved, it would place the changes on a new invoice.

CREATE PERMANENT SHIP UNITS

Shipment Planning

Indicates whether ship units should be flagged as Permanent on a shipment. Permanent ship units will not be removed when integration is instructed via XML to Replace All Children.

CREATE SHIPMENT GROUPS DURING SHIPMENT BUILDING

Shipment Planning

6.3.5

Indicates whether the shipment building process should create shipment groups or not. See Shipment Groups in Bulk Planning.

CURRENT TIME SHIPMENT STOP REDRIVE CONFIG GID

Service Time

6.1

Identifies the Shipment Stop Redrive Logic Configuration data to be used in determining redrive behavior when current time and current location data is received for a shipment.

DATA CONFIGURATION FOR ORDER BASE LINE PACKING

Order Management

23C

When you run the action, Order Base Line Packing, this parameter allows you to transfer data from Order Base to Order Release and Ship Unit Release Instruction to Ship Unit. You can set the data configuration at the Parameter Value drop-down list.

DATA QUEUES - USE INBOUND DATA QUEUES

Integration

6.0

Specifies whether the data queue should be used to limit the processing of new XML topics.

DATA QUEUES - USE QUEUE FOR TRANSPORT - FTP

Integration

6.0

Specifies whether the data queue should be used to control outbound transport of XML via FTP.

Note: FTP is not supported.

DATA QUEUES - USE QUEUE FOR TRANSPORT - HTTP

Integration

6.0

Specifies whether the data queue should be used to control outbound transport of XML via HTTP.

DATA QUEUES - USE QUEUE FOR TRANSPORT - QUEUE

Integration

6.0

Specifies whether the data queue should be used to control outbound transport of XML via Oracle Advanced Queuing.

Note: Oracle Advanced Queueing (OAQ) is no longer supported and will not function.

DATA QUEUES - USE QUEUE FOR TRANSPORT - SERVICE

Integration

6.0

Specifies whether the data queue should be used to control outbound transport of XML via web services.

DATA QUEUES - USE QUEUES FOR XML BUILD

Integration

6.0

Specifies whether the data queue should be used to control the generation of outbound XML.

DECREASE COMMITMENT USAGE WHEN TENDER DECLINE

Service Provider Assignment

When this parameter is TRUE and a tender is rejected by a carrier, the system will decrease the commitment usage against that carrier.

When the parameter is FALSE and the tender is rejected by a carrier the commitment usage will remain.

The total commitment usage count for all carriers is decreased when a tender is declined, regardless of the value of this parameter.

Note: For a given domain, always track commitments the same way. Do not change this parameter for a domain once you have started counting commitments.

DEFAULT ACTIVITY CODE FOR LOADING

Service Time

6.0

This determines the default activity code for loading. The valid values are: Load, Pickup Empty, and Pickload. These are hard-coded.

DEFAULT ACTIVITY CODE FOR UNLOADING

Service Time

6.0

This determines the default activity code for unloading. The valid values are: Unload, Dropoff Empty, and Drop Loaded. These are hard-coded.

DEFAULT ORDER CONFIG FOR SHIPMENT SHIP UNIT

S Ship Unit Calculation

6.3

This defines the default Order Configuration to be used when an order configuration is not specified.

DEFAULT POWER UNIT FOR LENGTH CALCULATION

Shipment Planning

19B

This allows you to select a tractor from the Power Unit table as the surrogate tractor for purposes of external distance engine information which provides weight and pulling length. This will be used by OTM to calculate the truck length used in external distance engines.

The default is "DEFAULT FOR PLANNING".

This is used in calculation of loaded equipment dimensions for external distance engines.

It is also part of the configuration for Sending Equipment Dimensions to External Distance Engines.

DEFAULT SERVICE PROVIDER FOR FLEET ASSIGNMENT

Fleet Management

6.3

If provided, the value of this parameter will be used as the service provider for the shipment in the scenarios where the driver or driver type do not have a rate offering specified. If this parameter is left with the default value of nothing, then there are no changes to shipment.

DEMURRAGE CONTRACT NUMBER REFNUM QUALIFIER ID

Demurrage Management

6.3

This defines the reference number qualifier corresponding to a contract number for demurrage transaction. The Contract Number Refnum is used in checking compatibility with the Contract Number field on the demurrage rule.

DEFAULT VOYAGE RATE SERVICE ID

Voyage Schedule

23.1

This parameter is configured to define the use of the internal or external voyage type and its related voyage engine to be referred to. By default, the Rate service is DEFAULT_VOYAGE_RATE_SERVICE, which has a Rate service type as VOYAGESCHEDULE.

DIAGNOSTIC PROCESS CONFIGURATION

General

6.0

Allows you to select a default diagnostics configuration.

DOCK SCHEDULING WORKBENCH LAYOUT ID

Action

23A

Specify the enhanced workbench layout to use for the action Manage Appointments. Default is DOCK SCHEDULING WORKBENCH.

DRIVER ASSIGNMENT MAXIMUM INSERTION DEPTH

Fleet Management

6.1

This is used by both the Assign Shipment to Driver and Unassign Shipment from Driver.

Used by Assign Shipment to Driver action to insert a new shipment before existing driver assignment. It indicates the maximum number of driver assignments you can insert before.

Used by Unassign Shipment from Driver to determine how many shipments can be unassigned. If a driver has been assigned shipments s1, s2,s3,...s10 and the parameter is set to 5, then only the last 5 shipments (shipments s6-s10) can be unassigned. If you try to unassign too many shipments, you will get an error "Could not unassign driver from shipment because there are too many driver assignments after this shipment."

DRIVER_ASSIGNMENT_PRIMARY_COST_CATEGORY_SET

Fleet Management

6.1

Used by Driver Assignment, this set will be passed to the rating engine. During the rating process, only rate categories whose categories are contained in the specific set will be evaluated. The results will be sorted to total weighted cost and the best option assigned.

DRIVER_ASSIGNMENT_SECONDARY_COST_CATEGORY_SET

Fleet Management

6.1

Used by Driver Assignment when comparing up to three cost category sets.

DRIVER_ASSIGNMENT_TERTIARY_COST_CATEGORY_SET

Fleet Management

6.1

Used by Driver Assignment when comparing up to three cost category sets.

DRIVER ASSIGNMENT RULE SET

Order Capture

6.0

Driver assignment rule set.

DYNAMIC PROGRAMMING MAX RECURSION DEPTH

Container Optimization

5.5 CU3

This parameter controls the long running execution of Enumerative algorithm. The default is 99999. If you face an issue with performance, you can lower this number. If the recursion depth exceeds, the algorithm will stop and revert to the QUICKPACKING ALGORITHM. This is only applicable for the Enumerative Algorithm.

DYNAMIC PROGRAMMING TIME OUT LIMIT

Container Optimization

5.5 CU3

This is a timer control to ensure that the Enumerative algorithm does not run for ever. This is a preferred control over DYNAMIC PROGRAMMING MAX RECURSION DEPTH parameter. This control should be used first. If it does not work, then use the DYNAMIC PROGRAMMING MAX RECURSION DEPTH parameter. If the algorithm times out, it will revert to QUICK PACKING ALGORITHM. Only applicable for Enumerative Algorithm. The default is 180 seconds.

DYNPOL DIRECT ENCOURAGEMENT FACTOR

Multi-tier

The higher the value, the more order releases that are encouraged to go direct. A number below 1.0 discourages direct shipments and a number above 1.0 encourages direct shipments. A value of 0 causes the system to select only orders that can go direct. A high value, such as 100, causes OTM to send every order direct than can go direct.

See also Bulk Plan Cost Based Routing.

DYNPOL DIRECT PRORATING FACTOR

Multi-tier

The default is 0.75. It represents the expected utilization of the typical direct TL shipment using the largest typically available equipment. For example, the default of 0.75 means that the typical direct TL shipments fill 75% of the largest typically available equipment. This amount is used to estimate the TL cost for an individual order bundle. The value for this parameter should be between 0 and 1.0, although a very small value is somewhat meaningless.

See also Bulk Plan Cost Based Routing.

DYNPOL DISTANCE MODE

Multi-tier

The default is "TL". This parameter indicates which rate transport mode represents the typical distance-based rate for a large truckload shipment.

See also Bulk Plan Cost Based Routing.

DYNPOL MAX CAPACITY VOLUME

Multi-tier

6.2

This parameter represents the volume capacity of the largest equipment that is typically available. If the parameter is set to NULL, the logic checks for the largest equipment available on each order bundle's lane.

See also Bulk Plan Cost Based Routing.

DYNPOL MAX CAPACITY WEIGHT

Multi-tier

This parameter represents the weight capacity of the largest equipment that is typically available. If the parameter is set to NULL, the logic checks for the largest equipment available on each order bundle's lane.

See also Bulk Plan Cost Based Routing.

DYNPOL MAX POOL CAPACITY VOLUME

Multi-tier

6.2

This parameter is the same as DYNPOL MAX CAPACITY VOLUME except that it overrides the other only for prorated cost calculations for shipments going into a pool.

See also Bulk Plan Cost Based Routing.

DYNPOL MAX POOL CAPACITY WEIGHT

Multi-tier

This parameter is the same as DYNPOL MAX CAPACITY WEIGHT except that it overrides the other only for prorated cost calculations for shipments going into a pool.

See also Bulk Plan Cost Based Routing.

DYNPOL MULTISTOP LINEHAULS TO POOL

Multi-tier

6.2.5

If set to true, the dynamic pool selection logic can create linehauls that deliver to multiple deconsolidation pool locations. The logic will still try to consolidate linehauls going to the same pool location before consolidating linehauls going to different pools locations.

See also Bulk Plan Cost Based Routing.

DYNPOL PERFORM MULTIPOOL OPTIMIZATION

Multi-tier

6.2

This parameter enables dynamic pooling multi-pool optimization. This step occurs at the end of dynamic pooling logic, and uses the multi-stop consolidation column generation algorithm. In this step, all of the intermediate shipments and pool selections considered during the dynamic pooling logic are reconsidered to obtain a final set of multi-stop shipments and pool selections. Enabling this step allows the logic to improve solution quality, at the cost of some additional run-time.

This should be used only when the parameter MULTISTOP CONSOLIDATION ALGORITHM TYPE is set to "3. Column Generation".

The default is false (off).

See also Bulk Plan Cost Based Routing.

DYNPOL POOL PRORATING FACTOR

Multi-tier

The default is 0.75. It represents the expected utilization of the typical linehaul-into-pool TL shipment using the largest typically available equipment. For example the default of 0.75 means that the typical linehaul-into-pool TL shipments fill 75% of the largest typically available equipment. This amount is used to estimate the TL cost for an individual order bundle. The value for this parameter should be between 0 and 1.0, although a very small value is somewhat meaningless.

See also Bulk Plan Cost Based Routing.

DYNPOL SKIP FAVORITE POOL STEP

Multi-tier

If set to True, the system will not select pools for order bundles based upon their favorite pools.

DYNPOL SKIP MULTISTOPS DIRECT STEP

Multi-tier

If set to True the system will not select order bundles for direct shipments before selecting which pool the order bundles will go through.

See also Bulk Plan Cost Based Routing.

EQUIPMENT ASSIGNMENT RULE SET

Order Capture

6.0

Equipment assignment rule set.

EQUIPMENT REFERENCE UNIT FOR UTILIZATION

22A

This parameter defines which Equipment Reference Units (ERU) is used for the utilization calculation. The ERU utilization logic is as follows:

If there is a rounding ERU on the shipment, this rounding ERU is used for the ERU utilization calculation.
If a shipment contains an ERU that is defined by the planning parameter EQUIPMENT REFERENCE UNIT FOR UTILIZATION, this ERU is used for the ERU utilization calculation.
If shipment does not contain an ERU that is defined by the planning parameter EQUIPMENT REFERENCE UNIT FOR UTILIZATION, the sum of the ERU utilization will be used for the ERU utilization calculation.

ETA SHIPMENT STOP REDRIVE CONFIG GID

Service Time

6.1

Identifies the Shipment Stop Redrive Logic Configuration data to be used in determining redrive behavior when ETA data is received for a shipment stop.

EVALUATE SPA FOR SHIPMENTS FROM SPLIT ORDERS

Service Provider Assignment

6.1

Indicates whether to enforce Service Provider Assignment (SPA) rules for shipment from split order (order release/order movement).

See also "Plan Shipments with Carrier Commitment" parameter.

If set to false, shipments with split orders will not go through service provider assignment logic (same as prior to 6.1). The default is true.

FAIL ON FATAL RATING EXCEPTION

Exception Handling

6.4.2

If set to TRUE, when the rating engine encounters an internal error which is deemed to be catastrophic, the rating engine will immediately fail with the error: RECatastrophicException. All planning processes (build shipment, bulk plan, etc.) will fail and shut down immediately.

Note: Currently, this exception occurs only when unable to connect to the external rating engines such as SMC, SMC with Carrier Connect, RatewareXL, and RatewareXLCarrierConnection.

The default is FALSE meaning the rating engine will behave normally.

FALLBACK RATE RECORD FOR SPOT BID SPOT RATE

Collaboration

23C

While awarding a spot bid based on a spot rate for a shipment from the Award Bid screen or View All Bid Options screen, the spot rate is created based on the rate record on the shipment. When the shipment does not have the rate record on it, this parameter value is used to create the spot rate.

The parameter value is set as Default. To use this parameter, choose the appropriate rate record for the parameter value.

FALLBACK RS NUM OF DAYS

Rates

6.3.6

The fallback rate service is used for driving the shipment if the regular rate service is unable to drive the shipment. For example, you have voyage information for two months but a possible shipment came in for three months in the future.

This parameter is used to decide how far in the future to start using the fallback rate service. If a rate offering attributes tab has a fallback rate service, and if the order (order release/order movement) early pick up time minus the current time is greater than or equal to the value for this parameter, then OTM will use the fallback rate service. The default value is 90 days, meaning the rate inquiry shipment needs to be 90 plus days into the future before the FALLBACK Rate Service will be considered.

Note: Bulk plan is not affected by this parameter.

FAVOR HIGH DEFICIT SERVICE PROVIDER IN TRANS OPT

Service Provider Assignment

When this parameter is TRUE the Build Shipments actions (Build on Primary Leg, Direct, and Multistop) will select a carrier that has the most deficits.

When this parameter is FALSE the system selects a carrier that has a deficit but will assign the least cost carrier amongst all the deficit carriers.

Note: Bulk plan is not affected by this parameter.

FEDEX CHARGE TOKEN SET

Rates

23C

Select the required FedEx charge token set. To define a FedEx charge token set, see Charge Token Set. The default value is DEFAULT_FEDEX_CTSET.

FETCH DIGITAL FREIGHT RATES

Collaboration

24C

When you set this parameter to true and if there is any digital freight rate offering while running the spot bid tender action, OTM fetches the digital freight cost and adds it as bid amount on the Spot Bid Tender Response screen for all selected digital freight carriers. Default: false.

FIELD NAME FOR SSU ACTUAL RECEIVED

Shipment Actual

19C

Set this parameter to a field in the S_SHIP_UNIT table. That field will then be used when running the Remove Planned S Ship Units and Shipment Actual Processing agent actions.

FIELD VALUE FOR SSU ACTUAL RECEIVED

Shipment Actual

19C

Set this parameter to a value found in the field in the S_SHIP_UNIT table that you specified in the FIELD NAME FOR SSU ACTUAL RECEIVED parameter. That value will then be used when running the Remove Planned S Ship Units and Shipment Actual Processing agent actions.

FIND DEMURRAGE RULE SET

Demurrage Management

6.3

This parameter finds the demurrage rule for a demurrage transaction while calculating the charges. This rule set contains the following rules:

Demurrage Equipment Group Profile Rule
Demurrage Flex Commodity Profile Rule
Demurrage Start Event SCAC Code Rule
Demurrage Start Event Region Rule
Demurrage End Event SCAC Code Rule
Demurrage End Event Region Rule
Demurrage Contract No Rule (Contract Rule)
Demurrage Involved Party Rule (Shipper/Consignee Rule)

FIND FLIGHTS BACKWARDS

Service Time

This enables OTM to find the latest possible flight prior to a declined flight. Downstream shipments will be re-driven, upstream shipments will not be re-driven. If an upstream shipment arrive time is later than the new flight, OTM will set that shipment to TIME_INFEASIBLE.

If there is a Max Wait time defined on the rate service, it may prevent assigning an earlier flight to an air shipment.

FIND FLIGHTS NUM OF DAYS AFTER CURRENT ARRIVAL

Service Time

When you attempt to change a flight on a shipment, this value indicates the number of days after the flight's current scheduled arrival for which available flights will be displayed.

FIND FLIGHTS NUM OF DAYS BEFORE CURRENT DEPARTURE

Service Time

When you attempt to change a flight on a shipment, this value indicates the number of days prior to the flight's current scheduled departure for which available flights will be displayed.

FIND ITINERARY RULE SET

General

5.5 CU4

Configures the default itinerary rule set.

FIND RATE OFFERING RULE SET

General

5.5 CU4

Configures the default rate offering rule set.

FIND RATE RECORD RULE SET

General

5.5 CU4

Configures the default rate record rule set.

FLEET AWARE BULK PLAN

Fleet Management

6.4

When set to true, it will allow the creation of any work assignments in a bulk plan. Fleet Aware Bulk Planning works only with Network Routing Flow. (i.e. the ORDER ROUTING METHOD parameter is set to Network Routing). See Fleet and Bulk Planning.

FLEET CHECK DRIVER FEASIBILITY ADVANCED

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the later phase of Driver Assignment action.

FLEET CHECK DRIVER FEASIBILITY BASIC

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the initial phase of Driver Assignment action.

FLEET CHECK DRIVER FEASIBILITY DEFAULT

Fleet Management

6.0

Points to the rule-set consisting of all rules related to the driver that would be checked during Check Shipment Feasibility action.

FLEET CHECK EQUIPMENT FEASIBILITY ADVANCED

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the later phase of Equipment Assignment action.

FLEET CHECK EQUIPMENT FEASIBILITY BASIC

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the initial phase of Equipment Assignment action.

FLEET CHECK EQUIPMENT FEASIBILITY DEFAULT

Fleet Management

6.0

Points to the rule-set consisting of all rules related to the equipment that would be checked during Check Shipment Feasibility action.

FLEET CHECK EQUIPMENT TYPE FEASIBILITY ADVANCED

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the later phase of Equipment Assignment action.

FLEET CHECK EQUIPMENT TYPE FEASIBILITY BASIC

Fleet Management

6.0

Points to the rule-set consisting of all rules that would be checked during the initial phase of Equipment Type Assignment action.

FLEET CHECK EQUIPMENT TYPE FEASIBILITY DEFAULT

Fleet Management

6.0

Points to the rule-set consisting of all rules related to the equipment type that would be checked during Check Shipment Feasibility action.

FLEET CHECK POWERUNIT FEASIBILITY DEFAULT

Fleet Management

6.3.2

Points to the rule-set consisting of all rules related to the Power Unit Assignment action. The default value is PowerUnitCompatibilityDefault.

FLEET DEFAULT DRIVER SAVED QUERY ID

Fleet Management

6.1

Used as the default saved query ID by Assign Driver to Shipment Best Option/Show Options action

FLEET DEFAULT EQUIPMENT SAVED QUERY ID

Fleet Management

6.1

Used as the default saved query ID by Assign Equipment to Shipment Best Option/Show Options action.

FLEET DEFAULT EQUIPMENT TYPE SAVED QUERY ID

Fleet Management

6.1

Used as the default saved query ID by Assign Equipment Type to Shipment Best Option/Show Options action.

FLEET DEFAULT SERVPROV PROFILE ID

Fleet Management

6.3

This parameter is used to determine the default service provider profile while Assigning Backhaul Shipments. Default value is null.

If you set this to a service provider profile, the shipments will be filtered based on the service provider on the service provider profile on the Assign Backhaul Shipment: Show Options page.

FLEET DEFAULT SHIPMENT SAVED QUERY ID

Fleet Management

6.1

Used as the default saved query ID by Assign Shipment to Driver Best Option/Show Options action.

FLEET EQUIPMENT CONFIG ID

Fleet Management

6.1

Use this parameter to specify which FLEET EQUIPMENT logic configuration ID you want to use.

FLEET IGNORE SUBSTITUTABILITY FOR MULTI EQUIP

Fleet Management

6.3.2

When set to False, equipment types can be substituted for with other equipment that are in the same equipment profile. No substitution of multi-equipment is permitted when this parameter is set to True.

Default-False.

FLEET OPTIMIZATION CONFIG ID

Fleet Management

6.1

This is the load configuration ID for the fleet bulk plan process that contains all the logic parameters.

FLEET REDRIVE FREIGHT SHIPMENTS

Fleet Management

6.0

Redrive the freight dependent shipments during assignment and unassignment. The relationship between parent shipment and downstream shipments can be either freight related or driver related. When this parameter is FALSE, business freight dependent downstream shipments are not redriven, but driver related downstream shipments are.

FULL SHIPMENT CAPACITY PERCENTAGE THRESHOLD

Shipment Planning

Indicates full shipment capacity percentage threshold used in the multi-stop algorithm. Shipments exceeding this value are not considered for multi-stop optimization.

GENERIC ESTIMATION RATE SERVICE ID

Bulk Plan

Contains the rate service ID that estimates the time from consolidation pool to destination, so we can calculate the time window at the consolidation pool to allow bundling to the consolidation pool.

Cross-dock to destination transit time estimation also uses this.

GENERATE PLANNING TASK MODEL FILES

Bulk Plan

19B

Indicates whether to generate planning task model file names during bulk plan. The default is False, so no planning task model files are generated, (otherwise there could be a lot). These files can be useful for support to research optimization issues.

GET THE DRIVER HOME

Fleet Management

6.3

If this parameter is included in the parameter set, the driver's home will be added as the last stop on a shipment. This setting can be overridden by criteria on the Assign Driver and Assign Shipment to Driver actions.

Default is false.

GET TIME ZONE FROM PLANFROM AND PLANTO LOCATIONS

Bulk Plan

When set to False, Oracle Transportation Management considers early/late pickup/delivery dates to be in the time zones of the source and destination locations, even if Plan From and/or Plan To locations are used.

Default is true.

GTM EBS INTEGRATION CONFIG ID

GTM EBS Integration

6.4.3

This parameter allows you to select the logic configuration that governs EBS-GTM integration functionality.

Default is GTM EBS INTEGRATION DEFAULT.

GTM LOGIC CONFIGURATION

GTM

21A

This parameter allows you to select the general logic configuration for GTM.

Default is GTM LOGIC CONFIGURATION DEFAULT.

HOLD AS LATE AS POSSIBLE

Service Time

If this parameter is true, then the latest departure is equal to the earliest of the late pickup dates of the orders (order release/order movement) on a shipment. The start time of the shipment is adjusted backwards from the latest departure until a feasible start time is found.

If this parameter is false, then the earliest departure is equal to the latest of the early pickup dates of the orders on a shipment. The start time of the shipment is adjusted forwards from the earliest departure until a feasible start time is found.

Redrive does not work well if using this parameter and the parameter "PLAN SHIPMENTS WITH CARRIER COMMITMENT", and you have multi-leg shipments. Redrive may redrives some shipments early. The property glog.business.serviceprovider.redriveShipments can prevent service provider assignment logic from redriving the shipment graphs of multi-leg shipments.

IGNORE ACTUAL TIMES DURING ADD OR UNASSIGN ORDER

Shipment Management

6.2.6

Set this parameter to true if you wish to add or unassign an order release from an existing shipment which has Actual Departure set on its first pickup stop. The default is false.

IGNORE ORDER MOVEMENT OPERATIONAL DATES

Multi-tier

6.2

This should be set to true if you are not concerned with order movements, and false if you are using order movements. When it is true, OTM will not use or compute the operational early pickup and late delivery windows. The default is True.

Note: This must be set to 'False' if you are using order movements.

This was a property in 6.1.

IGNORE SAW CAPACITY AND COMMITMENT

Shipment Planning

5.5 CU4

Allows you to specify whether shipment as work (SAW) shipments should use capacity and carrier commitment resources or not.

If set to true, SAW shipments will not go through the capacity and carrier commitment logic when being uploaded. No capacity or carrier commitment usage will be assigned or modified. If there is no capacity or carrier commitment, the SAW shipment will not be affected and will still be assigned the correct service provider and rated appropriately.

The default is FALSE, "do not ignore".

IGNORE SERVPROV FLEET CHECK

Shipment Planning

21A

If you set this parameter to true, OTM will ignore the fleet check for service provider for the Insert/Remove Non-Freight Related (NFR) Stop actions.

The default value is false.

INBOUND ORDER TYPES

General

6.2

Use this parameter to classify an order release as Inbound. By associating one or more Order Release Types this parameter, you control which order releases are inbound. The direction of the order release is used by the Map Order Release Shipment Routes action. If an order release is associated with both parameters, it will be considered Outbound. This supports a single value.

INCLUDE CLOSED CONSOL FOR SHOW OPTIONS

Shipment Planning

6.2.8

Use this parameter to designate whether or not a shipment used during the build shipment on primary leg when set to True. When set to False, the BOOKING_CLOSED consol is not returned.

Default = True.

INCLUDE TIHI THUS ON PACKAGE ITEM IN THU PROFILE

Ship Unit Building

21C

If you set this parameter to true and neither Transport Handling Unit (THU) nor THU profile is specified on the order release line then the system dynamically includes TiHi THUs of the packaged item into the THU Profile during the ship unit building process.

The default value is false.

INSTANCE COMPLETION DISCOUNT PERCENT

Cooperative Route Planning and Execution

5.5 CU4

The costing of each option within the algorithm reduces the cost of any option which represents a fully utilized route instance.

This parameter influences the amount of cost reduction that is given to options that complete an instance. The default is 10.0. The maximum value is 100.

This reduces the cost of any option that represents a fully utilized route instance by 10% within the cooperative routing optimizer.

Note: Setting this to a negative value gives priority to leaving instances incomplete, instead of trying to complete them.

INTERLINE FLIGHTS ALLOWED

Service Time

6.2.8

This parameter controls the use of code sharing for interim airline flights. A flight is considered a valid flight option for a service provider if the service provider is involved in at least one of the interim flights. The service provider must be on all of the interim flights for that flight to be valid. When set to true, the order (order release/order movement) will be planned as expected. When set to false, the order will fail to plan.

Default = FALSE.

INVOICE SPLIT RULE

Settlement

6.3.7

Allows you to set a default parameter for splitting an invoice. When a split rule is not provided on the 'Generate Invoice' agent, 'Create Invoice' action or Generate all Auto Pay Invoices process, OTM considers this parameter. Based on the value provided in this parameter, OTM splits and generates multiple invoices. If the parameter is NULL (the default), OTM creates a single invoice.

JOB CONSOLIDATION TYPE

Brokerage and Forwarding

The selected consolidation type will be placed on the job created by the Book with Internal NVOCC action.

KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN

Shipment Planning

23A

When set to TRUE, this parameter allows you to retain the current service provider on the remaining shipments after performing the unassign orders/unassign order movements actions.

Default: FALSE

KEWILL CHARGE TOKEN SET

Note: BluJay Solutions Parcel (formerly Kewill Flagship Parcel Rates) is not supported.

Rates

6.3.7

Selects the required Kewill charge token set. To define a Kewill charge token set, see Charge Token Set. The default value is DEFAULT_KCTSET.

LOAD CONFIG ENGINE TYPE

Container Optimization

This determines the engine type used for load configuration. The valid values are: Pattern Based, Pattern Based Optimize, Volume Estimation, and No Load Config. Along with this parameter, the parameter LOAD CONFIG VOLUME THRESHOLD needs to be set to at least a small value for ANY load configuration engine to be used. If not, load configuration is skipped.

To use 3D placement load configuration, you need to set this parameter to No Load Config. Then set Use 3D Based Load Config to true on the Logic Configuration - Container Optimization page.

LOAD CONFIG STACKING HEIGHT DIFF TOLERANCE

Container Optimization

Note: This is no longer used.

LOAD POINT PENALTY SCALING FACTOR

Container Optimization

24B

This parameter allows you to control the trade-off between Load Point Penalty and Shipment Cost when Container Optimization logic is consolidating orders with different load points (See USE LOAD POINT PENALTIES IN PACKING). The higher this scaling factor, the more important the load point penalties are when compared to shipment cost. However, even when the penalties are small compared with shipment cost, the Container Optimization logic will still try to consolidate orders in a way that will minimize the load point penalties. This scaling factor is used to compare different consolidations. The default value is 1.0.

LOCATION ALIAS SHIPMENT SAVED QUERY ID

Conditional Booking

6.3.7

Location alias can be used to help find the location ID, if the location ID is not provided by the service provider. The default is LOCATION ALIAS DEFAULT.

LOCATION CAPACITY OPTIMIZER MAX RUNTIME

Location Capacity

The maximum run time of the optimization process in the bulk plan. Setting this parameter overrides the value of the Problem Timeout field on the planning task.

LOCATION CAPACITY OPTIMIZER PERCENTAGE TOLERANCE

Location Capacity

The logic looks at the tolerance percentage; for example, x% means that the final solution chosen would at most x% away from the optimal. Setting this parameter overrides the value of the Problem Optimality %field on the planning task.

LOCATION CAPACITY OPTIMIZER TIME SPAN

Location Capacity

This is the time span or horizon for which different shipment start times are tried. It is only used if the Check Location Capacity parameter is set to TRUE and the Use Greedy Capacity Assignment Algorithm is set to false.

LOCATION CAPACITY OPTIMIZER TIME STEP

Location Capacity

This is the time step durations between each shipment start time trials. It is only used if the Check Location Capacity parameter is set to TRUE and the Use Greedy Capacity Assignment Algorithm is set to false.

LOCATION CAPACITY SHIPMENT GRAPH SORT CRITERIA

Location Capacity

18D

This parameter determines how the shipment collection is sorted when using the greedy capacity assignment algorithm (only enabled when USE GREEDY CAPACITY ASSIGNMENT ALGORITHM is true ). The prior shipment gets the right to occupy the location capacity first. Valid values are {0: Priority, 1: Late Delivery Date The default is '0:Priority'.

LOGIC CONFIG SET ID

Container Optimization

6.2

With this parameter, you are able to specify a Logic Configuration Set and the Container Optimization logic will run using the specifications in each set, and return the best result.

If container optimization related logic parameters are defined in both in the CONTAINER OPT CONFIG ID parameter and here; CONTAINER OPT CONFIG ID will overwrite that defined by LOGIC CONFIG SET ID. This is the reverse of 6.2.

LTL SPLIT CAPACITY TYPE

Bulk Plan

5.5 CU4

The Split Capacity Type for LTL (less-than-truckload) split functionality is specified in this parameter. The default value is VOLUME.

With LTL splitting, the order releases are split and combined with other orders to achieve higher equipment utilization.

See the following in the Order Management Guide: Order Configuration and Order Modification Workflow.

LTL SPLIT ONLY USE EQUIPMENT ON SHIPMENTS

Bulk Plan

5.5 CU3

When set to TRUE, the system only considers the equipment on the From and To shipment for the LTL split. See also the Solution Improvement Configuration topic.

LTL SPLIT PACKING METHOD

Bulk Plan

5.5 CU3

Controls which packing algorithm to use while packing equipment for an LTL split.

1. Dynamic Programming

2. Quick Packing

If you enter a number other than the ones listed here, the system acts as if you had entered a 1. See also the Solution Improvement Configuration topic.

MANUAL VAT ROUNDING ADJUSTMENT ON

Settlement

Enables acceptable rounding errors to be adjusted.

MANUAL VAT ROUNDING THRESHOLD

Settlement

Allows configuring an acceptable rounding error threshold for validation.

MAPS CONFIG ID

Maps Management

6.3

Specifies which map logic configuration to use.

MARK DRIVER HOME STOP FIXED

Fleet Management

6.4.3

This parameter is used by the Assign Driver (to Shipment) and Assign Shipment (to Driver) actions. The Optimize driver assignment action uses the MARK DRIVER HOME STOP FIXED logic configuration parameter instead of this parameter.

If set to No, the return home stop is not marked as permanent for the driver's current assignment and also the "Stop_Not_Removable" special service is not set on the home stop. So the next assignment for the driver will start from the last freight stop of the current assignment.

If set to Yes, the return home stop is marked as permanent for the driver's current assignment and also the "Stop_Not_Removable" special service is set on the home stop. So the next assignment for the driver will start from the home location.

If set to "Based on Driver Shift", the "Stop_Not_Removable" special service is set on the home stop, but the permanent flag is not set on the stop. The state of the special service and permanent flag is used as an indicator for the logic to decide whether to remove the home stop based on the driver shifts or not during the next assignment. If the next assignment for the driver falls on the same shift as the current assignment, then the home stop will be removed. For the next assignment, the driver will start from the last freight stop of the current assignment. But, if the next assignment for the driver falls on the next shift or outside the current shift, then the home stop is not removed from the current assignment. The driver will go home after the current assignment and start from the home location for the next assignment.

The values for this parameter are effective only if the parameter "Get the Driver Home" is set to true. Otherwise it always uses the default approach (default value is No).

MATCH DEMURRAGE TRANSACTION EQUIPMENT FIELDS

Demurrage Management

6.3

This enables you to select how you want tracking events to match with demurrage transactions. This parameter is used for both Match Demurrage Transaction and Create/Update Demurrage Transaction agent actions.

The following values are possible:

EQUIPMENT INITIAL NUMBER (default)

EQUIPMENT ID

EQUIPMENT REFNUM QUALIFIER AND VALUE

MATCH DEMURRAGE TRANSACTION LOCATION FIELDS

Demurrage Management

6.3

The locations for the actual placement and constructive placement may not always be the same. If the parameter 'Use as Demurrage Location' on Create/Update Demurrage Transaction agent action or if the parameter 'Match Demurrage Transaction Location with' on the Match Demurrage Transaction agent action, has the value 'Event Car Destination Location', these fields come from Event Destination Location fields of the tracking event. If the parameter value is 'Event Location', then these fields come from Event Location fields on the tracking event.

The following values are possible:

CITY/STATE/COUNTRY (default)

LOCATION ID

SPLC

MATCH DEMURRAGE TRANSACTION SCAC FIELDS

Demurrage Management

6.3

The following values are possible:

RAILROAD REPORTING SCAC (default)

SERVICE PROVIDER ALIAS AND VALUE

MAX BUNDLE OVERLAP TOLERANCE

Bulk Plan

Use this parameter to encourage bundling. This parameter extends the order releases/order movements time windows on both sides before computing their overlaps during bundling.

MAX SEARCH RADIUS DISTANCE

Order Management

6.3

When running the Move Order to (Existing) Shipment action, this parameter specifies the radial search distance to find available shipments. If the parameter is not set, the default value used by the action is 100 miles.

MAXIMUM NUMBER OF COMPARTMENTS PER BUNDLE

Bulk Plan

A numeric value for the maximum number of compartments Oracle Transportation Management plans in a single order bundle.

MAXIMUM VOLUME PER BUNDLE

Order Management

A numeric value for the maximum volume for order release/order movement Oracle Transportation Management uses for a single bundle.

MAXIMUM WEIGHT PER BUNDLE

Order Management

A numeric value for the highest weight for order release/order movement allowed for a single order bundle.

MAX NUMBER OF PRIORITIES

Bulk Plan

6.3.1

This is used to slot the orders (order release/order movement) into the respective priority groups. The default is 1000.

See NUMBER OF PRIORITY GROUPS parameter to see how the two work together.

MAX NUMBER OF RATE RECORDS FOR SPLIT ORDER

Shipment Planning

5.5 CU4

This parameter is checked only if "Allow Different Rate Records For Split Orders" parameter is true. If this parameter is set to 3, it means Oracle Transportation Management allows different rate records but limits the number to only 3 (3 cheapest ones). The two settings below mean the same thing:
1. Allow Different Rate Records For Split Orders = false
2. Allow Different Rate Records For Split Orders = true and Max Number Of Rate Records For Split Order = 1

The default is 3.

Note: If this parameter is greater than the default of 3, and the parameter ALLOW DIFFERENT RATE RECORDS FOR SPLIT ORDERS is true, the shipment building logic may create a huge number of shipment options, filling up memory. The property glog.business.itinerary.maxSplitOptions defines the maximum split options allowed. Above this value, order planning will fail.

MAX NUMBER OF RETENDERS

Collaboration

21A

The maximum number of times to retry tendering a shipment. When you run the Secure Resources or Tender Shipment action, this parameter is checked for how many attempts remain to re-tender the offer. If you set this parameter for a shipment, OTM considers the maximum number of retender value set on this parameter.

If this parameter is not set for a shipment, OTM considers the MAX_NUM_RETENDERS workflow parameter and retenders three times which is the default value of this workflow parameter.

MAX NUM DAYS TO EXTEND PATH WITH GS SHIPMENTS

23C

MAX NUM DAYS TO TRY SERVICE TIME ESTIMATION

Service Time

Oracle Transportation Management evaluates service time for each individual leg (before evaluating all legs together), and exclude options that would never be feasible. This helps multi-leg scenarios because it excludes will obviously not work BEFORE those are evaluated in the large matrix of shipping combinations.

The system evaluates service time for each individual leg (before evaluating all legs together), and exclude options that would never be feasible. This helps multi-leg scenarios because it excludes options that will obviously not work BEFORE those options are evaluated in the large matrix of shipping combinations. The system also uses the minimum transit time from the previous leg when estimating the end time of the next leg (instead of average transit time). This logic is controlled by the properties file: glog.business.shipment.estimateServiceTime = TRUE and should only be used in multi-leg planning scenarios.

This parameter indicates the maximum number of days out to run the service time estimation (to prevent estimating orders (order releases/order movements) that are certain to be feasible).

MAX NUM OF ITINERARIES ALLOWED

Bulk Plan

6.3

Limits the number of itineraries allowed. When the itineraries from the search is over this limit, the rate inquiry will not process successfully and you will get an error message.

Default is 200.

MAX NUM OF ITINERARY LOCATION COMBINATIONS

Bulk Plan

A numeric value for the largest number of locations that Oracle Transportation Management can use when planning multi-leg shipments. Shipments that travel over large areas may have hundreds or thousands of possible solutions. Entering a value limits the number of solutions.

See Bulk Plan Tuning Direct Shipment Building for more details.

MAX NUM REPLAN

Bulk Plan

Specifies the number of times re-planning is permitted when failures occur during the bulk plan process.

MAX NUM SHIPMENTS TRIED WHEN INSERT ORDER

Shipment Planning

This is the maximum number of shipments Oracle Transportation Management evaluates when you try to insert an order release on a shipment using the Insert Order agent action.

MAX REDRIVE COUNT

Service Time

6.0

This controls the number of redrives for the simulation drive routing. The time step amount is determined by looking at all the constraints from the previous drive (order windows, location windows, rush hour windows, capacity constraint windows, driver calendars, etc.) and determining the amount of time by which each stop's arrival and departure times hit or miss each of the windows. Maximum wait time is also considered. The smallest of the hits or misses is used for the time step amount. If a feasible solution is not found by this number of redrives, the algorithm will stop. This only applies for LOOKUP, EXTERNAL DRIVE and SIMULATION rate service types.

MILESTONE ERROR SEVERITY

Bulk Plan

Determines the minimum severity of bulk plan milestone errors for database collection. Bulk plan milestone errors are collected if the severity is at least the value you specify here. Values are: WARNING, ERROR, EXCEPTION, and NONE.

MIN BUNDLING TIME WINDOW

Order Management

6.2

The minimum time window overlap allowable in bundling.

MIN BUNDLING TIME WINDOW AFTER CURRENT TIME

Order Management

When building a shipment, the early pickup date/time on the order (order release/order movement) is used by default. If the early pickup date/time is not valued, OTM will use the current time. Current time by itself will not work if the shipment start time is in the past by the time you tender the shipment to a carrier. To handle this issue, use this parameter to take current time + the value of this parameter to use as the planned start time of a shipment. For instance if the value was 2 hours and you run build shipments at 3:45 p.m., the planned start time of the shipment would be 5:45 p.m.

If the order release has no early pickup value, this parameter should be populated. Setting this to 1 hour is good. Otherwise, in show network routing options - ocean, the few seconds between when the options are generated and when one is selected causes a service time infeasibility, because the OTM will think that the shipments are a few seconds too late.

Note: Both MIN BUNDLING TIME WINDOW AFTER CURRENT TIME and NUM OF SHIFTS PER DAY parameters are overridden by the planning day settings.

MIN BUNDLING TIME WINDOW FOR PLANNING

Order Management

6.4.2

This controls order release and order movement bundling.

When this is set to 0 (the default), order bundling can bundle order releases which have any time window overlap, and can bundle order movements that have identical time windows. Note that, under this setting, order movement bundling is much more restrictive than order release bundling with respect to time window overlap.

When this is set to a non-zero duration, then either order releases or order movements can bundle if the resulting bundle pickup and delivery early/late time windows are each at least as long as specified duration. Also, order releases or order movements with identical pickup and delivery windows can bundle together even if these windows are shorter than the specified duration.

In the following example, for simplicity's sake, let's assume that the delivery windows are wide open, and we'll only look at the pickup windows.

OM1 has pickup window 02:00 to 08:00, and
OM2 has pickup window 04:00 to 09:00.

If OM1 and OM2 bundle together, the resulting bundle would have pickup window 04:00 to 08:00 (4 hours long). If the new parameter is set to 4 hours or less, this bundle would be allowed. If it is set to more than 4 hours, the bundle would not be allowed, and the two order movements would plan as separate bundles. However, if OM3 and OM4 both have pickup window 10:00 to 10:05, these can bundle regardless of the parameter setting, because their windows are identical.

MINIMIZE WAIT TIME AT DECONSOL POOLS

Service Time

5.5 CU4

Gives you control over whether to minimize the wait time at a deconsolidation pool. With this set to FALSE, the shipment should start at the early pick up date if there are no other constraints.

Default = TRUE

MINIMIZE WAIT TIME IN SERVICE TIME CALCULATION

Service Time

Use this parameter to have Oracle Transportation Management look for opportunities to minimize the wait time on a shipment by potentially adjusting start time or other variables depending on the constraints defined on rates, etc. By default, this parameter is off which may result in sub-optimal, time feasible shipments depending on the details of the shipment.

MINIMUM ORDERS FOR MILESTONE COLLECTION

Bulk Plan

The minimum number of orders (order release/order movement) needed for milestone collection. If you set this parameter to 0 then no milestones are collected.

MINIMUM TIME BETWEEN MILESTONE UPDATES

Bulk Plan

The minimum amount of time between milestone progress updates.

MIN INBOUND UNLOAD TIME AT XDOCK

Bulk Plan

5.5 CU4

Indicates the minimum time needed for unloading at the cross-dock.

This is used only when the parameter "MULTISTOP FAVOR SAME DOWNSTREAM SHIPMENT" is set to true. The default is 0.

See also Bulk Plan Cost Based Routing.

MODE PROFILE ID FOR CARRIER COMMITMENT

Service Provider Assignment

This parameter holds mode profiles. Any carrier commitments are limited to the modes defined by this parameter.

For example, if you bulk plan an order (order release/order movement) for the mode of TL and this parameter has TL defined in it, then if there is a carrier commitment for the lane, then that carrier commitment will be used. However if you bulk plan an order with a mode of LTL and the parameter only has TL in it, then all valid carriers will be considered for this shipment, not just the carrier with the carrier commitment.

MODE PROFILE ID FOR ROUTE EXECUTION

Cooperative Route Planning and Execution

6.0

Controls how shipments are assigned to route instances.

This allows you to expand the types of shipments considered for the route instance. Now, all shipments that would otherwise be planned under any mode compatible with the specified mode profile ID will be allowed to go on the route instance.

For example: You set up TL route instances. Some shipments would be planned on Intermodal carriers if they do not go on route instances. You can allow these shipments to be candidates for a TL route instance by setting this parameter to a mode profile that is compatible with both TL and Intermodal modes. (If the shipment is planned on the route instance, it will be planned as a TL shipment, as was the case prior to this enhancement.) A shipment that would normally go LTL will still not be a candidate to go on the route instance.

This affects both shipment creation (in bulk plan and the Build Shipment actions) and also the Route Instance Leg - Assign Shipment and Shipment - Assign to Route Instance Leg actions, and their associated Find Potential Shipments and Find Potential Route Instance Legs actions. So in the previous example, a shipment planned Intermodal can show up under the Find Potential Shipments action for a TL route instance leg, and the TL route instance leg can show up under the Find Potential Route Instance Legs for an Intermodal shipment. (Previously this was only possible by ignoring the Mode constraint.) Be aware that these actions in CU5 are run under the domain default parameter set.

If a shipment would normally be planned on a mode incompatible with the MODE PROFILE ID FOR ROUTE EXECUTION, it still can be planned onto a route instance with that same mode.

The default is TL. In order to obtain the behavior prior to this enhancement, set up the parameter with a mode profile compatible with no modes at all.

Note that the default value will not necessarily give the same behavior as existed prior to 6.0.

MULTILEG SERVICE TIME CALC STEP

Service Time

6.0

For service time API that calculates an Array of TshipmentCollections, each leg calculates the service time with an early start time to get a feasible solution. It then adds this MULTILEG SERVICE TIME CALC STEP to the feasible start time and calculates service time again on same shipment. Shipments on each leg will have a list of feasible service time results that start at different times controlled by this MULTILEG SERVICE TIME CALC STEP. Then service time routing will find a short service time from all choices on each leg and render a final solution.

This impacts solution quality and run time. The smaller the parameter, the better the solution quality, but longer the run time.

MULTILEG START TIME SEARCH SPACE

Service Time

6.0

Duration service time calculation for multi-leg or arbitrary shipment (an arbitrary shipment is converted to multiple shipments, each shipment is corresponding to one leg of rate service), the drive routing estimates the earliest and latest start time for each leg, then drives each leg with different start times around this earliest/latest start time to get different drive results. This parameter controls how much of a time window it will be for the start times.

MULTISTOP CONFIG ID

Multistop

This determines which configuration to use for multi-stop. The configurations are defined in Logic Configuration. The configuration is a collection of related parameters and algorithms used by planning logic. It can handle different scenarios and be shared by different parameter sets.

Note: The other multi-stop parameters are on the Logic Configuration page.

MULTISTOP POOL LINEHAUL SHIPMENT WITH DIRECT

Multi-tier

Use this parameter to specify if Oracle Transportation Management should try to multi-stop the line haul shipment to a deconsolidation pool (or from a consolidation pool) with the direct/multi-stop shipments to make it cost effective.

If the value is marked (true), then this parameter looks to the BUILD DIRECT SHIPMENT OPTION FOR BULK PLAN to continue processing (which varies slightly when used with the MULTISTOP POOL LINEHAUL SHIPMENT WITH DIRECT parameter).

If the value is not marked, Oracle Transportation Management will not try to multi-stop the line haul shipment to a pool.

See also Bulk Plan Cost Based Routing.

MULTISTOP POOL LINEHAUL WITH DIRECT ALL AT ONCE

Multi-tier

5.5 CU3

When set to True, the pool cross-dock skips steps regardless of the settings of the following:

BUILD DIRECT SHIPMENT OPTION FOR BULK PLAN
MULTISTOP POOL LINEHAUL SHIPMENT WITH DIRECT
SEGMENT MULTISTOP SHIPMENTS BY POOLS

Following are the steps that are skipped:

1-multistop linehaul shipments to deconsolidation pool

2: multistop direct shipments

3: multistop direct multistop shipments with linehauls shipment to deconsol pools

4: out of cross-dock, multistop linehaul shipments to deconsolidation pool

5: multistop direct shipment from cross-dock

6: multistop cross-dock outbound direct multistop shipment with cross-dock outbound line haul shipments to deconsolidation pool

Instead, it performs the following:

1: multistop direct shipments and linehaul shipment to deconsol pools all at once

2: when there is cross-dock involved, multistop cross-dock outbound direct shipments with cross-dock outbound linehaul shipments to deconsol pool at once.

The default is False and the behavior is the same as it has been.

See also Bulk Plan Cost Based Routing.

MULTISTOP XDOCK INBOUND AFTER OUTBOUND COMPLETE

Multistop

5.5 CU4

When set to true, cross-dock inbound consolidation is performed after cross-dock outbound planning is complete.

The default is false.

See also Bulk Plan Cost Based Routing.

MULTISTOP XDOCK INBOUND SHIPMENT WITH DIRECT

Multi-tier

Use this parameter if Oracle Transportation Management should try to multi-stop the shipments to/from a cross-dock with the direct/multi-stop shipments to make it cost effective.

If the value is not marked, Oracle Transportation Management will not try to multi-stop cross-dock shipments with direct shipments.

See also Bulk Plan Cost Based Routing.

NAT NAL UPDATE REMARK QUALIFIER GID

Fleet Management

6.2.3

Remark Qualifier GID for Remark Text to be considered from tracking event for NAT NAL Override Action.

The agent action "UPDATE HOURS OF SERVICE STATE" is required to propagate this to the driver. When a new tracking event is created, remarks can be entered via "Detail" tab > Remarks section. Multiple remarks (by selecting a Remark Qualifier ID and the corresponding Remark Text) can be entered here. If one of the remark qualifier ID's entered here matches this parameter's value, then the corresponding Remark Text will be pulled and copied over to the driver assignment's description field, while executing "UPDATE HOURS OF SERVICE STATE" agent action.

NAT UPDATE TOLERANCE

Fleet Management

6.1

Tolerance within which the updated NAT needs to be from previous NAT. A NULL value indicates check not performed.

NETWORK ROUTING CONFIG ID

Multi-tier

6.3

This determines the network routing logic configuration set used.

See also Bulk Plan Cost Based Routing.

OPTIMIZED ORDER BASE BUNDLING

Order Management

6.2

Controls which bundling algorithm to use. Non-optimized bundling would bundle with the given sequence of bundles while optimized bundling uses container optimization to produce better bundles. For example, if MAX WEIGHT PER BUNDLE is set to be 1000 LB and 4 bundles passed in with weight 500LB, 400LB, 600LB and 500LB, non-optimized bundling will produce 3 bundles: (500LB, 400LB), (600LB) and (500LB) while optimized bundling would generate only 2 bundles (500LB, 500LB), (400LB, 600LB).

ORDER BASE BUNDLING RULE SET

General

5.5 CU4**

Configures the default order base bundling rule set.

ORDER BASE COPY TOTAL WEIGHT VOLUME

General

5.5 CU4

Determines if the Total Weight and Volume are copied from the Line when creating a new release instruction. The default is false. If True, the Total Weight and Total Volume fields display on the Order Base Line Release Instruction. If false, they are hidden.

ORDER BUNDLE LOADING TIME WINDOW SPAN

Order Management

6.3

Defines a window of time that enables you to load shipments in the past.

For example, you have a shipment with a pickup window of July 10 to July 12, and this parameter is set to 3 months. If the current date is August 10, it will cover the pickup window for the system to load this shipment.

ORDER MOVEMENT GROUPING TYPE

Multi-Tier

6.3

This controls whether the recommended starting period is considered in the order movement grouping logic.

Without Start Date (default): the logic only considers Leg Consolidation Group in creating order movement group and only considers leg consolidation group sequencing factor in sequencing order movement groups; recommended starting period is not considered.

With Start Date: order movement groups will be created for each leg consolidation group and "recommended starting period". The groups will then be sequenced by recommended starting period and then by sequencing factor.

With non-negative sequencing factor, start date is set to be the later date of "order movement early pickup date" and "order movement operation early pickup date"on the leg;

With negative sequencing factor, start date is set to be the earlier date of "order movement late delivery date" and "order movement operation late delivery date"on the leg.

Note: This is only for Network Routing.

ORDER RELEASE BUNDLING RULE SET

General

5.5 CU4**

Configures the default order release bundling rule set.

The rules 'Order Bundle IncoTerms Rule' (obIncoTermsRule) and 'Order Bundle Term Location Text Rule' (obtltRule)" are expected to be used together in order to have them applied in order bundling process in bulk plan. Additionally, these rules need to be added to this parameter in order to have "Order Bundle Term Location Text Rule" applied.

ORDER ROUTING METHOD

Multi-tier

6.3

This parameter specifies which routing logic is used; either Network Routing or Cost-based Routing. Cost-based Routing (the pre-6.3 routing logic) is the default.

See also Bulk Plan Cost Based Routing.

PERFORM SHIP UNIT REPACK

Ship Unit Building

6.3

When set to True, grants permission to repack ship units as part of shipment ship unit building. Default = False.

Note: Ship unit repack does not apply to ground schedule and consol shipments.

PLANNING DAY DURATION

Bulk Plan

23C

When you are bulk planning order releases such that all the planned orders are shipped starting on a particular planning day, this parameter will determine that planning day end time. You can specify the duration of the planning day in this parameter, and to calculate the planning day end time, the application will add this duration to the value set for the parameter PLANNING DAY START OFFSET.

The order release pickup time window will still be honored.

Default: 365D 0M

PLANNING DAY START OFFSET

Bulk Plan

23C

When you are bulk planning order releases such that all the planned orders are shipped starting on a particular planning day, this parameter will determine the start time of the planning day. The time will set off from the next midnight from the current time.

For example, the value for this parameter is set to 1D 5H 30M. If you plan on Tuesday 4/4, the next midnight is Wednesday 0:00. Hence, the planning day start will be Thursday at 5:30 a.m.

The order release pickup time window will still be honored.

Default: 0D (For this value, if the bulk plan planning day fields are blank, there will be no planning day restriction, and the parameter PLANNING DAY DURATION is ignored.)

PLANNING GROUP THAT RUN XDOCK POST LTL SPLIT

Multi-tier

Use this parameter to control whether orders can be split/consolidated by different ship units beyond one truckload. Use this to allow Oracle Transportation Management to consider splitting a shipment by different ship units but it does not split an actual ship unit.

Assign the planning groups to control this processing. The same planning group should also be assigned to the orders that will be planned into the cross-dock.

After the standard cross-dock planning process completes, the following post LTL split-consolidation process is run.

Identify all cross-dock shipments and collect all cross-dock inbound shipments. For each inbound shipment, find its outbound shipments and based on the start time of each outbound shipment and the handling time for the inbound/outbound, set the latest arrival time on the inbound shipment, i.e., do not violate the outbound shipments start time.
Consolidate the inbound shipments.

LTL split-consolidate process (allow only one split for each shipment).

1. Sort all the shipments in ascending weight/volume order.

2. Select the least weighted shipment and try to split as much as possible by ship unit and put the split portion on the second least weighted shipment that has the same source/destination (and also feasible). Put the leftover portion on the shipment in the sorted list that has the most weight/volume, same source and destination, but still have the space for the leftover portion. Always keep the original shipments on the consolidated shipments.

If such a split cannot happen, exit the process.

3. Take out the split shipment from the sorted list. Go to step 1

Add consolidated inbound shipments and recalculate their handling shipments.
Collect all cross-dock outbound shipments. For each outbound shipment, find its handling shipments and based on the end time of each handling shipment set the earliest start time on the outbound shipment.
Add consolidated outbound shipments and recalculate their handling shipments.

PLAN ORDERS WITH DATE EMPHASIS PAST

Order Management

6.0

When this is true, orders releases will be planned as if their time window emphasis is set to PAST.

If the parameter is false, driver assignment can fail due to time infeasibility.

PLAN SHIPMENT ON ROUTE INSTANCE

Cooperative Route Planning and Execution

When this is set to True, planning will try to match and assign direct shipments to route instances in bulk plan and build direct shipment. The default is False.

PLAN SHIPMENTS WITH CARRIER COMMITMENT

Service Provider Assignment

If this is turned on, OTM planning will use the Service Provider Assignment optimization logic in order to find the best assignments of shipments to service providers, taking into account capacity limits as well as commitment allocation and commitment count. Even when no commitments are set up, this logic will still try to optimize based only on capacity limits.

If this is turned off, OTM planning logic will not go through any optimization logic for service provider assignment. It will ignore commitment allocation and commitment count. It will not ignore capacity limits, but it will assign service providers one shipment at a time, and so may make sub-optimal choices.

If there are no capacity limits, commitment allocation, or commitment count, neither setting of this parameter provides any benefit.

The property glog.business.serviceprovider.redriveShipments can prevent service provider assignment logic from redriving the shipment graphs of multi-leg shipments. This redrive does not work well with multi-leg shipments with the parameter "Hold as Late as Possible" set, because it drives some shipments early.

PLAN THRU POOL BEFORE XDOCK

Multi-tier

Use this parameter to specify whether you want Oracle Transportation Management to plan through a pool before a cross-dock.

When true, Oracle Transportation Management will try to plan the order releases through the pool first, and then try to plan through the cross-dock.

If false, Oracle Transportation Management will try to plan the orders through the cross-dock first, and then try to plan through the pool.

See also Bulk Plan Cost Based Routing.

PM EMISSION GRAM PER MILE

FTI Parameters

6.1

Used for tracking particle matter emissions on the green dashboard.

Changes to this parameter are not considered until the server restarts. *

PREFER XDOCK SHIPMENTS THAN DIRECT SHIPMENTS

Multi-tier

The Value check box indicates that you want Oracle Transportation Management to build shipments that go through the cross-dock whenever possible. Oracle Transportation Management uses more planning solutions that include the cross-dock. If you do not mark the Value check box the system builds shipments that travel direct whenever possible.

See also Bulk Plan Cost Based Routing.

PRE-SPLIT LARGE ORDER RELEASES IN CONTAINER OPT

Container Optimization

6.2.1

Pre-splits large order releases before performing container optimization logic.

See the following in the Order Management Guide: Order Configuration and Order Modification Workflow.

PREVENT UPDATE ON NAT CHECK FAILURE

Fleet Management

6.1

Prevent update of NAT (next available time) if it fails the NAT UPDATE TOLERANCE check.

PRIORITY IN USE

Bulk Plan

6.0

Controls whether to use order priority in planning. The Priority field appears on order bases, order releases and order movements.

This parameter, along with the Use Priority in Conopt Sorting parameter, must be set in order to use ship unit priority for equipment packing.

PROC_DEFAULT_BID_GID

Sourcing

This refers to a bid that will be used as a template for populating pre bids. Note that you must change the default value of DEFAULT to a va lid bid ID.

NOTE: This functionality is not yet available in 6.3 and later.

PROC_IS_MAX_PCT_LOADS_EDITABLE

Sourcing

Indicates if changes are allowed to the MAX_PCT_LOADS_REQUESTED field.

PROC_IS_MIN_PCT_LOADS_EDITABLE

Sourcing

Indicates if changes are allowed to the MIN_PCT_LOADS_REQUESTED field.

PROCUREMENT SOLVER MAXTIME

Sourcing

This value represents the maximum number of seconds the sourcing solver should run. A value of zero means that the time is unlimited.

PROCUREMENT SOLVER PERCENT OPTIMAL

Sourcing

This value controls how close to optimal the solution should be. The value must fall between 0 and 100.

PROPAGATION TYPE

Shipment Quantities

6.0

This parameter allows you to set a default value for the Shipment Quantities Propagation field - None, Up, Down, or Both.

Default = Down

PROVINCIAL VAT CONFIGURATION ID

Settlement

This allows you to specify the Provincial VAT configuration to be used. Parameter must point to a valid Provincial VAT Configuration. Within the configuration, you have to reference the following setup data:

Province Code Profiles to accommodate the various combinations of Source and Destination provinces that apply.

VAT Codes in Vat Code Ordered sets to indicate which VAT codes to apply in sequence when the logic determines a qualifying source and destination province profile pair.

Province Source for cases when the logic has to determine something for a particular province such as the service provider's provincial registration number. This specifies where to obtain that province.

PUBLISH PROCESSING REQUEST ON CREATION

Tracking Event

6.2.2

Indicates whether to publish the lifetime event TRACKING EVENT - PROCESSING REQUEST at the time of event creation. Default: True.

This parameter does exactly what the property "glog.trackingevent.publishProcessingRequestOnCreation" does but is provided as a parameter to give flexibility to set this at different levels. This parameter is used only when the property is set to the default value of True.

QUOTE USES RIQ ROUTE

Brokerage and Forwarding

When set to true, clicking either Get Rate button on the Order Release Constraints tab will return a fixed itinerary and the rate offering will be updated from the primary leg. If more than one leg is designated as primary, the rate offering will be based on the first primary leg found in the itinerary.

When set to false, clicking either Get Rate button on the Order Release Constraints tab will return rate offerings.

RAIL AXLE WEIGHT IMBALANCE THRESHOLD

Container Optimization

24B

This parameter is used to define the threshold for the truck imbalance ratio. This parameter would only come into play if the axle weights were less than the max allowed and the car was overloaded to one end.

The default value is 1.0.

For example, If set to 0.9 means axle weights are considered balanced as far as the imbalance ratio is >=0.9 and considered imbalance if the ratio <0.9.

Note: You can set the value between 0 and 1. If the value is set greater than 1.0 then logic considers it as 1.0.

RAISE ALERT ON NAL CHANGE

Fleet Management

6.1

Raise Driver lifetime event if the new NAL (next available time) is different from previous NAL (next available location).

RAISE ALERT ON NAT FAILURE

Fleet Management

6.1

Raise Driver life time event if the new NAT is off previous NAT by more than NAT UPDATE TOLERANCE

RATE ALL EQUIPMENT GROUPS IN SHIPMENT BUILDING

Shipment Planning

5.5 CU5

When this parameter is true, the logic rates all equipment groups in order to pick the cheapest, and not necessarily the best fit, equipment.

The default is FALSE. This has better performance as it does not cost all equipment groups).

RATE OFFERING FOR SPOT MARKET RATES

Collaboration

24C

When you set this parameter value with a rate offering that offers market rate, OTM fetches the current market cost using this value when you run the following shipment actions:

Spot Bid Tender
Fetch and Update Market Cost

Default value is blank, which means the application does not fetch the market cost.

Note: This parameter is also applicable for the action 'Update Open Tender' for spot bid tendered shipments.

RATE SHIPMENT BASED ON FIRST/LAST FREIGHT STOPS

Fleet Management

6.2.3

When set to TRUE for shipments of TRANSPORT type, rating search will be based on the lane from the first stop that is not of type NFR to the last stop which is not of type NFR.

Default = FALSE.

RATING ENGINE ALWAYS CALCULATES TIERED RATES

Rates

5.5 CU4

Causes the rating engine to cost a shipment as if it had happened in the applicable time period. Doing so causes the rating engine to return rates with tiered costs even when the shipment has not yet been finalized into the time period. See Configuring Tiered Rating.

The default is FALSE.

RATING ENGINE STORES DETAILED COST INFORMATION

Rates

If true, Oracle Transportation Management stores a breakdown of the calculations for each individual shipment cost type and displays the results on the Financial tab of the Shipment Manager and the Rate Inquiry Results page.

RECALC ORDER EARLIEST EST PICKUP DATES

Order Management

6.4.2

When this is set to TRUE, the order release Earliest Estimated Pickup Date will be recalculated when the estimated departure time has changed. Default is FALSE.

RECALC ORDER LATEST EST DELIVERY DATES

Order Management

5.5 CU4

This indicates if the recalculate Order Release's Latest Estimate Delivery Date is needed. The default is FALSE.

RECHARGE FOR VOUCHER SAVED QUERY ID

Settlement

22A

This specifies the saved query required to run the Perform Recharge action on a voucher. If no value is provided in the Saved Query field of the Perform Recharge action page, the application uses the saved query specified by this parameter when running the action.

Default value of this parameter is RECHARGE FOR VOUCHER DEFAULT.

RECHARGE REQUIRED VOUCHER REFNUM QUALIFIER

Settlement

22A

This specifies the recharge qualifier required to perform the Determine Recharge action on a voucher. If no value is provided in the Recharge Required Voucher Refnum Qualifier field on the Determine Recharge action page, the application uses the value specified by this parameter when running the action.

Default value of this parameter is RECHARGE REQUIRED.

REDRIVE TIME VIOLATED DOWNSTREAM SHIPMENTS ONLY

Service Time

6.2.6

This provides more control over the decision to redrive downstream shipments during a shipment action. The default is True, and this will result in the same behavior as prior to this enhancement. That is, downstream shipments will only be redriven if the action causes an upstream shipment's end time to overlap with the start time of the downstream shipment.

When set to False, the parameter will cause all downstream shipments to be redriven even if there is no time overlap with upstream shipments.

REFERENCE QUALIFIER FOR SHIPMENT W/O APPOINTMENTS

Appointment Management

6.3.1

Specifies at the domain level which reference qualifier is displayed in the Shipments Without Appointments table on the Manage Appointments page. Its value format and value options are the same as its system property counterpart: glog.appointment.swa.shipmentRefnum.

RERATE ALL SHIPMENTS AFTER BULK PLAN

Bulk Plan

If set to true, all shipments are re-rated after the bulk plan process is complete. Works in conjunction with the Active check box on a rate offering.

RERATE ALL SHIPMENTS IN RIQ

RIQ

6.3.4

This parameter provides the option in Rate Inquiry Rate and Route to re-rate shipments before OTM lists them as options, and therefore, will only select rate records that are effective for all the shipments. Without this parameter, when multi-leg shipments are built, Rate Inquiry can assign expired rates to shipments of subsequent legs when the expired rate is valid at the start of the first leg. This is because when determining rates, service time is not considered, hence rate record effectiveness is checked based on order start date instead of the shipment's start date.

If set to true, all shipments are re-rated before they are presented as options in Rate Inquiry Rate and Route. The default is false.

Note: Currently, this only impacts the Rate and Route option. It is not valid for the Rates or Network Rate and Route options.

RETAIN EMPTY SEQUIPMENTS ON SHIPMENT

Shipment Actual

21A

If set to true, OTM will retain shipment equipment which becomes empty when there are still other non-empty shipment equipment on the shipment for Shipment Actuals or shipment modification (SMD) and Order Release - Mod - Propagate Changes.

Since Order Release - Mod - Edit Shipment is used for shipment with one shipment equipment (no split), this planning parameter is not applicable for this agent action.

The default value is false.

RETENDER TO DIGITAL FREIGHT FROM N ITERATIONS

Service Provider Assignment

23C

Determines from which iteration the digital freight rates are considered for the step tender. If the parameter value is set, OTM considers digital freight rates for tender. If the parameter value is greater than zero, the digital freight rates are considered.

Default value is 0.

For example, if the shipment is planned with carrier A and parameter is set to 2, and you perform the action step tender, the first tender is sent to B. After the step time (second iteration), it considers the digital freight rates and send the tender to the next carrier.

RIQ HAZMAT SPECIAL SERVICE CODE

Rates

Holds the Special Service Code that should be used when selecting the Hazardous Cargo requirement on the International RIQ page.

RIQ RATE EXPIRE NUM DAYS

Brokerage and Forwarding

On the International RIQ results page, if any of the rate options expire in less than the number of days defined here, then it will be flagged as such on the page.

RIQ ROUTE ITINERARY RULE SET

General

5.5 CU4**

Configures the default rate inquiry route itinerary rule set.

RIQ UI HIDE/DISPLAY COST FIELD

Financials

6.2

Controls the display of the Cost field on the Rate Inquiry screen. The values are Hide or Display. The default is Display.

RIQ UI HIDE/DISPLAY WEIGHTED COST FIELD

Financials

6.2

Controls the display of the Weighted Cost field on the Rate Inquiry screen. The values are Hide or Display. The default is Display.

RIQ UI SORT BY

Financials

6.2

Allows you to sort the costs on the Rate Inquiry screen by cost or weighted cost. The default value is cost.

ROUTE EXECUTION ALLOW MULTISTOP SHIPMENTS

Cooperative Route Planning and Execution

5.5 CU3

If set to True, multi-stop shipments can be assigned to route instances.

The default is False.

ROUTE EXECUTION DEADHEAD RATE DISTANCE ID

Cooperative Route Planning and Execution

Used to calculate the deadhead distance if using cooperative routing.

The default is "LOOK UP ELSE ESTIMATE.

ROUTE EXECUTION DEADHEAD RATE SERVICE ID

Cooperative Route Planning and Execution

Used to calculate the rate service on deadhead distance if using cooperative routing.

The default is TL-SIM.

ROUTE EXECUTION EMPTY DISTANCE COST

Cooperative Route Planning and Execution

This allows you to define the deadhead distance cost for route execution.

Note: This cost is not saved in the system and is only used for determining how shipments are assigned to routes.

The default is 0.1.

ROUTE EXECUTION EMPTY TRANSIT TIME COST

Cooperative Route Planning and Execution

5.5 CU3

This parameter is a per-minute planning cost for time between shipments on consecutive route instance legs.

Note: This cost is not saved in the system and is only used for determining how shipments are assigned to routes.

The default is 0.

ROUTE EXECUTION INSTANCE MAX DURATION

Cooperative Route Planning and Execution

5.5 CU3

If the parameter is not 0, then it constrains the route instance assignments based on the time of the shipment on the first leg and on the last leg. The constrained value is the time between the first stop on the first leg of the shipment and the last stop on the last leg. The bulk plan results adhere to this parameter if the MINIMIZE WAIT TIME IN SERVICE TIME CALCULATION parameter is activated.

The default is 0, which means this constraint is ignored.

ROUTE EXECUTION SEARCH WINDOW DAYS

Cooperative Route Planning and Execution

This parameter indicates how far on either side the logic will search for instances or shipments. In the bulk plan, this is used to determine which instances to look for. (i.e., if the cooperative routing shipment would start on 11/15, and if this parameter is set to 3, then the logic will try to match to instances that are active any time between 11/12 and 11/18). In the Route Instance Leg action "Assign Shipments" in Find Potential Shipments, this is used to determine which shipments to look for. (i.e., if the route instance leg has a departure window of 11/15 2:00 - 5:00, then the logic will consider all shipments that begin between 11/12 2:00 and 11/18 5:00.)

RUN HAZMAT QUALIFICATION PROCESS

Shipment Planning

The Hazmat Qualification Process looks up each line item on a new shipment in the hazmat tables and assigns the corresponding hazmat_item_gid to the shipment ship unit line. The hazardous classification of an item is determined using the packaged item, the hazmat region from the itinerary, the transportation mode of the shipment, and the packaging type from the packaged item.

See Hazardous Material Settings and Implications.

RUN TRAILER BUILD IN BULK PLAN

Bulk Plan

When set to TRUE, Oracle Transportation Management will keep the trailer build functionality separate from the bulk trailer build functionality.

The default is set to TRUE for backwards compatibility, and allows you to run the trailer build functionality against a group of shipments that have already been bulk planned. If you intend to use the bulk trailer build functionality, however, this parameter must be set to FALSE.

SAME COST PER CARRIER FOR SPLIT ORDER

Shipment Planning

5.5 CU4**

Default: false.

When this is true, each carrier has the same cost for all shipments on a split order (order release/order movement) regardless of the equipment option and/or weight/volume on each shipment. This parameter simplifies the optimization process of selecting service providers.

SEGMENT MULTISTOP SHIPMENTS BY POOLS

Multi-tier

If you use the setting of FALSE, all shipments are sent into multi-stop at once. If you set it to TRUE each shipment goes through each pool into multi-stop separately.

See also Bulk Plan Cost Based Routing.

SET FIXED STOP TIME ON NEW SHIPMENTS

Shipment Planning

When the parameter is set to true, for each planned shipment, go through each stop, if this stop is pickup/deliver any order (order release/order movement)at the order's source/destination (for example, this stop is some order's source or destination), Oracle Transportation Management will set this stop's time to be fixed.

SET LAST STOP TO 99

Shipment Planning

Flag indicating whether to set the last stop number to 99 for the shipment stop sequence numbers of the shipment produced from the planning engine. The beginning number is set to 1, so setting the last stop number to 99 enables subsequent feeds to Oracle Transportation Management for interim stop information to be inserted after the original shipment.

Not only does this parameter apply to shipments newly created by the planning logic; it also affects shipments that are modified by planning actions (such as the merge shipments actions).

SET PAYMENT TERMS ON BUILT SHIPMENTS

Settlement

Defines if the build shipment process should copy the payment terms from the order release or itinerary leg to the resulting shipment (Financials tab).

SET SHIPMENT STOP TIMES USING EARLY PICKUP

Service Time

Use this parameter to set the shipment stop arrival/departure date/time on all shipment stops for planned, estimated, and actual dates/times using the order release early pickup date/time.

SETTLEMENT REVERSAL ACCRUALS

Settlement

Has four values: OFF, BUY, SELL, and BOTH. This parameter controls whether accruals are reversed or continue to accrue at settlement. When a voucher (buy side) or bill (sell side) is allocated, accruals logic still triggers (assuming accruals are enabled and allowed by the shipment status existing logic). If the parameter is configured to reverse the accrual for the given perspective, the accrual amount should be reversed (negative accrual generated) for the amount from the allocation, however, it should not reverse more than has been accrued already. Once an accrual has been reversed in full, the ACCRUAL status should be changed to CLOSED.

SHIPMENT ETA RATE DISTANCE GID

Collaboration

This parameter determines the type of distance calculation used when Oracle Transportation Management is estimating the arrival time based on receipt of an actual stop time for a shipment which has not been assigned a rate offering.

SHIPMENT OR ORDER AMOUNTS

Shipment Quantities

6.0

This parameter allows you to set a default value for the Shipment Quantities Edit By field.

Default = Shipment

SHIPMENT PREFERENCE CRITERIA

Service Provider Assignment

23A

This parameter provides an option for the user to select a rule by which one shipment will be preferred over another in the Service Provider Assignment Optimization logic, when there are limited resources (i.e. due to Capacity Limits). These new rules apply only when the parameter PLAN SHIPMENTS WITH CARRIER COMMITMENT is turned on.

For a bulk plan in which there are not enough equipment resources for all of the orders to be shipped, this parameter allows the user to ensure that the equipment resources are assigned to the more important shipments (e.g. the shipments with higher priority orders, or shipments with the most freight by weight/volume/ERU).

The following are the available options for this parameter at this time.

0. None: No preference criteria is used for shipments.

1. Priority: A shipment with a higher priority will be preferred over a shipment with lower priority. This is same in effect as setting USE PRIORITY IN SPA = true.

2. Total weight: A shipment with a higher total weight will be preferred over a shipment with lower total weight.

3. Total volume: A shipment with a higher total volume will be preferred over a shipment with lower total volume.

4. Total ERU: A shipment with a higher total ERU count will be preferred over a shipment with lower total ERU count.

The default option is set to None. When SHIPMENT PREFERENCE CRITERIA is "0. None", and USE PRIORITY IN SPA is set to true, SHIPMENT PREFERENCE CRITERIA will be internally forced to "1. Priority". In all other cases, the parameter setting for SHIPMENT PREFERENCE CRITERIA takes precedence over USE PRIORITY IN SPA.

SHIP UNIT LINE REFNUM QUAL

Shipment Quantities

6.0

This parameter controls which Refnum Qual should be grid flattened. Null means no field will be shown.

SHIP UNIT MIN IMPACT

Ship Unit Building

6.3.7

When this parameter is set to true, only ship units which are impacted by edits, either directly or indirectly, will be rebuilt. Otherwise when changes are received, all ship units are rebuilt, regardless of whether or not they are impacted by the changes.

SHIP UNITS OR LINE ITEMS

Shipment Quantities

6.0

This parameter allows you to set a default value for the Shipment Quantities Ship Unit or Line Item field.

Default = Ship Unit

SHORT CIRCUIT LEG

Multi-tier

If set to true, when planning the order release on an itinerary, Oracle Transportation Management will start with the leg whose previous legs destination matches the order releases Plan From Location and only plan up to the leg whose destination matched the orders Plan To location.

Order will specify in the Plan From/To locations from which point and up to which point on the itinerary it needs to be planned.
When matching to the itinerary, order source/destination will be used to match to the itinerary source/destination regions.
When planning shipment for the order on its legs, Oracle Transportation Management will check to see if the Plan From/To locations match any of the intermediate nodes of the itinerary and, if so, only plan it on the intervening legs.

Note: This parameter does not work with network routing.

SHOW ASSIGNED UNTENDERED SHIPMENTS

OF SERVPROV

Appointment Management

6.3.5

When you are logged into OTM as a service provider, this parameter controls which shipments are displayed on the Dock and Yard Manager for the service provider to which the parameter set is assigned. The default value is TRUE.

TRUE: All shipments assigned to the service provider are shown.
FALSE: Shipments that are assigned and tendered to the service provider are shown.

SKIP INITIAL SCREEN

Shipment Quantities

6.0

Parameter to allow you to skip the initial Shipment Quantities screen.

The default is False.

SOLUTION IMPROVE CONFIG ID

Bulk Plan

This parameter allows you configure a Solution Improvement Configuration ID that controls whether Oracle Transportation Management evaluates the shipments created from a bulk plan run for opportunities to improve solution quality, specifically, to reduce cost.

SOURCING CONFIG ID

Sourcing

6.4.3

This parameter allows you configure a Sourcing Logic Configuration ID that controls Oracle Transportation Sourcing.

SMD SYNC SHIP UNIT COUNT WITH LINE COUNT

Shipment Actual

6.4.3

When this is true and modification is via order release line, OTM will copy the packaged item count from the order release line to the ship unit count.

SMD SYNC WITH ORDER

Shipment Actual

6.4.3

Controls how an unplanned count in shipment actuals is handled. When set to true, unplanned count of shipment ship unit will be created and associated with unplanned order movement. When false, the unplanned count of shipment ship unit will not be created.

So if true, Oracle Transportation Management will synchronize with the order. That is, if the count is reduced, Oracle Transportation Management will create a shipment ship unit and order movement to hold the unplanned count. For unplanned order movement, Oracle Transportation Management will not do anything since they are already synchronized with the order.

If false, Oracle Transportation Management will not synchronize with the order. That is, if count is reduced, Oracle Transportation Management will not create shipment ship unit and order movement to hold the unplanned count. Oracle Transportation Management will also reduce the count from unplanned order movement since OTM does not want to synchronize with an order but wants to be consistent with the propagated shipment change.

SPA CONSTRAINED ORDER EQUIPMENT TYPE PROFILE

Service Provider Assignment

24C

This parameter enables Service Provider Assignment (SPA) logic that will prioritize the planning of unsplittable single ship unit orders that can be accommodated by only a subset of available Equipment Types. For example, if a large unsplittable order (e.g., a large steel coil) can be transported only by itself on the largest equipment type, then this logic will prefer to assign the largest equipment type to this order, rather than use it for smaller orders that have consolidated onto a large shipment. The smaller orders can be re-planned onto smaller shipments that use smaller equipment types (whereas the large order cannot).

You can enable this SPA logic when this parameter is set to an Equipment Type Profile. This profile should define a subset of available equipment types. SPA will prioritize a shipment with a single unsplittable order with a single ship unit, where this shipment can be accommodated only by equipment types in this equipment type profile.

Even if the SHIPMENT PREFERENCE CRITERIA parameter is set to prefer Total Weight, this shipment will be preferred to heavier shipments. If it is set to Priority, and this shipment has Medium priority, then the other shipments with Medium priority will be preferred. However, at the same time, other High priority shipments will get an overall preference.

Note: This logic is only enabled when PLAN SHIPMENTS WITH CARRIER COMMITMENT is set to true, and is only relevant for scenarios where the subset of equipment types is constrained by Capacity Limits (for example, when there is only one equipment of the largest equipment type, so that it should be reserved for a large order).

SPA EVALUATE VIA POINTS AND VOYAGES

Service Provider Assignment

6.2.2

When using arbitraries, setting this to true allows the service provider assignment logic to change shipment via point locations based upon service provider, and thus allows the service provider assignment logic to select a service provider for a shipment even if different service providers require different via point locations.

In addition to this parameter being true, the leg needs to define a service provider profile that contains the service providers that should be considered in service provider assignment logic.

Using this functionality will remove the service provider assignment's ability to select equipment group/type. The equipment group from the cheapest service provider will be used.

SPA GROUP BY ORDER LOCATIONS

Service Provider Assignment

6.1

Indicates whether to group shipments by order source and/or destination locations while enforcing service provider assignment (SPA) rules. Applies to order releases and order movements.

SPA GROUP MODE PROFILE ID

Service Provider Assignment

6.1

Shipments on the itinerary leg matching this mode profile ID will be grouped by order source and/or destination locations while enforcing Service Provider Assignment (SPA) rules. Applies to order releases and order movements.

SPA MAX DAYS TO CONSIDER

Service Provider Assignment

19B

This parameter determines how many extra possible start days OTM will consider for each shipment, subject to capacity limits. When using this parameter, it is best to set this no larger than needed, as it can have a performance impact. For example, if two extra days is sufficient to find the right resources, then there is no reason to set it higher than 2.
The default is "0" (zero). See the Service Provider Assignment and Resource Management topic, Service Provider Assignment Time Window Functionality section, for more details.

SPA TIME CHANGE POLICY

Service Provider Assignment

19B

This parameter provides priority level control about whether OTM should discourage delaying the shipment start date in order to take advantage of a cheap but capacity-limited service provider. For example, there is a cheap carrier that has only one truck per day. Should I delay my shipment departure to tomorrow to get the cheap truck, or should I let it ship today on an expensive truck? The options are '0. Discourage Time Change', '1. Discourage Time Change For High Priority Shipments', '2. Discourage Time Change For High & Medium Priority Shipments', '3. Encourage Time Change'.

See the Service Provider Assignment and Resource Management topic, Service Provider Assignment Time Window Functionality section, for more details.

The default is '0. Discourage Time Change'.

SPOT BID RESPONSE TIME BEFORE SHIPMENT START

Collaboration

This parameter determines the cutoff time for spot bid responses based on the start time of the shipment.

STATUS TYPE ENABLES SHIP UNIT ACTUAL

STATUS VALUE ENABLES SHIP UNIT ACTUAL

Order Management

20B

These parameters are used together to define an external status and status value to indicate the ship unit actual status for the ship units of an order release. When an order release has an external status type and value that matches the values defined by these parameters, that order release’s ship units are in “Ship Unit Actual Enabled” status, otherwise, they are in “Ship Unit Actual Not Enabled” status.

You need to add an external status with its possible values into OTM for order releases. For more information, see Status Types.

For example, you could add an external status as“SHIP UNIT ACTUAL” with two possible values “SHIP UNIT ACTUAL ENABLED” and “SHIP UNIT ACTUAL NOT ENABLED”. The default value is “SHIP UNIT ACTUAL NOT ENABLED”. After you add an external status, every new order release you create in OTM will have a status type “SHIP UNIT ACTUAL” with value “SHIP UNIT ACTUAL NOT ENABLED”.

Next, you need to set the parameters to map to the external status type you defined. Set STATUS TYPE ENABLES SHIP UNIT ACTUAL to “SHIP UNIT ACTUAL” and set STATUS VALUE ENABLES SHIP UNIT ACTUAL to “SHIP UNIT ACTUAL ENABLED”. If an order release has matching status type and value to what the parameters are set, this order release’s ship units are Ship Unit Actual Enabled.

Note: Planning parameter set at the domain level will be used rather than the planning parameter used in planning.

You can configure an agent to change order release’s “SHIP UNIT ACTUAL” status to another status. For example, you can change SHIP UNIT ACTUAL ENABLED to SHIP UNIT ACTUAL ENABLED status using a database SQL query. For more information about how to configure an agent to run an SQL query, see Direct SQL Update Utility Agent Action.

The agent actions below look at the ship unit actual status for an order release:

ORDER RELEASE – MOD – EDIT SHIPMENT

ORDER RELEASE – MOD = PROPAGATE CHANGES

STATUS TYPE PREVENTS SHIPMENT MOD

STATUS VALUE PREVENTS SHIPMENT MOD

Shipment Actual

6.4.3

These parameters are used together to define an external status and status value. When a shipment has an external status type and value that matches the values defined by these parameters, that shipment will not be affected by the Order Release - Mod - Propagate Changes agent action.

The first parameter defines the external status type and the second parameter specifies the external status value. When a shipment with a status of ACTUAL has a value ACTUAL_APPLIED, the the Order Release - Mod - Propagate Changes agent action will cease modifying the shipment. If no shipments are found to propagate the changes from the order, the OMD agent will fail.

For example, define an external status as "ACTUAL" and set the initial value to be "ACTUAL_NOT_APPLIED". Then every new shipment will have an "ACTUAL" status of "ACTUAL_NOT_APPLIED". Next, an agent could be configured to change that status to "ACTUAL_APPLIED" when a shipment actual is applied to the shipment. If these parameters are set to "ACTUAL" and "ACTUAL_APPLIED," and the shipment now has that status and value, the shipment will no longer be modified by the Order Release - Mod - Propagate Changes agent action.

STEP TENDER WAIT FOR SERVPROV RESPONSE

Service Provider Assignment

23C

When you perform a step tender, the service provider may receive the tender during their non-working hours. Set this parameter to true to give additional time to the service provider to respond to the step tender. The additional time is the difference between the tender received time and the start time of their business working hours.

For example, if the tender is sent to the service provider at 4 AM and the service provider starts working at 6 AM, considering the step time as one hour, the next tender is sent to the subsequent service provider after a wait time of 3 hours (6 AM - 4 AM + step time).

Note: This parameter works along with the parameters, STEP TENDER WAIT FOR SERVPROV RESPONSE DURATION and PERCENTAGE RESPONSE TIME BEFORE SERVPROV CLOSE, if they are set.

STEP TENDER WAIT FOR SERVPROV RESPONSE DURATION

Service Provider Assignment

23C

When you perform step tender, use this parameter to add the wait time to the step time before sending the tender to the subsequent service provider. If the tender is received in non-working hours and the service provider is closed for the next couple of days, to avoid longer waiting hours, a minimum value between next working hours and the parameter value is set as step time.

For example, if the tender is sent to the service provider at 4 AM and the service provider starts working at 6 AM, considering the step time as one hour, additional time is 3 hours. But, if this parameter value is set to one hour, then the additional time is 2 hours (Parameter value + step time). The system considers minimum additional time which is two hours in this case.

Note: You can use this parameter only when the parameter STEP TENDER WAIT FOR SERVPROV RESPONSE is set to true.

STOP ACTUAL SHIPMENT STOP REDRIVE CONFIG ID

Service Time

6.1

Identifies the Shipment Stop Redrive Logic Configuration data to be used in determining redrive behavior when Actual data is received for a shipment stop

SUBLD CONTAINER OPTIMIZATION CONFIG ID

Ship Unit Building

6.3

Identifies the Container Optimization Config ID. Click the value to see details of the configuration.

TRUCK LOAD AVG MILES PER GALLON

FTI Parameters

6.1

Used for tracking fuel consumption averages on the green dashboard.

Changes to this parameter are not considered until the server restarts. *

TRY MULTIPLE EQUIPMENT IF CAPACITY IS IDENTICAL

Bulk Plan

Indicates whether different equipment can substituted when planning a shipment if the capacity for both types of equipment is the same. Enter Y to allow equipment substitution; otherwise, enter N.

UPPER LIMIT FOR LOW PRIORITY RANGE

Bulk Plan

6.0

Sets the upper limit for the low order priority range. Priority is on order bases, order releases and order movements and affects planning.

UPPER LIMIT FOR MEDIUM PRIORITY RANGE

Bulk Plan

6.0

Sets the upper limit for the medium order priority range. Priority is on order bases, order releases and order movements and affects planning.

USE CAPACITY OVERRIDE BY SERVPROV

Shipment Planning

6.3.5

Determines what objects to consider for matching to a shipment for capacity override lines.
If false (the default), for capacity override lines with a type of "Shipment", only transport mode will be considered when matching to a shipment. For capacity override lines with a type of "Equipment", only the equipment group will be considered when matching to a shipment. Service provider will never be considered.

If true, for capacity override lines with a type of "Shipment", transport mode and service provider will be considered when matching to a shipment. For capacity override lines with a type of "Equipment", equipment group, transport mode, and service provider will be considered when matching to a shipment.

The setting of this parameter will affect Capacity Override by Service Provider.

USE DYNAMIC POOL SELECTION

Multi-tier

If set to True, the dynamic pool selection logic will be used in bulk planning.

If the USE DYNAMIC POOL SELECTION parameter is set to true, the dynamic pooling algorithm is used with the following parameters available for further tuning of the dynamic pooling algorithm.

See also Bulk Plan Cost Based Routing.

USE GREEDY CAPACITY ASSIGNMENT ALGORITHM

Location Capacity

18D

This parameter determines whether to use the greedy algorithm or the optimization algorithm for location capacity. The default is FALSE so the optimization algorithm will be used by default.

USE LEVEL OF SERVICE FOR ARBITRARIES

Rates

6.3.6

When set to true, this enables the use of level of service and supports slow/fast arbitrary functionality. Levels of service are used on rate offering lane special services.

The default is false, which disables level of service and slow/fast arbitrary functionality.

USE MULTIPASS MULTISTOP

Multistop

6.0

Determines if the multi-pass multi-stop consolidation based on priority is executed. If True, and the Priority in Use parameter is also True, the multi-stop logic will be invoked multiple times, one for each priority. The basic assumption of this approach is that only limited or constrained resources are available for the given set of orders (order releases/order movements)to be planned. Under this scenario, first the shipments that contain high priority orders are considered, then medium priority then low priority will be consolidated. This ensures the least number of resources is needed to handle high and medium priority orders. This approach leads to poor solution quality when there is no real resource crunch.

USE OR ORDER CONFIG FOR SSU CALCULATION

S Ship Unit Calculation

6.3

When set to True, the order configuration defined on an order release will be used when calculating shipment ship units and shipment ship unit lines.

When set to False, the order configuration defined in a parameter DEFAULT ORDER CONFIG FOR SHIPMENT SHIP UNIT will be used when calculating shipment ship units and shipment ship unit lines.

USE ORDER SERVPROV IF ORDER SELL SERVPROV NULL

Order Management

If this parameter is set to True and the sell side service provider is null, the buy side service provider on the order release will be copied to the sell side service provider. This applies to the buy and sell service provider in the same manner.

USE PRIORITY IN BUNDLING

Bulk Plan

6.0

Determines if the priority influences order bundling during planning. If time windows of order movements and their corresponding commodities are compatible, order movements would be bundled together in a single bundle. If this is set to true, priority will be considered so if time windows and commodities are compatible but there are two different priorities, the order movements will be bundled in two different bundles based on their priorities.

USE PRIORITY IN CONOPT SORTING

Container Optimization

6.0

Determines if the priority influences sorting in container optimization. The list of ship units that are given as an input to container optimization are sorted based on container optimization metrics such as weight and volume. Priority is an additional criterion while sorting these ship units. If priority is true, the sorting happens by priority. If the priorities are equal, they are then sorted by ID. This change is effective in the following algorithms:

Quick Packing algorithm

Legacy algorithm

Enumerative algorithm

The following are not affected by the priority setting: Multi-container MIP algorithm and Single Container MIP algorithm.

This parameter, along with the Priority In Use parameter, must be set in order to use ship unit priority for equipment packing.

USE PRIORITY IN COST SAVINGS

Multistop

6.0

Determines if the priority influences the multi-stop cost savings calculation. Priority is on order bases, order releases and order movements. Only in savings algorithm (Concurrent, Sequential and Column Generation Iterations) will priority will have an impact on how the shipments are paired and selected. The other two algorithms remain unaffected. Savings algorithm works by evaluating a pair of shipments to see whether combining them will provide savings over leaving them uncombined.

In order for this parameter to be effective:

- bundling must be turned off, (set MAXIMUM WEIGHT PER BUNDLE and/or MAXIMUM VOLUME PER BUNDLE to zero to turn it off)

In addition, the following other parameters need to be set as follows:

- USE MULTIPASS MULTISTOP turned off,

- MULTISTOP COST SAVING CHECK TYPE set to:

2.Perform cost savings check at end of process

- MULTISTOP DISABLE SAME OD PAIRING set to true

Also, see th eproperties:

Property glog.business.consolidation.multistop.prioritysavingsalgorithm

Property glog.business.consolidation.multistop.priorityagressiveness

Note: This will only have an impact if the MULTISTOP CONSOLIDATION ALGORITHM TYPE parameter is set to Concurrent Savings or Sequential Savings.

USE PRIORITY IN SPA

Service Provider Assignment

6.0

Determines if the priority influences service provider assignment. Priority is on order bases, order releases and order movements.

USE RATE PREFERENCE

Bulk Plan

The USE RATE PREFERENCE parameter has Oracle Transportation Management use your defined Rate Preferences when building shipments. If you do not set the parameter, Oracle Transportation Management will disregard your Rate Preference definitions. Preferred rates will not be checked in international rate inquiry when parameter is set to false.

The valid values are:

0. No Rate Preferences
1. Preferred Only - will only select available preferred service providers. Non-preferred service providers will not be considered.
2. Preferred Rates if Available - will select the best from the preferred service providers if any are available. If there are none available, then it selects an available non-preferred service provider. Non-preferred rates will be included in case the preferred rates in any given transport mode is later found to be infeasible for whatever reason.

USE SINGLE SERVICE PROVIDER RULE

Service Provider Assignment

20C

This specifies if and how the single service provider rule will be used during service provider assignment for location routing.

0. Do not use: In this case, single-service-provider rule will not be used. This is the default.

1. By day: In this case, a single service provider will be assigned to all the shipments visiting a single-service-provider location on a given day. If the location already has shipments planned with one service provider on a given day, the same service provider will be reselected in subsequent planning for other shipments visiting the location on the same day. If more than one service provider is already used at the location on a given day, OTM will optimally select one of those service providers.

2. By bulk plan: In this case, a single service provider will be assigned to all the shipments visiting a single-service-provider location under one bulk plan, regardless of what service providers are previously assigned going into that location.

VALIDATE EQUIPMENT BY RATES

Bulk Plan

5.5 CU4

Default value is TRUE. If the value is set to true, after equipment groups are selected from orders (order releases/order movements), leg and locations, they will be further validated by rates before calling container optimization. That is, equipment groups without rates will be disregarded and will not be sent to container optimization.

Set it to false to disable the validation process to improve performance.

VAT CONFIGURATION ID

Settlement

A VAT CONFIGURATION ID is required in order to calculate European VAT.

VERBOSE ROUTE EXECUTION SHORTEST PATH LOGGING ON

Cooperative Route Planning and Execution

5.5 CU4

Determines whether shortest path logic will log in detail during the Route Execution column generation.

Note: This can generate so much logging that it can potentially bring down the system.

VIEW FLEET BULK PLAN RESULTS LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Fleet Bulk Plan Results. Default is FLEET BULK PLAN RESULTS.

VIEW INBOUND SHIPMENTS LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Inbound Shipments. Default is VIEW SHIPMENTS.

VIEW ORDER RELEASES LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Order Releases. Default is VIEW ORDER RELEASES.

VIEW OUTBOUND SHIPMENTS LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Outbound Shipments. Default is VIEW SHIPMENTS.

VIEW SHIPMENTS LAYOUT ID

Action

6.4.3

Specify the enhanced workbench layout to use for the action Map Shipments. Default is VIEW SHIPMENTS.

VOLUME PADDING FACTOR BETWEEN STOPS

Multistop

This parameter represents the amount of volume capacity to reserve to separate items over consecutive stops. This space will be considered as lost or wasted space. The formula for total amount of padding or wastage is given by (number of pickup stops + number of delivery stops - 2) * VOLUME PADDING FACTOR BETWEEN STOPS. For example, if this parameter is 10 CU FT, and the shipment contains 1 pickup stop and 3 delivery stops, the total padding is calculated as (1 + 3 - 2) * 100, which equates to 20 CU FT. The default value is zero (no padding).

VOUCHER VAT TAX TYPE

Settlement

This differentiates between European VAT and provincial. The valid options are:

EURO_VAT

PROVINCIAL

VOYAGE BEFORE ARRIVAL OR AFTER DEPARTURE

Voyage Schedule

23.1

This parameter is used to decide whether to search the voyage schedules before arrival or after departure from a specific date. Possible values are:

- Before Arrival
- After Departure (default value)

VOYAGE EXTERNAL ALL ROUTES

Voyage Schedule

23.1

This parameter indicates whether all or only the best voyages should be requested. By default, the parameter value is set to false and the application will fetch the best voyages. If you set the parameter value to true, the application will fetch all voyages.

VOYAGE LOOKUP NUM OF WEEKS

Voyage Schedule

23.1

In the case of the parameter "VOYAGE BEFORE ARRIVAL OR AFTER DEPARTURE" is "After departure", this parameter is used to define how many weeks to look ahead from the mentioned date, when it is "Before Arrival" how many weeks to look backward from the mentioned date. Possible values are:

- 2 weeks (default value)

- 4 weeks

- 6 weeks

WA MIN SHIPMENTS FOR MILESTONE COLLECTION

Work Assignment Planning

19B

The minimum number of shipments needed for milestone collection. If you set this parameter to 0 then no milestones are collected. If you only have a small number of shipments, set this parameter to 1.

Default is 10.

WA MIN TIME BETWEEN MILESTONE UPDATES

Work Assignment Planning

19B

The minimum amount of time between milestone progress updates.

WORK ASSIGNMENT MILESTONE ERROR SEVERITY

Work Assignment Planning

19B

Determines the minimum severity of work assignment planning milestone errors for database collection. Work assignment planning milestone errors are collected if the severity is at least the value you specify here. Values are: WARNING, ERROR, EXCEPTION, and NONE.

WEIGHT AND VOLUME TYPE

Shipment Quantities

6.0

Parameter to allow you to set a default value (Gross or Net) for the Shipment Quantities Weight/Volume Type field.

Default = Gross

WEIGHT FOR HIGH PRIORITY

Bulk Plan

6.0

Indicates the relative significance to be associated with a high priority order release/order movement and is used to determine the weighted priority of a shipment.

Valid values are 1-100. The default is 100.

WEIGHT FOR LOW PRIORITY

Bulk Plan

6.0

Indicates the relative significance to be associated with a medium priority order release/order movement and is used to determine the weighted priority of a shipment.

Valid values are 1-100. The default is 1.

WEIGHT FOR MEDIUM PRIORITY

Bulk Plan

6.0

Indicates the relative significance the weight to be associated with a low priority order release/order movement and is used to determine the weighted priority of a shipment.

Valid values are 1-100. The default is 50.

WEIGHT PADDING FACTOR BETWEEN STOPS

Multistop

6.3

This parameter represents the amount of weight capacity to reserve to separate items over consecutive stops. This space will be considered as lost or wasted space. The formula for total amount of padding or wastage is given by (number of pickup stops + number of delivery stops - 2) * WEIGHT PADDING FACTOR BETWEEN STOPS. For example, if this parameter is 100 LBS, and the shipment contains 1 pickup stop and 3 delivery stops, the total padding is calculated as (1 + 3 - 2) * 100, which equates to 200 LBS. The default value is zero (no padding).

* The OAS session does not log out when a TI user logs out of the system. The changes to these parameters do not get refreshed. Complete the following steps to get the latest values reflected.

Right-click on Dashboard menu under Transportation Intelligence and select "Open in new window".
Change the URL from http://<example.com:Port>/analytics/saw.dll?Dashboard to http://<example.com:Port>/analytics/saw.dll?Logoff and press Enter.

This kills the present session and when you click Dashboard again the new values for the Green Dashboard Emission Parameters are reflected.

**Indicates that this parameter was a property prior to being a parameter.

List of Parameters

Related Topics