Results for “lock_pool”

8 results




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

Overview

The APPS.OKE_POOLS_PARTIES_PUB package body is a public (PUB-classified) PL/SQL API within the Oracle E-Business Suite Oracle Knowledge and Enablers (OKE) module, which underpins Oracle Procurement Contracts and related sourcing functionality. Its principal business purpose is to provide a governed, validated interface for the creation, maintenance, and locking of funding pools and pool parties — the entities that define how contractual funding sources are grouped and how parties (for example, internal organizations, suppliers, or external entities) are associated with those pools.

The package body follows the standard OKE API architecture: it acts as a thin public wrapper that delegates transactional work to a private implementation package, OKE_POOL_PVT, after invoking the common activity framework routine OKE_API.START_ACTIVITY. This design enforces savepoint creation, API version compatibility checking, message-list initialization, and consistent error signaling across the module. The header comment ($Header: OKEPPPPB.pls 120.1 2005/05/27) confirms the file has been stable since the 11i era and carries forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package exposes eighteen procedures and functions, of which the core public entry points are:

  • CREATE_POOL — Creates a new funding pool record. It accepts a pool record structure based on oke_pool_pvt.pool_rec_type, initializes the API context, and delegates the actual insert to OKE_POOL_PVT.Insert_Row. On success it returns the populated pool record to the caller.
  • UPDATE_POOL — Modifies an existing funding pool, applying the same start-activity validation and delegating to the private update logic.
  • DELETE_POOL — Removes a funding pool, subject to the module's referential and status validations.
  • LOCK_POOL — Obtains a lock on a pool record to serialize concurrent modifications.
  • CREATE_PARTY — Associates a new party with a funding pool by inserting into the pool-parties relationship.
  • UPDATE_PARTY — Modifies the attributes of an existing pool-party association.
  • DELETE_PARTY — Removes a party from a pool.
  • LOCK_PARTY — Locks a pool-party record to prevent conflicting concurrent updates.

All procedures share the standard OKE API parameter contract: p_api_version, p_init_msg_list, and the OUT parameters x_return_status, x_msg_count, and x_msg_data. Return statuses are drawn from OKE_API constants (success, expected error, unexpected error), and unexpected or expected errors are raised as OKE_API.G_EXCEPTION_UNEXPECTED_ERROR or OKE_API.G_EXCEPTION_ERROR respectively.

Tables Accessed

The package operates against the following APPS-synonymed tables:

  • OKE_FUNDING_POOLS — The master table for funding pool definitions; read and written by CREATE_POOL, UPDATE_POOL, DELETE_POOL, and LOCK_POOL.
  • OKE_K_FUNDING_SOURCES — The funding source knowledge/definition table used to validate that a pool references a legitimate funding source.
  • OKE_POOL_PARTIES — The intersection table linking pools to parties; read and written by the party-level procedures.
  • PLITBLM — The standard EBS message-list table used by the API framework to accumulate and return error and informational messages to callers.

Usage Notes

OKE_POOLS_PARTIES_PUB is the sanctioned public interface for funding-pool maintenance and is typically invoked from OKE forms (for example, the funding pool and pool party maintenance windows) and from concurrent or custom PL/SQL programs that must create or amend pools programmatically. Callers should always supply a valid p_api_version, set p_init_msg_list to FND_API.G_TRUE when they want a fresh message list, and inspect x_return_status before consuming any OUT data.

The package is referenced by zero other documented packages, indicating it is a leaf-level API consumed directly by forms and external integrations rather than by other OKE APIs. Because it wraps OKE_POOL_PVT, direct calls to the private package should be avoided in custom code; the public body is the supported, upgrade-safe entry point across both 12.1.1 and 12.2.2. Note that the search term associated with this documentation query is unrelated to the object's technical content.