Unassign Order Buy/Sell

This action is accessed via the Order Release Manager (accessed via Order Management > Order Release > Order Release). Click Actions. Then select Order Management > Unassign Order Release > Unassign Order Buy or Sell.

Use this action to unassign an order release from a shipment and automatically delete any related order movements that exist for the order. Appropriate order release statuses are updated as a result of this action. This action takes all lines from their packed ship unit. If all lines for a ship unit are deleted, then the ship unit will also be deleted.

Note: If you wish to use this action and the shipment has a status of ENROUTE_ENROUTE, set the IGNORE ACTUAL TIMES DURING ADD OR UNASSIGN ORDER parameter to true.

When a shipment has only no-activity stop, the shipment should be removed. The exceptions are:

• schedule instance shipment
• consol shipment
• Shipment is_permanent flag is true

The property glog.business.unassignOrders.loadLimitedGraph controls how many shipments and order movements are brought in during the unassign order process. When true, OTM will bring in only the shipments that actually have the to-be-unassigned order releases and the order movements on those shipments. Note that only these shipments will be re-driven. This is recommended only when you are sure that no other shipments need to be re-driven as the result of this action. The default is false.

The property glog.business.consolidation.bulkplan.relaxOrderBundlePickupWindow (when true),allows an order release with the date emphasis set to BOTH and a pickup window in the past to be unassigned.

The property glog.business.orderActions.unassign.redriveShipmentWithOptimalStartTime determines if, when unassigning an order release, OTM will redrive the partial shipments with the original shipment's start time that is being unassigned (default is false, existing default behavior). When set to true, OTM will redrive the shipments using the optimal start time in the unassign process.

Fleet Shipments

This action also works for fleet shipments (shipments with fleet resources assigned) with some differences.

If the order release being removed is the only order release for the stop, the stop might need to be deleted. However, the stop will not be deleted when a fleet resource activity is being performed on the stop. For example, if the order release pickup is also the driver start location, this action will keep the stop and change the stop type from pickup to NFR (non-freight related).

If this action would result in removal of the last freight stop, this action will fail if:

• the last freight stop = the last shipment stop and the driver assigned to this shipment has a subsequent shipment assignment
• the last freight stop has a subsequent equipment drop-off

If this is the last order release on the shipment, it cannot be unassigned. You need to run the appropriate unassign fleet resource action first.

As a result of this unassignment, the shipment and it's downstream shipments will be redriven.

In-transit Shipments

Order releases of stops already visited/actualized cannot be unassigned.

The sequence of the actualized stop remains fixed after the unassign action.

If only the arrival time has been actualized, the order releases picked up on that stop can be unassigned. However, if that is the only order release on the stop, and unassign would remove the stop, the action will fail since the stop has already been visited.

As a result of this unassignment, the shipment and it's downstream shipments will be redriven.

The property glog.shipmentstatus.maxQueryResults controls the maximum number of in-transit shipment records. This is used from the stock keeping unit (SKU) data to navigate over to in-transit shipments.

Work Assignments

The Unassign Order - Buy action unassigns orders from shipments which belong to a work assignment. When the Status value of the work assignment is WA_DRIVER_ASSIGNMENT_ASSIGNED, orders will not be unassigned.

Note: During bulk plan, same process will be followed to unassign orders from shipments which belong to a work assignment.

When you run the Unassign Order - Buy action:

• Entire work assignment - all orders on all shipments on a work assignment will be unassigned and all shipments will be deleted. OTM will disband the entire work assignment.
• Entire shipment - all orders on a shipment will be unassigned and few shipments which belong to a work assignment are deleted but not all shipments of the work assignment. The work assignment with remaining shipments will be updated.

Note: If number of remaining shipments in the work assignment is less than the WA MIN SHIPMENTS IN TOUR logic parameter, then the work assignment feasibility code is set to WORK_ASSIGNMENT_LOGIC_PARAMETER_INFEASIBLE.

• Partial shipment - few orders will be unassigned from a shipment which belongs to a work assignment but not all orders of the shipment. Therefore, the shipment will not be deleted. The work assignment will be updated.

Let's look at the following example:

Consider there are two work assignments such as WA1 which consists of two shipments. Each shipment has one order release, Order A is on one shipment and Order B is on another. Similarly WA2 consists of two shipments, each has one order release, Order C and Order D.

When you select Order A and Order B  from the WA1 work assignment and run the Unassign Order – Buy action, OTM deletes two shipments and disbands the entire WA1 work assignment.

When you select Order A from WA1 work assignment and Order C from WA2 work assignment and run the Unassign Order – Buy action, OTM deletes one shipment from each work assignment and updates the two work assignments WA1 and WA2.