Results for “capitalized_interest”

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

Overview

OKL_K_LINES_H is the history (audit) table corresponding to OKL_K_LINES_B within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Lease and Finance Management (OKL) application. It resides in the OKL schema with status VALID. The table captures point-in-time, versioned snapshots of lease contract line records, preserving prior values whenever a contract line is created, amended, or otherwise modified. The _H suffix denotes historical storage, while _B denotes the current base record, following Oracle's standard convention for date-tracked entities.

From a data-modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is standalone. This suggests that the object is best modeled as a satellite-like history store keyed to the parent line entity, rather than as an independent hub or a link resolving relationships between hubs. The presence of MAJOR_VERSION in the primary key confirms that multiple versions of the same logical line coexist in the table, forming a slowly changing dimension history.

Key Information Stored

The documented physical schema contains 131 columns. The surrogate primary key is OKL_K_LINES_H_PK, defined on (ID, MAJOR_VERSION). The unique index OKL_K_LINES_H_U1 carries the same (ID, MAJOR_VERSION) combination, confirming that the business-key candidate is effectively the composite of the record identifier and its version number; ID links the historical row to its logical line identity, while MAJOR_VERSION distinguishes successive edits.

Among the most significant columns:

• KLE_ID and STY_ID — together with STY_ID_FOR, they associate the line with its lease/stream structure and identify the record's stream or type context.
• OBJECT_VERSION_NUMBER — supports optimistic locking and change detection between versions.
• LAO_AMOUNT, AMOUNT, CAPITAL_AMOUNT, and CAPITAL_REDUCTION — core financial values covering lease amount, capital, and reduction balances.
• TRACKED_RESIDUAL, RESIDUAL_VALUE, and RESIDUAL_GRNTY_AMOUNT — residual and residual-guarantee figures central to lease accounting.
• IMPLICIT_INTEREST_RATE, PRE_TAX_YIELD, AFTER_TAX_YIELD, PRE_TAX_IRR, and AFTER_TAX_IRR — yield and interest metrics used in profitability and pricing analysis.
• TERMINATION_VALUE, TERMINATION_PURCHASE_AMOUNT, REMARKETED_AMOUNT, REPURCHASED_AMOUNT, and GAIN_LOSS — end-of-term and remarketing data.
• DATE_FUNDING, DATE_ACCEPTED, DATE_TITLE_RECEIVED, and DATE_LAST_REAMORTISATION — key lifecycle dates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard WHO audit columns.
• Fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY — descriptive flexfield storage for client-specific data.

Common Use Cases and Queries

The primary use case is audit and change tracking: reconstructing the state of a contract line as of any prior period. Analysts query it alongside the base table to compare current versus historical values.

• Version history for a line: SELECT id, major_version, last_update_date, amount, capital_amount FROM okl_k_lines_h WHERE id = :p_id ORDER BY major_version;
• Point-in-time reconstruction: filter on CREATION_DATE or LAST_UPDATE_DATE to obtain the row effective at a given date.
• Residual and yield reporting: aggregate TRACKED_RESIDUAL, RESIDUAL_VALUE, PRE_TAX_YIELD, and AFTER_TAX_IRR across versions to trend pricing changes.
• Reamortization and termination analysis using DATE_LAST_REAMORTISATION, TERMINATION_VALUE, and GAIN_LOSS.

Related Objects

The most significant related objects are:

• OKL_K_LINES_B — the base table; joins on ID (and logically MAJOR_VERSION) to compare current against history.
• OKL_K_HEADERS_H and OKL_K_HEADERS_B — parent contract headers, related through the line's header/line hierarchy.
• OKL_K_LINES_H frequently joins to OKL stream/type reference tables via STY_ID and KLE_ID.
• OKL_K_LINES_H_PK / OKL_K_LINES_H_U1 — index objects enforcing the (ID, MAJOR_VERSION) integrity.
• Pricing and yield reference structures linked through PRC_CODE, NTY_CODE, and FCG_CODE.

Standard WHO audit attribution ties every row to the application user recorded in CREATED_BY and LAST_UPDATED_BY.