Results for “pon_bid_headers”

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

Overview

PON_BID_HEADERS is the header-level table in the Oracle Sourcing (PON) module that stores data for a supplier's response to a negotiation, commonly referred to as a bid or quote. In Oracle E-Business Suite 12.1.1 and 12.2.2, each row represents a single response submitted by a trading partner against a sourcing document (an auction or RFQ) defined in PON_AUCTION_HEADERS_ALL. The table carries 119 documented columns and is owned by the PON schema.

Its role in the Sourcing data model is central: it anchors the transactional response, capturing commercial, contact, status, procurement, and scoring attributes, and serves as the parent for the line-level and pricing children that comprise the full bid. The heuristic Data Vault classification flags this object as hub-leaning, since its primary key (BID_NUMBER) is referenced by numerous downstream tables. Under a Data Vault 2.0 modeling suggestion, PON_BID_HEADERS would be modeled as a hub keyed on the business identifier, with descriptive and status attributes potentially split into one or more satellites and relationships to the negotiation and supplier domains expressed as links.

Key Information Stored

The surrogate primary key, PON_BID_HEADERS_PK, is defined on BID_NUMBER. A unique index, PON_BID_HEADERS_U1, also enforces uniqueness on BID_NUMBER, making it the business-key candidate. Among the most significant columns:

• AUCTION_HEADER_ID — references PON_AUCTION_HEADERS_ALL, linking the bid to its parent negotiation.
• BID_STATUS / BID_STATUS_NAME — code and description reflecting the response's lifecycle state (for example draft, submitted, shortlisted).
• AWARD_STATUS / AWARD_STATUS_NAME — outcome of award determination against the negotiation.
• TRADING_PARTNER_ID, TRADING_PARTNER_NAME — supplier identity, related to HZ_PARTIES; VENDOR_ID additionally maps to PO_VENDORS.
• TRADING_PARTNER_CONTACT_ID and TRADING_PARTNER_CONTACT_NAME — responder contact details.
• BID_EFFECTIVE_DATE, BID_EXPIRATION_DATE, PUBLISH_DATE, CANCELLED_DATE — key temporal milestones for reporting bid activity.
• BID_CURRENCY_CODE, RATE, RATE_TYPE, RATE_DATE — currency and conversion context for bid amounts.
• DOCTYPE_ID — references PON_AUC_DOCTYPES and identifies the document type.
• VENDOR_SITE_ID, VENDOR_SITE_CODE — the supplier site for which the response is submitted.
• TOTAL_AWARD_AMOUNT, BUYER_BID_TOTAL — monetary totals used in award and analysis.
• PO_HEADER_ID, PO_TXN_FLAG, RELEASE_METHOD — linkage to downstream purchasing document creation.
• SHORTLIST_FLAG, SCORE_OVERRIDEN_FLAG, EVALUATION_FLAG — evaluation and shortlisting controls.
• ORIGINAL_BID_NUMBER, BID_REVISION_NUMBER — revision lineage for multi-round negotiations.

Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — are also present, plus later release columns such as REL12_DRAFT_FLAG and SUBMIT_STAGE.

Common Use Cases and Queries

Typical reporting scenarios include listing all responses to a negotiation, evaluating shortlisted suppliers, and tracking award outcomes. A basic join to the negotiation header returns bid context:

SELECT bh.bid_number, bh.bid_status_name, ah.auction_header_id
FROM   pon_bid_headers bh
JOIN   pon_auction_headers_all ah
       ON bh.auction_header_id = ah.auction_header_id
WHERE  bh.bid_status = 'SUBMITTED';

Suppliers can be resolved for spend or supplier-performance analytics:

SELECT bh.bid_number, hp.party_name, bh.total_award_amount
FROM   pon_bid_headers bh
JOIN   hz_parties hp ON bh.trading_partner_id = hp.party_id
WHERE  bh.award_status_name = 'AWARDED';

Line-level detail is retrieved by joining to PON_BID_ITEM_PRICES or PON_BID_SHIPMENTS on BID_NUMBER. These queries support negotiation dashboards, award analysis, and supplier response-cycle metrics.

Related Objects

The most significant related tables, based on documented foreign keys, include:

• PON_AUCTION_HEADERS_ALL — parent negotiation; join on AUCTION_HEADER_ID.
• HZ_PARTIES — trading partner and contact; join on TRADING_PARTNER_ID / TRADING_PARTNER_CONTACT_ID.
• PO_VENDORS — supplier master; join on VENDOR_ID.
• PON_AUC_DOCTYPES — document type; join on DOCTYPE_ID.
• PON_BID_ITEM_PRICES — line pricing; join on BID_NUMBER.
• PON_BID_SHIPMENTS — shipment-level bid detail; join on BID_NUMBER.
• PON_BID_REBATES — rebate tiers; join on BID_NUMBER.
• PON_AWARD_ALLOCATIONS — award distribution; join on BID_NUMBER.
• PON_TEAM_MEMBER_BID_SCORES and PON_TEAM_MEMBER_ATTR_SCORES — evaluator scoring; join on BID_NUMBER.

Together, these relationships demonstrate the table's hub role, connecting negotiation, supplier, pricing, and evaluation domains within the Oracle Sourcing schema.