Search Results party_rle_code




Overview
Explore in AI Chat

Overview

OKL_K_TOP_LINE_UV is an APPS-owned database view in Oracle EBS Release 12.1.1 and 12.2.2 that consolidates the top-level attributes of an OKL (Oracle Lease Management) contract line together with its associated style, item, and party role information. The view is defined over five documented base objects — OKC_K_LINES_B, OKL_K_LINES, OKC_LINE_STYLES_B, OKC_K_ITEMS, and OKC_K_PARTY_ROLES_B — all exposed in APPS through synonyms. In practice it serves as a flattened, denormalized reporting surface for lease and contract line data, joining the contract authoring (OKC) structures with the lease-specific (OKL) line extensions. The "_UV" suffix denotes a user view in the ETRM/OKL naming convention, and the view is intended primarily for read-only query and integration rather than transactional DML.

Underlying Base Objects

The view is defined over the following documented base objects, each referenced via an APPS synonym:

  • OKC_K_LINES_B (CLE) — the contract line base table supplying identity, status, currency, numbering, sequence, dates, and the owning contract header (CHR_ID/DNZ_CHR_ID).
  • OKL_K_LINES (KLE) — the lease line extension supplying monetary amounts and descriptive flexfield attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15).
  • OKC_LINE_STYLES_B (LSE) — the line style definition supplying the line style code (LTY_CODE).
  • OKC_K_ITEMS (ITEM) — items attached to the line, supplying object identifiers, UOM, item counts, and the exception flag.
  • OKC_K_PARTY_ROLES_B (PARTY) — party roles attached to the line, supplying party identifiers, role code, and object references.

The core join is anchored on lse.id = cle.lse_id, kle.id = cle.id, and item.cle_id = cle.id. The party join is an outer join on party.cle_id(+) = cle.id AND party.dnz_chr_id(+) = cle.dnz_chr_id, so lines without a party role are still returned. Because the party and item joins are one-to-many, the view can produce multiple rows per line — one per associated item and/or party role.

Key Columns

For the user's search term party_rle_code, the relevant column is PARTY_RLE_CODE, sourced as party.rle_code from OKC_K_PARTY_ROLES_B. It carries the party role code (for example, a lessee, lessor, or other role designation) associated with the contract line. Related party columns include PARTY_ID, PARTY_CLE_ID, PARTY_OBJECT1_ID1, PARTY_OBJECT1_ID2, PARTY_JTOT_OBJECT1_CODE, and PARTY_DNZ_CHR_ID.

Other significant columns, grouped by prefix, include: 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_DNZ_CHR_ID, LINE_CHR_ID); amount columns (LINE_AMOUNT, LINE_CAPITAL_AMOUNT); item columns (ITEM_ID, ITEM_UOM_CODE, ITEM_NUMBER_OF_ITEMS, ITEM_EXCEPTION_YN); style column (LS_LTY_CODE); and the fifteen descriptive flexfield attributes plus ATTRIBUTE_CATEGORY from OKL_K_LINES.

Common Use Cases and Queries

Typical usage includes lease line reporting, party role analysis, amount reconciliation, and downstream integration extracts. Because of the naming prefixing, all columns must be referenced by their aliased view names.

To list all lines and their party role codes:

  • SELECT line_id, line_line_number, party_id, party_rle_code FROM apps.okl_k_top_line_uv ORDER BY line_id;

To find lines bearing a specific role code:

  • SELECT line_id, line_lse_id, ls_lty_code, line_amount FROM apps.okl_k_top_line_uv WHERE party_rle_code = 'LESSEE';

To aggregate line amounts by currency, deduplicating repeated item/party rows:

  • SELECT DISTINCT line_id, line_currency_code, line_amount FROM apps.okl_k_top_line_uv;

Interpretation must account for the outer-join and one-to-many behavior: PARTY_RLE_CODE may be null when no role exists, and line-level amounts can repeat across rows generated by multiple items or roles. Filtering on PARTY_RLE_CODE also implicitly filters out lines without roles, since nulls are excluded by equality predicates.