Search Results awaiting_shipping




Overview
Explore in AI Chat

Overview

GMI_AAC_ORDER_NUM_V is an APPS-owned database view in Oracle E-Business Suite, documented through ETRM 12.2.2 and applicable to 12.1.1 and 12.2.2 environments. Its purpose is narrow and operational: it returns a distinct list of sales order numbers together with the warehouse code associated with those orders, but only for order lines that are in the AWAITING_SHIPPING flow status and that are tied to a released move-order transaction sourced from the warehouse management (WMS) or inventory transaction request flow. The view is therefore not a general-purpose order report; it is a targeted join that surfaces orders that are staged for shipment and already linked to internal move-order activity. In practice it supports reconciliation, warehouse-facing reporting, and lightweight integration queries where the "awaiting shipping" state is the driver.

The name prefix "GMI_AAC" reflects its association with the process manufacturing / Oracle Process Manufacturing (GMI) and advanced application configuration lineage, while the "ORDER_NUM" suffix confirms that the primary exposed business identifier is the order number rather than internal IDs.

Underlying Base Objects

The view is defined over five documented base objects, all presented to APPS through synonyms:

Structurally, the view builds an inline derived set (aliased SHP) by joining WSH_DELIVERY_DETAILS and IC_TXN_REQUEST_LINES on MOVE_ORDER_LINE_ID = LINE_ID while restricting RELEASED_STATUS = 'S'. That set returns SOURCE_HEADER_ID and SOURCE_LINE_ID pairs. The outer query then joins these to order lines and headers on matching header and line IDs, filters FLOW_STATUS_CODE = 'AWAITING_SHIPPING', and resolves the warehouse code by joining IC_WHSE_MST on MTL_ORGANIZATION_ID = OL.SHIP_FROM_ORG_ID. The final result is de-duplicated with DISTINCT.

Key Columns

The view projects only two columns:

  • ORDER_NUMBER (from OE_ORDER_HEADERS_ALL.ORDER_NUMBER) — the user-facing sales order identifier.
  • WHSE_CODE (from IC_WHSE_MST.WHSE_CODE) — the warehouse code of the ship-from organization associated with the order line.

Because the SELECT list is so compact, the view is intended as a lookup or validation source rather than a transactional extract. The filtering logic embedded in the definition means ORDER_NUMBER values appear only when the order line is awaiting shipping and a released move order and delivery detail exist for the same source line.

Common Use Cases and Queries

The most direct usage is retrieving the set of orders currently awaiting shipping and their warehouses:

  • Join to other order or delivery views on ORDER_NUMBER or WHSE_CODE to enrich reporting without re-implementing the AWAITING_SHIPPING and move-order logic.
  • Use as a validation list to confirm that a given order number is eligible in the shipping pipeline for a specific warehouse.
  • Feed lightweight dashboards or extracts listing warehouse-staged orders.

Example queries:

  • SELECT order_number, whse_code FROM apps.gmi_aac_order_num_v;
  • SELECT order_number FROM apps.gmi_aac_order_num_v WHERE whse_code = :warehouse;
  • SELECT v.order_number, v.whse_code FROM apps.gmi_aac_order_num_v v, apps.oe_order_headers_all h WHERE v.order_number = h.order_number;

Because the definition filters on flow status and released move orders, results reflect the live state of the shipping and transaction-request flow at query time. The view carries no stated bind variables and is safest treated as a read-only reporting object under the APPS schema.