Search Results base_price_unit




Overview
Explore in AI Chat

Overview

OKI_EXPIRED_LINES_V is a reporting view in the Oracle E-Business Suite Contracts Intelligence (OKI) module, a component historically associated with Oracle Contracts and Oracle Sales Intelligence. In EBS 12.1.1 and 12.2.2 the OKI module is documented as obsolete, and the view itself is recorded in the ETRM as not implemented in the database. Its purpose is nonetheless well defined by its definition: it exposes one row per expired contract line, joined to lookup and status information, so that reporting and integration consumers can enumerate contract lines whose end date has passed, along with their termination reason and lifecycle status. The user search term termination_meaning corresponds directly to the TRN.MEANING alias TERMINATION_MEANING, the decoded termination reason derived from the OKC_TERMINATION_REASON lookup. The view therefore serves as a denormalized, security-filtered read model over expired contract lines rather than as a transactional object.

Underlying Base Objects

The documented FROM clause references three objects: the base table OKI_EXPIRED_LINES (aliased ELE), the lookup table FND_LOOKUPS (aliased TRN), and the status view OKC_STATUSES_V (aliased STS). The ETRM metadata records no documented referenced base objects for the 12.2.2 view, so the definition above is the authoritative source. The join to FND_LOOKUPS is an outer join on LOOKUP_CODE plus LOOKUP_TYPE = 'OKC_TERMINATION_REASON', meaning expired lines without an assigned termination code still appear, with a null TERMINATION_MEANING. The join to OKC_STATUSES_V is an inner join on STS.CODE = ELE.STS_CODE, which resolves the internal status code into a user-facing status meaning. Access is further restricted by a predicate on OKC_UTIL.GET_K_ACCESS_LEVEL(ELE.CHR_ID, ELE.SCS_CODE) limiting rows to those with access level 'R' (read) or 'U' (update), enforcing Contracts folder-based security at the view level.

Key Columns

Common Use Cases and Queries

Typical uses include expired-line reporting, renewal analysis, and termination-reason trending. Because access is pre-filtered, the view is convenient for secured reporting without re-implementing folder security.

  • Listing terminated expired lines and their reasons:
SELECT contract_number, line_number, end_date,
       termination_meaning, date_terminated
  FROM oki_expired_lines_v
 WHERE trn_code IS NOT NULL
 ORDER BY end_date;
  • Counts by termination reason for a period:
SELECT end_period_name, termination_meaning, COUNT(*)
  FROM oki_expired_lines_v
 GROUP BY end_period_name, termination_meaning;
  • Expired lines with negotiated value by organization:
SELECT organization_name, contract_number,
       SUM(price_negotiated) total_value
  FROM oki_expired_lines_v
 GROUP BY organization_name, contract_number;

Because OKI is obsolete and the view is not implemented in current databases, equivalent results in supported releases are generally obtained from the OKC contract tables (OKC_K_LINES_B, OKC_K_HEADERS_B and their _TL tables) joined to OKC_STATUSES_V and FND_LOOKUPS using the same OKC_TERMINATION_REASON lookup.