Search Results okc_contract_party_pub




Overview
Explore in AI Chat

Overview

OKC_CONTRACT_PARTY_PUB is the public PL/SQL package that manages the parties (contacts and role assignments) associated with a contract in Oracle E-Business Suite's Enterprise Contracts (OKC) module, commonly delivered with ETRM (Enterprise Transaction and Risk Management). Residing in the APPS schema with a status of VALID, it forms the top layer of a three-tier API architecture. The public (PUB) layer provides a stable, documented interface; the private (PVT) layer performs the actual business logic; and the utility packages supply validation of low-level entity operations.

The package provides the primary programmatic route for creating, changing, locking, validating, and removing the individuals and organizations that comprise a contract's party list, together with the roles they occupy on that contract. It is the interface invoked by Contracts forms and by custom or integration code that must maintain contract party data without directly manipulating the underlying OKC tables.

Key Procedures and Functions

The documented API exposes twenty-one procedures and functions, organized into two logical groups — contact operations and party-role operations — plus a language-maintenance routine.

The consistent create/update/delete/lock/validate pattern mirrors the standard FND_API conventions, allowing callers to compose atomic operations inside a larger transaction.

Tables Accessed

The package's documented direct table dependency is PLITBLM, the standard PL/SQL interface table used by FND_MSG_PUB to return message text and error tokens. It reads PLITBLM to translate the messages raised during validation into language-specific text.

The remaining data-access work is delegated: OKC_CPL_PVT governs contract party records, OKC_CTC_PVT governs contact records, and OKC_CONTRACT_PARTY_PVT provides the underlying party logic. The API also depends on OKC_API (general contract operations), OKC_UTIL (shared utilities), FND_API (standard API error/return conventions), and FND_PROFILE (profile option lookups). Because these dependencies are documented as a dependency list rather than an explicit table map, the concrete table names are encapsulated inside those private packages.

Usage Notes

OKC_CONTRACT_PARTY_PUB is typically invoked from the Contracts workbench forms when users add, change, or delete parties and roles on a contract, and from concurrent or batch programs that build contract data. The ETRM metadata records it as referenced by twenty-five other database objects, confirming its role as a widely consumed integration point.

Custom code should call this public package rather than the PVT or utility packages, since only the PUB layer is guaranteed to remain stable across patch releases. Callers are expected to run VALIDATE_CONTACT or VALIDATE_K_PARTY_ROLE before attempting a create or update, invoke LOCK_CONTACT or LOCK_K_PARTY_ROLE before performing an update to prevent concurrent modification, and manage the FND_API return status to handle errors correctly. The package is not referenced by any other database object, so it sits at the top of the call hierarchy rather than being driven by internal triggers.