Search Results can_supplier_create_payments




Overview

APPS.PON_BID_DEFAULTING_PKG is a public PL/SQL package in Oracle E-Business Suite that supports the Sourcing (Oracle Sourcing / Negotiations) module. Its primary business function is to govern and automate the defaulting of bid content within a negotiation (auction), and to validate whether a supplier is permitted to bid. The package header declares AUTHID CURRENT_USER, meaning its objects are resolved under the privileges of the invoking user, consistent with standard EBS API conventions.

The package addresses the lifecycle of draft bids: it decides whether bidding is allowed, generates defaulted draft bids from existing source bids, copies purchase order lines into bid lines, applies pricing factors, and manages locking and amendment acknowledgement. In this way it underpins the bid-entry experience for suppliers and the surrogate-bid process used by buyers. The unit references negotiation header data, bidding parties, pricing, shipments, and attachments, reflecting its role as a consolidation point for bid-side defaulting logic.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. The most significant include:

Tables Accessed

The package reads and writes negotiation data through APPS synonyms, including PON_AUCTION_HEADERS_ALL (negotiation header), PON_AUCTION_ATTRIBUTES, PON_AUCTION_SECTIONS, PON_AUCTION_EXHIBIT_DETAILS, PON_AUCTION_ITEM_PRICES_ALL, PON_AUCTION_SHIPMENTS_ALL, and PON_AUC_PAYMENTS_SHIPMENTS for auction structure, pricing, and payments. Bid data is held in PON_BID_HEADERS, PON_BIDDING_PARTIES, PON_BID_ATTRIBUTE_VALUES, and PON_ACKNOWLEDGEMENTS. Supporting reference data comes from FND_CURRENCIES, FND_USER, FND_DOCUMENT_CATEGORIES, and FND_ATTACHED_DOCUMENTS.

Usage Notes

PON_BID_DEFAULTING_PKG is typically invoked from Sourcing bid-entry forms, supplier-facing bid pages, and internal or surrogate bid creation flows. It is referenced by one other package, indicating it is called programmatically rather than directly by users. Customizations should call the documented public procedures with valid negotiation and bidding-party identifiers, respecting the returned status and return code, and should not bypass IS_BIDDING_ALLOWED when validating whether a supplier may bid.