Search Results stock_enabled_flag

Overview

The APPS.EAM_REQUIREMENT_OPERATIONS_V view is an Enterprise Asset Management (EAM) reporting object that exposes material requirement operations associated with EAM work orders. It is defined as a view on top of WIP_REQUIREMENT_OPERATIONS, extended with additional columns needed to support the processing of one-off (non-inventoried, directly-procured) items. Because EAM work orders are executed as WIP entities in Oracle EBS, requirement lines for maintenance activities are physically stored in the WIP requirement operations table; this view presents them in a consolidated, reporting-friendly form.

The view is registered in the APPS schema and is marked VALID in ETRM. Its primary role is to serve as the data source for requirement/materials reporting and integration related to EAM work orders — for example, material pick lists, shortage analysis, requisition-driven material planning, and cost or quantity tracking per operation. It is not an entity for direct DML; it is consumed as a read-only query surface.

Underlying Base Objects

The documented referenced base objects are:

• WIP_REQUIREMENT_OPERATIONS_V (WROV) – a view supplying the requirement operation header attributes (item, UOM, organization, entity, operation sequence, quantities, dates, flex attributes).
• WIP_REQUIREMENT_OPERATIONS (WRO) – the base requirement operations table, joined by ROW_ID = ROWID, contributing supply/vendor-related columns (VENDOR_ID, UNIT_PRICE, SUGGESTED_VENDOR_NAME).
• MTL_SYSTEM_ITEMS (MSI) – the item master, joined on ORGANIZATION_ID, providing item-level attributes such as the STOCK_ENABLED_FLAG.
• EAM_MATERIAL_ALLOCQTY_PKG – a PL/SQL package invoked as a scalar function to compute the allocated quantity for a given work order, operation, organization and item.

The join condition is WROV.ROW_ID = WRO.ROWID AND WRO.ORGANIZATION_ID = MSI.ORGANIZATION_ID, meaning each requirement operation row is enriched with item-master and vendor/pricing data for the same organization.

Key Columns

• ROW_ID – the row identifier linking the requirement operation to its base record.
• INVENTORY_ITEM_ID – the required item; RECONCILED via MTL_SYSTEM_ITEMS.
• STOCK_ENABLED_FLAG – from MTL_SYSTEM_ITEMS; the flag of central interest to the user’s search. It distinguishes stocked (inventoried) items from non-stocked/expense items. For EAM one-off items the flag is typically N, driving direct-procurement behavior.
• CONCATENATED_SEGMENTS / ITEM_DESCRIPTION / ITEM_PRIMARY_UOM_CODE – descriptive item identity and UOM.
• INVENTORY_ASSET_FLAG, LOCATION_CONTROL_CODE, RESTRICT_SUBINVENTORIES_CODE, RESTRICT_LOCATORS_CODE – inventory control attributes.
• WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID, LINE_ID – work order/operation context.
• WIP_SUPPLY_TYPE / WIP_SUPPLY_MEANING – how the requirement is supplied (push, pull, etc.).
• DATE_REQUIRED, REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN, QUANTITY_PER_ASSEMBLY – demand and fulfillment quantities.
• SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, MRP_NET_FLAG, MPS_REQUIRED_QUANTITY, MPS_DATE_REQUIRED – supply and planning attributes.
• ALLOCATED_QUANTITY – computed by EAM_MATERIAL_ALLOCQTY_PKG.ALLOCATED_QUANTITY(WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, INVENTORY_ITEM_ID).
• RELEASED_QUANTITY, AUTO_REQUEST_MATERIAL – release and auto-request control.
• SUGGESTED_VENDOR_NAME, VENDOR_ID, UNIT_PRICE – sourcing and pricing from WIP_REQUIREMENT_OPERATIONS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1..15 – descriptive flexfield values.

Common Use Cases and Queries

Typical applications include materials requirement reporting for EAM work orders, distinguishing stocked from non-stocked items, shortage/availability checks, and vendor/pricing lookup for planned one-off purchases.

Example: list requirements with stock status for an organization.

• SELECT ROW_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, STOCK_ENABLED_FLAG, REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN, ALLOCATED_QUANTITY FROM APPS.EAM_REQUIREMENT_OPERATIONS_V

Example: non-stocked (one-off) items on open requirements.

• SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, CONCATENATED_SEGMENTS, REQUIRED_QUANTITY, QUANTITY_OPEN, UNIT_PRICE FROM APPS.EAM_REQUIREMENT_OPERATIONS_V WHERE STOCK_ENABLED_FLAG = 'N' AND QUANTITY_OPEN > 0

Example: vendor sourcing detail for a specific work order.

• SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, CONCATENATED_SEGMENTS, SUGGESTED_VENDOR_NAME, VENDOR_ID, UNIT_PRICE, DATE_REQUIRED FROM APPS.EAM_REQUIREMENT_OPERATIONS_V WHERE WIP_ENTITY_ID = :p_wip_entity_id

Because ALLOCATED_QUANTITY is computed via a package function, queries returning many rows incur PL/SQL call overhead; filtering by WIP_ENTITY_ID or ORGANIZATION_ID is recommended for performance.