Search Results okl_cs_service_lines_uv




Overview
Explore in AI Chat

Overview

The APPS.OKL_CS_SERVICE_LINES_UV view is a reporting and integration object within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It exposes service line details associated with lease and finance contracts, presenting a flattened, denormalized projection of contract service information that spans the Oracle Contracts (OKC) and Leasing (OKL) schemas. The view is particularly relevant in releases 12.1.1 and 12.2.2, where it remains VALID and is used to surface "sold service" style lines—those contract lines whose line style code resolves to SOLD_SERVICE—for downstream reporting, integration, and analytics.

Because it consolidates contract header attributes, line items, leasing line amounts, service item definitions, and translated status meanings into a single result set, the view reduces the need for complex multi-table joins in custom reports and interfaces. It is a user-facing (UV) view, indicating it is intended for consumption by application logic, forms, and external integrations rather than for direct transactional DML.

Underlying Base Objects

The view is defined over eight documented base objects, all referenced through APPS synonyms except one view:

Joins are enforced on line ID, contract ID (DNZ_CHR_ID), status code, and item identifiers, ensuring that only lines tied to valid, non-abandoned service contracts are returned (STS_CODE NOT IN 'ABANDONED').

Key Columns

  • CLE_ID — the contract line identifier, primary correlation key to OKC_K_LINES_B.
  • SERVICE_NAME — the name of the sold service item from OKX_SYSTEM_ITEMS_V.
  • AMOUNT — the monetary value of the service line from OKL_K_LINES.
  • START_DATE / END_DATE — the effective service period of the line.
  • STATUS — the translated status meaning (e.g., Active) derived from OKC_STATUSES_TL.
  • CONTRACT_NUMBER — the human-readable contract number from OKC_K_HEADERS_B.
  • CONTRACT_ID — the internal contract (DNZ_CHR_ID) identifier.
  • CURRENCY_CODE — the contract currency, enabling multi-currency reporting.

Common Use Cases and Queries

Typical scenarios include reporting active sold-service revenue by contract, reconciling service line amounts, and populating integration staging tables. A representative query:

  • SELECT CONTRACT_NUMBER, SERVICE_NAME, AMOUNT, START_DATE, END_DATE, STATUS, CURRENCY_CODE FROM APPS.OKL_CS_SERVICE_LINES_UV WHERE STATUS = 'Active' ORDER BY CONTRACT_NUMBER;

The view should be treated as read-only. Because it embeds USERENV('LANG') and OKX_SYSTEM_ITEMS_V, performance depends on proper indexing of OKC_K_LINES_B and OKC_K_ITEMS; querying by CONTRACT_NUMBER or CONTRACT_ID is generally most efficient.