Search Results okl_fe_adj_mat_versions




Overview
Explore in AI Chat

Overview

The OKL_FE_ADJ_MAT_VERSIONS table is a core data object within the Oracle E-Business Suite (EBS) module OKL (Lease and Finance Management). It functions as the master repository for version control of pricing adjustment matrices. In the context of lease and finance operations, these matrices are critical for defining and applying complex pricing rules, discounts, or adjustments to financial products. The table's primary role is to maintain a historical and current record of different iterations of an adjustment matrix, enabling auditability, compliance, and the ability to revert to or reference prior pricing structures. It is a fundamental component supporting the flexible pricing engine in Oracle's leasing solutions for both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's structure is centered around uniquely identifying and describing each version of an adjustment matrix. The primary key column, ADJ_MAT_VERSION_ID, serves as the unique identifier for every version record. A critical foreign key column is ADJ_MAT_ID, which links each version back to its parent adjustment matrix header defined in the OKL_FE_ADJ_MAT_ALL_B table. While the provided metadata does not list all columns, typical data stored in such a version table includes a version number or name, an effective start date (and potentially an end date) for the version's validity, the status of the version (e.g., Draft, Active, Historical), and creation/modification audit information (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). This structure allows multiple versions of a single pricing matrix to coexist for different time periods or purposes.

Common Use Cases and Queries

Common operational and reporting scenarios involve retrieving active versions for pricing calculations or auditing historical changes. A frequent query pattern is to join this table with its parent header table to list all versions for a specific adjustment matrix. For example:

  • Identifying the currently active version for transaction processing: SELECT * FROM OKL_FE_ADJ_MAT_VERSIONS WHERE ADJ_MAT_ID = :p_matrix_id AND STATUS = 'ACTIVE' AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE).
  • Reporting on the version history of a matrix for audit purposes: SELECT v.ADJ_MAT_VERSION_ID, v.VERSION_NUM, v.STATUS, v.START_DATE, v.END_DATE FROM OKL_FE_ADJ_MAT_VERSIONS v, OKL_FE_ADJ_MAT_ALL_B h WHERE v.ADJ_MAT_ID = h.ADJ_MAT_ID AND h.NAME = :p_matrix_name ORDER BY v.START_DATE DESC.
  • Data fixes or analyses often require queries that join this version table to its child detail tables (via foreign keys) to examine or update specific pricing rules tied to a particular version.

Related Objects

The OKL_FE_ADJ_MAT_VERSIONS table sits at the center of a key relationship hierarchy within the pricing subsystem. Its primary relationships, as documented, are:

  • OKL_FE_ADJ_MAT_ALL_B: This is the parent table. The foreign key on ADJ_MAT_ID establishes that a version belongs to a specific master adjustment matrix definition.
  • OKL_FE_RATE_SET_VERSIONS: This table holds a foreign key (ADJ_MAT_VERSION_ID) referencing OKL_FE_ADJ_MAT_VERSIONS, indicating that rate set versions can be associated with a specific adjustment matrix version.
  • OKL_FE_STD_RT_TMP_VERS (Standard Rate Template Versions): Similar to rate sets, standard rate template versions also reference a specific ADJ_MAT_VERSION_ID, linking pricing templates to adjustment matrix versions.

These relationships illustrate that a versioned adjustment matrix is a reusable component integrated into broader pricing constructs like rate sets and templates.