Results for “auction_creation_date”

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

Overview

The PON_BIDDING_PARTIES table is a core data object within the Oracle E-Business Suite PON – Sourcing module. It stores the parties participating in a negotiation, functioning as the authoritative registry that links a buyer-side auction (negotiation) to the suppliers (trading partners) invited to participate. Each row represents a single party's participation record for a given negotiation and invitation list, capturing invitation details, acknowledgement status, registration and access information, and requested-supplier attributes.

The table resides in the PON schema and is classified as VALID in Oracle EBS releases 12.1.1 and 12.2.2. Under the heuristic Data Vault classification mined from its foreign-key structure, PON_BIDDING_PARTIES is best modeled as a link table. This is consistent with its role: it resolves the many-to-many relationship between negotiations (auctions) and the trading partners who bid on them, rather than acting as a descriptive hub or a pure satellite.

Key Information Stored

The table is documented with 44 columns in the ETRM 12.2.2 physical schema. The most significant columns are:

• AUCTION_HEADER_ID – Identifies the negotiation (auction) to which the party record belongs; part of the primary key.
• LIST_ID – Identifies the bidder list or template associated with the invitation; part of the primary key.
• TRADING_PARTNER_ID – The supplier's party identifier in HZ_PARTIES; part of the primary key.
• TRADING_PARTNER_NAME and TRADING_PARTNER_CONTACT_NAME / CONTACT_ID – The supplier and its primary contact details.
• INVITATION_ID and REGISTRATION_ID – Track the invitation and supplier registration lifecycle.
• SUPP_ACKNOWLEDGEMENT / ACKNOWLEDGEMENT_TIME – Record whether the supplier acknowledged the invitation and when.
• ACCESS_TYPE – Indicates the level of access granted to the participating party.
• BID_CURRENCY_CODE and RATE / RATE_DSP – Currency and exchange-rate context for the negotiation.
• REQUESTED_SUPPLIER_ID / REQUESTED_SUPPLIER_NAME – Supplier requested for inclusion in the negotiation.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY – Standard audit columns.

The surrogate/business unique key is PON_BIDDING_PARTIES_UK, defined over the composite business keys (AUCTION_HEADER_ID, LIST_ID, TRADING_PARTNER_ID). This composite uniquely identifies a party's participation in a specific negotiation and list. No single generated surrogate sequence column is documented; the natural composite key serves as the enforcing unique constraint.

Common Use Cases and Queries

Typical scenarios include determining which suppliers were invited to a negotiation, tracking acknowledgement and registration status, and reconstructing bidder-list membership for reporting.

Retrieving all suppliers for a negotiation:

SELECT TRADING_PARTNER_ID, TRADING_PARTNER_NAME, SUPP_ACKNOWLEDGEMENT, ACCESS_TYPE
FROM   PON.PON_BIDDING_PARTIES
WHERE  AUCTION_HEADER_ID = :auction_header_id;

Joining to the auction header for negotiation context:

SELECT h.AUCTION_HEADER_ID, p.TRADING_PARTNER_NAME, p.INVITATION_ID
FROM   PON.PON_BIDDING_PARTIES p, PON.PON_AUCTION_HEADERS_ALL h
WHERE  p.AUCTION_HEADER_ID = h.AUCTION_HEADER_ID
AND    p.SUPP_ACKNOWLEDGEMENT = 'Y';

Reporting on pending acknowledgements and access types supports negotiation monitoring, while joining to HZ_PARTIES enriches supplier master attributes for analytics.

Related Objects

• PON_AUCTION_HEADERS_ALL – Referenced via AUCTION_HEADER_ID; holds the negotiation definition.
• PON_BIDDERS_LISTS – Referenced via LIST_ID; defines the bidder list membership.
• PON_AUCTION_TEMPLATES – Also referenced via LIST_ID; supplies template context for lists.
• HZ_PARTIES – Referenced via TRADING_PARTNER_ID; the trading-partner (supplier) master.

These relationships confirm the table's role as a linking object connecting negotiations, lists/templates, and supplier party records within the Sourcing module.