Search Results pon_bidding_parties




Overview
Explore in AI Chat

Overview

The PON_BIDDING_PARTIES table is a core data object within the Oracle E-Business Suite (EBS) Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It serves as the definitive repository for recording all supplier parties who are participants in a given negotiation event, such as an auction or RFx. Its primary role is to manage the relationship between a sourcing negotiation header and the list of invited or approved bidders, forming a critical link in the supplier engagement and bidding workflow. The table's integrity is enforced through its primary key and multiple foreign key relationships to master data tables, ensuring that all bidding parties are associated with valid negotiations and registered trading partners in the system.

Key Information Stored

The table's structure centers on three key identifiers that constitute its primary key. The AUCTION_HEADER_ID column links each record to a specific negotiation in the PON_AUCTION_HEADERS_ALL table. The LIST_ID associates the party with a specific bidder list, which may be sourced from either a template (PON_AUCTION_TEMPLATES) or a standalone list (PON_BIDDERS_LISTS). The TRADING_PARTNER_ID is the foreign key to the HZ_PARTIES table, uniquely identifying the supplier organization from the Trading Community Architecture (TCA) registry. While the provided metadata highlights these core columns, typical implementations may also include audit columns (CREATION_DATE, CREATED_BY), status flags indicating invitation or bidding status, and sequence numbers for ordering within the list.

Common Use Cases and Queries

This table is central to reporting and operational processes related to supplier participation. A common use case is generating an invitation list or bidder attendance report for a negotiation. Technical consultants often query this table to troubleshoot missing bidders or to validate data integrations. A typical SQL pattern joins to the auction header and party tables to list all participants for a specific negotiation:

  • SELECT pbpa.AUCTION_HEADER_ID, hp.PARTY_NAME FROM PON.PON_BIDDING_PARTIES pbpa JOIN HZ_PARTIES hp ON hp.PARTY_ID = pbpa.TRADING_PARTNER_ID WHERE pbpa.AUCTION_HEADER_ID = :p_auction_id;

Another frequent scenario involves identifying all negotiations where a specific supplier is invited, which is essential for supplier performance analysis.

Related Objects

The PON_BIDDING_PARTIES table maintains documented foreign key relationships with several key EBS objects, as per the provided metadata:

  • PON_AUCTION_HEADERS_ALL: Joined via AUCTION_HEADER_ID. This is the primary parent table, providing header-level details of the negotiation.
  • PON_AUCTION_TEMPLATES: Joined via LIST_ID. Links a bidding party record to a list defined within a sourcing template.
  • PON_BIDDERS_LISTS: Also joined via LIST_ID. Links a bidding party record to a standalone, reusable list of bidders.
  • HZ_PARTIES: Joined via TRADING_PARTNER_ID. This relationship ties the sourcing participant to the universal party definition within Oracle's Trading Community Architecture, providing access to the supplier's name, location, and other attributes.

These relationships are fundamental for any data extraction, reporting, or extension involving negotiation participants.