Search Results chg_log_id

Overview

The OKE_CHG_LOGS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It functions as a historical audit trail, systematically recording the complete lifecycle of status changes for contract change requests. In the context of managing complex project contracts, where amendments, variations, and modifications are frequent, this table provides an immutable log that is critical for compliance, auditability, and process transparency. It captures the sequence of status transitions, such as from "DRAFT" to "SUBMITTED" to "APPROVED," along with contextual information about each transition, thereby enabling users to reconstruct the exact history of any change request. Its role is integral to the workflow-driven change management processes in Oracle Project Contracts.

Key Information Stored

The table's primary purpose is to log each discrete status change event. Its structure is designed to capture the event, its context, and the actor involved. The critical columns include CHG_LOG_ID, which serves as the unique primary key for each log entry. The CHG_REQUEST_ID column foreign key links the log entry to its parent change request in the OKE_CHG_REQUESTS table. The CHG_STATUS_CODE identifies the specific status (e.g., "APPROVED," "REJECTED") that was applied at the time of the log entry, referencing the OKE_CHG_STATUSES_B table. To integrate with the Oracle Workflow engine, the WF_ITEM_TYPE and WF_ITEM_KEY columns identify the specific workflow instance governing the change request. Additional standard columns, such as CREATION_DATE and CREATED_BY, record the timestamp and the user (or process) responsible for creating the log entry, completing the audit trail.

Common Use Cases and Queries

The primary use case is generating audit reports and analyzing the progression of change requests. Support personnel and contract administrators frequently query this table to diagnose process delays, verify approval sequences, or resolve disputes by providing a complete history. A common reporting query retrieves the full history for a specific contract change, ordered chronologically:

• SELECT chg_log_id, chg_status_code, creation_date, created_by FROM oke.oke_chg_logs WHERE chg_request_id = :req_id ORDER BY creation_date;

Another critical use case is determining the current status of a change request by fetching the most recent log entry, which is also maintained via the foreign key relationship OKE_CHG_REQUESTS.LAST_CHG_LOG_ID. Performance tuning may involve analyzing status transition times, requiring joins with workflow tables to understand bottlenecks in the approval routing.

Related Objects

The OKE_CHG_LOGS table exists within a tightly integrated schema. Its documented foreign key relationships are fundamental to its operation:

• OKE_CHG_REQUESTS: This is the primary parent table. The relationship is defined on OKE_CHG_LOGS.CHG_REQUEST_ID = OKE_CHG_REQUESTS.CHG_REQUEST_ID. The OKE_CHG_REQUESTS table also maintains a direct pointer to the most recent log entry via its LAST_CHG_LOG_ID column.
• OKE_CHG_STATUSES_B: Provides the meaning for the status code logged, via OKE_CHG_LOGS.CHG_STATUS_CODE = OKE_CHG_STATUSES_B.CHG_STATUS_CODE.
• Oracle Workflow Tables (WF_ITEM_TYPES, WF_ITEMS): The table links to the workflow engine through the composite foreign key on (OKE_CHG_LOGS.WF_ITEM_TYPE, OKE_CHG_LOGS.WF_ITEM_KEY) to WF_ITEMS, and on WF_ITEM_TYPE to WF_ITEM_TYPES. This connects the status change log to the underlying workflow process instance.