Search Results coverage_line_id




Overview
Explore in AI Chat

Overview

OKS_ENT_LINE_DETAILS_V is an APPS-owned, VALID database view within the Oracle Service Contracts (OKS) module. It is documented in ETRM as a specialized entitlement-oriented view whose defining design constraint is that it "is supposed to be called only by passing service_line_id as bind variable." This statement is significant: the view is not intended as a general-purpose contract-lines listing, but as a single-row (or single-line) lookup that resolves entitlement details for one service line identified by its primary key, SVL.ID.

Functionally, the view joins contract header, contract line, contract item, inventory item, and coverage line information to present a consolidated entitlement record per service line. It surfaces the contract identity, the serviced product, the coverage defined against that product, the effective date range, a warranty indicator and the current status code. Because the driving filter is the service line identifier, the view is typically embedded in PL/SQL logic and Oracle Forms/Service Contracts screens that already hold a service_line_id in context, returning the descriptive and coverage attributes needed for display or downstream processing.

Underlying Base Objects

The documented referenced base objects are MTL_SYSTEM_ITEMS_B_KFV (a key flexfield view over inventory items), OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_LINES_V, and OKS_K_LINES_B. The view text confirms which of these are joined in the visible definition and how:

OKS_K_LINES_B appears in the documented dependency list as an OKS synonym supporting entitlement logic, though it is not directly referenced in the visible header-to-coverage join chain.

Key Columns

  • CONTRACT_ID, CONTRACT_NUMBER, MODIFIER — the contract header identity, including the contract number modifier used to distinguish versions or amendments.
  • SERVICE_LINE_ID — the primary bind-variable key; the identifier that must be supplied to retrieve a meaningful result.
  • SERVICE_NAME, SERVICE_DESCRIPTION — the serviced inventory item's concatenated segments and description, drawn from the key flexfield view.
  • COVERAGE_LINE_ID, COVERAGE_NAME, COVERAGE_DESCRIPTION — the coverage defined on the line, including the coverage item description.
  • SERVICE_START_DATE, SERVICE_END_DATE — the service line effective period.
  • WARRANTY_FLAG — derived via DECODE on SVL.LSE_ID: 1 yields 'N', 14 yields 'Y', 19 yields 'N', otherwise NULL. This maps the line subtype to a warranty indicator.
  • STATUS_CODE — the service line status (STS_CODE).

Common Use Cases and Queries

The view is most commonly used to resolve entitlement details for a known service line, for example when validating coverage during a service request or displaying contract coverage on a form. Typical usage passes a literal or bind variable:

  • SELECT contract_number, service_name, coverage_name, warranty_flag, status_code FROM oks_ent_line_details_v WHERE service_line_id = :service_line_id;
  • Entitlement lookups within integrations that need the coverage and warranty status for a given line.
  • Reporting joins that start from a driving query returning service_line_id values and then enrich each row using this view.

Because the definition is not optimized for set-based access, queries returning many rows without a service_line_id predicate can be inefficient; the documented intent is single-line retrieval by primary key.