Search Results okl_fe_eo_terms_v




Overview
Explore in AI Chat

Overview

OKL_FE_EO_TERMS_V is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the header records that define End-of-Term (EOT) options — the contractual choices available to a lessee when a lease reaches maturity, such as purchase, renewal, or return. The view is documented as VALID in both EBS 12.1.1 and 12.2.2, and retains the same definition across those releases.

The view serves a reporting and integration role. Because it presents EOT header data in a denormalized, language-resolved form, it can be queried directly by custom reports, concurrent programs, BI Publisher data models, and outbound interfaces without requiring the caller to reconstruct the join between the base and translation tables. Its name follows the OKL naming convention for a front-end (FE) read-only view, indicating it is intended for consumption rather than for DML. The view surfaces the column EOT_TYPE_CODE, the term-type classifier users commonly search on.

Underlying Base Objects

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

  • OKL_FE_EO_TERMS_B — the base (non-translated) table holding one row per end-of-term option header, including operational and descriptive columns.
  • OKL_FE_EO_TERMS_ALL_TL — the translation table carrying the language-specific description, keyed by END_OF_TERM_ID and LANGUAGE.

The join predicates are B.END_OF_TERM_ID = T.END_OF_TERM_ID and T.LANGUAGE = USERENV('LANG'), so the view returns exactly one description per header, translated to the session language. Columns are drawn from the base table (aliased B) except END_OF_TERM_DESC, which comes from the translation table (aliased T).

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all active EOT options by type, feeding lease-maturity workflows, and validating that a header exists before an interface load. A representative query filtering on the searched column is:

  • SELECT end_of_term_id, end_of_term_name, eot_type_code, org_id, sts_code FROM okl_fe_eo_terms_v WHERE eot_type_code = 'PURCHASE' ORDER BY end_of_term_name;
  • SELECT end_of_term_id, end_of_term_name, currency_code FROM okl_fe_eo_terms_v WHERE org_id = :p_org_id AND sts_code = 'ACTIVE' AND TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, TRUNC(SYSDATE));
  • SELECT DISTINCT eot_type_code FROM okl_fe_eo_terms_v ORDER BY eot_type_code; for populating a parameter LOV.

Because the view is read-only and filters on session language, it is safe for reporting but should not be used for DML; inserts and updates belong to the base tables through the OKL application APIs.