Search Results okc_k_lines




Overview
Explore in AI Chat

Overview

OKL_K_TOP_LINE_UV is a VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product. Its documented purpose is to provide a combined presentation of contract line and line item data — specifically, as the ETRM metadata states, a "combined view on okc_k_lines and okc_k_items for fee and service line pages." In practice, this view is the data source behind the OKL fee and service line user interface pages, and it is equally suitable for reporting and integration queries that need line-level detail joined with item, style, and party role information in a single flattened result set. Because it joins the generic Oracle Contracts (OKC) line and item tables with the OKL leasing line extension table, it bridges core contracts data with leasing-specific attributes, including descriptive flexfield columns.

Underlying Base Objects

The view text is defined over five documented base objects, all referenced through APPS synonyms:

  • OKC_K_LINES_B (alias CLE) — the contract line base table, supplying line identity, status, currency, line number, display sequence, dates, and the owning contract (CHR_ID) and document (DNZ_CHR_ID) keys.
  • OKL_K_LINES (alias KLE) — the leasing line extension table, supplying amount, capital amount, and the ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 flexfield columns.
  • OKC_LINE_STYLES_B (alias LSE) — the line style table, supplying the line type code (LTY_CODE) and style ID.
  • OKC_K_ITEMS (alias ITEM) — the contract line item table, supplying item identifiers, object references, unit of measure, exception flag, and item counts.
  • OKC_K_PARTY_ROLES_B (alias PARTY) — the party role table, supplying role code and party object references.

Joins are driven from the contract line: LSE.ID equals CLE.LSE_ID, KLE.ID equals CLE.ID, ITEM.CLE_ID equals CLE.ID, and ITEM.DNZ_CHR_ID equals CLE.DNZ_CHR_ID. The party role join is outer (PARTY.CLE_ID(+) and PARTY.DNZ_CHR_ID(+) equal the corresponding line columns), meaning lines without an associated party role are still returned.

Key Columns

Columns are prefixed to distinguish their source. LINE_ columns (LINE_ID, LINE_CLE_ID, LINE_STS_CODE, LINE_CURRENCY_CODE, LINE_LINE_NUMBER, LINE_DISPLAY_SEQUENCE, LINE_LSE_ID, LINE_START_DATE, LINE_END_DATE, LINE_AMOUNT, LINE_CAPITAL_AMOUNT, LINE_CHR_ID, LINE_DNZ_CHR_ID) describe the contract line and its leasing amounts. ITEM_ columns (ITEM_ID, ITEM_CLE_ID, ITEM_OBJECT1_ID1, ITEM_OBJECT1_ID2, ITEM_JTOT_OBJECT1_CODE, ITEM_CHR_ID, ITEM_DNZ_CHR_ID, ITEM_UOM_CODE, ITEM_EXCEPTION_YN, ITEM_NUMBER_OF_ITEMS) describe line items and their object references. PARTY_ columns (PARTY_ID, PARTY_RLE_CODE, PARTY_CLE_ID, PARTY_OBJECT1_ID1, PARTY_OBJECT1_ID2, PARTY_JTOT_OBJECT1_CODE, PARTY_DNZ_CHR_ID) describe associated party roles. LS_ columns (LS_LTY_CODE, LS_ID) identify the line style and type. ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 expose the leasing line descriptive flexfield.

Common Use Cases and Queries

Typical uses include fee and service line page rendering, leasing line reporting, and extracting contract line data with flexfield attributes and party roles. A representative query follows:

  • SELECT line_id, line_cle_id, line_line_number, line_amount, ls_lty_code, item_id, item_number_of_items, attribute1 FROM okl_k_top_line_uv WHERE line_dnz_chr_id = :p_dnz_chr_id ORDER BY line_display_sequence;
  • SELECT line_cle_id, line_currency_code, party_id, party_rle_code FROM okl_k_top_line_uv WHERE line_id = :p_line_id;
  • SELECT line_line_number, item_uom_code, item_exception_yn, line_capital_amount FROM okl_k_top_line_uv WHERE line_chr_id = :p_chr_id AND item_exception_yn = 'Y';

Because the party role join is outer, consumers should expect NULL PARTY_ columns for lines with no assigned role and filter accordingly. This view is read-only reporting metadata; it performs no DML and should not be used as a transaction entry point.