Search Results eam_work_order_direct_items_v




Overview
Explore in AI Chat

Overview

EAM_WORK_ORDER_DIRECT_ITEMS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined over the Enterprise Asset Management (EAM) module. Its documented purpose is to expose the direct item details associated with a work order. In EAM, a work order may require materials that are not defined as inventoried items in the item master; these are known as "direct items" and are typically procured on demand rather than issued from stock. This view consolidates the direct item requirements captured on the work order together with their associated purchasing activity, vendor defaults, and requisition status.

Because it presents procurement, vendor, and requirement data in a single denormalized structure, the view is well suited for reporting, inquiry forms, and integration extracts. It shields consumers from the multi-table joins required to reconstruct direct item demand, making it a convenient source for operational reporting on work order material requirements in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over both EAM/WIP and Oracle Purchasing base objects. The principal EAM source is WIP_EAM_DIRECT_ITEMS, which stores the direct item lines (description, UOM, unit price, need-by date, suggested vendor, quantity required) attached to a work order. WIP_REQUIREMENT_OPERATIONS supplies the requirement-to-operation association, including the operation sequence number.

Purchasing data is joined through PO_REQUISITION_LINES_ALL and PO_REQUISITION_HEADERS_ALL, which provide the requisition quantity and authorization status used in the SUM aggregations for quantity, quantity delivered, quantity ordered, and quantity cancelled. PO_DISTRIBUTIONS_ALL, PO_LINES_ALL, PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS supply purchasing distribution amounts, order type, and vendor name, site, contact, and phone fallback values. Category and item context is drawn from MTL_ITEM_CATEGORIES, MTL_DEFAULT_CATEGORY_SETS, and MTL_SYSTEM_ITEMS_KFV, while MFG_LOOKUPS resolves the UOM meaning. FND_GLOBAL supplies session context such as organization and user identifiers.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all direct items on a work order, tracking outstanding procurement against a need-by date, and extracting vendor defaults for downstream purchasing automation.

  • List direct items for a work order: 
    SELECT wip_entity_id, operation_seq_num, description,
       quantity_required, quantity_ordered, quantity_delivered
FROM   apps.eam_work_order_direct_items_v
WHERE  wip_entity_id = :p_wip_entity_id;
  • Identify items still short of the required quantity: 
    SELECT wip_entity_id, description, quantity_required, quantity
FROM   apps.eam_work_order_direct_items_v
WHERE  NVL(quantity,0) < quantity_required;
  • Review vendor defaults for direct items: 
    SELECT wip_entity_id, description, suggested_vendor_name,
       suggested_vendor_site, suggested_vendor_phone
FROM   apps.eam_work_order_direct_items_v;

Because the view is read-only and aggregates purchasing data, consumers should filter by organization and work order for performance and should not expect to update rows through it.