Results for “exception_coverage_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKS_ENT_COVERAGES_V view in the APPS schema is a Service Contracts (OKS) reporting object that consolidates entitlement coverage information attached to contract lines. It is delivered as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 codebase and is catalogued in the ETRM documentation with the description "View all Coverages attached to a Contract Line." The "ENT" prefix reflects its role in the entitlements data model, where service and warranty coverages are associated with serviceable items through contract lines. The view is not an operational table; it is a read-only construct intended for extracting entitlement/coverage data for reporting, reconciliation, and downstream integration into order management, service fulfillment, or third-party systems that consume entitlement records. Because it joins translated and base tables, it also respects the session language through USERENV('LANG'), making it suitable for multilingual deployments.

Underlying Base Objects

The view is defined over six documented base objects, all exposed to APPS through synonyms:

• OKC_K_HEADERS_ALL_B — contract header, providing the contract ID and contract number.
• OKC_K_LINES_B — contract lines, supplying line ID, start/end dates, and the DATE_TERMINATED value central to the search that prompted this article.
• OKC_K_LINES_TL — translated line name and description, filtered by session language.
• OKC_K_ITEMS — contract line items, where JTOT_OBJECT1_CODE is restricted to OKX_SERVICE or OKX_WARRANTY to isolate serviceable objects.
• OKS_K_LINES_B — the service-contract line extension holding EXCEPTION_COV_ID.
• OKS_COV_TYPES_TL — translated coverage type definitions, joined to COVERAGE_TYPE to derive the coverage meaning.

The join is anchored on HD.ID = KL.DNZ_CHR_ID, with line lookups restricted to LSE_ID IN (2, 15, 20), which corresponds to the line-level structure types used by service contracts.

Key Columns

• ACTUAL_COVERAGE_ID (KL.ID) — the contract line ID of the coverage line.
• CONTRACT_ID / CONTRACT_NUMBER — header identity for the parent contract.
• CONTRACT_LINE_ID (KL.CLE_ID) — the covered contract line entity.
• SERVICE_ITEM_ID — extracted from IT.OBJECT1_ID1 as a number.
• COVERAGE_NAME / COVERAGE_DESC — line-level name and description.
• COVERAGE_MEANING — the decoded coverage type from OKS_COV_TYPES_TL.
• START_DATE / END_DATE — the effective coverage window.
• DATE_TERMINATED — the date on which the coverage/line was terminated; null when still active. This column is critical for distinguishing live entitlements from lapsed ones.
• EXCEPTION_COVERAGE_ID — reference to an exception coverage record, if any.

Common Use Cases and Queries

Typical use cases include active-entitlement reports, expired-coverage reconciliation, and integration feeds that must exclude terminated coverages. A common query filters out terminated lines:

• SELECT contract_number, coverage_name, start_date, end_date FROM oks_ent_coverages_v WHERE date_terminated IS NULL;
• SELECT contract_number, coverage_name, date_terminated FROM oks_ent_coverages_v WHERE date_terminated IS NOT NULL AND date_terminated BETWEEN :from_date AND :to_date;
• SELECT service_item_id, coverage_meaning, end_date FROM oks_ent_coverages_v WHERE end_date >= SYSDATE;

Reports joining this view to service item master data often key on SERVICE_ITEM_ID, while coverage-type analysis groups on COVERAGE_MEANING. Because it unions multiple translated joins, queries should apply language-consistent filters and be run with the correct LANG session context to avoid missing rows.