Search Results eam_direct_items_recs_v

Overview

EAM_DIRECT_ITEMS_RECS_LITE_V is a lightweight reporting and integration view owned by the APPS schema within the Enterprise Asset Management (EAM) module of Oracle E-Business Suite. It presents direct item and material requirement lines associated with work orders, exposing the detail needed to monitor procurement, requisition, and receiving activity for non-stocked and directly charged items issued against EAM work orders. The view is described as a "light weight version" of EAM_DIRECT_ITEMS_RECS_V, meaning it delivers the core requisition, purchase order, and quantity information at reduced processing cost, making it preferable for high-volume extractions, concurrent program data sources, and downstream integrations where the full attribute set of the parent view is not required. It is commonly consumed by requisition and purchasing reports, material availability inquiries, and interface programs that push EAM demand into Oracle Purchasing and iProcurement.

Underlying Base Objects

The view is constructed as a UNION ALL of two query branches. The first branch is driven from the EAM_WO_DIRECT_ITEMS_LITE_V view, joined to MFG_LOOKUPS for the service line type meaning and to MTL_CATEGORIES_KFV for the concatenated category segment. The second branch draws from EAM_WO_REQ_PO_LITE_V, joined to MTL_CATEGORIES_KFV and MTL_SYSTEM_ITEMS_B_KFV to supply item and category descriptors. At the documented base object level, the view resolves over the EAM direct item and requisition-to-PO views together with WIP_EAM_DIRECT_ITEMS, WIP_REQUIREMENT_OPERATIONS, MFG_LOOKUPS, MTL_CATEGORIES_KFV, and MTL_SYSTEM_ITEMS_B_KFV. The union of these sources allows the view to report both direct item lines and the associated requisition and purchase order activity in a single result set.

Key Columns

• DIRECT_ITEM_TYPE / DIRECT_ITEM_TYPE_ID / DIRECT_ITEM_SEQUENCE_ID — Identifies the direct item classification and the unique line identifier.
• WIP_ENTITY_ID / ORGANIZATION_ID / OPERATION_SEQ_NUM — Links the line to the work order, inventory organization, and routing operation.
• ITEM_ID / ITEM_NAME / ITEM_DESCRIPTION / CATEGORY_ID / CONCATENATED_SEGMENTS — Item and category identification, including the concatenated category flexfield value.
• UOM_CODE, UNIT_PRICE, AMOUNT, AMOUNT_DELIVERED — Pricing and valuation attributes, with UNIT_PRICE defaulting to AMOUNT when a unit price is not populated.
• REQUIRED_QUANTITY, QUANTITY_RECEIVED, NEED_BY_DATE — Demand quantity, received quantity, and the required-by date.
• PO_QUANTITY_ORDERED — Derived as NVL(PO_QUANTITY_ORDERED,0) minus NVL(PO_QUANTITY_CANCELLED,0), providing the net purchased quantity on the line.
• PO_QUANTITY_CANCELLED, RQL_QUANTITY_ORDERED, RQL_AMOUNT_ORDERED, PO_AMOUNT_ORDERED — Requisition and purchase order quantity and amount measures, with requisition quantity similarly netted against cancellations.
• SUPPLIER_NAME, ORDER_TYPE_LOOKUP_CODE, SERVICE_LINE_TYPE_ID, MEANING — Supplier, order type, and a derived service line type (2 for FIXED PRICE, otherwise 1), with MEANING from MFG_LOOKUPS.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield columns available for extensibility.

Common Use Cases and Queries

A frequent requirement is to identify how much of a work order's direct item demand has been ordered on a purchase order — the "po_quantity_ordered" figure. This is answered directly from the net PO_QUANTITY_ORDERED column:

• SELECT WIP_ENTITY_ID, ITEM_NAME, REQUIRED_QUANTITY, PO_QUANTITY_ORDERED, PO_QUANTITY_CANCELLED, QUANTITY_RECEIVED FROM APPS.EAM_DIRECT_ITEMS_RECS_LITE_V WHERE NVL(PO_QUANTITY_ORDERED,0) > 0 ORDER BY WIP_ENTITY_ID;
• Material availability checks comparing required versus received quantities per operation.
• Supplier and spend analysis grouping PO_AMOUNT_ORDERED by SUPPLIER_NAME.
• Requisition backlog reporting using RQL_QUANTITY_ORDERED and RQL_AMOUNT_ORDERED.
• Data extracts feeding purchasing or inventory interfaces, filtered by ORGANIZATION_ID and NEED_BY_DATE.

The view should be queried in a read-only fashion, as it exposes no updateable columns and is intended for reporting and integration consumption.