Search Results okx_covered_lines_v




Overview
Explore in AI Chat

Overview

OKX_COVERED_LINES_V is a reporting view owned by the APPS schema in Oracle EBS Release 12.1.1 and 12.2.2, delivered as part of the OKX – Contracts Integration product. It presents the serviceable product lines associated with contracts held in the Oracle Contracts (OKC) repository, joined to their corresponding inventory item and unit-of-measure definitions. The view flattens the relationship between a contract line, the item it covers, and the descriptive attributes needed by downstream service and warranty processes, exposing one row per covered line with contract identifiers, item identifiers, quantity, and status.

The view is principally used for enquiry, reporting, and integration purposes where a normalized, read-only projection of covered contract lines is required. It supports service contract and subscription workflows by surfacing the covered items on active contracts, together with the flags that determine whether an item is serviceable.

Underlying Base Objects

The documented definition joins the following objects:

  • OKC_K_LINES_B — the base contract line table, supplying the line identifier, line number, dates, and terminated status.
  • OKC_K_LINES_TL — the translated line table, supplying the line name and item description in the user's language.
  • OKC_K_ITEMS — the covered-item table, keyed by CLE_ID to the contract line, providing the inventory item and organization identifiers, quantity, and unit of measure code.
  • OKX_SYSTEM_ITEMS_V — the system items view, supplying the item name, the serviceable product flag, and the service item flag used to exclude non-service items.
  • MTL_UNITS_OF_MEASURE_TL — the translated units of measure table, supplying the unit of measure description.
  • JTF_OBJECTS_B — the object registry, used to constrain the join to the OKX system items source via FROM_TABLE LIKE 'OKX_SYSTEM_ITEMS_V%'.

The item join is performed through character conversions, matching CIM.OBJECT1_ID1 to the item ID and CIM.OBJECT1_ID2 to the organization ID, with non-service items filtered out by SI.SERVICE_ITEM_FLAG = 'N'.

Key Columns

The principal columns returned by the view are:

Common Use Cases and Queries

A frequent requirement is to list the serviceable items covered on contracts, filtering by the serviceable product flag:

  • SELECT chr_id, line_number, item_name, quantity, unit_of_measure_code, status FROM okx_covered_lines_v WHERE serviceable_product_flag = 'Y';

Because the user searched for "serviceable_product_flag", the canonical query is that predicate. Common variations include restricting by active status, by item, or by contract:

  • SELECT * FROM okx_covered_lines_v WHERE serviceable_product_flag = 'Y' AND status = 'A';
  • SELECT line_number, item_name, start_date_active, end_date_active FROM okx_covered_lines_v WHERE chr_id = :contract_id ORDER BY line_number;
  • SELECT inventory_item_id, organization_id, SUM(quantity) FROM okx_covered_lines_v WHERE serviceable_product_flag = 'Y' GROUP BY inventory_item_id, organization_id;

These queries support service entitlement checks, warranty and coverage reporting, and integration feeds that must enumerate serviceable covered lines per contract. Note that STATUS is derived at runtime, so it reflects the query execution date rather than a stored value.