Search Results requisition_num




Overview
Explore in AI Chat

Overview

APPS.PO_REQ_LINES_IN_POOL_SEC_V is a reporting view in Oracle E-Business Suite that exposes purchase requisition lines that have been flagged as being "in pool" — that is, requisition lines available for sourcing activities such as RFQ (Request for Quotation) and auction processing. The view presents a security-oriented projection of requisition header and line data, filtering exclusively to those lines where PRL.REQS_IN_POOL_FLAG equals 'Y'. In the context of ETRM 12.1.1 and 12.2.2, this view serves as a lightweight, read-only interface used by sourcing and procurement modules to identify requisition demand that can be aggregated into negotiated sourcing events. Because the view joins header-level and line-level requisition tables and restricts output to pooled lines, it is commonly referenced by concurrent programs, descriptive flexfield-driven reports, and integration layers that need a consolidated, denormalized picture of pooled requisition demand without traversing the underlying base tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced in the ETRM metadata as synonyms resolved against the APPS schema:

  • PO_REQUISITION_HEADERS_ALL — the requisition header table, aliased as PRH, which supplies organization and header-level identifiers.
  • PO_REQUISITION_LINES — the requisition line table, aliased as PRL, which supplies line-level detail and the pool qualification flag.

The join is an equijoin on REQUISITION_HEADER_ID, correlating each header to its child lines, with the additional predicate PRL.REQS_IN_POOL_FLAG = 'Y' applied to restrict the result set. The view does not itself store data; it is a stored SQL definition whose results reflect the current state of the two requisition tables at query time.

Key Columns

The view exposes the following columns, as documented in the ETRM view text:

  • ORG_ID — the operating unit identifier from the requisition header, essential for multi-org security and reporting.
  • REQUISITION_HEADER_ID — the primary key of the parent requisition header.
  • REQUISITION_NUM — exposed as PRH.SEGMENT1, the user-visible requisition number. This is the column most frequently used when users search for a requisition by its business identifier.
  • REQUISITION_LINE_ID — the primary key of the requisition line.
  • LINE_NUM — the line number within the requisition.
  • SUGGESTED_VENDOR_NAME and SUGGESTED_VENDOR_LOCATION — free-text vendor suggestions captured on the line.
  • VENDOR_ID and VENDOR_SITE_ID — the identified supplier and site, when a valid vendor reference exists.
  • AUCTION_DISPLAY_NUMBER and AUCTION_HEADER_ID — the auction reference associated with the pooled line, supporting negotiated sourcing.
  • BLANKET_PO_HEADER_ID — the blanket purchase agreement header reference, where applicable.

Common Use Cases and Queries

Typical scenarios include identifying pooled demand for sourcing events, validating vendor suggestions against actual vendor assignments, and producing requisition-level reports filtered by operating unit. A representative query searching by requisition number is:

SELECT requisition_num, line_num, suggested_vendor_name, vendor_id, auction_display_number FROM apps.po_req_lines_in_pool_sec_v WHERE requisition_num = :requisition_num AND org_id = :org_id;

To list all pooled lines for an operating unit:

SELECT requisition_num, requisition_line_id, line_num, blanket_po_header_id FROM apps.po_req_lines_in_pool_sec_v WHERE org_id = :org_id ORDER BY requisition_num, line_num;

Because the view already enforces the REQS_IN_POOL_FLAG = 'Y' predicate, consumers need not re-apply the pool filter, reducing the risk of inconsistent logic across reports and interfaces. Note that the view is defined on PO_REQUISITION_LINES rather than PO_REQUISITION_LINES_ALL, so the ETRM-documented form reflects the single-organization line table as shipped in the referenced releases.