Search Results okc_k_accesses




Overview
Explore in AI Chat

Overview

The OKC_K_ACCESSES table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. It functions as the central repository for managing and storing authorization rules within the contract management system. As indicated by its description, this table defines the level of access granted to a specific resource (an individual user) or a resource group for a given contract. This mechanism is fundamental for implementing security and data visibility controls, ensuring that only authorized personnel can view, modify, or administer specific contracts based on their assigned roles and responsibilities.

Key Information Stored

The table's primary purpose is to map access rights between contracts, users, and groups. Its structure, inferred from the provided metadata, centers on several key foreign key relationships. The primary identifier is the ID column, which is the table's primary key. The CHR_ID column links the access record to a specific contract header in the OKC_K_HEADERS_B table. To specify the grantee, the table uses either the RESOURCE_ID, linking to an individual in JTF_RS_RESOURCE_EXTNS (the Resource Manager entities), or the GROUP_ID, linking to a group defined in JTF_RS_GROUPS_B. While the exact column for the access level (e.g., VIEW, MODIFY, ADMIN) is not explicitly named in the excerpt, it is implied by the table's description and is a critical piece of data stored alongside these foreign keys.

Common Use Cases and Queries

This table is primarily accessed for security enforcement and audit reporting. Common operational scenarios include determining if a user has permission to open a particular contract or generating a report of all users with administrative rights over a set of contracts. A typical query might join OKC_K_ACCESSES to OKC_K_HEADERS_B and JTF_RS_RESOURCE_EXTNS to list all contracts a specific user can access. For example: SELECT kha.access_level, okh.contract_number, res.resource_name FROM okc_k_accesses kha, okc_k_headers_b okh, jtf_rs_resource_extns res WHERE kha.chr_id = okh.id AND kha.resource_id = res.resource_id AND res.resource_name = '&USER_NAME'; Another common use case is administrative maintenance, such as inserting or deleting access records when user responsibilities change, which is typically performed via the standard Contracts Core user interface or supported APIs.

Related Objects

As defined by its foreign keys, OKC_K_ACCESSES has direct and essential relationships with three other EBS tables. The link to OKC_K_HEADERS_B anchors the access rule to a specific contract. The links to the Resource Manager tables, JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B, connect the rule to the underlying EBS user and group definitions. This table is also referenced by the primary key constraint OKC_K_ACCESSES_PK. While not listed in the excerpt, it is highly probable that this table is accessed by various OKC package bodies (e.g., OKC_K_ACCESS_PVT) that contain the program logic for validating and processing contract access rights.