Search Results line_style




Overview
Explore in AI Chat

Overview

OKL_CS_SERVICE_ASSETS_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined under the OKL (Leasing and Finance Management) product family. Its documented purpose is to expose service contract line details, combining contract header, line, item, customer account, and asset information into a single flattened structure. The view is reported as VALID in ETRM 12.2.2 and is referenced from the Oracle Leasing and Finance Management module, which integrates with Oracle Service Contracts (OKC) and Oracle Install Base (CSI) to reconcile leased assets against the service contracts that cover them.

Because it is a view rather than a base table, it does not store data; instead it derives results dynamically from the underlying OKC, OKX, and OKL objects. This makes it suitable for reporting, integration extracts, and ad-hoc queries where service contract line and asset detail must be presented together. The view is typically surfaced through BI Publisher reports, custom concurrent programs, or direct SQL used by technical consultants building interfaces between EBS and external systems.

Underlying Base Objects

The documented base objects referenced by OKL_CS_SERVICE_ASSETS_UV are:

The view definition is a UNION ALL of two branches. The first branch joins OKC contract lines with items, customer accounts, system items, asset lines, and ship-to/bill-to site uses, but is short-circuited by a WHERE 1!=1 predicate, effectively producing no rows. The second branch, which drives actual output, derives from OKC_K_ITEMS, OKC_K_LINES_V filtered through OKC_LINE_STYLES_B where LTY_CODE='COVER_PROD', and OKX_SYSTEM_ITEMS_V, with asset attributes supplied by OKL_CS_ASSET_LINES_V.

Key Columns

Common Use Cases and Queries

Typical usages include service coverage reporting, asset-to-contract reconciliation, and extraction feeds for downstream systems. A representative query listing active service lines for a contract is:

  • SELECT contract_id, service_line_number, service_name, asset_name, service_start_date, service_end_date FROM apps.okl_cs_service_assets_uv WHERE contract_id = :p_contract_id ORDER BY service_line_number;
  • SELECT asset_name, customer_account_name, service_start_date, service_end_date FROM apps.okl_cs_service_assets_uv WHERE TRUNC(SYSDATE) BETWEEN service_start_date AND service_end_date;
  • SELECT contract_id, COUNT(*) FROM apps.okl_cs_service_assets_uv GROUP BY contract_id HAVING COUNT(*) > 1;

Because the view calls underlying OKC and OKX views, query performance depends on the indexes on OKC_K_ITEMS, OKC_K_LINES_V, and CSI_ITEM_INSTANCES. For large extracts, restrict by contract or date range and avoid unrestricted full scans. All queries should be issued against the APPS schema or a synonym with appropriate grants.