Search Results okc_cac_pvt




Overview
Explore in AI Chat

Overview

OKC_CAC_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle E-Business Suite Contracts (OKC) module, specifically the Contract Access Control (CAC) functionality. The API classification "PVT" indicates that this package is intended for internal use by the Contracts application and its related APIs rather than direct invocation by end users or external integrations. Its principal business role is to manage contract-level access records stored in the OKC_K_ACCESSES and OKC_K_ACCESSES_H tables, which govern which users, resources, and resource groups are authorized to view or work with a given contract or contract version. The package implements a complete row-level data manipulation pattern—insert, lock, update, delete, and validate—together with versioning operations that allow access setups to be copied, created, or restored across contract versions. In this way it acts as the persistence and business-rule layer behind the Contract Access Control user interface and the broader OKC_API surface.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions, of which the following are named. The core data manipulation routines are INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, and VALIDATE_ROW, which respectively create a new access row, obtain an exclusive lock on an existing row, modify an existing row, remove a row, and apply validation rules to a row before it is persisted. The versioning operations are CREATE_VERSION, CHANGE_VERSION, and RESTORE_VERSION, which manage access records as contract versions are created, changed, or rolled back. API_COPY provides a mechanism for copying access data, typically when duplicating a contract or propagating access from one version to another. The procedure abbreviated QC is a quality-control or consistency-check routine. Because the metadata does not expose parameter lists, no signatures are asserted here; callers should consult the package specification or the Contract Access Control forms for the exact interface.

Tables Accessed

The package operates primarily against the OKC_K_ACCESSES table, the base table holding contract access records, and OKC_K_ACCESSES_H, its history/audit companion that preserves prior versions of access rows. OKC_K_ACCESSES_V and the resource views OKC_RESOURCE_GROUPS_V and OKC_RESOURCE_USERS_V supply validation and lookup data for the resource and group identifiers referenced by access rows. OKC_K_HEADERS_B identifies the owning contract header, and JTF_RS_GROUPS_B and JTF_RS_RESOURCE_EXTNS supply resource group and resource extension information from the shared JTF resource tables. PLITBLM is the standard PL/SQL table type utility. Dependencies also include OKC_API, OKC_P_UTIL, OKC_DEBUG, OKC_VERSION_PVT, FND_API, FND_GLOBAL, FND_PROFILE, and APP_EXCEPTIONS, reflecting the standard EBS API error-handling, profile, and session-context conventions.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, OKC_CAC_PVT is invoked indirectly. The Contract Access Control maintenance forms and the public OKC_API layer call this private package to persist and validate access changes; it is also referenced by ten other database objects, confirming its role as a shared internal service. Developers writing custom extensions should not call OKC_CAC_PVT directly, since private packages are not part of the supported public interface and their signatures may change between releases. Instead, extensions should route through OKC_API or the supported Contract Access Control forms. Debug tracing is available through OKC_DEBUG, and messages are standardised via FND_API and APP_EXCEPTIONS, so error handling follows the usual EBS API pattern.