Results for “okc_k_processes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_K_PROCESSES is a transactional table in the OKC (Contracts Core) schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It defines the use of a particular process for a particular contract. In practical terms, the table records the association between a contract header and a process definition, capturing which contract lifecycle process (for example, a fulfillment, approval, or renewal process template) has been applied to a given contract, and optionally the change request that introduced that association. The table is a core component of the Contracts Core process framework used by Oracle Contracts, Oracle Sales Contracts, and related modules that rely on contract process tracking.

From a data-vault modeling perspective, the metadata heuristic classifies OKC_K_PROCESSES as satellite-leaning. It sits adjacent to the OKC_K_HEADERS_B hub (parent contract) and carries descriptive, process-instance attributes rather than acting as a pure relationship table. The candidate that best anchors it to a contract is CHR_ID, while PDF_ID anchors it to a process definition and CRT_ID to a change request, giving the row a composite business identity.

Key Information Stored

The table exposes 30 documented columns. The most important ones for functional and reporting purposes are:

• ID — surrogate primary key, enforced by OKC_K_PROCESSES_PK and also the unique index OKC_K_PROCESSES_U1.
• CHR_ID — foreign key to OKC_K_HEADERS_B, identifying the contract header the process applies to.
• PDF_ID — foreign key to OKC_PROCESS_DEFS_B, identifying the process definition being used.
• CRT_ID — foreign key to OKC_CHANGE_REQUESTS_B, tying the process use to a specific change request.
• PROCESS_ID — internal process instance identifier.
• IN_PROCESS_YN — flag indicating whether the process is currently active for the contract.
• USER_ID — the user associated with the process record.
• OBJECT_VERSION_NUMBER — used for optimistic locking in the OAF-based Contracts UI.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-org / data security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) columns available to extend process instances.

The unique index OKC_K_PROCESSES_U2 on (CHR_ID, PDF_ID, CRT_ID) is the business-key candidate: it prevents duplicate application of the same process definition to a contract within a given change request.

Common Use Cases and Queries

Typical scenarios include determining which process a contract is following, reporting on active versus inactive processes, and tracing process application to change requests. Sample query patterns include:

• Locating all processes associated with one contract: SELECT ID, PDF_ID, IN_PROCESS_YN FROM OKC_K_PROCESSES WHERE CHR_ID = :chr_id;
• Finding contracts currently in process: SELECT CHR_ID, PDF_ID FROM OKC_K_PROCESSES WHERE IN_PROCESS_YN = 'Y';
• Joining to header and definition for a reporting view: SELECT kh.CONTRACT_NUMBER, pd.NAME, kp.IN_PROCESS_YN FROM OKC_K_PROCESSES kp, OKC_K_HEADERS_B kh, OKC_PROCESS_DEFS_B pd WHERE kp.CHR_ID = kh.ID AND kp.PDF_ID = pd.ID;
• Auditing process creation activity: SELECT CREATED_BY, CREATION_DATE FROM OKC_K_PROCESSES WHERE CHR_ID = :chr_id ORDER BY CREATION_DATE;

These queries support process compliance reporting, change-request impact analysis, and operational dashboards tracking contract progression.

Related Objects

• OKC_K_HEADERS_B — joined on OKC_K_PROCESSES.CHR_ID = OKC_K_HEADERS_B.ID; the parent contract header.
• OKC_PROCESS_DEFS_B — joined on OKC_K_PROCESSES.PDF_ID = OKC_PROCESS_DEFS_B.ID; the process definition catalog.
• OKC_CHANGE_REQUESTS_B — joined on OKC_K_PROCESSES.CRT_ID = OKC_CHANGE_REQUESTS_B.ID; the change request that authorized the process use.
• OKC_CR_K_ACCESSES — child table referencing OKC_K_PROCESSES via OKC_CR_K_ACCESSES.CPS_ID = OKC_K_PROCESSES.ID, storing change-request access records.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for privilege and security-group filtering.
• OKC_K_PROCESSES_PK / _U1 / _U2 — the primary key and unique constraints that enforce row identity and the composite business key.