Search Results okx_service




Overview
Explore in AI Chat

Overview

APPS.OKL_CS_SERVICE_LINES_UV is a reporting and integration view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, defined within the Oracle Enterprise Trade and Fulfillment (ETRM) / Oracle Contracts (OKC/OKL) module family. The view consolidates sold service lines from service contracts and exposes them alongside the associated service item name, line amount, contract dates, status description, contract number, and currency. Its primary role is to provide a denormalized, business-friendly projection of contract line data filtered specifically to service items that are sold (not abandoned) and are flagged as service items rather than vendor warranties.

Because it joins service contract structures with the OKX service item view, OKL_CS_SERVICE_LINES_UV is useful for reporting, downstream integrations, and operational queries that need a flat list of active service lines. It is commonly consulted by developers and analysts searching for objects related to okx_service, since the view is a convenient entry point into service item data tied to contracts.

Underlying Base Objects

The view is defined over the following documented base objects (all referenced as synonyms owned by APPS unless noted):

The join chain requires the line style to equal SOLD_SERVICE, the status code to be other than ABANDONED, the item to be a service item (SERVICE_ITEM_FLAG = 'Y') and not a vendor warranty (VENDOR_WARRANTY_FLAG = 'N'), and the item reference code to equal OKX_SERVICE.

Key Columns

  • CLE_ID — identifier of the contract line (from OKC_K_LINES_B).
  • NAME — name of the service item (from OKX_SYSTEM_ITEMS_V).
  • AMOUNT — line amount (from OKL_K_LINES).
  • START_DATE / END_DATE — effective period of the service line.
  • MEANING — translated description of the line status.
  • CONTRACT_NUMBER — contract header number.
  • DNZ_CHR_ID — internal contract header identifier used throughout the join.
  • CURRENCY_CODE — currency of the contract.

Common Use Cases and Queries

Typical usage includes extracting all active sold service lines for a contract, reporting service revenue by item, and feeding downstream service management or billing processes. A representative query follows:

  • Retrieve service lines for a specific contract number.
  • Aggregate service amounts by currency.
  • List service lines by status meaning.

For example: SELECT contract_number, name, amount, currency_code, meaning FROM apps.okl_cs_service_lines_uv WHERE contract_number = :p_contract_number;. Because the view filters on service_item_flag, vendor_warranty_flag, line style, and excludes abandoned lines, consumers should not expect warranty or non-service lines to appear.