Search Results line_reference




Overview

APPS.OKL_CS_SERVICE_ASSETS_UV is a multi-part UNION ALL view in Oracle E-Business Suite that consolidates service asset information from Oracle Contracts (OKC) and Oracle Lease Management (OKL) source data. The view is designed to present service line details — contract identifiers, line references, service names, item identifiers, service date ranges, and customer/address attributes — in a single flattened result set suitable for reporting, integration, and inquiry purposes within the ETRM (Enterprise Trade and Relationship Management) product family.

The "_UV" suffix indicates a user-facing view that is typically consumed by OAF-based inquiry pages, concurrent programs, and customer-facing extracts rather than by the base transaction engine. A notable characteristic of this view is that the first branch of its UNION ALL uses a literal WHERE 1!=1 predicate, meaning the first SELECT acts as a structural placeholder that defines the column shape and data types of the result set, while the second branch — populated by an inline inline-view from OKC_K_ITEMS, OKC_K_LINES_V, and OKX_SYSTEM_ITEMS_V — supplies the actual rows.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKC_K_LINES_V (VIEW) — the contract line view supplying line identifiers, cognomen (line reference), line number, and start/end dates.
  • OKC_K_ITEMS (SYNONYM) — the contract line item table exposing object1_id1 and object1_id2, which link a service line to its inventory item or product definition.
  • OKC_LINE_STYLES_B (SYNONYM) — the line style base table; the join on lty_code='COVER_PROD' restricts results to covered-product lines.
  • OKL_CS_ASSET_LINES_V (VIEW) — the service asset line view providing asset name, asset description, and line style used for the address-related columns.
  • OKX_SYSTEM_ITEMS_V (VIEW) — the system item view supplying item name and description.
  • OKX_CUSTOMER_ACCOUNTS_V (VIEW) — provides the customer account name.
  • OKX_CUST_SITE_USES_V (VIEW) — used twice (aliased BTO and STO) to resolve bill-to and ship-to site address descriptions.
  • CSI_ITEM_INSTANCES (SYNONYM) and ARP_ADDR_LABEL_PKG (PACKAGE) — supporting objects referenced in the view's metadata lineage.

Key Columns

  • contract_id — the DNZ_CHR_ID from OKC_K_LINES_V, identifying the contract header.
  • line_id, line_reference, service_line_number — the contract line identifier, its cognomen (the value many users search for as "line reference"), and the sequential line number.
  • service_name — the description of the service from the system item view.
  • object1_id1 / object1_id2 — inventory item identifiers linking the service line to the covered product; rows where object1_id2 equals '#' are excluded.
  • service_start_date / service_end_date — the effective coverage period of the service line.
  • customer_account_name — the name of the customer account associated with the service.
  • line_bto_address / line_sto_address — bill-to and ship-to address descriptions derived respectively from the OKX_CUST_SITE_USES_V instances.
  • name / lse_type — asset name and line style attributes carried from the OKL_CS_ASSET_LINES_V join.

Common Use Cases and Queries

The view is most commonly queried to retrieve service coverage lines by contract, by covered item, or by line reference. A typical filter is on the searched term, line_reference:

  • Locate all service lines for a specific contract: SELECT contract_id, line_reference, service_name, service_start_date, service_end_date FROM apps.okl_cs_service_assets_uv WHERE contract_id = :p_contract_id;
  • Search by line reference: SELECT contract_id, line_id, service_name FROM apps.okl_cs_service_assets_uv WHERE line_reference = :p_line_ref;
  • Report active service coverage by customer: SELECT customer_account_name, service_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;
  • Link service lines to inventory items: SELECT line_reference, object1_id1, object1_id2, line_bto_address FROM apps.okl_cs_service_assets_uv WHERE object1_id2 <> '#';

Because the first UNION ALL branch is a no-row placeholder, all returned data originates from the OKC/OKL service line branch joined to OKX system items, customer accounts, and site uses, filtered to line styles with code COVER_PROD.