Results for “create_negotiation”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PO_NEGOTIATIONS_SV1 is a server-side PL/SQL package in the Oracle E-Business Suite Purchasing module, classified as an internal "OTHER" API rather than a published open interface. Its business purpose is to support the creation, maintenance, and lifecycle management of sourcing negotiations — the auction, RFQ, and blanket renegotiation documents that precede or amend formal purchase orders and agreements. The package acts as a service layer between the Sourcing (PON) application logic and the underlying Purchasing and negotiation schema objects.

The "_SV1" suffix indicates a versioned internal service package. It is not intended for direct customer invocation and carries no documented public API contract. It exists primarily to be called by higher-level Sourcing packages, and it in turn calls lower-level data-access utilities such as PO_TBL_NUMBER and PO_TBL_VARCHAR100 (used to bulk-transfer numeric and character collections) and reads requisition data from PO_REQUISITION_LINES_ALL.

Key Procedures and Functions

The ETRM metadata documents 17 procedures and functions. Their purposes are as follows:

• CREATE_NEGOTIATION — Creates a single negotiation document from supplied sourcing data.
• CREATE_NEGOTIATION_BULK — Bulk variant for creating multiple negotiations in a single operation, used for high-volume sourcing scenarios.
• DELETE_NEGOTIATION_REF — Removes a reference linking a negotiation to its originating or related document.
• UPDATE_NEGOTIATION_REF — Updates an existing negotiation reference record.
• UPDATE_NEGOTIATION_LINE_REF — Updates the line-level reference association for a negotiation.
• CHECK_NEGOTIATION_REF — Validates whether a negotiation reference exists and is consistent.
• UPDATE_REQ_POOL — Maintains the pool of requisitions available to be placed on a negotiation.
• REMOVE_FROM_REQ_POOL — Removes requisitions from the pool once consumed.
• RETURN_REQS_TO_POOL — Returns requisitions to the pool when a negotiation is cancelled or reworked.
• RENEGOTIATE_BLANKET — Initiates a renegotiation against an existing blanket purchase agreement.
• GET_AUCTION_DISPLAY_LINE_NUM — Derives the display line number for auction lines.
• COPY_REQ_UDA_TO_SOL — Copies requisition descriptive flexfield (UDA) values onto sourcing lines.
• UPDATE_SOL_REF_DELETE_ALL — Clears all sourcing-line references during amendment or deletion.
• UPDATE_SOL_REF_DELETE_LINE — Deletes a single sourcing-line reference.
• UPDATE_SOL_REF_AMEND — Updates sourcing-line references when an amendment is applied.

Tables Accessed

The package reads and writes the core Purchasing and Sourcing tables. PO_REQUISITION_LINES_ALL supplies requisition lines feeding the pool. PON_AUCTION_HEADERS_ALL, PON_AUCTION_HEADERS_EXT_B, and PON_AUCTION_HEADERS_EXT_TL hold auction header data (base, extension, and translated). PON_AUCTION_ITEM_PRICES_ALL stores auction item pricing. The interface tables PON_AUC_HEADERS_INTERFACE, PON_AUC_HEADERS_INTERFACE_S, PON_AUC_ITEMS_INTERFACE, and PON_ATTACHMENTS_INTERFACE carry staged inbound data. FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, and FND_DOCUMENTS_TL manage negotiation attachments. MTL_SYSTEM_ITEMS_KFV and MTL_UNITS_OF_MEASURE resolve item and UOM descriptions, while FINANCIALS_SYSTEM_PARAMETERS provides ledger and operating-unit context.

Usage Notes

PO_NEGOTIATIONS_SV1 is an internal service package, invoked indirectly through the Sourcing HTML user interface and its associated concurrent programs rather than from a client form. It is referenced by seven packages, including PON_AUCTION_CREATE_PO_PKG, PON_AUCTION_PKG, PON_AWARD_PKG, PON_NEGOTIATION_HELPER_PVT, PON_NEG_UPDATE_PKG, POR_AMENDMENT_PKG, and PO_NEGOTIATION_REQ_NOTIF, confirming its role as a foundational layer for auction creation, award, amendment, and notification flows. Custom code should not call this package directly; the supported extension points are the documented open interfaces and public APIs. In EBS 12.1.1 and 12.2.2 the package is VALID in the APPS schema and may change between patch levels, so modifications should be avoided.