Search Results service_starting_delay

Overview

APPS.OE_MTL_SYSTEM_ITEMS_V is a view in the Oracle E-Business Suite Order Management (ONT) product schema. In ETRM 12.2.2 the object is registered with a status of VALID, but its product documentation categorically states "No longer used." This designation reflects the historical role of the view: in earlier releases it exposed a filtered projection of the master item definition, restricted to items enabled for customer order processing, so that Order Management forms, reports, and concurrent programs could resolve item validation without querying the full MTL_SYSTEM_ITEMS table directly. By 12.1.1 and 12.2.2 Oracle had consolidated order-entry item validation onto the multi-org compliant MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL pair and the secured MTL_SYSTEM_ITEMS_V view, leaving OE_MTL_SYSTEM_ITEMS_V as a backward-compatibility object that remains compiled in the database but is no longer referenced by seeded ONT code.

Because the object is documented as unused, it must be treated as deprecated. Custom integrations, Discoverer workbooks, or legacy reports that still reference it will continue to parse and execute, but Oracle does not guarantee its content, columns, or even its continued existence in future releases.

Underlying Base Objects

The documented referencing metadata for the view lists a single base object: MTL_SYSTEM_ITEMS, accessed through a synonym. The view text confirms this with a simple pass-through projection — every column in the SELECT list corresponds to a column on the item master, including INVENTORY_ITEM_ID, ORGANIZATION_ID, SEGMENT1 through SEGMENT20, and the various enabled flags. There are no joins to MTL_ITEM_CATEGORIES, MTL_PARAMETERS, or the order-management setup tables in the documented definition.

This is significant for the 12.1.1 and 12.2.2 file systems, where MTL_SYSTEM_ITEMS is retained only as a synonym or compatibility layer. The authoritative item master in these releases is MTL_SYSTEM_ITEMS_B (base attributes) joined with MTL_SYSTEM_ITEMS_TL (translated descriptions). The view therefore does not automatically inherit the multi-org item security or translation logic applied by MTL_SYSTEM_ITEMS_V, and it carries no organization access control of its own. Where the synonym resolves to the _B table, description and long-description columns may be unavailable or stale.

Key Columns

• INVENTORY_ITEM_ID / ORGANIZATION_ID — the composite key identifying an item within a specific inventory organization; the natural join condition for any query against inventory or order tables.
• SEGMENT1 – SEGMENT20 — the item key flexfield segments, stored generically; SEGMENT1 is conventionally the item number.
• CUSTOMER_ORDER_FLAG / CUSTOMER_ORDER_ENABLED_FLAG — indicate whether the item is orderable and whether the orderable attribute is currently enabled.
• SHIPPABLE_ITEM_FLAG, INTERNAL_ORDER_FLAG, SERVICE_ITEM_FLAG, INVENTORY_ITEM_FLAG — item type and usage flags consumed by order-entry validation.
• SO_TRANSACTIONS_FLAG, STOCK_ENABLED_FLAG, BOM_ENABLED_FLAG, BUILD_IN_WIP_FLAG — supply and manufacturing capability indicators, including the flag that governs WIP supply behavior.
• UNIT_OF_ISSUE, ALLOW_SUBSTITUTE_RECEIPTS_FLAG, ALLOW_UNORDERED_RECEIPTS_FLAG, RETURNING_FLAG-equivalents such as RETURNABLE_FLAG — receipt and return processing controls.
• ATTRIBUTE1 – ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield storage carried through from the item master.
• ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — date-range enablement used to determine whether an item is active at a given point in time.

Common Use Cases and Queries

Given the "no longer used" status, the recommended approach is to migrate any dependent SQL to MTL_SYSTEM_ITEMS_V. A legacy query such as the following may still be encountered in custom reports:

SELECT organization_id, segment1, description, customer_order_flag, wip_supply_type
FROM apps.oe_mtl_system_items_v
WHERE organization_id = :org_id
AND customer_order_enabled_flag = 'Y';

Note that the column name the user searched for, wip_supply_subinventory, is not present in the documented view text. WIP supply information is held on the item master as WIP_SUPPLY_TYPE, WIP_SUPPLY_SUBINVENTORY, and WIP_SUPPLY_LOCATOR_ID, and is exposed through MTL_SYSTEM_ITEMS_B. The absence of these columns from the documented OE view text is consistent with its deprecated, narrow scope. Analysts seeking supply subinventory values for a given item should query MTL_SYSTEM_ITEMS_B or the supported MTL_SYSTEM_ITEMS_V, for example:

SELECT msi.organization_id, msi.segment1, msi.wip_supply_type,
       msi.wip_supply_subinventory
FROM apps.mtl_system_items_b msi
WHERE msi.organization_id = :org_id
AND msi.segment1 = :item_number;

In summary, OE_MTL_SYSTEM_ITEMS_V should be regarded as a deprecated compatibility view over MTL_SYSTEM_ITEMS within the ONT schema. New development, and any correction of existing WIP supply or subinventory reporting, should target the supported multi-org item views in the INV schema.