Search Results oke_k_lines_h




Overview
Explore in AI Chat

Overview

The OKE_K_LINES_H table is a core data object within the Oracle E-Business Suite Project Contracts (OKE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the historical repository for extended line information from project contracts. Its primary role is to maintain a complete, versioned audit trail of changes made to contract lines. This historical tracking is essential for compliance, auditing, and understanding the evolution of contractual terms and deliverables over the lifecycle of a project contract. The table works in conjunction with its base table, OKE_K_LINES, storing a new historical record each time a major version of a contract line is created or modified.

Key Information Stored

The table stores a snapshot of all attributes from a project contract line at a point in time. While the specific column list is not detailed in the provided metadata, the structure is defined by its primary and foreign keys. The composite primary key consists of K_LINE_ID, which uniquely identifies the contract line, and MAJOR_VERSION, which denotes the specific historical snapshot. Critical foreign key columns include PROJECT_ID and TASK_ID, linking the contract line data to the underlying project and task structures in Oracle Projects (PA). This linkage is fundamental for integrating contract management with project execution, billing, and revenue recognition. Each row effectively represents a complete historical state of an extended contract line.

Common Use Cases and Queries

A primary use case is auditing the complete change history of a contract line for internal review or external compliance. Analysts may query this table to determine what was changed, when, and between which versions. Another key scenario is reporting on contractual metrics over time, such as tracking how the value, quantity, or associated project of a line item has evolved across contract amendments. A common SQL pattern involves joining OKE_K_LINES_H with OKE_K_HEADERS_H to get a consolidated historical view of the contract and its lines. For example:

  • SELECT h.k_line_id, h.major_version, h.project_id, h.creation_date FROM oke_k_lines_h h WHERE h.k_line_id = :line_id ORDER BY h.major_version;

This retrieves the version history for a specific contract line, which is crucial for understanding amendments and generating historical project contract reports.

Related Objects

The OKE_K_LINES_H table has integral relationships with several other historical and transactional tables, as documented by its foreign keys. Its primary relationship is with the base transactional table OKE_K_LINES (on K_LINE_ID). It also maintains a relationship with the core contract line history table OKC_K_LINES_BH (on K_LINE_ID, MAJOR_VERSION), anchoring the OKE extensions to the foundational Oracle Contracts data. For project integration, it references PA_PROJECTS_ALL and PA_TASKS (on PROJECT_ID and TASK_ID). Furthermore, it is the parent table for other historical extension tables, including OKE_K_TERMS_H, OKE_K_USER_ATTRIBUTES_H, and OKE_K_STANDARD_NOTES_BH, all joining on the composite key (K_LINE_ID, MAJOR_VERSION). This structure ensures a synchronized historical record across all extended attributes of a project contract line.