Search Results eam_wo_direct_items_lite_v




Overview
Explore in AI Chat

Overview

The view APPS.EAM_WO_DIRECT_ITEMS_LITE_V is a lightweight reporting view within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It is documented in ETRM as a slimmed-down variant of the heavier EAM_WORK_ORDER_DIRECT_ITEMS_V view. Its role is to expose the direct items associated with a work order — that is, non-inventory, externally procured items entered against a work order operation — in a form that is cheaper to query than its full-featured counterpart. In EBS 12.1.1 and 12.2.2 the view retains a VALID status in the APPS schema and is intended for reporting, integration, and inquiry purposes where the complete column set of the base view is not required. By projecting a reduced set of columns and otherwise identical join logic, the LITE view reduces the parsing and execution overhead of direct-item reporting. When a user searches for quantity_required in the context of this object, they are searching for the required-quantity column that the view publishes as the alias QUANTITY_REQUIRED.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists the following referenced base objects: MFG_LOOKUPS (view), MTL_DEFAULT_CATEGORY_SETS, MTL_ITEM_CATEGORIES, MTL_SYSTEM_ITEMS_KFV, PO_DISTRIBUTIONS_ALL, PO_LINES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, WIP_EAM_DIRECT_ITEMS, and WIP_REQUIREMENT_OPERATIONS (all synonyms pointing to their underlying APPS tables). The central base table is WIP_EAM_DIRECT_ITEMS (aliased WED), which stores the direct-item records attached to a WIP entity and operation sequence. It is joined to the purchasing tables — requisition headers/lines, PO lines, and PO distributions (aliased PD) — to aggregate ordered, received, and cancelled quantities. MFG_LOOKUPS supplies the DIRECT_ITEM_TYPE meaning, while the MTL item and category objects and WIP_REQUIREMENT_OPERATIONS support the broader reporting context. The LITE view essentially reuses this join structure but substitutes literal NULL values (for ITEM_ID, ITEM_NAME, EFFECTIVITY_CONTROL, and EAM_ITEM_TYPE) where the full view performs additional item-master lookups.

Key Columns

The columns of primary interest include:

Common Use Cases and Queries

The view is typically used to report the direct-material demand against work orders, to reconcile required versus ordered and received quantities, and to feed integration extracts. A representative query selecting the required quantity for a given work order might read:

  • SELECT wip_entity_id, operation_seq_num, item_description, quantity_required, quantity_ordered, quantity_received FROM apps.eam_wo_direct_items_lite_v WHERE wip_entity_id = :p_wip_entity_id ORDER BY operation_seq_num;
  • SELECT organization_id, wip_entity_id, item_description, quantity_required - quantity_received AS shortfall FROM apps.eam_wo_direct_items_lite_v WHERE quantity_required > NVL(quantity_received,0);
  • SELECT direct_item_type, SUM(quantity_required), SUM(amount) FROM apps.eam_wo_direct_items_lite_v GROUP BY direct_item_type;

Because the view performs aggregation over the purchasing tables, any query that groups or filters on quantity columns should account for the summarized nature of QUANTITY_ORDERED, QUANTITY_RECEIVED, and the PO-level quantities. Where item-master attributes or effectivity control are required, the full EAM_WORK_ORDER_DIRECT_ITEMS_V should be used instead, as the LITE view intentionally returns NULL for those columns.