Search Results oke_pool_parties_s
Overview
OKE_PARTY_PVT is a private PL/SQL package body owned by the APPS schema within Oracle E-Business Suite, classified under the ETRM repository as a PVT (private) API. It forms part of the Oracle Knowledge Extensions (OKE) module, which underpins Oracle Procurement Contracts and the broader Contracts Core functionality in releases 12.1.1 and 12.2.2. The package encapsulates the low-level data manipulation logic required to associate parties — suppliers, customers, and internal organizations registered in Oracle Trading Community Architecture (HZ) — with funding pools. Funding pools represent the budgetary groupings against which contract and procurement funding is tracked and consumed. By centralizing insert, update, delete, and locking behavior for the OKE_POOL_PARTIES entity, OKE_PARTY_PVT provides the private implementation layer that public OKE APIs such as OKE_API and OKE_FUNDING_UTIL_PKG call upon. It is not referenced by any other database object, confirming its role as an internal helper package rather than a published integration point.
Key Procedures and Functions
The package exposes a set of standard table-handler routines. The documented entries are:
- INSERT_ROW — Creates a new party-to-funding-pool association record in the underlying pool parties table, populating the mandatory columns and audit attributes required for the row to participate in funding allocation logic.
- UPDATE_ROW — Modifies an existing association, typically to adjust attributes such as funding source, currency, or the active status of the party within the pool. Updates are performed against the row identified by its primary key.
- DELETE_ROW — Removes a party's association from a funding pool when the relationship is no longer valid, such as when a supplier ceases to be an eligible funding source.
- LOCK_ROW — Issues a SELECT ... FOR UPDATE against the target row to guarantee transactional isolation, preventing concurrent modification of a pool party record while a caller is validating or mutating it.
The metadata reports seven documented procedures or functions in the ETRM listing, though only these four are named in the excerpt. The remaining entries are internal helpers supporting validation and currency conversion. No parameter lists are documented, and callers should not assume public signatures — all invocation occurs through the public OKE packages.
Tables Accessed
The package reads and writes through APPS synonyms. The principal transactional table is OKE_POOL_PARTIES, with its companion sequence OKE_POOL_PARTIES_S supplying primary key values — this is the object most directly related to the search term "oke_pool_parties_s". Supporting tables include HZ_PARTIES for party identity and eligibility validation, FND_CURRENCIES for currency code validation on amounts and funding records, OKE_FUNDING_POOLS for pool header context, and OKE_K_FUNDING_SOURCES for the funding source definitions that qualify which parties may participate. DUAL and PLITBLM are referenced for standard PL/SQL constructs — the latter typically as a PL/SQL index-by table type used in bulk processing.
Usage Notes
OKE_PARTY_PVT is invoked indirectly. The Funding Pool and Pool Parties setup is maintained through the Contracts Core user interface, and the forms layer routes DML through the public OKE API stack, which in turn calls this private package. Concurrent programs that seed or migrate funding pool membership — including data conversion routines during 12.1.1 to 12.2.2 upgrades — also reach this package through OKE_API. Custom extensions should never call OKE_PARTY_PVT directly; the supported integration surface is OKE_API and OKE_FUNDING_UTIL_PKG, which handle validation, error stacking via FND_API, and exception propagation. Direct calls would bypass these safeguards and risk orphaned rows in OKE_POOL_PARTIES. The absence of inbound database dependencies confirms the package is a terminal implementation layer, and any diagnostic tracing of pool party behavior should begin with the public wrappers before descending into this body.
-
SEQUENCE: OKE.OKE_POOL_PARTIES_S
12.2.2
owner:OKE, object_type:SEQUENCE, object_name:OKE_POOL_PARTIES_S, status:VALID,
-
SYNONYM: APPS.OKE_POOL_PARTIES_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OKE_POOL_PARTIES_S, status:VALID,
-
SYNONYM: APPS.OKE_POOL_PARTIES_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OKE_POOL_PARTIES_S, status:VALID,
-
SEQUENCE: OKE.OKE_POOL_PARTIES_S
12.1.1
owner:OKE, object_type:SEQUENCE, object_name:OKE_POOL_PARTIES_S, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.OKE_PARTY_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OKE_PARTY_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.OKE_PARTY_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:OKE_PARTY_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.OKE_PARTY_PVT SQL Statements
12.2.2
-
APPS.OKE_PARTY_PVT SQL Statements
12.1.1
-
APPS.OKE_PARTY_PVT dependencies on OKE_POOL_PARTIES_S
12.1.1
-
APPS.OKE_PARTY_PVT dependencies on OKE_POOL_PARTIES_S
12.2.2
-
APPS.OKE_PARTY_PVT dependencies on OKE_POOL_PARTIES
12.1.1
-
APPS.OKE_PARTY_PVT dependencies on OKE_POOL_PARTIES
12.2.2
-
PACKAGE BODY: APPS.OKE_PARTY_PVT
12.2.2
-
PACKAGE BODY: APPS.OKE_PARTY_PVT
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1