Search Results pon_auction_summary




Overview
Explore in AI Chat

Overview

The PON_AUCTION_SUMMARY table is a temporary data structure within the Oracle E-Business Suite Sourcing module (PON). Its primary role is to serve as a transient repository for aggregated data generated to populate the auction summary user interface. As a temporary table, it is populated during runtime processes to consolidate and calculate summary-level information for items within a specific sourcing auction. This design allows for efficient generation of the summary display without persisting the calculated data long-term, optimizing performance for the "auction summary page" as indicated in the documentation.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of AUCTION_ID, BATCH_ID, and LINE_NUMBER. This key uniquely identifies summary records for a specific auction line within a processing batch. The AUCTION_ID column links the data to the parent auction event. The BATCH_ID likely facilitates the management of concurrent summary generation processes. The LINE_NUMBER associates the summary data with a specific line item from the auction. A critical foreign key relationship exists with the PON_AUCTION_ITEM_PRICES_ALL table, using AUCTION_ID and LINE_NUMBER, anchoring the summary to the detailed price and bid information. Another significant column is TRADING_PARTNER_ID, which holds a foreign key to HZ_PARTIES, linking to the supplier (trading partner) involved in the auction summary calculations.

Common Use Cases and Queries

The table is primarily accessed during the rendering of the auction summary page for a buyer or analyst. A typical use case involves querying all summary lines for a completed auction to review aggregated bid statistics, such as low bid, average bid, or number of bids per item. Since it is a temporary table, direct reporting or historical analysis is not its intended purpose; persistent data for such needs resides in transactional tables like PON_AUCTION_ITEM_PRICES_ALL. A sample query pattern to retrieve summary data for a specific auction would be:

  • SELECT * FROM PON_AUCTION_SUMMARY WHERE AUCTION_ID = :p_auction_id ORDER BY LINE_NUMBER;

This data is typically generated and consumed programmatically by Oracle Sourcing application logic rather than through ad-hoc user queries.

Related Objects

The PON_AUCTION_SUMMARY table has defined relationships with several core EBS objects. Its primary foreign key dependency is on PON_AUCTION_ITEM_PRICES_ALL, the main table for storing detailed bid line information. The relationship via AUCTION_ID and LINE_NUMBER ensures summary data aligns with the granular bid history. The foreign key on TRADING_PARTNER_ID references HZ_PARTIES, the Trading Community Architecture (TCA) table for storing party information, linking summary data to specific supplier entities. As a temporary working table, it is closely associated with the application programs and pages that generate and display the auction summary, rather than having a wide array of persistent dependencies.