Search Results okl_fe_eo_terms_b




Overview

APPS.OKL_FE_EO_TERMS_V is a reporting view within the Oracle E-Business Suite Enterprise Contracts (OKL) module, specifically in the End of Term (EOT) functional area used by Oracle Lease and Finance Management. The view exposes End of Term terms — the contractual rules that determine what happens when a lease or financing contract reaches maturity, such as asset return, purchase option exercise, or renewal. It consolidates descriptive and transactional attributes into a single, translation-aware presentation layer that applications and reports can query without performing their own join and language filtering logic.

The object name carries the standard EBS convention. The _V suffix identifies it as a view rather than a base table, while the underlying tables follow the _B (base, language-independent) and _TL (translated, language-dependent) naming pattern. The companion identifier okl_fe_eo_terms_b refers directly to the base table over which this view is built, and users searching for that name are typically attempting to reconcile the physical table with its reporting view counterpart. The view is defined in the APPS schema and is documented as part of the ETRM 12.1.1 / 12.2.2 metadata set, ensuring behavioral consistency across both release families.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

  • OKL_FE_EO_TERMS_B — the base table holding all language-independent columns, including identifiers, status, effective dating, currency, organization, and the DFF attribute columns 1 through 15.
  • OKL_FE_EO_TERMS_ALL_TL — the translated table holding the language-specific description column, END_OF_TERM_DESC.

The two objects are joined on END_OF_TERM_ID, and the translated side is filtered by T.LANGUAGE = USERENV('LANG'). This predicate dynamically restricts results to the session language of the connected user, so the view returns each End of Term record exactly once, with the description rendered in the appropriate language where a translation exists.

Key Columns

Common Use Cases and Queries

The view is most frequently used in reporting, data extraction, and integration scenarios where End of Term definitions must be presented to users or downstream systems without duplicating the base/translation join. Typical uses include populating value sets and LOVs, validating setup data, and feeding interfaces that reference End of Term terms by name and description.

A basic query retrieves active terms for the current operating unit:

SELECT end_of_term_id, end_of_term_name, end_of_term_desc, eot_type_code, sts_code FROM apps.okl_fe_eo_terms_v WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, SYSDATE + 1);

A lookup-by-name scenario supports integration and troubleshooting, since users often know the term name but not its ID:

SELECT end_of_term_id, end_of_term_name, end_of_term_desc, currency_code, product_id FROM apps.okl_fe_eo_terms_v WHERE UPPER(end_of_term_name) = UPPER(:p_name);

A join to base tables for extension attributes demonstrates that the view can be combined with OKL_FE_EO_TERMS_B when DFF context is required in a denormalized extract. Because the view already enforces the language predicate, it is preferable to OKL_FE_EO_TERMS_ALL_TL alone whenever language-independent columns are also needed.