Results for “bid_line_number”

50+ results




Overview
Explore in AI Chat

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

Overview

PON.PON_AWARD_ALLOCATIONS is a Sourcing (PON) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records how an awarded supplier response is distributed across the requisition lines that funded a negotiation. When a buyer awards a sourcing event, the total awarded quantity of a negotiation line frequently must be satisfied by more than one backing purchase requisition line. PON_AWARD_ALLOCATIONS captures that distribution, storing one row per awarded bid line and original requisition line combination together with the allocated quantity and funds.

In Data Vault terms, the metadata's heuristic classification for this object is a link. This is a reasonable modeling suggestion: the table resolves many-to-many associations between awarded negotiation lines (identified by BID_NUMBER and BID_LINE_NUMBER) and requisition artifacts (ORIG_REQ_LINE_ID, ORIG_REQ_HEADER_ID, SPLIT_REQ_LINE_ID). It is not a standalone hub but an intersection carrying descriptive measures (ALLOCATED_QTY, ALLOCATED_FUNDS) and audit columns, which places it close to a link-satellite hybrid.

Key Information Stored

The documented schema contains 14 columns. The most consequential are:

  • ORIG_REQ_LINE_ID — the original purchase requisition line that backs the award; part of the primary key and a foreign key to PO_REQUISITION_LINES_ALL. This is the column most frequently searched by developers tracing award-to-requisition lineage.
  • BID_NUMBER — the negotiation/bid header identifier; joins to PON_BID_HEADERS.
  • BID_LINE_NUMBER — the awarded response line within the bid.
  • AUCTION_HEADER_ID — the parent auction header, joining to PON_AUCTION_HEADERS_ALL for auction-originated events.
  • ORIG_REQ_HEADER_ID — the header of the backing requisition, joining to PO_REQUISITION_HEADERS_ALL.
  • SPLIT_REQ_LINE_ID — a second requisition line reference used where the original line was split during allocation.
  • ALLOCATED_QTY — the quantity of the awarded line attributed to that requisition line.
  • ALLOCATED_FUNDS — the monetary value attributed to the same allocation.
  • IS_LINKED_PR_LINE_YN — a flag indicating whether the allocation has been linked to a purchase requisition line.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns maintained by the concurrent manager and forms layer.

The primary key is PON_AWARD_ALLOCATIONS_PK, a composite of ORIG_REQ_LINE_ID, BID_LINE_NUMBER, and BID_NUMBER. A unique index, PON_AWARD_ALLOCATIONS_U1, is documented over the same three business-key candidates, confirming there is no separate surrogate identifier; the business key and the physical key coincide.

Common Use Cases and Queries

The predominant use case is reconciling a sourcing award back to the demand that generated it. A typical query retrieves all allocations for a bid line:

  • SELECT ORIG_REQ_LINE_ID, ORIG_REQ_HEADER_ID, ALLOCATED_QTY, ALLOCATED_FUNDS FROM PON_AWARD_ALLOCATIONS WHERE BID_NUMBER = :bid AND BID_LINE_NUMBER = :line;
  • Reverse lookup: SELECT BID_NUMBER, BID_LINE_NUMBER, ALLOCATED_QTY FROM PON_AWARD_ALLOCATIONS WHERE ORIG_REQ_LINE_ID = :req_line; — used to determine which award consumed a requisition line.
  • Joining to PO_REQUISITION_LINES_ALL on ORIG_REQ_LINE_ID to report item, quantity, and unit price alongside allocated quantity.

Reporting scenarios include award-to-demand traceability, allocation balancing checks (sum of ALLOCATED_QTY per bid line versus awarded quantity), and funds-consumption analysis via ALLOCATED_FUNDS. Because IS_LINKED_PR_LINE_YN indicates linkage status, it is also useful in reconciliation reports identifying allocations not yet propagated to requisition lines.

Related Objects

  • PON_BID_HEADERS — joined on PON_AWARD_ALLOCATIONS.BID_NUMBER; provides negotiation header context.
  • PON_AUCTION_HEADERS_ALL — joined on AUCTION_HEADER_ID; used for auction-based negotiations.
  • PO_REQUISITION_LINES_ALL — referenced twice, via ORIG_REQ_LINE_ID and SPLIT_REQ_LINE_ID; the demand-side line definitions.
  • PO_REQUISITION_HEADERS_ALL — joined on ORIG_REQ_HEADER_ID; supplies requisition header attributes.
  • PON_BID_LINES / PON_AUCTION_HEADERS_ALL dependent views and the Sourcing award process logic that populates this table at award time.

Because the table is written by the Sourcing award process rather than directly by users, most custom reporting reads it through joins to the bid and requisition families rather than through supported public APIs.