Search Results okc_cr_k_accesses




Overview
Explore in AI Chat

Overview

The OKC_CR_K_ACCESSES table is a core intersection table within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a critical junction that manages the associations between a contract change request and the various entities involved in its workflow. Specifically, it links a change request (CRT_ID) to either a workflow process (CPS_ID) or a specific user (USER_ID). This table is fundamental for tracking and controlling access, status, and the progression of change requests throughout their lifecycle in both Oracle EBS 12.1.1 and 12.2.2. Its role is to maintain the relational integrity between the change request and the processes or users authorized to act upon it, enabling the structured management of contract amendments.

Key Information Stored

The table's structure is defined by a composite primary key and foreign key relationships. The primary columns are:

  • CRT_ID: The foreign key column referencing the unique identifier (CHANGE_REQUEST_ID) in OKC_CHANGE_REQUESTS_B. This column anchors the record to a specific contract change request.
  • CPS_ID: The foreign key column referencing the unique identifier (ID) in OKC_K_PROCESSES. This associates the change request with a specific workflow or approval process.
  • USER_ID: This column stores the identifier for a user associated with the change request, typically for tracking ownership or specific access rights.

The table's composite primary key (OKC_CR_K_ACCESSES_PK) on these three columns ensures a unique combination of change request, process, and user, preventing duplicate associations.

Common Use Cases and Queries

This table is primarily queried for workflow monitoring, access validation, and audit reporting. A common use case is identifying all active processes for a given change request to determine its current approval stage. For instance, to list all processes associated with a specific change request ID, one might execute:

SELECT a.crt_id, a.cps_id, p.process_name FROM okc_cr_k_accesses a, okc_k_processes p WHERE a.cps_id = p.id AND a.crt_id = :change_request_id;

Another typical scenario is verifying user authorization to modify or approve a change request by checking for the user's ID in the access records for that request. Reporting on the distribution of change requests across different processes also relies on joining this intersection table with its parent tables.

Related Objects

The OKC_CR_K_ACCESSES table is centrally linked to two key master tables via documented foreign key constraints:

  • OKC_CHANGE_REQUESTS_B: The master table for contract change requests. The foreign key from OKC_CR_K_ACCESSES.CRT_ID references OKC_CHANGE_REQUESTS_B.CHANGE_REQUEST_ID.
  • OKC_K_PROCESSES: The table defining workflow processes. The foreign key from OKC_CR_K_ACCESSES.CPS_ID references OKC_K_PROCESSES.ID.

These relationships are essential for any data retrieval involving the full context of a change request's workflow associations. Developers and integrators must use these joins to construct accurate reports or interfaces.