Results for “requisition_number”

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

Overview

PON_BACKING_REQUISITIONS is a transactional table in the PON (Sourcing) schema that records the association between negotiated auction lines and the internal purchase requisitions that fund or back them. In Oracle EBS 12.1.1 and 12.2.2, the table serves as the linkage mechanism that ties a negotiation (auction) item line to one or more requisition lines, enabling procurement organizations to track which demand sources support a sourcing event. The table is owned by the PON schema and is classified as VALID in the ETRM reference for both releases.

Based on the foreign key structure, the object can be modeled heuristically as a link table in a Data Vault sense. It resolves a many-to-many style relationship between negotiation item pricing records and requisition line entities, carrying its own descriptive attributes (quantities, requisition numbers, audit columns) alongside the associative keys. This classification is a modeling suggestion derived from the FK topology rather than a formally declared property.

Key Information Stored

The table exposes eleven documented columns. The most significant are the keys and business attributes:

• AUCTION_HEADER_ID — Identifier of the parent negotiation (auction) header. Part of the primary key and of the unique business-key index.
• LINE_NUMBER — The negotiation item line number within the auction. Part of the primary key and references PON_AUCTION_ITEM_PRICES_ALL.
• REQUISITION_LINE_ID — Identifier of the requisition line backing the negotiation line. Part of the primary key and references PO_REQUISITION_LINES_ALL.
• REQUISITION_HEADER_ID — Identifier of the requisition header, referencing PO_REQUISITION_HEADERS_ALL and enabling header-level joins.
• REQUISITION_NUMBER — The user-facing requisition number, useful for reporting without a join.
• REQUISITION_QUANTITY — The quantity associated with the backing requisition line.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard EBS audit columns tracking who created and last modified each row.

The surrogate primary key is PON_BACKING_REQUISTIONS_PK (note the spelling in the metadata) over (AUCTION_HEADER_ID, LINE_NUMBER, REQUISITION_LINE_ID). A separate unique index, PON_BACKING_REQUISITIONS_U1, covers the same column set and represents the documented business-key candidate for this object.

Common Use Cases and Queries

Typical scenarios include identifying which requisitions back a given negotiation, reconciling sourced demand against requisition demand, and reporting on sourcing coverage for procurement analysis. A representative query joining to the negotiation header and requisition header:

• List backing requisitions for an auction: SELECT b.REQUISITION_NUMBER, b.REQUISITION_QUANTITY FROM PON.PON_BACKING_REQUISITIONS b WHERE b.AUCTION_HEADER_ID = :auction_id;
• Join to requisition lines for detail: SELECT rl.LINE_NUM, b.REQUISITION_QUANTITY FROM PON.PON_BACKING_REQUISITIONS b, PO.PO_REQUISITION_LINES_ALL rl WHERE b.REQUISITION_LINE_ID = rl.REQUISITION_LINE_ID;
• Aggregate demand per negotiation line: group by AUCTION_HEADER_ID and LINE_NUMBER, summing REQUISITION_QUANTITY.

These patterns support sourcing reconciliation reports, demand-tracing extracts, and audit inquiries.

Related Objects

The FK relationships documented for this table define its principal dependencies:

• PON_AUCTION_ITEM_PRICES_ALL — joined via LINE_NUMBER and AUCTION_HEADER_ID; holds negotiation item pricing.
• PO_REQUISITION_HEADERS_ALL — joined via REQUISITION_HEADER_ID; the requisition header.
• PO_REQUISITION_LINES_ALL — joined via REQUISITION_LINE_ID; the requisition line.

In practice, PON_BACKING_REQUISITIONS is also read alongside negotiation header tables in the PON schema when rendering sourcing event detail. Because it is a link object, its integrity depends entirely on the referenced auction and requisition entities remaining valid.