Search Results okl_fe_std_rt_tmp_vers

Overview

The OKL_FE_STD_RT_TMP_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 module. It functions as the standard rate template versions table, central to the management and versioning of financial rate templates. These templates are critical for defining the pricing, interest, or fee structures applied to lease and finance contracts. The table's primary role is to maintain a historical and current record of different iterations of a standard rate template, enabling audit trails, compliance, and the ability to apply the correct rate version to a contract based on its effective dates.

Key Information Stored

The table stores metadata and control information for each version of a rate template. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal its critical data elements. The primary key is STD_RATE_TMPL_ID, which uniquely identifies each version record. A crucial foreign key is ADJ_MAT_VERSION_ID, linking the rate template version to a specific version of an adjustment matrix (OKL_FE_ADJ_MAT_VERSIONS), which likely contains the detailed rate rules or schedules. Other essential columns typically found in version-controlled tables include effective start and end dates (EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE), a version number, a status indicator (e.g., 'DRAFT', 'ACTIVE', 'HISTORICAL'), and creation/modification audit fields. The table acts as a version header, with detailed rate sets linked via the OKL_FE_RATE_SET_VERSIONS table.

Common Use Cases and Queries

This table is primarily accessed for configuration management, reporting, and data validation. Common operational scenarios include retrieving the active version of a rate template for a given date, auditing changes to rate structures over time, and validating template setups before contract booking. Sample SQL patterns include finding all versions for a specific template or identifying the currently effective version.

• Retrieve Active Template Version: SELECT * FROM OKL_FE_STD_RT_TMP_VERS WHERE STD_RATE_TMPL_ID = &template_id AND SYSDATE BETWEEN EFFECTIVE_FROM_DATE AND NVL(EFFECTIVE_TO_DATE, SYSDATE) AND STATUS = 'ACTIVE';
• Audit History Report: SELECT STD_RATE_TMPL_ID, VERSION_NUMBER, EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE, CREATED_BY, CREATION_DATE FROM OKL_FE_STD_RT_TMP_VERS WHERE STD_RATE_TMPL_ID = &template_id ORDER BY VERSION_NUMBER;
• Integration Validation: Queries often join this table to OKL_FE_RATE_SET_VERSIONS and OKL_FE_ADJ_MAT_VERSIONS to ensure all related components for an active template are correctly configured.

Related Objects

The OKL_FE_STD_RT_TMP_VERS table is a central node in the Financial Engine's rate configuration schema. Its key relationships, as documented, are:

• OKL_FE_STD_RT_TMP_ALL_B: This is the base table for the standard rate template entity. The foreign key on STD_RATE_TMPL_ID links a version record back to its master template definition.
• OKL_FE_ADJ_MAT_VERSIONS: The foreign key on ADJ_MAT_VERSION_ID establishes a direct relationship to a specific version of an adjustment matrix, which holds the detailed calculation rules.
• OKL_FE_RATE_SET_VERSIONS: This table holds detailed rate set lines and references back to a standard rate template version via the STD_RATE_TMPL_VER_ID column, forming a parent-child relationship.

This structure ensures data integrity and supports complex financial product configuration where rates, matrices, and templates are independently versioned and assembled.