Search Results oe_items_ord_mv




Overview
Explore in AI Chat

Overview

OE_ITEMS_ORD_MV is an APPS-owned view within the Oracle Order Management (ONT) module, valid in both EBS 12.1.1 and 12.2.2. It is built directly on the materialized view OE_ITEMS_MV and, as its documented description states, "displays all the Orderable items after taking the Orderability Rules into account." In practical terms, the view answers the runtime question: given the current operating unit, customer, ship-to, order type, and sales context, which items may legitimately be entered on an order line?

The view is therefore a reporting and integration surface rather than a transactional table. Order Management's item validation engine consults this orderability logic when a user or interface attempts to add an item to an order. Downstream consumers — custom reports, order import interfaces, pricing engines, and configurators — can query OE_ITEMS_ORD_MV to reproduce the same visibility rules that the Order Management forms apply.

Underlying Base Objects

The documented base objects referenced by the view are:

The view joins OE_ITEM_ORDERABILITY to OE_ITEMS_MV and constrains item validation to the operating unit's organization and the user's language (LANGUAGE = USERENV('LANG')). Because the OE_ITORD_UTIL functions are session-context dependent, results vary by the environment in which the query executes.

Key Columns

Common Use Cases and Queries

Typical applications include validating whether an item is orderable for a specific customer before loading an order, diagnosing why an item does not appear in the Order Management item list, and reconciling orderability rule setups.

SELECT ITEM, ITEM_DESCRIPTION, INVENTORY_ITEM_ID, ORGANIZATION_ID
FROM   APPS.OE_ITEMS_ORD_MV
WHERE  INVENTORY_ITEM_ID = :p_inventory_item_id;

To list all orderable items currently visible for a given sold-to customer:

SELECT DISTINCT ITEM, ITEM_DESCRIPTION
FROM   APPS.OE_ITEMS_ORD_MV
WHERE  SOLD_TO_ORG_ID = :p_sold_to_org_id
ORDER  BY ITEM;

Because the view invokes OE_ITORD_UTIL session functions, queries should be executed within the appropriate application context (for example, initialized via FND_GLOBAL) so that the operating unit, customer, and order-type values resolve correctly. For best performance, filter on INVENTORY_ITEM_ID or SOLD_TO_ORG_ID, and avoid unbounded full scans against OE_ITEMS_MV, which can be large. Note that references in older code to the single-table name OE_ITEMS_ORD_MV differ from OE_ITEMS_MV; the former applies rule filtering, while the latter does not.