Search Results direct_item_type_id




Overview
Explore in AI Chat

Overview

APPS.EAM_WO_DIRECT_ITEMS_LITE_V is a supplementary Oracle EBS view that consolidates direct item requirements associated with Enterprise Asset Management (EAM) work orders. Direct items are purchased goods and services charged directly to a work order without being stocked in inventory; the view surfaces the requisition and purchase order activity generated against those requirements. Its primary consumers are EAM work order forms, which reference the view to display and manage direct item lines without coding against the underlying transactional tables directly.

The view is classified as a "Lite" view, a naming convention Oracle applies to simplified views intended to reduce form-level coding complexity. Oracle explicitly warns that this view is not a supported query or data manipulation interface and that its definition may change substantially in subsequent minor or major releases. Consequently, it should be treated as an internal forms construct rather than a stable integration or reporting API. The object resides in the APPS schema and is VALID in both 12.1.1 and 12.2.2 environments, though form-driven definitions of this type are known to evolve between point releases.

Underlying Base Objects

The view is defined over a combination of transactional and reference objects. Direct item records originate from WIP_EAM_DIRECT_ITEMS, which stores the requirement line detail tied to a work order. WIP_REQUIREMENT_OPERATIONS links those requirements to work order operations through WIP_ENTITY_ID and OPERATION_SEQ_NUM. Item master information is joined from MTL_SYSTEM_ITEMS_KFV, with categorization supplied by MTL_ITEM_CATEGORIES and the relevant category set identified through MTL_DEFAULT_CATEGORY_SETS.

Procurement activity is consolidated from PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL for requisition-side quantities and amounts, and from PO_LINES_ALL and PO_DISTRIBUTIONS_ALL for purchase order commitment and delivery information. Lookup decoding is provided by MFG_LOOKUPS, which supplies descriptive meaning for the direct item type and related lookup codes. This multi-table join is what allows a single row in the view to present requirement, sourcing, and receipt status simultaneously.

Key Columns

The view is keyed primarily by WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, and DIRECT_ITEM_SEQUENCE_ID, which together identify a specific direct item requirement on a specific work order operation. ITEM_ID carries the inventory item identifier for non-stockable items, while ITEM_NAME, ITEM_DESCRIPTION, and UOM_CODE provide descriptive attributes.

The user's search term, DIRECT_ITEM_TYPE, is exposed as a VARCHAR2(80) descriptive value derived from lookup decoding, accompanied by DIRECT_ITEM_TYPE_ID, the internal numeric identifier. Related attributes include CATEGORY_ID, DEPARTMENT_ID, EFFECTIVITY_CONTROL, and EAM_ITEM_TYPE. Quantity tracking is comprehensive: QUANTITY_REQUIRED, QUANTITY_ORDERED, QUANTITY_RECEIVED, RQL_QUANTITY_ORDERED, PO_QUANTITY_ORDERED, and PO_QUANTITY_CANCELLED collectively describe the requisition-to-receipt lifecycle. Monetary columns UNIT_PRICE, AMOUNT, AMOUNT_DELIVERED, RQL_AMOUNT_ORDERED, and PO_AMOUNT_ORDERED support amount-based lines, distinguished by ORDER_TYPE_LOOKUP_CODE. NEED_BY_DATE, AUTO_REQUEST_MATERIAL, and SUPPLIER_NAME complete the operational picture.

Common Use Cases and Queries

Typical usage includes reviewing outstanding direct item commitments on a work order, auditing requisition and PO coverage against required quantities, and driving auto-request material processing. Because the view is forms-oriented and unsupported for direct query, custom reporting should generally target the base tables instead. Where querying is necessary for diagnostic purposes, a constrained select is appropriate:

  • SELECT wip_entity_id, operation_seq_num, item_name, direct_item_type, quantity_required, quantity_ordered, quantity_received FROM apps.eam_wo_direct_items_lite_v WHERE wip_entity_id = :p_wip_entity_id;
  • SELECT direct_item_type, order_type_lookup_code, SUM(quantity_required), SUM(quantity_ordered) FROM apps.eam_wo_direct_items_lite_v WHERE organization_id = :p_org_id GROUP BY direct_item_type, order_type_lookup_code;
  • SELECT item_name, supplier_name, po_quantity_ordered, po_quantity_cancelled FROM apps.eam_wo_direct_items_lite_v WHERE need_by_date BETWEEN :p_from AND :p_to;

Each query should be restricted by organization and entity identifiers to avoid full scans across consolidated procurement data.