Search Results oks_cov_types_v




Overview
Explore in AI Chat

Overview

The OKS_COV_TYPES_V view is a reporting and integration object in the Oracle E-Business Suite (EBS) Service Contracts (OKS) module. It is owned by the APPS schema and holds a VALID status across release levels 12.1.1 and 12.2.2. As its name implies, the view presents coverage types — the classification values that define the nature of coverage a service contract provides to a customer's covered item (for example, parts-only, labor-only, full coverage, or preventive maintenance).

Because coverage type is referenced throughout the Service Contracts data model — on contract lines, entitlements, and coverage records — this view primarily serves as a denormalized, translation-aware lookup. Rather than exposing the raw base tables, it flattens the code, the language-specific meaning and description, and the full set of descriptive flexfield and audit columns into a single consumable result set. This makes it suitable for reports, Discoverer/BI Publisher queries, and inbound/outbound interface work where a human-readable coverage type label is required alongside the internal code. It is not a transactional table; it is a reference view whose rows change only when coverage types are configured or translated.

Underlying Base Objects

Consistent with the ETRM documented view text, OKS_COV_TYPES_V is defined over two APPS synonyms:

  • OKS_COV_TYPES_B — the base (non-translated) table holding the coverage type code and its operational attributes.
  • OKS_COV_TYPES_TL — the translation table holding the language-specific meaning and description.

The join is performed on B.CODE = T.CODE, and the language is restricted by T.LANGUAGE = USERENV('LANG'). This restriction returns only the rows whose translation matches the session language, so the view yields the correct meaning and description for the current user's locale without the caller having to filter explicitly. The ROW_ID column is sourced from B.ROWID.

Key Columns

  • ROW_ID — the ROWID of the underlying B-table row, useful as a unique identifier.
  • CODE — the internal coverage type code, the joined key between base and translation tables.
  • MEANING — the translated display name of the coverage type.
  • DESCRIPTION — the translated longer description.
  • IMPORTANCE_LEVEL — a ranking/priority indicator associated with the coverage type.
  • ENABLED_FLAG — indicates whether the coverage type is active and available for use.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range for the coverage type.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments carrying client-specific attributes.

Common Use Cases and Queries

Typical uses include populating coverage type list-of-values in custom forms or OAF pages, joining to contract/coverage tables when a readable coverage type is needed, and validating inbound interface data before posting to Service Contracts. The ENABLED_FLAG and date columns are frequently applied as filters so only currently valid types are returned.

List all enabled coverage types for the current language:

SELECT code, meaning, description
FROM   apps.oks_cov_types_v
WHERE  enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN
       NVL(start_date_active, TRUNC(SYSDATE))
       AND NVL(end_date_active, TRUNC(SYSDATE))
ORDER BY meaning;

Look up a single coverage type label by code:

SELECT meaning, importance_level
FROM   apps.oks_cov_types_v
WHERE  code = :p_code;

When querying from a custom schema, prefix the view with the APPS schema or use a synonym granting SELECT to the working schema, since the object is owned by APPS.