Search Results delete_k_party_role




Overview

OKL_K_PARTY_ROLES_PVT is a private (PVT-classified) PL/SQL API within the Oracle Lease Management (OKL) module of Oracle E-Business Suite. It provides the internal application programming interface responsible for creating, maintaining, and removing party role assignments on lease and contract instruments. Party roles associate a specific party — such as a lessee, lessor, guarantor, vendor, or contact — with a contract, and carry the descriptive attributes that determine how that party participates in the agreement.

The package is versioned and owned by APPS. Its internal subtype declarations (kplv_rec_type and kplv_tbl_type) are inherited from OKL_KPL_PVT, tying the party-role structure directly to the core OKL party-role entity. Because it is a private API, it is not intended for direct third-party invocation; it acts as the implementation layer beneath the public OKL APIs and the Oracle Contracts (OKC) integration surface. The header revision indicates a long-stable interface, which is significant for upgrade and migration planning.

Key Procedures and Functions

  • CREATE_K_PARTY_ROLE — Inserts a new party role record for a contract. It is overloaded to accept either a single record (p_kplv_rec) or a set of records (p_kplv_tbl), supporting both single-row form operations and set-based bulk processing. It carries paired OKC migration structures (cplv_rec_type/cplv_tbl_type) so that an OKC-side party-role definition and an OKL-side party role can be created consistently within one call. The standard API return convention (x_return_status, x_msg_count, x_msg_data) applies.
  • UPDATE_K_PARTY_ROLE — Modifies an existing party role, again provided in single-record and table overloads. The dual record/table input and output signatures allow the caller to retrieve the persisted structures after the update.
  • DELETE_K_PARTY_ROLE — Removes a party role assignment from the contract. This is the logical end-state operation for party roles whose participation has ended.

Each procedure follows the OKL API standard: an API version argument, an initialization flag (p_init_msg_list), and the outbound status and message parameters. Message handling is delegated to the OKL message stack.

Tables Accessed

The metadata documents two underlying objects reached through APPS synonyms:

  • OKC_K_PARTY_ROLES_B — the base table holding party-role definitions against contract instruments. This is the primary persistence target for the create, update, and delete operations and is shared with the Oracle Contracts schema, reflecting the OKC/OKL integration that the migration record types imply.
  • PLITBLM — a generic message or list table used by the OKL API framework to buffer and return multi-row error and status messages to the caller.

Usage Notes

OKL_K_PARTY_ROLES_PVT is referenced by eighteen other packages, confirming its position as a shared internal service rather than a standalone entry point. It is typically invoked indirectly: from OKL forms and business logic when a user adds or changes a party on a lease contract, from concurrent programs that process contracts in bulk, and from custom extensions that must stay synchronized with the standard OKL behavior. Because it is a private package, custom code should prefer the corresponding public OKL APIs where available. When direct invocation is unavoidable in 12.1.1 or 12.2.2, custom callers must honor the overloaded signatures, pass a valid API version, and inspect x_return_status together with the message count and data before committing.