Results for “oke_k_lines_h”

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

Overview

OKE_K_LINES_H is a historical (versioned) table in the OKE — Project Contracts module of Oracle E-Business Suite, documented as valid in both 12.1.1 and 12.2.2. It stores historical, extended line-level information for project contracts. Each row captures the state of a contract line as of a specific major version, allowing the application to preserve prior revisions of lines alongside the current definition held in OKE_K_LINES. In that sense, the table functions as an auditable history store rather than the live transactional record.

The primary key OKE_K_LINES_H_PK is composed of (K_LINE_ID, MAJOR_VERSION), and the unique index OKE_K_LINES_H_U1 mirrors the same column pair. Because the key includes MAJOR_VERSION, multiple historical rows can exist per contract line, with K_LINE_ID identifying the line and MAJOR_VERSION identifying the revision. Based on the foreign key structure and the column layout, the heuristic Data Vault classification is satellite-leaning: the table behaves as a versioned satellite attached to the OKE_K_LINES hub, joined on K_LINE_ID and MAJOR_VERSION. This classification is a modeling suggestion mined from the FK topology, not an Oracle-published designation.

Key Information Stored

The table is documented with 104 columns in the 12.2.2 physical schema. The most significant columns fall into identification, project association, commercial terms, and government-contract attributes:

• K_LINE_ID — surrogate identifier of the contract line; part of the primary key and the principal join to OKE_K_LINES.
• MAJOR_VERSION — the revision number; second component of the primary key and the unique index OKE_K_LINES_H_U1, distinguishing historical states.
• PARENT_LINE_ID — self-referencing parent for hierarchical line structures.
• PROJECT_ID and TASK_ID — foreign keys to PA_PROJECTS_ALL and PA_TASKS, tying the line to a project and task.
• BILLING_METHOD_CODE — the billing method governing the line.
• LINE_QUANTITY, UNIT_PRICE, UOM_CODE — quantity, price, and unit of measure for the line.
• DELIVERY_DATE and PROPOSAL_DUE_DATE — key milestone dates.
• BILLABLE_FLAG, SHIPPABLE_FLAG, COMPLETED_FLAG — status and behavior indicators.
• CUSTOMER_ITEM_ID — foreign key to MTL_CUSTOMER_ITEMS, with CUSTOMER_ITEM_NUMBER as the descriptive counterpart.
• LINE_VALUE, LINE_VALUE_TOTAL, TARGET_PRICE, CEILING_PRICE, FIXED_FEE, AWARD_FEE — commercial and fee amounts relevant to reporting.
• AS_OF_DATE — the effective/version as-of date associated with the historical record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Additional columns support government and specialized contract constructs, including export licensing, definite/undefinitized pricing, progress payments, and cost-share ratios. These are relevant primarily for niche reporting rather than routine joins.

Common Use Cases and Queries

Typical use cases center on version history and audit:

• Retrieving the full revision history of a contract line by filtering on K_LINE_ID and ordering by MAJOR_VERSION.
• Comparing the current line (OKE_K_LINES) against a specific historical version.
• Point-in-time reporting using AS_OF_DATE to reconstruct line terms as they existed at a given revision.
• Joining to OKE_K_STANDARD_NOTES_BH, OKE_K_TERMS_H, and OKE_K_USER_ATTRIBUTES_H on (K_LINE_ID, MAJOR_VERSION) to assemble a complete historical line view.

A representative query pattern joins the current and historical tables:

SELECT h.k_line_id, h.major_version, h.line_quantity, h.unit_price, h.line_value
FROM   oke.oke_k_lines_h h
WHERE  h.k_line_id = :p_line_id
ORDER BY h.major_version DESC;

A project-oriented report could aggregate LINE_VALUE by PROJECT_ID over a chosen revision set. Because MAJOR_VERSION participates in the key, any join to OKE_K_LINES or the satellite history tables must include both K_LINE_ID and MAJOR_VERSION to avoid fan-out.

Related Objects

The following relationships are documented in the ETRM metadata:

• OKE_K_LINES — referenced via K_LINE_ID; the current line definition. Joined together with MAJOR_VERSION.
• OKC_K_LINES_BH — referenced via (K_LINE_ID, MAJOR_VERSION); the contracts core line history.
• PA_PROJECTS_ALL — referenced via PROJECT_ID; supplies project context.
• PA_TASKS — referenced via TASK_ID; supplies task context.
• MTL_CUSTOMER_ITEMS — referenced via CUSTOMER_ITEM_ID; identifies customer items.
• OKE_K_STANDARD_NOTES_BH — references this table on (K_LINE_ID, MAJOR_VERSION).
• OKE_K_TERMS_H — references this table on (K_LINE_ID, MAJOR_VERSION).
• OKE_K_USER_ATTRIBUTES_H — references this table on (K_LINE_ID, MAJOR_VERSION).

These child history tables descend from OKE_K_LINES_H by the same compound key, confirming its role as the parent versioned record for extended contract line information. Queries that traverse this family should consistently carry both K_LINE_ID and MAJOR_VERSION to preserve version integrity.