Search Results oke_party_pvt




Overview
Explore in AI Chat

Overview

OKE_PARTY_PVT is an internal, private PL/SQL package in the APPS schema that serves as the foundational data-access layer for party and pool-party relationships within the Oracle E-Business Suite Contracts (OKE) module, part of Oracle Procurement Contracts and the wider Enterprise Contracts suite. The package carries the "PVT" API classification, indicating it is not part of the published public API surface exposed to external or customer integration code. Instead, it provides the low-level row manipulation logic used by the public packages OKE_POOLS_PARTIES_PUB and OKE_PARTY_PVT, which in turn support the funding pool and party-assignment features of Procurement Contracts. The business purpose of the package is to maintain the rows in OKE_POOL_PARTIES and its history table that associate parties — suppliers, customers, or internal organizations — with funding pools, thereby supporting the allocation and tracking of funds across contracts. Because the package is marked VALID in the ETRM 12.1.1 / 12.2.2 metadata, it is a system-owned object that should not be modified or invoked directly by customer extensions.

Key Procedures and Functions

The ETRM documentation records four documented entry points within the package, though the full body contains several more private helper routines. The principal documented procedures are:

  • INSERT_ROW — Creates a new pool-party association row, populating the base table OKE_POOL_PARTIES and its corresponding multi-org/time-tracked shadow entity. This is the primary creation path for party-to-pool assignments.
  • UPDATE_ROW — Modifies an existing pool-party association, such as changing the effective dates, attribute values, or the relationship attributes held on the association record.
  • DELETE_ROW — Removes a pool-party association, performing the logical deletion required for the time-tracked table.
  • LOCK_ROW — Obtains a row-level lock on the target OKE_POOL_PARTIES record to preserve concurrency control before a subsequent update or delete within the same transaction.

These routines are the write primitives that the public API wrappers rely upon; they do not expose a rich parameter list to callers and are intended solely for intra-package or sibling-package consumption.

Tables Accessed

The package reads and writes the following tables, accessed through APPS synonyms:

  • OKE_POOL_PARTIES and OKE_POOL_PARTIES_S — the base and shadow (time-tracked) tables that store the actual party-to-pool association records. These are the core tables manipulated by the package.
  • HZ_PARTIES — the TCA party registry, read to validate and resolve party identifiers when creating or updating associations.
  • OKE_FUNDING_POOLS and OKE_K_FUNDING_SOURCES — the funding pool header and funding source definition tables, read to confirm the pool and source context of an association.
  • FND_CURRENCIES — read to validate currency codes attached to funding or association attributes.
  • DUAL and PLITBLM — utility tables used for sequence lookups and for driving PL/SQL table (index-by-table) based mass operations.

The package further depends on OKE_API and STANDARD (the Oracle Forms standard library), indicating it supports form-driven data manipulation typical of the Contracts UI.

Usage Notes

OKE_PARTY_PVT is invoked indirectly, not directly. It is referenced by OKE_POOLS_PARTIES_PUB and by OKE_PARTY_PVT, and it in turn depends on OKE_API and OKE_POOL_PARTIES. The package is exercised primarily through the Procurement Contracts funding-pool maintenance forms and through the public published API layers when pool-party associations are created or changed. Because it is a private (PVT) package owned by APPS and marked Oracle proprietary/confidential, custom code should never call OKE_PARTY_PVT directly; integrators should instead use the published OKE_POOLS_PARTIES_PUB API. Direct modification is unsupported and would be overwritten by patching or upgrades in 12.1.1 and 12.2.2 environments.