Search Results delete_party

Overview

OKE_POOLS_PARTIES_PUB is the public PL/SQL API for the Oracle E-Business Suite Oracle Knowledge Enterprise (OKE) module, which underpins the Oracle Procurement Contracts and Project Contracts functionality. The package governs the creation and maintenance of funding pools and the parties associated with those pools. A funding pool represents a grouping of monetary resources — typically associated with a contract, funding source, or project — against which contract terms and financial obligations may be defined and tracked. The public designation (API classification PUB) indicates that the package is intended for external invocation by forms, concurrent programs, and custom integration code rather than being restricted to internal package use.

The source header identifies the package as AUTHID CURRENT_USER, meaning all unqualified references to database objects resolve through the calling user's schema and privileges rather than the package owner's. This is a standard EBS construct that allows the package to be used within multiple operating contexts while respecting the invoker's security model.

The package defines subtype aliases for the pool and party record structures, delegating their underlying definitions to OKE_POOL_PVT and OKE_PARTY_PVT. This pattern separates public API signatures from private implementation types.

Key Procedures and Functions

The package exposes eight documented procedures, organized into pool operations and party operations, each available in single-record and table-based (bulk) overloads where applicable.

• CREATE_POOL — Creates a new funding pool and returns the newly assigned funding_pool_id in the output record. An overloaded form accepts and returns a table of pool records for bulk creation.
• UPDATE_POOL — Updates an existing funding pool. The source documentation notes that updating the currency code is not permitted, making currency an immutable attribute once a pool is created. A bulk overload mirrors the create pattern.
• DELETE_POOL — Removes a funding pool. The source comment describes this routine as performing cascading deletes, so dependent records such as pool parties are removed along with the parent pool.
• LOCK_POOL — Acquires a lock on a pool record, typically to prevent concurrent modification during a read-modify-write cycle.
• CREATE_PARTY — Creates a party association for a funding pool, recording which internal or external party is linked to the pool.
• UPDATE_PARTY — Modifies the attributes of an existing pool party association.
• DELETE_PARTY — Removes a party association from a pool. This is the procedure returned in searches for "delete_party" and is the documented entry point for severing a party from its funding pool without deleting the pool itself.
• LOCK_PARTY — Locks a pool party record for controlled concurrent access.

All procedures follow the standard EBS API convention of accepting p_api_version and p_init_msg_list and returning x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

• OKE_FUNDING_POOLS — The primary table storing funding pool definitions. Read and written by CREATE_POOL, UPDATE_POOL, DELETE_POOL, and LOCK_POOL.
• OKE_POOL_PARTIES — Stores the association between funding pools and parties. Directly manipulated by the CREATE_PARTY, UPDATE_PARTY, DELETE_PARTY, and LOCK_PARTY routines.
• OKE_K_FUNDING_SOURCES — Holds the funding source definitions referenced by pools, supporting validation of pool configuration.
• PLITBLM — The EBS message-table utility used to accumulate and retrieve API messages through the x_msg_count and x_msg_data out parameters.

Usage Notes

OKE_POOLS_PARTIES_PUB is typically invoked from the OKE contract funding setup forms, from concurrent programs that mass-maintain pool and party data, and from custom PL/SQL integration code. Callers should always supply a valid p_api_version, check x_return_status for OKE_API.G_RET_STS_SUCCESS after each call, and iterate x_msg_count / x_msg_data to extract error messages. DELETE_PARTY should be used to remove individual party associations; DELETE_POOL should be used only when removing the entire pool, given its documented cascading behavior.