Search Results req_line_qty




Overview
Explore in AI Chat

Overview

APPS.EAM_WO_REQ_PO_LITE_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as EAM.EAM_WO_REQ_PO_LITE_V. Its status is VALID in both 12.1.1 and 12.2.2. As documented in the ETRM metadata, it is a "lite" view intended to simplify forms coding within the Enterprise Asset Management (EAM) module, tying work order operations to the requisition and purchase order documents that supply them. Because it is a forms-support view, Oracle explicitly warns against querying or altering data through it in production, noting that its definition may change dramatically in subsequent minor or major releases. The view is therefore best understood as a read-only reporting convenience rather than a stable integration interface. It is particularly relevant when users search on requisition_status, since that column is exposed directly and reflects the approval/document state of the associated requisition.

Underlying Base Objects

The documented base objects behind this view are: MTL_UNITS_OF_MEASURE, PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL. All are referenced through APPS synonyms. The Purchasing tables supply the document chain: PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL provide requisition number, line, status, and quantities; PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL provide the corresponding purchase order, release, schedule, and distribution detail; PO_LINE_TYPES supplies the ORDER_TYPE_LOOKUP_CODE context (quantity-based versus amount-based lines); and MTL_UNITS_OF_MEASURE resolves the UOM_CODE. The EAM work order side is represented by WIP_ENTITY_ID and OPERATION_SEQ_NUM, linking each row back to the discrete work order operation that generated the demand.

Key Columns

Common Use Cases and Queries

Typical scenarios include tracking which requisitions and POs back a work order operation, monitoring outstanding versus received quantities, and reporting by requisition status. Because the view is unsupported for modification, queries should be read-only. A representative query filtering on requisition status follows:

  • SELECT wip_entity_id, operation_seq_num, requisition_number, requisition_status, po_number, po_status, item_description, quantity_ordered, quantity_received FROM apps.eam_wo_req_po_lite_v WHERE organization_id = :org_id AND requisition_status = 'APPROVED';
  • SELECT requisition_number, po_number, vendor_name, unit_price, currency_code, need_by_date FROM apps.eam_wo_req_po_lite_v WHERE wip_entity_id = :wip_entity_id ORDER BY operation_seq_num;

Analysts should confirm against the base Purchasing tables where audit-grade accuracy is required, given the documented volatility of this forms-oriented view.