Search Results requisiton_line_id

Overview

APPS.EAM_WORK_ORDER_REQ_PO_V is a Web view-type database view in the Oracle E-Business Suite APPS schema. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, it is designed to simplify access from Oracle Self-Service Web Applications, and it shows purchase order and requisition details of an Enterprise Asset Management (EAM) work order. The view consolidates requisition header and line information, purchase order header, line, and distribution information, receiving quantities, and vendor master attributes into a single denormalized projection keyed by WIP entity and operation sequence.

Its principal value lies in the fact that a work order's direct procurement activity is normally distributed across several purchasing tables. Rather than requiring report authors and integrators to join PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and the vendor views manually, EAM_WORK_ORDER_REQ_PO_V exposes the combined result. The status of the object is VALID, and it is owned by APPS.

Underlying Base Objects

The documented referenced base objects for the 12.2.2 metadata are: FND_GLOBAL (PACKAGE), MTL_UNITS_OF_MEASURE (SYNONYM), PO_DISTRIBUTIONS_ALL (SYNONYM), PO_HEADERS_ALL (SYNONYM), PO_LINES_ALL (SYNONYM), PO_LINE_LOCATIONS_ALL (SYNONYM), PO_LINE_TYPES (SYNONYM), PO_REQUISITION_HEADERS_ALL (SYNONYM), PO_REQUISITION_LINES_ALL (SYNONYM), PO_VENDORS (VIEW), PO_VENDOR_CONTACTS (VIEW), and PO_VENDOR_SITES_ALL (VIEW).

Requisition numbering and line identifiers derive from PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL. Purchase order numbering, line identifiers, order type, and release identifiers derive from PO_HEADERS_ALL, PO_LINES_ALL, and, where releases are present, PO_RELEASE_ID. Schedule and shipment detail, including need-by dates and quantity ordered, are sourced from PO_LINE_LOCATIONS_ALL, while PO_DISTRIBUTIONS_ALL supplies the actual ordered and cancelled quantities at the distribution level. Unit of measure descriptions come from MTL_UNITS_OF_MEASURE, order type classification from PO_LINE_TYPES, and supplier attributes from PO_VENDORS, PO_VENDOR_CONTACTS, and PO_VENDOR_SITES_ALL. FND_GLOBAL supplies the session context used to restrict rows by operating unit and organization.

Key Columns

• WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID — identify the work order and operation against which the requisition and PO activity was raised, and the inventory organization context.
• REQUISITION_NUMBER, REQUISITION_HEADER_ID, REQUISITON_LINE_ID — the requisition number, header key, and line key. Note the documented spelling of REQUISITON_LINE_ID (missing the second "I"); this is the column matched by the search term "requisiton_line_id".
• PO_NUMBER, PO_HEADER_ID, PO_LINE_ID, PO_RELEASE_ID — the purchase order identity and, where applicable, release identity.
• ITEM_ID, ITEM_DESCRIPTION, UOM_CODE, VENDOR_ITEM_NUM — item and unit of measure attributes.
• RQL_QUANTITY_ORDERED, QUANTITY_ORDERED, PO_QUANTITY_ORDERED, PO_QUANTITY_CANCELLED, QUANTITY_RECEIVED — requisition ordered quantity, PO ordered quantity, actual distribution-level ordered and cancelled quantities, and received quantity.
• UNIT_PRICE, CURRENCY_CODE, AMOUNT — pricing and extended amount on the PO or requisition line.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE, VENDOR_CONTACT_ID, VENDOR_CONTACT, VENDOR_PHONE — supplier, site, and contact information.
• CATEGORY_ID, NEED_BY_DATE, ORDER_TYPE_LOOKUP_CODE, DIRECT_ITEM_SEQUENCE_ID — purchasing category, required date, order type classification, and the direct item sequence linking the requisition line to the work order operation.

Common Use Cases and Queries

Typical uses include EAM procurement reporting, work order cost and commitment analysis, open requisition and PO tracking against operations, and supplier spend analysis by work order. The view also supports integration extracts in which requisition line detail must be reconciled to PO lines and receipts.

To retrieve all requisition and PO lines for a work order:

• SELECT wip_entity_id, operation_seq_num, requisition_number, requisiton_line_id, po_number, po_line_id, item_description, rql_quantity_ordered, quantity_ordered, quantity_received, vendor_name FROM apps.eam_work_order_req_po_v WHERE wip_entity_id = :p_wip_entity_id AND organization_id = :p_org_id ORDER BY operation_seq_num, requisition_number;

To trace a specific requisition line to its purchase order and supplier:

• SELECT requisition_number, requisiton_line_id, po_number, po_line_id, vendor_name, vendor_site, unit_price, currency_code, amount FROM apps.eam_work_order_req_po_v WHERE requisiton_line_id = :p_requisition_line_id;

To analyze ordered, cancelled, and received quantities by supplier:

• SELECT vendor_name, SUM(po_quantity_ordered) ordered_qty, SUM(po_quantity_cancelled) cancelled_qty, SUM(quantity_received) received_qty FROM apps.eam_work_order_req_po_v WHERE need_by_date BETWEEN :p_from_date AND :p_to_date GROUP BY vendor_name;

Because the view is a Self-Service Web view and references FND_GLOBAL, queries should be executed with the correct operating unit and organization context, and access should be granted through the APPS schema rather than by direct grants on the underlying purchasing tables.