Search Results create_contract_access

Overview

OKE_K_ACCESS_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle E-Business Suite Contracts (OKE) module, specifically the Oracle Knowledge Base / contract access control infrastructure. Its API classification, PVT, indicates that it is a private package — one not intended for direct invocation by external callers or custom code. Instead, it exists to support higher-level public packages and concurrent processes that manage which users, parties, or organizations are permitted to view or modify a given contract.

In the context of Oracle EBS 12.1.1 and 12.2.2, access control is enforced consistently across contract authoring, query, and reporting. This package encapsulates the low-level operations behind that enforcement: creating access records for a contract, obtaining a row-level lock before an access definition is modified, and updating an existing access definition. The object status is VALID, confirming it is compiled and functional in the documented environment.

Key Procedures and Functions

The ETRM metadata documents three procedures/functions. Their names and described purposes are as follows:

• CREATE_CONTRACT_ACCESS — Establishes a new contract access record, associating the contract with the party or entity that is being granted or defined access rights. It represents the insertion path for access-control data.
• LOCK_ROW — Implements row-level concurrency control on the underlying access record, ensuring that concurrent sessions cannot simultaneously alter the same access definition. This is the serialization point within the package.
• UPDATE_CONTRACT_ACCESS — Modifies an existing contract access record, supporting changes to the access definition after it has already been created.

No parameter lists are documented in the supplied metadata; parameter signatures should be confirmed by inspecting the package specification in a validated APPS schema. The three procedures collectively implement the create-lock-update lifecycle typical of a private data-maintenance package within the OKE module.

Tables Accessed

The single documented table reference is PA_PROJECT_PARTIES, accessed through an APPS synonym. This table is the Projects foundation storing the associations between a project and the parties (customers, organizations, individuals) involved in it. Because contracts in OKE are linked to projects, the access-control logic in this package derives its party context from PA_PROJECT_PARTIES. The package therefore reads party-to-project associations and, via its create and update procedures, contributes to the resulting access records maintained on the contract side.

Usage Notes

As a private (PVT) package, OKE_K_ACCESS_PVT is not a public extension point and should not be called directly by customer-developed code. The dependency metadata shows it is referenced by OKE_KCOPY_PKG, the Kernel copy package used when duplicating contracts and their associated knowledge/access definitions. This confirms that the package is invoked internally during copy operations, where access definitions must be reproduced and locked for consistency.

Typical invocation paths are therefore form-driven transactions (contract authoring and copy forms) and concurrent or background processes executed by the OKE framework. The presence of LOCK_ROW indicates the package is exercised inside multi-user transactional flows where concurrent updates to contract access are possible. Developers troubleshooting access-related behavior should trace callers such as OKE_KCOPY_PKG rather than invoking this package directly, and should rely on public OKE APIs for custom extensions. On both EBS 12.1.1 and 12.2.2, the object resides in the APPS schema with a VALID status and depends only on the SYS STANDARD package, indicating minimal external footprint.