Order Release Status

Order releases may be assigned the following status types:

• BILLED: entities the billing state of the order release.
• ORDER DELIVERED: Suppose the order is planned on 3 shipments on the last leg. If neither shipments is ENROUTE_COMPLETED, this order will have a status of DELIVERED-NOT_STARTED. If one of the shipments is ENROUTE_COMPLETED, this order will have a status of DELIVERED-PARTIAL. If all shipments are ENROUTE_COMPLETED, this order will have a status of DELIVERED-COMPLETED. This  status type and value require that an agent be setup to properly set the Order Delivered status values.
• ORDER MODIFIED: is assigned to a new order release to indicate when modifications are received to the order base that was used to create the order release. The status value of ORDER MODIFIED_DEINED is assigned as a result of running an agent with the Order Base - Mod - No Processing action. ORDER MODIFIED_ACKNOWLEDGED is set when you use the Modification Acknowledge action.
• OR_HD_LOAD_STATUS: This is used for Transportation Intelligence only. It determines if the ETL process should extract this data and load these objects and all related data to the HDOWNER schema for Transportation Intelligence (TI) (See Data Flow to TI). The status is not ready to load when the order release is created. If you have an active agent, once the status is changed to ready to load, the ETL process will run.
• ORDER RELEASE GUARANTEED DELIVERY: Guaranteed Delivery is a special type of notification where the receiver sends a response back to the sender indicating whether the received message can or has been processed (reserved for future use).
• PLANNING: identifies the planning state of  the order release from a buy perspective. Some, but not all, of the status values for this status type are:
• • UNSCHEDULED: This value is assigned when the order release has been planned on a shipment/order movement and then the order has been unassigned for whatever reason. You can plan any order release with the status value again.
  • PLANNED-FAILED: This value is assigned when Oracle Transportation Management cannot create a shipment/order movement for the order release according to the rules of shipment planning logic. You can plan any order release with the status value again.
  • PLANNED-FINAL: Order release that has been planned on a shipment or order movement. Once an order release is assigned this status you cannot build another direct shipment for the release unless you use the Unassign Order  action to remove the order release from the existing shipment. However, order releases with this status value can be re-planned in bulk planning.
  • PLANNED-HOLD: This status prevents the order release from being planned.
  • EXECUTED-PARTIAL: This status value is set when some of the shipments built from this order are moved to execution. You cannot build another shipment for this order release unless you withdrawal the tender on the shipment that was originally build from this order and unassign it.
  • EXECUTED-FINAL: This status value is set when all of the shipments built from this order are moved to execution. You cannot build another shipment for this order release unless you withdrawal the tender on the shipment that was originally build from this order and unassign it.
  • ITEM OUT OF DATE: When the property glog.order.newOrderReleaseLine.checkItemEffectiveDates is set to true, this status is set on a standalone order release when a new order release line is created and its Item out of date. This condition exists if the early pickup date on the order is outside the packaged item effective and expiration date range. You cannot plan the order release with an out of date item.
• PLANNING_SELL: Identifies the planning state of the order release from a sell perspective. The PLANNING_SELL status values are the same as PLANNING except that they assigned as a result of planning sell shipments for the order release.
• QUANTITY VALIDATION DESTINATION: Same as for SOURCE below, but the location checks will compare the order destination to each ship shipment's destination and look for shipments with a destination location with a SHIP FROM/SHIP TO role. This status is set by the Determine Quantity Validation agent action.
• QUANTITY VALIDATION SOURCE: These statuses are set by the Determine Quantity Validation agent action:
• • MATCH: If ALL of the shipments have a BOL_ACTUALS status of ENTERED_TRANSMISSION and the total shipment ship unit quantity is equal to the order release ship unit quantity, then the order release status QUANTITY VALIDATION SOURCE is set to MATCH.
  • NOT STARTED: If NONE of the shipments have a BOL_ACTUALS status of ENTERED_TRANSMISSION the order release status QUANTITY VALIDATION SOURCE should be set to NOT STARTED.
  • OVER: If ALL of the shipments have a BOL_ACTUALS status of ENTERED_TRANSMISSION and the (total shipment ship unit quantity + ship unit quantity on the unplanned order movements) > order release ship unit quantity, the order release status QUANTITY VALIDATION SOURCE is set to OVER.
  • PARTIALLY LOADED: If only some of the shipments have a BOL_ACTUALS status of ENTERED_TRANSMISSION, the order release status QUANTITY VALIDATION SOURCE is set to PARTIALLY LOADED.
  • UNDER: If ALL of the shipments have a BOL_ACTUALS status of ENTERED_TRANSMISSION and the (total shipment ship unit quantity + ship unit quantity on the unplanned order movements) < order release ship unit quantity, the order release status QUANTITY VALIDATION SOURCE is set to UNDER.

You can define which statuses are displayed for each user by creating a status type filter and then using Manage User Access to associate the User Access Type of Status Type Filter with a particular user. When you have done so, a small arrow appears near the top of the Status window. Clicking the arrow displays all of the statuses, not just the ones displayed by the filter. Bold statuses are ones that appear in the filter, and regular ones are statuses hidden by the filter.