Search Results covred_level

Overview

APPS.OKS_PROD_DETAILS_V is a service contract reporting view in Oracle E-Business Suite, owned by the APPS schema and defined in the Oracle Contracts (OKS/OKC) module. It flattens the relationship between a service contract (or subscription) and the products, systems, and customer accounts that the contract covers, exposing one row per covered item or covered line. The view is a UNION ALL of three SELECT branches, each targeting a distinct group of line styles (LSE_ID values), which allows the same reporting structure to serve hardware items, customer accounts, and systems coverage under a single consistent column layout.

The view is commonly used in ETRM/TeleService reporting, service contract integration extracts, and custom dashboards where users need to answer questions such as "which products are covered by this contract and at what level?" The COVRED_LEVEL column (a typographical variant of "covered level") returns the line style name from OKC_LINE_STYLES_TL, which identifies the coverage category for the line.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_K_HEADERS_B — contract header (joined via DNZ_CHR_ID = K.ID, and INV_ORGANIZATION_ID is used to reach the item master).
• OKC_K_LINES_B — contract lines; DNZ_CHR_ID, CLE_ID, ID, LINE_NUMBER, LSE_ID, and PRICE_NEGOTIATED are sourced here.
• OKC_LINE_STYLES_TL — line style translations supplying the NAME exposed as COVRED_LEVEL, filtered by USERENV('LANG').
• OKC_K_ITEMS — covered items; OBJECT1_ID1, NUMBER_OF_ITEMS, and UOM_CODE are drawn here.
• OKX_SYSTEM_ITEMS_V — item descriptions used for COVD_DESCRIPTION.
• CS_CUSTOMER_PRODUCTS_ALL / CS_CUSTOMER_PRODUCTS — Installed Base customer products supplying CURRENT_SERIAL_NUMBER.
• OKX_CUSTOMER_ACCOUNTS_V — customer/party accounts for the covered-level 35 branch.
• Related OKX views such as OKX_SYSTEMS_V, OKX_CUST_SITE_USES_V, and OKX_PARTIES_V support the underlying party/account resolution. ARP_ADDR_LABEL_PKG and CSICUMPI_PUB are referenced supporting packages.

Key Columns

• CONTRACT_ID — header identifier (OKC_K_HEADERS_B.ID), used to group covered lines by contract.
• LINE_ID — the parent contract line (OKC_K_LINES_B.CLE_ID).
• COVD_LINE_ID / COVD_LINE_NUMBER / COVD_LINE_LSE_ID — the covered line's identifier, sequence number, and line style.
• COVRED_LEVEL — line style name indicating the level of coverage (for example the LSE_ID 7, 9, 18, 25, or 35 categories).
• COVERED_SYSTEM — populated as NULL in the view text.
• COVERED_SERIAL_NO — serial number from CS_CUSTOMER_PRODUCTS for the covered installed-base product.
• COVD_DESCRIPTION — item or account description from the OKX item/account views.
• OBJECT_ID — the reference identifier of the covered object in OKC_K_ITEMS.
• QUANTITY / QTY_UOM — number of covered items and its unit of measure.
• PRICE — negotiated price on the contract line.

Common Use Cases and Queries

A typical query lists all covered products for a contract, including serial number and coverage level:

SELECT contract_id, covd_line_number, covred_level,
       covd_description, covered_serial_no,
       quantity, qty_uom, price
  FROM apps.oks_prod_details_v
 WHERE contract_id = :p_contract_id
 ORDER BY covd_line_number;

Reporters aggregate quantity and value by coverage level to summarize contract entitlement:

SELECT covred_level, COUNT(*) covered_lines, SUM(quantity) total_qty
  FROM apps.oks_prod_details_v
 GROUP BY covred_level;

To trace an installed-base serial back to its contract, filter on COVERED_SERIAL_NO. Because the view UNIONs three lineage branches and joins translated line styles, queries joining it to OKC tables should account for possible duplicate scoping and always include CONTRACT_ID or LINE_ID predicates for performance.