Search Results customer_account_name




Overview
Explore in AI Chat

Overview

OKS_LINE_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKS - Service Contracts module. Its status is VALID across EBS 12.1.1 and 12.2.2. The view consolidates service contract line information into a single denormalized result set, combining contract line attributes with service item descriptions, customer account names, and bill-to and ship-to address descriptions. It is intended primarily for reporting, extract, and integration scenarios in which a flat, human-readable representation of service contract lines is required without navigating the normalized OKC contract schema directly.

Because the view is defined in the APPS schema and joins several other Apps-owned views and synonyms, it is queryable from any custom concurrent program, BI Publisher report, or SQL*Plus session with the appropriate APPS grants. The view exposes only service lines: the WHERE clause constrains the result set to line styles identified by LSE_ID values of 1, 12, 14, and 19, requires a non-null header identifier (CHR_ID), and excludes sub-lines by requiring CLE_ID to be NULL.

Underlying Base Objects

The view is defined over the following documented base objects:

The inner joins to OKC_K_ITEMS and OKX_SYSTEM_ITEMS_V mean that a contract line is returned only when a matching item record and system item definition exist; the customer account and address joins are outer joins, so lines without a resolved account or site use still appear with NULL values in those columns.

Key Columns

  • CONTRACT_ID — Contract header identifier (L.DNZ_CHR_ID), the primary link back to the contract header.
  • LINE_ID — Contract line identifier (L.ID), the unique key for the service line.
  • LINE_REFERENCE — User-visible line reference (L.COGNOMEN).
  • SERVICE_LINE_NUMBER — Line number within the contract (L.LINE_NUMBER).
  • SERVICE_NAME — Description of the service item from OKX_SYSTEM_ITEMS_V.
  • OBJECT1_ID1 / OBJECT1_ID2 — Inventory item identifier pair that defines the service item.
  • SERVICE_START_DATE / SERVICE_END_DATE — Effective coverage period for the line.
  • CUSTOMER_ACCOUNT_NAME — Name of the customer account associated with the line.
  • LINE_BTO_ADDRESS / LINE_STO_ADDRESS — Line-level bill-to and ship-to address descriptions.

Common Use Cases and Queries

Typical scenarios include active service coverage reporting, customer entitlement extracts, and reconciliation of service lines to inventory items. A basic query listing all service lines for a contract follows:

  • SELECT contract_id, line_id, service_line_number, service_name, service_start_date, service_end_date FROM oks_line_details_v WHERE contract_id = :p_contract_id ORDER BY service_line_number;
  • SELECT customer_account_name, service_name, service_start_date, service_end_date FROM oks_line_details_v WHERE service_end_date >= SYSDATE;
  • SELECT l.contract_id, l.line_reference, l.object1_id1, l.object1_id2, l.line_bto_address FROM oks_line_details_v l WHERE l.service_name LIKE :p_service_pattern;

Because the view is not indexed independently, performance depends on the underlying OKC_K_LINES_V and its base tables; filtering by CONTRACT_ID or by the service date range is advisable in high-volume extracts.