Results for “okl_leaseapp_templ_versions_b”

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

Overview

The OKL_LEASEAPP_TEMPL_VERSIONS_B table resides in the OKL schema and is a core data object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It stores the version records associated with lease application templates, providing the versioning backbone that allows a single template definition to be revised, activated, and retired over time without destroying the historical definition. Each row represents one version of a lease application template, discriminated by a version number and bounded by validity dates.

In Data Vault modeling terms, the metadata classifies this table as standalone, which suggests it behaves as an independent entity rather than a dependent child of a parent business key. Functionally, however, it carries satellite-like characteristics: it holds descriptive attributes (version status, validity window, template references, and the standard 15 ATTRIBUTE columns) tied to a versioned parent template. The recommended interpretation is a satellite anchored to a lease application template hub, with its version-specific descriptive context materialized in this table.

Key Information Stored

The physical schema documents 30 columns. The most significant are summarized below.

• ID — The surrogate primary key of the table, enforced by the OKL_LAV_PK constraint. It also backs the unique index OKL_LAV_U1, making it the documented business-key candidate.
• LEASEAPP_TEMPLATE_ID — The foreign reference to the parent lease application template to which this version belongs. This is the primary join path for retrieving all versions of a given template.
• VERSION_NUMBER — The sequential numeric identifier of the version, distinguishing one revision from another.
• VERSION_STATUS — The lifecycle state of the version (for example, draft, active, or obsolete), controlling which version is eligible for use.
• VALID_FROM / VALID_TO — The effective date range during which the version is valid, enabling date-effective querying.
• LEASEAPP_TEMPLATE_ID and CONTRACT_TEMPLATE_ID — References that anchor the version to its lease application template and any associated contract template.
• CHECKLIST_ID — A foreign key to PER_CHECKLISTS, linking the version to a checklist definition used during application processing.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic-locking column used for concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, providing extensibility for customer-specific version attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns capturing creation and modification metadata.

Common Use Cases and Queries

Typical usage centers on resolving the correct version of a template for a given point in time and auditing version history. A common reporting query retrieves all active versions of a template:

SELECT v.ID, v.VERSION_NUMBER, v.VERSION_STATUS, v.VALID_FROM, v.VALID_TO
FROM OKL.OKL_LEASEAPP_TEMPL_VERSIONS_B v
WHERE v.LEASEAPP_TEMPLATE_ID = :template_id
  AND v.VERSION_STATUS = 'ACTIVE';

A date-effective lookup resolves the version in force on a specific date:

SELECT v.ID, v.VERSION_NUMBER
FROM OKL.OKL_LEASEAPP_TEMPL_VERSIONS_B v
WHERE v.LEASEAPP_TEMPLATE_ID = :template_id
  AND :as_of_date BETWEEN v.VALID_FROM AND v.VALID_TO;

Additional scenarios include auditing version proliferation across templates, reconciling checklist assignments through CHECKLIST_ID, and extracting DFF values from the ATTRIBUTE columns for custom reporting. Because the table is standalone in Data Vault terms, joins are driven primarily through the template and checklist foreign keys rather than through a parent hub.

Related Objects

• PER_CHECKLISTS — Referenced through OKL_LEASEAPP_TEMPL_VERSIONS_B.CHECKLIST_ID; supplies the checklist definition associated with the template version.
• LEASEAPP_TEMPLATE_ID (parent template table) — The owner of the version records; joining on this column links each version to its parent lease application template.
• CONTRACT_TEMPLATE_ID (contract template table) — Associates the version with a contract template used downstream in lease authoring.
• OKL_LEASEAPP_TEMPL_VERSIONS_TL — The translated (language) companion table that typically pairs with the _B base table for user-facing descriptions.
• OKL_LAV_PK (constraint) and OKL_LAV_U1 (index) — The primary key and unique index enforcing row identity on ID.

Understanding this table's versioning model is essential when querying lease application templates, since the effective version must be resolved before template content can be reliably consumed by downstream lease origination logic.