Search Results recover_prev_amend_draft

Overview

PON_AUCTION_HEADERS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Sourcing (Oracle Sourcing / Oracle iProcurement sourcing) auction engine. Its central role is to manage the header-level state of an auction or negotiation — including auction metadata, bid ranking, best-price evaluation, and proxy bidding — against the underlying tables PON_AUCTION_HEADERS_ALL and its dependent child records. In ETRM terms the package is classified as an "OTHER" API, meaning it is not published as a formally supported open interface but remains a core internal component of the Sourcing application.

The package is validated. Its only explicit external dependency is on SYS.STANDARD (the PL/SQL STANDARD package), signalling that it is largely self-contained and relies on the APPS synonyms for its data access. It sits at the heart of the auction processing logic, and is referenced by PON_PRINTING_PKG and PON_RESPONSE_PVT, which confirms its role in printing negotiation documents and in processing supplier responses.

Key Procedures and Functions

ETRM documents 21 procedures and functions, oriented around three functional themes: proxy bidding, price and ranking evaluation, and auction information maintenance.

• Proxy bidding: UPDATE_PROXY_BID, IS_BETTER_PROXY_PRICE, IS_BETTER_PROXY_PRICE_BY_SCORE, CANCEL_PROXY_BID_LINE, and CANCEL_ALL_PROXY_BID_LINES manage the automatic bidding mechanism on behalf of suppliers. The IS_BETTER_* functions compare an incoming price (or scored price) against the current proxy position to determine whether a new bid should be placed.
• Price and ranking: GET_BID_BREAK_PRICE and GET_BID_BREAK_PRICE_WITH_PE return break prices (with and without a price element), NEW_BEST_PRICE and NEW_BEST_MAS_PRICE compute the new best price for standard and multi-attribute scoring auctions, and UPDATE_RANK maintains bid ranking. APPLY_PRICE_FACTORS applies price factor adjustments to a bid.
• Header information: UPDATE_AUCTION_INFO, UPDATE_AUCTION_INFO_DISQUALIFY, and UPDATE_AUCTION_INFO_TECH_SHORT update auction header information, including disqualification and technical-shortlisting status. RECOVER_PREV_AMEND_DRAFT restores a prior amendment draft, and SET_BUYER_BID_TOTAL sets the buyer's total for the auction.
• Utility helpers: GET_AUC_HEADER_ID_ORIG_ROUND resolves the original-round header ID, GET_MOST_RECENT_BID_NUMBER returns the latest bid number, GET_FND_USER_ID resolves an FND user, and CHECK_IS_BID_VALID validates a bid before processing.

Tables Accessed

The package reads and writes the principal auction and bid tables through APPS synonyms. PON_AUCTION_HEADERS_ALL and PON_AUCTION_ITEM_PRICES_ALL hold the auction header and item price records updated by UPDATE_AUCTION_INFO and the price routines. PON_BID_HEADERS, PON_BID_HEADERS_S, and PON_BID_ITEM_PRICES hold supplier bid headers and item prices used by ranking, best-price, and proxy-bid evaluation. PON_BIDDING_PARTIES and PON_BID_ATTRIBUTE_VALUES provide supplier participation and attribute-level scoring data. Business rules are sourced from PON_AUC_BIZRULES and PON_AUC_DOCTYPE_RULES, driving mask and rule behaviour. Finally, FND_USER and the FND_DOCUMENTS / FND_ATTACHED_DOCUMENTS / FND_DOCUMENT_CATEGORIES family support user identification and negotiation document attachments.

Usage Notes

PON_AUCTION_HEADERS_PKG is invoked indirectly by the Sourcing application rather than called directly by end users. It is most commonly reached through the Oracle Sourcing and iProcurement Java/Forms front end when buyers create or amend auctions, when the bidding engine evaluates supplier responses, and when proxy bids are placed. PON_PRINTING_PKG calls it while generating printable auction documents, and PON_RESPONSE_PVT calls it when processing supplier responses, indicating that the package is exercised during both the buyer-side setup and supplier-side bidding phases.

Because the package is not a published API, customizations and extensions should avoid calling its subprograms directly unless the calling code is fully regression-tested against the specific patch level. Any custom integration should prefer documented open interfaces and treat PON_AUCTION_HEADERS_PKG as internal implementation, since its signature and behaviour are subject to change across EBS 12.1.1 and 12.2.2 releases.