Results for “sts_code”

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

Overview

The OKS_COVERED_LEVEL_V view is a Service Contracts (OKS) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is defined as the "Covered level view for Contract details form," meaning it supplies the covered-item level information rendered on the Service Contracts Contract Details form. The view resolves the relationship between a service contract line, the inventory item it covers, and the associated contract header, returning one row per covered item with its effective dates and status. Because it joins inventory item master data (via OKX_SYSTEM_ITEMS_V) to contract line and header data, the view is primarily intended for form-driven display and lightweight reporting rather than bulk data extraction. It carries a VALID status in the ETRM dictionary, confirming it is a supported, active database object in the documented releases.

Underlying Base Objects

Per the 12.2.2 ETRM metadata, the view is defined over the following referenced objects, all exposed through APPS synonyms except the item view:

• OKC_K_HEADERS_B (SYNONYM) — the contract header base table, providing the inventory organization context via INV_ORGANIZATION_ID.
• OKC_K_ITEMS (SYNONYM) — the contract line item table, supplying the object reference (OBJECT1_ID1) and the covered-level entity link (CLE_ID).
• OKC_K_LINES_B (SYNONYM) — the contract line base table, providing line start/end dates, status code, and the owning contract ID.
• OKX_SYSTEM_ITEMS_V (VIEW) — the system items view exposing the item NAME and ORGANIZATION_ID used to match the item to the correct inventory organization.

The internal view text further references the OKC_K_LINES_V, OKC_K_ITEMS_V, and OKC_K_HEADERS_V views. The WHERE clause fixes LSE_ID = 19 (the covered-level line style) and requires KL.CLE_ID IS NULL and MTL.ORGANIZATION_ID = KH.INV_ORGANIZATION_ID, which constrains results to top-level covered items within the contract's inventory organization.

Key Columns

• NAME — the inventory item name (from OKX_SYSTEM_ITEMS_V / MTL), identifying the covered product or service item.
• START_DATE — the effective start date of the covered level line.
• END_DATE — the effective end date of the covered level line.
• STS_CODE — the status code of the contract line, indicating whether the covered level is active, expired, or otherwise.
• DNZ_CHR_ID — the contract header identifier (the "donor" contract ID) linking the covered level back to its parent contract in OKC_K_HEADERS_B.

Common Use Cases and Queries

The view is typically used to list covered items for a given contract, to reconcile coverage against inventory organizations, or to feed the Contract Details form. A representative query returns all covered items for a specific contract:

SELECT name, start_date, end_date, sts_code, dnz_chr_id FROM apps.oks_covered_level_v WHERE dnz_chr_id = :contract_id AND sts_code = 'ACTIVE';

To report active coverage by item across contracts:

SELECT name, COUNT(*) covered_count FROM apps.oks_covered_level_v WHERE sts_code = 'ACTIVE' GROUP BY name ORDER BY covered_count DESC;

Note that the view fixes LSE_ID = 19 and restricts to CLE_ID IS NULL, so it surfaces only the top covered level and should not be substituted for OKC_K_ITEMS when sub-level or component coverage detail is required. Queries against it inherit the APPS schema privileges and the inventory-organization join, so item names resolve only where the header organization matches the item organization.