Search Results pon_multiple_response_pkg

Overview

PON_MULTIPLE_RESPONSE_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and is part of the Sourcing (Oracle Sourcing / Negotiations) module, sharing the PON prefix with the core negotiation and bidding infrastructure. Its central business purpose is to manage the creation, defaulting, and loading of supplier responses — commonly referred to as bids — against an auction or negotiation header. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is consistent with its role as an internal API invoked from within the Sourcing application stack.

The name "MULTIPLE_RESPONSE" reflects the scenario in which more than one response may exist for a given negotiation, supplier, or evaluator, and the package must determine which response to load, whether a rebid is occurring, and whether prior responses were amended, withdrawn, or disqualified. The multiple_resp_enabled term that leads users to this object relates directly to the MULTIPLE_RESP_ENABLED function, which governs whether the multiple-response feature is active for a given negotiation. This package's header revision (120.0, dated 2011) places it firmly in the 12.1.1 and 12.2.x code lines.

Key Procedures and Functions

• CHECK_AND_LOAD_BID — The main public procedure. It determines whether a new bid (response) is to be created or an existing defaulted bid loaded, and returns a substantial set of OUT parameters describing the outcome. These include the loaded or created bid number, a rebid indicator, the source bid number, flags indicating whether the source bid lay on a previous amendment or round, whether the prior bid was disqualified or withdrawn (with a withdrawal reason), and whether an existing draft was edited. It also returns status and error codes. Its IN parameters cover the auction header, draft number, trading partner and contact identifiers and names, the creating user, vendor and vendor site identifiers and codes, surrogate-bid buyer trading partner details, the evaluator user and an evaluation flag, and an action code that triggers special processing such as creating a new amendment draft.
• MULTIPLE_RESP_ENABLED — A function that reports whether the multiple-response capability is enabled, typically evaluated against a negotiation header. This is the entry point most commonly associated with the user search term multiple_resp_enabled.
• GET_LATEST_NEG_WITH_RESP — A function that retrieves the latest negotiation associated with a response, supporting the logic by which the package identifies the most recent relevant negotiation for a supplier or evaluator.

Tables Accessed

The package reads and writes several core Sourcing tables via APPS synonyms:

• PON_AUCTION_HEADERS_ALL — The negotiation/auction header, consulted to validate the negotiation, resolve multiple-response settings, and interpret the action code.
• PON_BID_HEADERS — The supplier response header, where new bids are created and existing drafts, amendments, rounds, and withdrawal or disqualification state are read and updated.
• PON_BID_ITEM_PRICES — Line-level response pricing, defaulted or carried forward when a prior bid is loaded into a new draft or rebid.
• PON_CONTRACTS — Used to resolve contract and trading-partner context associated with the response.

Usage Notes

PON_MULTIPLE_RESPONSE_PKG is an internal application API rather than a public extension point. It is referenced by two other packages, confirming that it sits beneath the Sourcing bidding flow and is called by higher-level orchestration code. In practice it is invoked from the Sourcing supplier-facing bidding pages, from evaluator response handling, and from surrogate-bid entry performed on a supplier's behalf by a buyer. Because the AUTHID CURRENT_USER clause ties execution to the calling user's privileges, custom code should invoke it only within a session that already carries the appropriate Sourcing responsibilities. When extending or debugging multiple-response behaviour, the MULTIPLE_RESP_ENABLED function is the correct first call to confirm whether the feature applies to the negotiation before invoking CHECK_AND_LOAD_BID.