Search Results pon_bid_headers

Overview

The PON_BID_HEADERS table is a core data object within the Oracle E-Business Suite Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for header-level information pertaining to a supplier's response, or bid, to a negotiation (auction). Each record in this table represents a single, complete bid submission from a trading partner. Its fundamental role is to anchor the bid within the system, linking it to the parent negotiation, the supplier, and the supplier's contact, while also acting as the parent entity for all detailed line-level bid data. The integrity of the sourcing process is maintained through its defined primary and foreign key relationships, ensuring data consistency across the bid lifecycle from submission through award.

Key Information Stored

The table's structure is designed to capture the essential metadata of a bid. The primary key, BID_NUMBER, uniquely identifies each bid submission. Critical foreign key columns establish core relationships: AUCTION_HEADER_ID links the bid to its parent negotiation in PON_AUCTION_HEADERS_ALL, VENDOR_ID references the supplier from PO_VENDORS, and TRADING_PARTNER_CONTACT_ID ties to the specific contact person in HZ_PARTIES. Other significant columns typically include BID_STATUS to track the state of the bid (e.g., DRAFT, SUBMITTED, AWARDED), CREATION_DATE, LAST_UPDATE_DATE, and CREATED_BY for audit purposes. The table also stores overall bid attributes such as currency, payment terms, and scoring information that apply at the header level.

Common Use Cases and Queries

This table is central to reporting and process flows in Sourcing. Common use cases include generating bid participation reports for a specific auction, tracking the status of all bids from a particular supplier, and extracting data for bid analysis and award decisions. A typical query would join PON_BID_HEADERS with PON_AUCTION_HEADERS_ALL to list all bids for an auction, including supplier details. For example:

SELECT bh.BID_NUMBER, bh.BID_STATUS, v.VENDOR_NAME, ah.AUCTION_TITLE
FROM PON.PON_BID_HEADERS bh,
    PON.PON_AUCTION_HEADERS_ALL ah,
    PO.PO_VENDORS v
WHERE bh.AUCTION_HEADER_ID = ah.AUCTION_HEADER_ID
AND bh.VENDOR_ID = v.VENDOR_ID
AND ah.AUCTION_HEADER_ID = :p_auction_id;

Another common pattern is querying the table to find all awarded bids for a vendor to analyze historical performance.

Related Objects

PON_BID_HEADERS has extensive relationships within the Sourcing schema, acting as a parent table for numerous child entities that store bid details. As documented in the ETRM, key foreign key relationships include:

• Parent Tables (Foreign Keys from PON_BID_HEADERS): PON_AUCTION_HEADERS_ALL (AUCTION_HEADER_ID), HZ_PARTIES for both TRADING_PARTNER_ID and TRADING_PARTNER_CONTACT_ID, PO_VENDORS (VENDOR_ID), and FND_USER (TRADING_PARTNER_CONTACT_NAME).
• Child Tables (Foreign Keys to PON_BID_HEADERS.BID_NUMBER): PON_AWARD_ALLOCATIONS, PON_BID_ITEM_PRICES, PON_BID_PAYMENTS_INTERFACE, PON_BID_PAYMENTS_SHIPMENTS, PON_BID_PRICE_DIFFERENTIALS, PON_BID_REBATES, PON_BID_SHIPMENTS, PON_OPTIMIZE_BID_CLASS, PON_OPTIMIZE_RESULTS, PON_TEAM_MEMBER_ATTR_SCORES, and PON_TEAM_MEMBER_BID_SCORES. These dependencies underscore that the BID_NUMBER is the critical identifier for all subsequent bid-related data.