Results for “okl_k_lines_u1”

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

Overview

OKL.OKL_K_LINES is the Oracle Lease Management (OKL) extension table that stores lease-specific attributes for each contract line. Oracle Contracts core, through OKC_K_LINES_B, provides the generic contract line structure shared across all contract families; OKL_K_LINES carries the additional columns required exclusively for leases, loans, and related financial instruments. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the OKL schema (APPS design data OKL.OKL_K_LINES) and is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10.

Each row corresponds one-to-one with a contract line identified by ID, which is also the primary key (OKL_K_LINES_PK) and the column behind the unique index OKL_K_LINES_U1 — the index referenced by the user's search term. A second non-unique index, KLE_SUB_FK_I, supports foreign-key lookups on SUBSIDY_ID. Because the table is transaction-level data with a stable primary key, its heuristic Data Vault classification is hub-leaning: it can be modelled as a hub keyed on ID, with the many descriptive financial columns behaving as a satellite.

Key Information Stored

The most significant columns are:

• ID — surrogate primary key; unique index OKL_K_LINES_U1; joins to OKC_K_LINES_B and is the parent key for most OKL child tables.
• KLE_ID — self-referencing foreign key used to relate a lease line to a parent line row in this same table.
• STY_ID — foreign key to OKL_STRM_TYPE_B, defining the stream type (rental, residual, fee) associated with the line; STY_ID_FOR distinguishes the "for" stream type.
• OBJECT_VERSION_NUMBER — mandatory optimistic-locking column used by the OKL framework during concurrent updates.
• Residual and remarketing columns: RESIDUAL_VALUE, TRACKED_RESIDUAL, RESIDUAL_PERCENTAGE, DATE_RESIDUAL_LAST_REVIEW, REMARKETED_AMOUNT, DATE_REMARKETED, REPURCHASED_AMOUNT, DATE_REPURCHASED, GAIN_LOSS, and FLOOR_AMOUNT.
• Termination and buyout: TERMINATION_PURCHASE_AMOUNT, TERMINATION_VALUE, DATE_LAST_REAMORTISATION, and DATE_LAST_CLEANUP.
• Cost and asset attributes: OEC / ESTIMATED_OEC, INITIAL_DIRECT_COST, EXPECTED_ASSET_COST, CAPITAL_AMOUNT, CAPITALIZED_INTEREST, VENDOR_ADVANCE_PAID, and TRADEIN_AMOUNT.
• Yield and tax metrics: PRE_TAX_YIELD, AFTER_TAX_YIELD, IMPLICIT_INTEREST_RATE, PRE_TAX_IRR, AFTER_TAX_IRR, and the corresponding SUB_* subsidy-adjusted values.
• SUBSIDY_ID — foreign key to OKL_SUBSIDIES_ALL_B, with SUBSIDY_OVERRIDE_AMOUNT.
• CLG_ID, QTE_ID, and ORIG_CONTRACT_LINE_ID — links to collateral, quoting, and originating contract line records.
• Descriptive asset fields: MANUFACTURER_NAME, MODEL_NUMBER, YEAR_BUILT, YEAR_OF_MANUFACTURE, and DELIVERED_DATE.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the 15 ATTRIBUTE* descriptive flexfield columns.

The full table documents 130 columns, most of which are optional financial and asset-detail attributes.

Common Use Cases and Queries

Typical usage involves joining OKL_K_LINES to OKC_K_LINES_B through ID to obtain both the generic contract line and its lease-specific detail:

• Lease portfolio reporting — extract residual value, termination purchase amount, and OEC for every active lease line.
• Remarketing and gain/loss analysis — aggregate REMARKETED_AMOUNT, REPURCHASED_AMOUNT, and GAIN_LOSS by period using DATE_REMARKETED.
• Subsidy and yield review — join to OKL_SUBSIDIES_ALL_B on SUBSIDY_ID to reconcile pre-tax and after-tax yields, including subsidy-adjusted (SUB_*) metrics.
• Asset-detail queries — filter by MANUFACTURER_NAME, MODEL_NUMBER, or YEAR_BUILT for asset-based portfolio reporting.

A representative pattern: SELECT k.ID, k.RESIDUAL_VALUE, k.TERMINATION_PURCHASE_AMOUNT, c.CONTRACT_NUMBER FROM OKL_K_LINES k, OKC_K_LINES_B c WHERE k.ID = c.ID AND k.TRACKED_RESIDUAL IS NOT NULL; — always constrain by indexed columns and bind on ID where possible, since the table is large in production lease implementations.

Related Objects

The table is a central parent for many OKL child entities. The most significant relationships include:

• OKC_K_LINES_B — parent Contracts core line; joined on OKL_K_LINES.ID = OKC_K_LINES_B.ID.
• OKL_K_LINES (self-join) — KLE_ID relates lease lines to a parent lease line.
• OKL_SUBSIDIES_ALL_B — joined on SUBSIDY_ID.
• OKL_STREAMS — cash-flow streams reference KLE_ID. The stream type is driven by STY_ID → OKL_STRM_TYPE_B.
• Asset-tracking children: OKL_INS_ASSETS, OKL_INS_POLICIES_B, OKL_ASSET_CNDTNS, and OKL_ASSET_RETURNS_B all join on KLE_ID.
• Tax and invoicing children: OKL_TXL_ASSETS_B, OKL_TXL_AR_INV_LNS_B, OKL_TXL_AP_INV_LNS_B, and OKL_PROPERTY_TAX_ALL_B.
• Transaction and bulk-processing structures: OKL_SIF_LINES, OKL_SIF_FEES, OKL_SIF_TRX_PARMS, OKL_CNTR_LVLNG_LNS_B, and OKL_CNSLD_AR_LINES_B.
• Quoting and property data: OKL_TXL_QUOTE_LINES_B (via KLE_ID and SPLIT_KLE_ID) and OKL_POOL_CONTENTS.

Together these dependents confirm OKL_K_LINES as the operational anchor for lease-level financial, asset, and residual data in Oracle Lease Management.