Search Results eam_work_order_req_po_v




Overview
Explore in AI Chat

Overview

APPS.EAM_WORK_ORDER_REQ_PO_V is a predefined Oracle E-Business Suite view that consolidates requisition and purchase order activity associated with Enterprise Asset Management (EAM) work orders. Its documented description states simply that the view "shows purchase order and requisition details of a work order." In practical terms, it presents a work-order-centric procurement picture: for each work order (identified by WIP_ENTITY_ID and, where applicable, WIP_OPERATION_SEQ_NUM and WIP_RESOURCE_SEQ_NUM), the view discloses the originating requisition, the resulting purchase order, vendor and pricing information, and summarized delivery, ordered, and cancelled quantities and amounts.

The view is owned by the APPS schema and is marked VALID in ETRM for both 12.1.1 and 12.2.2. Because it is a view rather than a table, it exposes no storage of its own; consumers read live procurement data reconciled against work order demand. This makes it a convenient reporting and integration construct for maintenance and supply-chain analysis, avoiding the need to reconstruct join logic across the several EAM and Purchasing tables manually.

Underlying Base Objects

The view is defined over a mixture of Purchasing tables, units-of-measure lookups, vendor views, and a key flexfield package. Documented base objects include:

Key Columns

Common Use Cases and Queries

Typical uses include tracking procurement progress against maintenance work orders, reconciling requisition-to-PO conversion, and driving supplier delivery reporting. A representative query:

  • SELECT wip_entity_id, req_number, po_number, vendor_name, po_line_qty, quantity_delivered, quantity_cancelled FROM apps.eam_work_order_req_po_v WHERE wip_entity_id = :work_order_id;
  • SELECT req_number, po_number, SUM(amount_ordered) FROM apps.eam_work_order_req_po_v GROUP BY req_number, po_number;

Because the view aggregates quantities and amounts, callers should constrain by work order or organization and apply appropriate GROUP BY logic when summarizing.