Search Results base_lost_amount




Overview
Explore in AI Chat

Overview

APPS.OKI_EXP_NOT_RENEWED_V is a public Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as OKI.OKI_EXP_NOT_RENEWED_V. It belongs to the Oracle Contracts (OKI/OKC) family of objects and exposes information about service or subscription contracts that have expired and were not renewed. The view is documented as a public view "which may be useful for custom reporting or other data requirements," and its status is VALID.

Functionally, the view presents an aggregated, period-based picture of lost contract renewals. Rather than surfacing individual contract lines, it reports counts of non-renewed contracts by customer, sales representative, authoring operating unit, and GL period, together with the monetary value forfeited. This makes it a reporting-oriented object rather than a transactional one, and it is commonly consumed by renewal or "churn" analytics, contract performance dashboards, and custom concurrent programs.

The object of interest in the user's search, BASE_LOST_AMOUNT, is the numeric measure that quantifies the revenue value lost when contracts expired without renewal, expressed in the ledger's base currency. Because the view carries period and currency-consistent amounts, it is well suited to period-over-period comparisons without further conversion logic.

Underlying Base Objects

The view is defined over the base table OKI_EXP_NOT_RENEWED, and the documentation explicitly states that it contains "language specific information" — that is, it joins translated (language-dependent) attributes onto the underlying table so that names such as CUSTOMER_NAME, AUTHORING_ORG_NAME, and SALESREP_NAME are returned in the session's language.

No additional base objects are documented in the ETRM metadata. In practice, the view inherits its fact data (contract counts, lost amounts, period keys, party and organization identifiers) directly from OKI_EXP_NOT_RENEWED, while the descriptive name columns are resolved through the standard EBS multilingual (MLS) translation mechanism used by Oracle Contracts.

Key Columns

  • ID — Internal identifier for the row.
  • PERIOD_NAME / PERIOD_SET_NAME / PERIOD_TYPE — General Ledger period identifiers used to determine valid periods and to group results by accounting period.
  • AUTHORING_ORG_ID / AUTHORING_ORG_NAME — Operating unit in which the contract was authored, exposed as both ID and translated name.
  • CUSTOMER_PARTY_ID / CUSTOMER_NAME — Contract customer, by party ID and name.
  • CONTACT_ID / SALESREP_NAME — Contract contact identifier and the name of the responsible sales representative.
  • SCS_CODE — Category (sub-class) code for the contract, enabling segmentation by contract type.
  • CONTRACT_COUNT — Count of contracts that expired and were not renewed.
  • BASE_LOST_AMOUNT — The amount lost (not renewed), expressed in the base currency. This is the primary numeric measure of the view.
  • REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrent Manager audit columns identifying the program run that populated the row.

Common Use Cases and Queries

Typical uses include churn analysis, sales representative performance reporting, and periodic lost-revenue reporting by operating unit or contract category.

  • Total amount lost per period:
SELECT period_name, SUM(base_lost_amount) lost_amt
FROM   apps.oki_exp_not_renewed_v
GROUP  BY period_name
ORDER  BY period_name;
  • Lost revenue by sales representative and customer:
SELECT salesrep_name, customer_name,
       SUM(contract_count) contracts, SUM(base_lost_amount) lost_amt
FROM   apps.oki_exp_not_renewed_v
WHERE  authoring_org_id = :org_id
GROUP  BY salesrep_name, customer_name
ORDER  BY lost_amt DESC;
  • Contract category breakdown for a given period set.

Because the view is a reporting construct, callers should restrict by PERIOD_NAME, AUTHORING_ORG_ID, and REQUEST_ID to align results to a specific program run, and apply standard EBS security considerations (operating unit access) when exposing BASE_LOST_AMOUNT externally.