Results for “vendor_item_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

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:

• PO_DISTRIBUTIONS_ALL (synonym) — the central work order procurement link, supplying WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, DESTINATION_ORGANIZATION_ID, WIP_RESOURCE_SEQ_NUM, quantities, amounts, and the PO_LINE_ID/PO_RELEASE_ID keys.
• PO_HEADERS_ALL and PO_LINES_ALL (synonyms) — purchase order header and line attributes such as SEGMENT1 (PO number), currency, vendor, and item data.
• PO_LINE_LOCATIONS_ALL (synonym) — shipment-level data including NEED_BY_DATE.
• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL (synonyms) — requisition number, line, quantities, vendor suggestions, and pricing.
• PO_LINE_TYPES (synonym) — line type classification used in the join.
• MTL_UNITS_OF_MEASURE (synonym) — UOM codes for both requisition and PO quantities.
• PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS (views) — vendor name, site code, and contact information.
• FND_GLOBAL (package) — supplies session/org context.

Key Columns

• WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM — identify the work order and its operation/resource context.
• REQ_NUMBER, REQ_LINE_QTY, REQUISITION_LINE_ID, REQUISITION_HEADER_ID — requisition identity and quantity.
• PO_NUMBER, PO_LINE_ID, PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_QTY — purchase order identity and quantity.
• QUANTITY_DELIVERED, QUANTITY_ORDERED, QUANTITY_CANCELLED, AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT — aggregated fulfilment and value measures.
• VENDOR_NAME, VENDOR_SITE_CODE, vendor contact columns — supplier detail, resolved from PO first and otherwise from requisition suggestions.
• CURRENCY_CODE, UNIT_PRICE, NEED_BY_DATE, ITEM_ID, CATEGORY_ID, ORDER_TYPE_LOOKUP_CODE — commercial and scheduling attributes.

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.