Results for “fcg_code”

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

Overview

OKL_K_LINES is a shadow table owned by the OKL schema within Oracle Lease and Finance Management (OKL), one of the products that ships on the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack. The table exists because Oracle Lease Management extends Oracle Contracts Core, whose standard contract line definition is held in OKC_K_LINES_B and OKC_K_LINES_TL. OKL_K_LINES carries the lease-specific attributes that do not fit into those standard Contracts Core line tables. Every lease line created in OKL therefore has a corresponding row in both OKL_K_LINES and OKC_K_LINES_B, with the shared identifier providing the vertical join between the two halves of the line record.

In 12.2.2 the documented physical schema contains 130 columns and a single primary key constraint, OKL_K_LINES_PK, defined on ID. A unique index, OKL_K_LINES_U1, is also defined on ID, making it the business-key candidate for the object. From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification: ID is the stable surrogate identifier shared with OKC_K_LINES_B, and the table anchors numerous dependent lease objects. It also exhibits link characteristics, since it references OKL_SUBSIDIES_ALL_B and contains a self-referencing relationship, and satellite characteristics, since it stores a wide set of descriptive and financial attributes.

Key Information Stored

The table is best understood as the lease extension of a contract line. Its most significant columns are:

• ID — primary key and the join key back to OKC_K_LINES_B; the unique index OKL_K_LINES_U1 makes it the business-key candidate.
• KLE_ID — the lease line identifier used by a large number of downstream OKL tables to reference this line.
• STY_ID — the line style or type, determining how the line behaves in lease processing.
• OBJECT_VERSION_NUMBER — optimistic locking column standard to EBS multi-tier forms.
• LAO_AMOUNT, CAPITAL_AMOUNT, CAPITAL_REDUCTION, CAPITALIZED_INTEREST — the core financial measures of the leased line.
• RESIDUAL_VALUE, RESIDUAL_PERCENTAGE, RESIDUAL_CODE, CAPITAL_REDUCTION_PERCENT, RESIDUAL_GRNTY_AMOUNT — residual and residual-guarantee treatment of the asset.
• IMPLICIT_INTEREST_RATE, PRE_TAX_YIELD, AFTER_TAX_YIELD, PRE_TAX_IRR, AFTER_TAX_IRR and the SUB_ variants — the yield and return calculations used by pricing and accounting.
• SUBSIDY_ID, SUBSIDY_OVERRIDE_AMOUNT, FEE_CHARGE, FEE_TYPE, FEE_PURPOSE_CODE — subsidy and fee handling on the line.
• CLG_ID, NTY_CODE, FCG_CODE, PRC_CODE — classification identifiers used elsewhere in lease processing.
• QTE_ID — linkage back to the originating quote.
• STREAM_TYPE_SUBCLASS, PAY_INVESTOR_FREQUENCY, PAY_INVESTOR_EVENT — billing and investor payment stream characteristics.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit trail.

Manufacturer and model attributes such as MANUFACTURER_NAME and MODEL_NUMBER, and legacy balance columns such as AMOUNT_BALANCE_LEGACY and DT_EFFECTIVE_BALANCE_LEGACY, are also present.

Common Use Cases and Queries

The most common requirement is to combine the standard Contracts Core line with its lease shadow attributes. A typical reporting query joins the two on ID:

• SELECT kb.ID, kb.CLE_ID, kl.LAO_AMOUNT, kl.RESIDUAL_VALUE, kl.IMPLICIT_INTEREST_RATE FROM OKC_K_LINES_B kb, OKL_K_LINES kl WHERE kb.ID = kl.ID; — a lease-line extract for pricing or residual reporting.
• Queries aggregating by KLE_ID to gather all dependent detail rows from OKL_STREAMS, OKL_INS_ASSETS, OKL_ASSET_RETURNS_B and similar tables.
• Reconciliation queries comparing LAO_AMOUNT or CAPITAL_AMOUNT against booked stream amounts.
• Audit queries filtering on LAST_UPDATE_DATE, CREATED_BY and OBJECT_VERSION_NUMBER to identify recently modified lease lines.
• Reporting on residual exposure using RESIDUAL_VALUE, RESIDUAL_PERCENTAGE and TRACKED_RESIDUAL.

Because the table underpins so many dependent objects, it is normally queried through the lease line view or the Lease Management application rather than directly.

Related Objects

• OKC_K_LINES_B — the Contracts Core base line table, joined on OKL_K_LINES.ID = OKC_K_LINES_B.ID.
• OKL_SUBSIDIES_ALL_B — referenced through OKL_K_LINES.SUBSIDY_ID.
• OKL_STREAMS — billing streams tied to the lease line via KLE_ID.
• OKL_INS_ASSETS / OKL_INS_POLICIES_B — insurance asset and policy records linked by KLE_ID.
• OKL_ASSET_CNDTNS / OKL_ASSET_RETURNS_B — asset condition and return documentation linked by KLE_ID.
• OKL_CNSLD_AR_LINES_B / OKL_CNSLD_AR_STRMS_B — consolidated receivables lines and streams linked by KLE_ID.
• OKL_TXL_QUOTE_LINES_B / OKL_TXL_QTE_LINES_ALL_B — quote lines referencing the line through KLE_ID and SPLIT_KLE_ID.
• OKL_PRTFL_LINES_B — portfolio line associations.
• OKL_SIF_LINES / OKL_SIF_FEES — stream interface records linked by KLE_ID.

The OKL_K_LINES_PK constraint on ID, together with OKL_K_LINES_U1, enforces uniqueness of the lease line identifier across the shadow and core tables.