Results for “okl_fe_eo_term_vers_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKL_FE_EO_TERM_VERS_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It exposes the version history of End of Term (EOT) options, which define the contractual alternatives available to a lessee when a lease reaches maturity — such as returning, purchasing, or renewing the leased asset. The view is owned by the APPS schema and holds a VALID status in the ETRM data dictionary.

Its principal purpose is to present EOT option version records joined with their corresponding header-level attributes, allowing downstream reports, concurrent programs, and integration interfaces to retrieve versioned EOT configuration data through a single, denormalized query surface. Because the view exposes END_OF_TERM_NAME and END_OF_TERM_DESC from the header alongside the version-level keys, it is frequently used by implementers searching for objects related to the end_of_term_name attribute.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, OKL_FE_EO_TERM_VERS_V is defined over two referenced base objects:

• OKL_FE_EO_TERMS_V (VIEW) — the EOT option header source, aliased as HDR in the view definition.
• OKL_FE_EO_TERM_VERS (SYNONYM) — the EOT option version source, aliased as VER.

The two sources are joined on the EOT identifier: HDR.END_OF_TERM_ID = VER.END_OF_TERM_ID. This relationship confirms that each version row inherits its descriptive header attributes (currency, EOT type, product, category, and name/description) from the parent EOT option definition. Because both referenced objects are themselves views or synonyms rather than physical tables, this object is a layered reporting view that ultimately resolves to the underlying OKL base tables.

Key Columns

The view exposes eighteen columns. The version-identifying columns — END_OF_TERM_VER_ID, VERSION_NUMBER, and OBJECT_VERSION_NUMBER — uniquely identify each version and support optimistic locking. The header reference END_OF_TERM_ID links the version to its parent.

The version-level lifecycle columns include STS_CODE, EFFECTIVE_FROM_DATE, and EFFECTIVE_TO_DATE. Corresponding header-level lifecycle attributes are exposed under aliased names — HDR_STS_CODE, HDR_EFFECTIVE_FROM_DATE, and HDR_EFFECTIVE_TO_DATE — preventing column-name collisions in the flat result set.

Business classification is carried by CURRENCY_CODE, EOT_TYPE_CODE, PRODUCT_ID, CATEGORY_TYPE_CODE, and ORIG_END_OF_TERM_ID. The descriptive columns END_OF_TERM_NAME and END_OF_TERM_DESC are the fields most commonly referenced when searching for EOT option descriptions.

Common Use Cases and Queries

Typical scenarios include retrieving the current active version of an EOT option, auditing version history, and driving downstream option-processing logic. A basic retrieval of all current version records follows:

• SELECT END_OF_TERM_ID, END_OF_TERM_NAME, VERSION_NUMBER, STS_CODE, EFFECTIVE_FROM_DATE FROM OKL_FE_EO_TERM_VERS_V WHERE STS_CODE = 'ACTIVE';

To list all versions for a specific option name:

• SELECT END_OF_TERM_NAME, VERSION_NUMBER, EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE FROM OKL_FE_EO_TERM_VERS_V WHERE END_OF_TERM_NAME = :p_name ORDER BY VERSION_NUMBER;

To reconcile version-level and header-level status:

• SELECT END_OF_TERM_VER_ID, VERSION_NUMBER, STS_CODE, HDR_STS_CODE FROM OKL_FE_EO_TERM_VERS_V WHERE STS_CODE <> HDR_STS_CODE;

Because the view joins header and version data, queries should filter on the appropriate status column for the intended business context, and joins to product or category reference tables can be added via PRODUCT_ID and CATEGORY_TYPE_CODE.