Search Results okc_k_processes




Overview

The OKC_K_PROCESSES table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a junction table that establishes and manages the relationship between a specific contract and a specific business process. Its primary role is to define the application of a particular process, such as an approval or change workflow, to a particular contract document. This linkage is essential for enabling and tracking the lifecycle management of contracts within the Oracle EBS system, ensuring that contractual agreements follow defined operational procedures.

Key Information Stored

The table stores foreign key references that create the critical associations between entities. The primary columns include the ID (serving as the primary key), CHR_ID (linking to the contract header in OKC_K_HEADERS_B), PDF_ID (linking to the process definition in OKC_PROCESS_DEFS_B), and CRT_ID (linking to a change request in OKC_CHANGE_REQUESTS_B, if applicable). These columns collectively record which process is assigned to which contract, and optionally, the specific change request instance driving that process.

Common Use Cases and Queries

A primary use case is reporting on the workflow status of contracts. For instance, identifying all contracts currently in a specific approval process or tracing the process history for a given contract. Common SQL queries involve joining this table to the contract headers and process definitions tables.

  • Find processes for a contract: SELECT p.* FROM okc_k_processes p, okc_k_headers_b h WHERE p.chr_id = h.id AND h.contract_number = 'CONTRACT123';
  • List contracts using a specific process definition: SELECT h.contract_number FROM okc_k_processes p, okc_k_headers_b h, okc_process_defs_b d WHERE p.chr_id = h.id AND p.pdf_id = d.id AND d.name = 'MASTER_AGREEMENT_APPROVAL';

This table is also central for any custom integrations or extensions that need to trigger actions based on contract process state changes.

Related Objects

As indicated by its foreign keys, OKC_K_PROCESSES is integrally connected to several key tables. It is a child of OKC_K_HEADERS_B (contracts), OKC_PROCESS_DEFS_B (process templates), and OKC_CHANGE_REQUESTS_B. Conversely, it is a parent table to OKC_CR_K_ACCESSES, which manages access control for change requests linked to these contract-process associations. This relationship hierarchy underscores its position as a central hub for contract process execution data.