Search Results requisition_line_num




Overview
Explore in AI Chat

Overview

APPS.PO_REQ_LINES_IN_POOL_SRC_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data object PO.PO_REQ_LINES_IN_POOL_SRC_V. Its documented purpose is to simplify forms coding within the Oracle Purchasing module, specifically in support of the sourcing and auction (negotiation) flows that draw requisition lines into a sourcing pool. Oracle explicitly warns that this is a supplementary view intended for forms development and not for direct querying or data alteration; its structure may change dramatically in subsequent minor or major releases, and any custom dependency upon it carries upgrade risk.

The view presents a denormalized projection of requisition line data enriched with auction context, organization, and project/task information. It is a read-only construct; DML against it is not supported and would be unsafe even where syntactically possible. For Oracle EBS 12.1.1 and 12.2.2 the object exists as a VALID view in the APPS schema, and the presence of MODIFIED_BY_AGENT_FLAG ties it directly to the agent-driven sourcing functionality where negotiation agents act on behalf of buyers.

Underlying Base Objects

The ETRM metadata records that PO_REQ_LINES_IN_POOL_SRC_V is defined over the following synonym-referenced base objects:

On the dependency side, PO_REQ_LINES_IN_POOL_SRC_V is referenced by APPS.PON_AUCTION_CREATE_PO_PKG, the negotiation package that creates purchase orders or auction artifacts from requisition lines. This confirms the view's role as the forms-facing read layer for auction sourcing. Because it is a view rather than a table, no physical storage or indexing exists on the object itself; performance depends entirely on the underlying base tables.

Key Columns

  • REQUISITION_HEADER_ID / REQUISITION_LINE_ID — primary identifiers linking back to the requisition header and line tables.
  • REQUISITION_NUMBER / REQUISITION_LINE_NUM — user-visible requisition and line numbering.
  • REQUISITION_QUANTITY — requested quantity on the line.
  • NEED_BY_DATE — the required-by date carried from the line.
  • CREATION_DATE — standard who column recording row creation.
  • MODIFIED_BY_AGENT_FLAG — VARCHAR2 flag indicating whether the line was modified by an automated sourcing/negotiation agent rather than a human buyer. This is the column most directly relevant to agent-driven sourcing and to any audit of automated requisition changes.
  • AUCTION_HEADER_ID / AUCTION_LINE_NUMBER — the negotiation (auction) header and line to which the requisition line has been linked in the sourcing pool.
  • ORG_ID — the operating unit / organization identifier, enabling multi-org filtering.
  • PROJECT_NUMBER / TASK_NUMBER — project and task context resolved from PA_PROJECTS_ALL and PA_TASKS for project-charged requisitions.

Common Use Cases and Queries

Typical scenarios include auditing requisition lines that an agent has touched, reconciling requisition lines to active auctions, and reporting on project-charged lines awaiting sourcing. Because Oracle discourages direct querying, such SQL should be treated as diagnostic rather than production code. A representative query filtering on the searched column is:

  • SELECT REQUISITION_NUMBER, REQUISITION_LINE_NUM, REQUISITION_QUANTITY, AUCTION_HEADER_ID, AUCTION_LINE_NUMBER, ORG_ID, PROJECT_NUMBER, TASK_NUMBER FROM APPS.PO_REQ_LINES_IN_POOL_SRC_V WHERE MODIFIED_BY_AGENT_FLAG = 'Y' AND ORG_ID = :p_org_id;
  • Join the view to PO_REQUISITION_LINES_ALL on REQUISITION_LINE_ID when additional line attributes are needed beyond the projected set.
  • Filter on AUCTION_HEADER_ID IS NOT NULL to isolate lines already placed in an auction pool.

Given the documented volatility warning, any reporting requirement should preferably be built against the base tables (PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_REQ_DISTRIBUTIONS_ALL) rather than this view, and should be revalidated on upgrade from 12.1.1 to 12.2.2.