Search Results calculate_summary

Overview

PON_BUYER_SUMMARY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Sourcing (PON) product family and supports the buyer-facing summary reporting layer of the auction and negotiation workflow. Its principal purpose is to aggregate bidding activity associated with a sourcing auction and persist that aggregated result into summary tables that buyers and approvers use for evaluation and award decisions. The package is classified as OTHER in the ETRM metadata, meaning it is not part of the published public API surface; it is an internal implementation object that backs Oracle Sourcing business flows. The header comment ($Header: PONBUSUS.pls 120.0) indicates that the package has been stable since at least 2005 and has carried forward into the current Release 12 code line largely unchanged. Because the package writes to summary entities rather than to transactional auction data, it operates as a derived-data utility invoked on demand or after bidding events, and it does not itself enforce auction business rules.

Key Procedures and Functions

ETRM documents two procedures in the package specification:

• calculate_summary — Accepts an auction identifier as input and returns a batch identifier as an OUT NOCOPY parameter. This procedure is the primary entry point: it reads the current bidding state for the supplied auction, computes the buyer summary figures, and records the operation under the returned batch identifier. The batch identifier allows multiple summary calculations to be grouped and distinguished, which is useful when summaries are regenerated repeatedly during an active auction.
• bid_count_info — Accepts an auction identifier and returns six OUT NOCOPY counters that categorize bidder activity along two dimensions: bid completeness (no bid, partial bid, full bid) and auction state (open versus closed). This gives the buyer a snapshot of participation, for example how many invited parties have submitted complete responses while the auction remains open, and how many did so before closure.

Tables Accessed

The documented table references, resolved through APPS synonyms, fall into four functional groups. Auction definition and state are read from PON_AUCTION_HEADERS_ALL, with item-level pricing read from PON_AUCTION_ITEM_PRICES_ALL. Bidder and response data are read from PON_BIDDING_PARTIES, PON_BID_HEADERS, and PON_BID_ITEM_PRICES; HZ_PARTIES supplies the trading partner identity attributes needed to describe bidders. The computed output is written to PON_AUCTION_SUMMARY, with PON_AUCTION_SUMMARY_S serving as the corresponding sequence or surrogate-key source. DUAL is used for trivial single-row PL/SQL selects. In summary, the package reads the auction and bidding tables and writes to the auction summary tables.

Usage Notes

PON_BUYER_SUMMARY_PKG is not referenced by any other documented package, which confirms that it sits at the top of its call chain and is invoked directly by Oracle Sourcing forms, HTML-based negotiation pages, or concurrent programs that refresh buyer summary information. Typical invocation points include opening or refreshing the buyer summary and bid-count region of the negotiation workbench, and scheduled or event-driven regeneration of summary rows when bidding activity must be reflected in evaluation reports. Custom code should treat the package as an internal object: the signature may change between patch levels, and callers must supply a valid auction identifier. When integrating, ensure that PON_AUCTION_SUMMARY rows are not written concurrently with an active calculate_summary call, and commit or roll back the transaction consistently with the surrounding Sourcing flow so that the returned batch identifier remains meaningful.