Search Results po_requisition_lines_v




Overview
Explore in AI Chat

Overview

PO_REQUISITION_LINES_V is an Oracle E-Business Suite view owned by the APPS schema and delivered under the Purchasing (PO) product family. In the ETRM metadata it is classified with the description "10SC ONLY - Retrofitted," indicating that the object originated in an earlier release and has been retrofitted into the 12.1.1 / 12.2.2 code line rather than being a natively introduced view. Its status is VALID, and it serves as a denormalized, presentation-oriented projection of requisition line data.

Functionally, the view presents the requisition line as a document author sees it: line identity and numbering, item and category information, quantities and units of measure, pricing, delivery and destination details, sourcing defaults, and a wide block of descriptive flexfield (DFF) attributes (ATTRIBUTE1 through ATTRIBUTE15 plus ATTRIBUTE_CATEGORY). It also resolves foreign keys into readable values — buyer and deliver-to person names, organization names, location codes, UN numbers, and hazard classes. Because it flattens many of these relationships, the view is commonly used as a reporting and integration surface for requisition-line extracts, BI Publisher data templates, and custom concurrent programs, avoiding the multi-table joins that a direct query against PO_REQUISITION_LINES would otherwise require.

Underlying Base Objects

The view is defined principally over PO_REQUISITION_LINES, from which it derives the core line columns (ROWID, REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, ITEM_ID, ITEM_REVISION, CATEGORY_ID, ITEM_DESCRIPTION, QUANTITY, UNIT_PRICE, NEED_BY_DATE, and the DFF attributes). The documented ETRM base-object list confirms this synonym along with a broad set of supporting objects resolved by the view's joins, including:

Key Columns

Identity and structure columns include REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, LINE_TYPE, and PARENT_REQ_LINE_ID. Quantity and pricing columns include QUANTITY, QUANTITY_RECEIVED, QUANTITY_DELIVERED, QUANTITY_CANCELLED, UNIT_PRICE, CURRENCY_CODE, CURRENCY_UNIT_PRICE, RATE, RATE_TYPE, and RATE_DATE. Sourcing and status columns include SOURCE_TYPE_CODE, DESTINATION_TYPE_CODE, SUGGESTED_VENDOR_NAME, ENCUMBERED_FLAG, CLOSED_CODE, CANCEL_FLAG, CANCEL_REASON, and DOCUMENT_TYPE_CODE. Resolution columns carry human-readable values such as FULL_NAME (buyer/deliver-to), organization and location names, UN_NUMBER, and HAZARD_CLASS. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are exposed for change tracking.

Common Use Cases and Queries

Typical scenarios include extracting open requisition lines by buyer, reporting demand by need-by date, and feeding downstream systems with pricing and vendor defaults.

  • Requisition lines by buyer and status.
  • Open/uncancelled demand by need-by date.
  • Vendor and pricing extract for integrations.

Sample query:

SELECT requisition_line_id, line_num, item_description, quantity, unit_price, need_by_date, full_name
FROM apps.po_requisition_lines_v
WHERE cancel_flag = 'N'
  AND need_by_date >= SYSDATE
ORDER BY need_by_date;

Because the view references PO_REQ_DIST_SV1 and HR security packages, execution cost is higher than querying the base table directly; filter on indexed requisition or buyer columns where possible.