Results for “remove_from_req_pool”

7 results




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

Overview

APPS.PO_NEGOTIATIONS_SV1 is the core server-side PL/SQL package body that implements the negotiation APIs for Oracle Purchasing in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the programmatic entry point for creating, updating, and deleting sourcing negotiations — RFQs, quotations, auctions, and blanket purchase agreements — and for managing the requisition pool from which negotiation lines are sourced. The package is classified under ETRM as OTHER rather than a formal public API, but its procedures are invoked both by Oracle's own applications and by external Java clients.

The header comment ($Header: POXNEG1B.pls 120.47.12020000.2) identifies the file as POXNEG1B.pls, part of the Purchasing negotiation module. The embedded comment for create_negotiation_bulk explains its raison d'être: it exists as a wrapper around create_negotiation because the req_lines_table_type used by the internal API is declared inside the package and is therefore not visible to Java callers. This design pattern — a bulk wrapper exposing PL/SQL collections as PO_TBL_NUMBER and PO_TBL_VARCHAR tables — is characteristic of the R12 negotiation APIs.

Key Procedures and Functions

The documented 17 subprograms fall into three functional groups.

Tables Accessed

The package touches the following documented tables through APPS synonyms:

Usage Notes

PO_NEGOTIATIONS_SV1 is normally invoked indirectly. The Oracle Purchasing negotiation and auction forms call create_negotiation_bulk for programmatic creation, while the Autocreate and sourcing flows use update_req_pool, remove_from_req_pool, and return_reqs_to_pool to maintain requisition availability. External Java clients call create_negotiation_bulk directly, which is precisely why that wrapper was introduced.

The package is referenced by seven other packages, confirming its role as a shared service layer rather than a standalone module. Because it is classified as OTHER rather than a formal public API, Oracle does not guarantee interface stability; customizations should call the documented public entry points (create_negotiation_bulk in particular) and avoid relying on internal helpers. All array parameters must be populated as PO_TBL_NUMBER and PO_TBL_VARCHAR collections, and callers must supply a valid API version. Standard EBS error-handling conventions apply: exceptions are raised with FND_MSG_PUB messages and callers should check the returned message stack.