Results for “okl_fe_eo_term_vers”

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

Overview

The OKL_FE_EO_TERM_VERS table is a core repository within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its documented description identifies it as the "End-of-Term Values Versions table." In the leasing lifecycle, end-of-term processing governs what happens to an asset or contract when the lease term expires — whether the lessee returns, purchases, or renews the asset, and what residual or contractual values apply at that point. This table stores the versioned definitions of those end-of-term value sets, allowing multiple iterations to be maintained, tracked by effective dates, and associated with a specific end-of-term setup header.

Based on the heuristic Data Vault classification mined from its foreign key structure, this object is hub-leaning: it holds a stable, uniquely identified business entity (the end-of-term version) keyed by a surrogate identifier, and it is referenced by several dependent satellites and detail tables. The version dimension (VERSION_NUMBER, EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE) further suggests it functions as a versioned master record rather than a transactional fact.

Key Information Stored

The table contains 28 documented columns. The most significant are summarized below.

• END_OF_TERM_VER_ID — the surrogate primary key defined by OKL_FE_EO_TERM_VERS_PK. It also appears as the sole column in the unique index OKL_FE_EO_TERM_VERS_U1, making it the business-key candidate for unambiguous identification.
• END_OF_TERM_ID — foreign key to OKL_FE_EO_TERMS_ALL_B, tying the version to its parent end-of-term header/definition.
• VERSION_NUMBER and OBJECT_VERSION_NUMBER — the human-readable version sequence and the internal optimistic-locking counter used by the EBS framework.
• EFFECTIVE_FROM_DATE and EFFECTIVE_TO_DATE — the date-range boundaries that determine which version is active at any point in time.
• STS_CODE — the status code reflecting the lifecycle state of the version.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns used for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard who-audit columns applied to all EBS transactional tables.

Common Use Cases and Queries

Typical reporting resolves the currently effective version for a given end-of-term setup. A representative query joins the version table to its header and filters by the effective-date window:

• Active-version lookup: SELECT v.END_OF_TERM_VER_ID, v.VERSION_NUMBER, v.EFFECTIVE_FROM_DATE, v.EFFECTIVE_TO_DATE FROM OKL_FE_EO_TERM_VERS v WHERE v.END_OF_TERM_ID = :p_id AND SYSDATE BETWEEN v.EFFECTIVE_FROM_DATE AND NVL(v.EFFECTIVE_TO_DATE, SYSDATE).
• Version history audit: ordering all versions by VERSION_NUMBER for a given END_OF_TERM_ID to trace configuration changes over time.
• Flexfield reporting: extracting ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for client-defined end-of-term value rules.
• Referential integrity checks: identifying orphaned objects, values, or rate-set versions that point at a version identifier with no surviving master row.
• Status reporting: grouping by STS_CODE to quantify active versus obsolete versions.

Related Objects

The table participates in a well-defined network of foreign-key relationships within the OKL schema.

• OKL_FE_EO_TERMS_ALL_B — parent header; joined on END_OF_TERM_ID.
• OKL_FE_EO_TERM_OBJECTS — dependent detail; references this table via END_OF_TERM_VER_ID.
• OKL_FE_EO_TERM_VALUES — stores the individual end-of-term values for a version; references END_OF_TERM_VER_ID.
• OKL_FE_RATE_SET_VERSIONS — links rate-set versions to an end-of-term version through END_OF_TERM_VER_ID.

Together these objects form the end-of-term configuration model, with OKL_FE_EO_TERM_VERS acting as the version hub that child detail records depend upon.