Results for “okl_fe_eo_term_values”

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

Overview

The OKL.OKL_FE_EO_TERM_VALUES table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It stores the End-of-Term (EOT) values associated with lease and finance contracts, capturing the residual, contractual, or settlement amounts that apply at the conclusion of a contract term. These values are essential to lease accounting, asset disposition planning, and financial reporting where the projected or negotiated value of an asset at contract maturity must be tracked and versioned.

In Oracle EBS 12.1.1 and 12.2.2, this table resides in the OKL schema and is delivered with a VALID status. It operates as a supporting detail table for the End-of-Term versioning model, and its foreign key dependency on OKL_FE_EO_TERM_VERS indicates that EOT values are organized under a versioning parent, allowing multiple iterations of EOT terms to coexist. Based on the mined foreign key structure, the table carries a satellite-leaning Data Vault classification, suggesting it is best modeled as a descriptive satellite attached to the version hub represented by OKL_FE_EO_TERM_VERS, rather than as an independent hub or a link between distinct business entities.

Key Information Stored

The table contains 26 documented columns. The most significant columns for functional and technical analysis are the following:

• END_OF_TERM_VALUE_ID — The surrogate primary key of the table, enforced by OKL_FE_EO_TERM_VALUES_PK and also backed by the unique index OKL_FE_EO_TERM_VALUES_U1. It uniquely identifies each EOT value record.
• END_OF_TERM_VER_ID — The foreign key referencing OKL_FE_EO_TERM_VERS. This column links each value record to its parent End-of-Term version, establishing the versioning context.
• EOT_TERM — The end-of-term period or term identifier associated with the record, used to distinguish among successive or alternative term definitions.
• EOT_VALUE — The monetary or quantitative value defined for the end-of-term condition. This is the principal business measure stored in the table and is typically the target of reporting and calculation logic.
• OBJECT_VERSION_NUMBER — The standard Oracle EBS optimistic locking column used to manage concurrent updates on the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns. These enable customer-specific extension of the EOT value records without schema modification, and they support context-sensitive attribute segments governed by ATTRIBUTE_CATEGORY.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS who-column audit fields, recording record provenance and the identity and session of the most recent modification.

The distinction between the surrogate primary key (END_OF_TERM_VALUE_ID) and any business-key candidate is important: the documented unique index OKL_FE_EO_TERM_VALUES_U1 is defined on the same surrogate column, meaning no separate natural business key is enforced by a unique constraint in the documented metadata. Business uniqueness is therefore effectively governed by the combination of the parent version reference and the term identifier, rather than by a dedicated unique index.

Common Use Cases and Queries

Typical applications of this table include lease residual value reporting, end-of-term settlement processing, contract amendment versioning, and financial reconciliation of EOT obligations. Because the table is version-aware, queries frequently join to OKL_FE_EO_TERM_VERS to retrieve only the active or most recent version of EOT terms.

A representative query retrieving EOT values for a given version is:

• SELECT v.end_of_term_value_id, v.eot_term, v.eot_value FROM okl.okl_fe_eo_term_values v WHERE v.end_of_term_ver_id = :p_version_id ORDER BY v.eot_term;

A join pattern resolving the parent version context is:

• SELECT vals.eot_term, vals.eot_value, vers.end_of_term_ver_id FROM okl.okl_fe_eo_term_values vals, okl.okl_fe_eo_term_vers vers WHERE vals.end_of_term_ver_id = vers.end_of_term_ver_id;

Reporting scenarios often aggregate EOT_VALUE by EOT_TERM to produce residual value schedules, or filter on the DFF columns (for example, ATTRIBUTE_CATEGORY = 'MyContext') to extract customer-specific EOT classifications. Audit queries typically order by LAST_UPDATE_DATE or filter on CREATED_BY to trace changes made to EOT value records over time.

Related Objects

The following objects are the most significant related or dependent entities based on the documented foreign key relationship and standard OKL module dependencies:

• OKL_FE_EO_TERM_VERS — The parent versioning table. Joined via OKL_FE_EO_TERM_VALUES.END_OF_TERM_VER_ID = OKL_FE_EO_TERM_VERS.END_OF_TERM_VER_ID. This is the sole documented foreign key relationship.
• OKL_FE_EO_TERM_VALUES_PK — The primary key constraint enforcing uniqueness of END_OF_TERM_VALUE_ID.
• OKL_FE_EO_TERM_VALUES_U1 — The unique index on END_OF_TERM_VALUE_ID, functioning as a business-key candidate within the documented schema.
• OKL_OKC_HEADERS_ALL / OKL_CONTRACTS (OKL contract headers) — Typically reached transitively through the End-of-Term version parent to associate EOT values with their originating lease or finance contract.
• OKL_FE_EO_TERMS / OKL_FE_EO_TERM_VERS — The broader End-of-Term term definition family that frames the version hierarchy containing these values.
• Oracle EBS Descriptive Flexfield views for OKL EOT values — Reporting views that expose the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 segments in user-friendly form.

Developers and analysts should treat OKL_FE_EO_TERM_VALUES as a satellite detail table always accessed in the context of its version parent, and should avoid treating END_OF_TERM_VALUE_ID as a meaningful business identifier in external interfaces.