Search Results okl_fe_eo_term_vers_pk

Overview

The OKL_FE_EO_TERM_VERS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the OKL (Lease and Finance Management) product family. It serves as the version control repository for End-of-Term (EOT) values associated with lease or finance contracts. In the context of the Fair Value Engine (FE), this table enables the management of multiple valuation scenarios over time. It allows financial analysts to create, track, and compare different sets of assumptions—such as residual values, purchase options, or renewal rates—for a single contract's termination, providing critical auditability and support for "what-if" financial analysis.

Key Information Stored

The table's primary purpose is to store metadata for each unique version of end-of-term assumptions. Its structure is anchored by the END_OF_TERM_VER_ID column, which is the primary key (OKL_FE_EO_TERM_VERS_PK). A critical foreign key is the END_OF_TERM_ID column, which links each version back to its parent end-of-term definition in the OKL_FE_EO_TERMS_ALL_B table. While the specific descriptive columns are not detailed in the provided metadata, typical version tables in this module include fields for a version number, an effective date or date range, a status (e.g., 'DRAFT', 'APPROVED'), a description, and audit columns like CREATED_BY and CREATION_DATE. This structure isolates version-specific attributes from the core term definition and the detailed valuation data itself.

Common Use Cases and Queries

This table is central to fair value accounting and lease portfolio analysis. Common operational and reporting use cases include retrieving all versions for a specific contract term to review historical assumption changes, identifying the currently active version for financial reporting, or comparing two versions side-by-side. A typical query would join this table to its parent and child tables to build a complete valuation snapshot.

Sample Query Pattern:
SELECT vers.version_number, vers.effective_from_date, term.contract_id
FROM OKL_FE_EO_TERM_VERS vers,
OKL_FE_EO_TERMS_ALL_B term
WHERE vers.end_of_term_id = term.end_of_term_id
AND term.contract_id = :p_contract_id
ORDER BY vers.effective_from_date DESC;
This pattern is foundational for custom reports auditing EOT value changes or for data extracts used in external valuation models.

Related Objects

The OKL_FE_EO_TERM_VERS table sits at the center of a key data model, with defined relationships to several other FE objects. As per the provided metadata, it has the following key dependencies:

• OKL_FE_EO_TERMS_ALL_B: The parent table. The foreign key on END_OF_TERM_ID establishes that a master end-of-term definition can have multiple versions.
• OKL_FE_EO_TERM_OBJECTS: A child table, likely storing the specific assets or items being valued at the end-of-term for each version.
• OKL_FE_EO_TERM_VALUES: A critical child table expected to hold the actual calculated or inputted fair values, rates, and amounts for each version.
• OKL_FE_RATE_SET_VERSIONS: Another child table, indicating that specific discount rate sets or yield curves can be linked to an end-of-term valuation version.

Development or integration efforts involving EOT values must consider this entire hierarchy, typically accessing data via published Oracle APIs rather than direct table manipulation.