Results for “okl_k_lines_full_v”

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

Overview

OKL_K_LINES_FULL_V is a VALID PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Lease and Finance Management product family. In ETRM releases 12.1.1 and 12.2.2, it serves as the consolidated "full" presentation layer for contract line data, joining the generic Contracts Core line definition with the lease-specific contract line extension. The view is defined by joining OKC_K_LINES_B, OKC_K_LINES_TL, and OKL_K_LINES so that a single query returns both the base contract line attributes and the lease management attributes attached to those lines.

Its primary role is to provide a reporting- and integration-friendly denormalized interface over the normalized Contracts/Lease model. Rather than requiring a developer to manually join the core line tables, the translation table, and the lease extension table, the view exposes one row per contract line (identified by ID and CLE_ID) with all columns pre-resolved. This makes it the reference object for ad hoc SQL, custom reports, and outbound interfaces that need contract line detail for lease and finance agreements.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is defined over the following referenced base objects:

• OKC_K_LINES_B (SYNONYM) — the Contracts Core base table holding the non-translatable attributes of a contract line.
• OKC_K_LINES_TL (SYNONYM) — the Contracts Core translation table holding language-dependent descriptive text such as NAME, COMMENTS, and ITEM_DESCRIPTION.
• OKL_K_LINES (SYNONYM) — the Lease and Finance Management extension table holding lease-specific line columns.

In the view text, the aliases CLEB and CLET refer to the core line base and translation rows respectively, while lease-specific columns are sourced through the OKL_K_LINES join. The view therefore behaves as a superset: every core contract line is decorated with its lease attributes, providing a unified contract-line record across both product layers.

Key Columns

The view exposes the full column set of a contract line. Notable columns include:

• ROW_ID, ID, OBJECT_VERSION_NUMBER — row identity and optimistic locking support.
• CHR_ID, CLE_ID, CLE_ID_RENEWED, CLE_ID_RENEWED_TO, LSE_ID, DNZ_CHR_ID — foreign keys linking the line to its contract header, renewal chain, lease, and related documents.
• LINE_NUMBER, DISPLAY_SEQUENCE, STS_CODE, TRN_CODE — line ordering, status, and transaction context.
• NAME, COMMENTS, ITEM_DESCRIPTION, OKE_BOE_DESCRIPTION, BLOCK23TEXT — descriptive/translated text sourced from OKC_K_LINES_TL.
• PRICE_UNIT, PRICE_UNIT_PERCENT, PRICE_NEGOTIATED, PRICE_NEGOTIATED_RENEWED, PRICE_LEVEL_IND, INVOICE_LINE_LEVEL_IND — pricing and billing-level indicators.
• START_DATE, END_DATE, DATE_TERMINATED — line effective dating.
• HIDDEN_IND, EXCEPTION_YN, TEMPLATE_USED, DPAS_RATING, SFWT_FLAG — control and classification flags.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF (descriptive flexfield) columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include lease line reporting, renewal chain analysis, pricing review, and custom inbound/outbound interfaces that populate or read lease contract lines. A representative query retrieving active lines for a contract header is:

• SELECT id, cle_id, line_number, name, start_date, end_date, sts_code, price_negotiated FROM okl_k_lines_full_v WHERE chr_id = :p_chr_id AND NVL(hidden_ind,'N') = 'N' ORDER BY display_sequence;
• Reporting on renewal lineage: SELECT id, cle_id, cle_id_renewed, cle_id_renewed_to, line_number FROM okl_k_lines_full_v WHERE cle_id_renewed IS NOT NULL;
• Pricing/valuation extracts: SELECT chr_id, lse_id, price_unit, price_negotiated, dpas_rating FROM okl_k_lines_full_v WHERE trn_code = :p_trn_code;

Because the view already resolves the core-to-lease join, it is the preferred source for any lease line extract; direct joins across OKC_K_LINES_B, OKC_K_LINES_TL, and OKL_K_LINES should generally be avoided in favor of this object.