Results for “whse_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMI_AAC_ORDER_NUM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and delivered under the GMI (Process Manufacturing Inventory) product family. Its documented purpose is to expose orders that have reached both the BOOKED and PICK RELEASED states and that still contain open move order lines. In practical terms, the view returns a distinct list of sales order numbers together with the warehouse code from which the associated shipment is being staged.

Because it joins order management, shipping, and process manufacturing inventory tables into a single denormalized result set, the view serves as a lightweight reporting and integration surface. Rather than requiring report authors or interface developers to reconstruct the multi-table join logic themselves, the view encapsulates the business condition of interest: an order that is progressing through fulfillment but whose move order lines have not yet been fully transacted. This makes it suitable for dashboards, concurrent programs, and inbound/outbound interface logic that need to identify "in-flight" pick-released orders without querying the base tables directly.

Underlying Base Objects

The view is defined over five referenced base objects, all accessed through APPS synonyms. The shipping leg is supplied by WSH_DELIVERY_DETAILS, which links delivery details to inventory move order lines. The process manufacturing inventory contribution comes from IC_TXN_REQUEST_LINES (the move order lines, filtered on RELEASED_STATUS = 'S' to indicate pick release) and IC_WHSE_MST (the warehouse master, providing WHSE_CODE and the organization identifier). Order information is drawn from OE_ORDER_HEADERS_ALL (order number and header identifier) and OE_ORDER_LINES_ALL (line-level flow status and ship-from organization).

The internal inline view joins WSH_DELIVERY_DETAILS to IC_TXN_REQUEST_LINES on MOVE_ORDER_LINE_ID = LINE_ID with RELEASED_STATUS = 'S', yielding the SOURCE_HEADER_ID and SOURCE_LINE_ID pair that maps a delivery detail back to its originating order line. The outer query then correlates those identifiers to OE_ORDER_LINES_ALL and OE_ORDER_HEADERS_ALL and further constrains OL.FLOW_STATUS_CODE to 'AWAITING_SHIPPING'. Finally, IC_WHSE_MST is joined on MTL_ORGANIZATION_ID = OL.SHIP_FROM_ORG_ID so each returned row carries the correct warehouse code. A SELECT DISTINCT eliminates duplication arising from the multi-table join.

Key Columns

• ORDER_NUMBER — the order number from OE_ORDER_HEADERS_ALL, identifying the booked sales order that has open move order lines.
• WHSE_CODE — the warehouse code from IC_WHSE_MST, indicating the inventory organization (ship-from warehouse) associated with the order line.

These are the only two columns projected by the view. All filtering logic is embedded in the definition, so consumers receive a pre-qualified result set with no further predicates required for the primary business condition.

Common Use Cases and Queries

Typical scenarios include fulfillment status reporting, warehouse workload analysis, and interface extraction of orders awaiting shipment confirmation. A basic listing retrieves all qualifying orders and their warehouses:

• SELECT order_number, whse_code FROM apps.gmi_aac_order_num_v;
• SELECT whse_code, COUNT(*) FROM apps.gmi_aac_order_num_v GROUP BY whse_code;
• SELECT order_number FROM apps.gmi_aac_order_num_v WHERE whse_code = :p_warehouse;

Because the view already enforces BOOKED, PICK RELEASED, AWAITING_SHIPPING, and open move order line conditions, reports can treat its output as a ready-made worklist. Note that the view exposes no order line or quantity detail; where line-level granularity is required, the underlying OE_ORDER_LINES_ALL and IC_TXN_REQUEST_LINES tables must be queried directly. As with any APPS view, access should be granted through standard responsibility and menu configuration rather than direct grants, and the view should not be modified since it is an Oracle-delivered object.