Results for “okc_k_processes_h”

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

Overview

OKC_K_PROCESSES_H is a history (or audit mirror) table within the OKC — Contracts Core module of Oracle E-Business Suite, owned by the OKC schema and valid in both release 12.1.1 and 12.2.2. As stated in the ETRM metadata, it is a mirror image of the base table OKC_K_PROCESSES, and column-level semantics are inherited from that base object rather than redefined here. The suffix "_H" conventionally denotes a versioned or historical companion table in Oracle EBS, used to retain successive major versions of the base record so that the current state in OKC_K_PROCESSES is preserved alongside prior states.

From a heuristic Data Vault perspective — mined from the documented FK structure — this table is classified as standalone. In Data Vault modeling terms, a standalone object of this shape (composite key of ID plus MAJOR_VERSION, descriptive and audit columns, no dependent child joins) is best modeled as a satellite attached to the base process hub/link represented by OKC_K_PROCESSES. This is a modeling suggestion only; no enforced parent-child FK to the base table is documented.

Key Information Stored

The physical schema documents 31 columns. The following are the most significant for querying and integration:

• ID — Surrogate/primary identifier carried from the base process record. Part of the composite primary key OKC_K_PROCESSES_H_PK.
• MAJOR_VERSION — The version discriminator. Combined with ID, it forms the primary key and the unique business-key candidate OKC_K_PROCESSES_H_U1 (ID, MAJOR_VERSION).
• PROCESS_ID — Reference to the underlying process definition being versioned.
• PDF_ID, CHR_ID, USER_ID, CRT_ID — Document, contract-header, user, and contract/record reference identifiers linking the process row to its contract context.
• IN_PROCESS_YN — Status flag indicating whether the process is currently in progress.
• OBJECT_VERSION_NUMBER — Optimistic locking counter maintained by the Oracle framework for concurrent updates.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/data-security scoping.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) storage columns.

The documented PK is OKC_K_PROCESSES_H_PK (ID, MAJOR_VERSION), and OKC_K_PROCESSES_H_U1 (ID, MAJOR_VERSION) is the unique index corresponding to the same business key.

Common Use Cases and Queries

Primary use cases include version-history reporting, audit reconstruction, and point-in-time analysis of contract processes. Analysts join this table back to OKC_K_PROCESSES on ID to compare the current row against its prior versions.

Typical pattern — retrieve all versions of a process:

• SELECT ID, MAJOR_VERSION, PROCESS_ID, IN_PROCESS_YN, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC_K_PROCESSES_H WHERE ID = :p_id ORDER BY MAJOR_VERSION DESC;

Audit pattern — find rows changed within a window:

• SELECT * FROM OKC_K_PROCESSES_H WHERE LAST_UPDATE_DATE BETWEEN :from_date AND :to_date AND SECURITY_GROUP_ID = :sgid;

Reconciliation pattern — detect drift between base and history:

• SELECT b.ID FROM OKC_K_PROCESSES b, OKC_K_PROCESSES_H h WHERE b.ID = h.ID AND b.OBJECT_VERSION_NUMBER <> h.OBJECT_VERSION_NUMBER;

Related Objects

• OKC_K_PROCESSES — The base table this object mirrors; join on ID.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; enforces data security.
• OKC_K_PROCESSES_H_PK / OKC_K_PROCESSES_H_U1 — Primary key constraint and unique business-key index (ID, MAJOR_VERSION).
• OKC_K_LINES / OKC_K_HEADERS — Contract line and header objects indirectly linked through CHR_ID and CRT_ID.
• OKC_K_PROCESSES APIs (OKC_PROCESS_PUB) — Business logic that populates and versions process rows.
• FND_USER — Resolves CREATED_BY, LAST_UPDATED_BY, USER_ID to user identities for audit reporting.