Search Results pon_auction_events




Overview

The PON_AUCTION_EVENTS table is a core data object within the Oracle E-Business Suite Sourcing (PON) module. It serves as a master repository for event-level information that groups together multiple related sourcing negotiations, such as auctions or RFQs. Its primary role is to define a common context—like a specific trading partner event or a scheduled bidding round—under which multiple individual negotiation headers (PON_AUCTION_HEADERS_ALL) can be organized. This structure enables efficient management and reporting on batches of negotiations that share a common business purpose or timeline.

Key Information Stored

While the provided metadata specifies key structural relationships, the central column is EVENT_ID, which serves as the table's primary key. This unique identifier links all related negotiations. Crucially, the table stores trading partner details through foreign key relationships to the HZ_PARTIES table. The TRADING_PARTNER_ID column identifies the supplier organization involved in the event, and the TRADING_PARTNER_CONTACT_ID identifies the specific contact person at that organization. Other typical columns in such a table, though not explicitly listed here, would include data to describe the event's purpose, status, creation date, and schedule.

Common Use Cases and Queries

A primary use case is generating consolidated reports for all negotiations belonging to a specific sourcing event. For instance, a buyer may need to see the total spend or number of active bids across all line items in every auction tied to a quarterly supplier event. Another common scenario is validating trading partner information at the event level before negotiations are published. A sample query to list all negotiation headers for a given event would be:

  • SELECT pah.auction_header_id, pah.document_number FROM pon_auction_headers_all pah, pon_auction_events pae WHERE pae.event_id = pah.event_id AND pae.event_id = :p_event_id;

Data from this table is also critical for integration points, such as when sourcing events need to be interfaced with external supplier portals or financial systems for spend analysis.

Related Objects

The PON_AUCTION_EVENTS table has defined relationships with several other key EBS objects, as documented in the metadata:

  • PON_AUCTION_HEADERS_ALL: This is the primary child table. The EVENT_ID column in PON_AUCTION_HEADERS_ALL is a foreign key referencing PON_AUCTION_EVENTS.EVENT_ID. This links individual negotiations to their parent event.
  • HZ_PARTIES (Two Relationships): The table holds two foreign keys to the Trading Community Architecture (TCA) registry.
    • TRADING_PARTNER_ID references HZ_PARTIES to store the supplier party details.
    • TRADING_PARTNER_CONTACT_ID references HZ_PARTIES to store the contact person's party details.

These relationships ensure data integrity and enable joins to retrieve complete event information, including supplier names and contact details from the TCA model.