Results for “okl_ls_rt_fctr_sets_b”

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

Overview

OKL_LS_RT_FCTR_SETS_B is the Rate Card (Lease Rate Set) header table within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). In Oracle ETRM configurations, this table functions as the master record for a Lease Rate Set, which defines the pricing basis — interest rates, rate factors, and associated calculation parameters — applied to a lease or loan transaction during origination and periodic revaluation. Each row represents a distinct rate set header that drives downstream rate factor lines, amortization schedules, and yield computations.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This suggests the table is best modeled as a descriptive satellite attached to a core hub or link (for example, a product or transaction-type hub), rather than as a standalone hub. The presence of two self-referencing foreign keys on ORIG_RATE_SET_ID reinforces its role as a descriptive, version-aware structure that hangs off a primary business entity.

Key Information Stored

The table's primary key is OKL_LS_RT_FCTR_SETS_PK, defined on the column ID. This ID column is the surrogate primary key and the primary join path to dependent tables. The most significant columns documented in the metadata include:

• ID — surrogate primary key; uniquely identifies each rate set header and serves as the parent key for rate factor line tables.
• PDT_ID — foreign key to OKL_PRODUCTS; identifies the leasing product to which this rate set applies, constraining eligible transactions.
• TRY_ID — foreign key to OKL_TRX_TYPES_B; identifies the transaction type (for example, lease origination, renewal, or refinance) the rate set governs.
• ORIG_RATE_SET_ID — self-referencing foreign key to OKL_LS_RT_FCTR_SETS_B; identifies the originating or parent rate set, enabling versioning, copying, and lineage across rate set revisions.

Business-key candidates are typically formed from the combination of product, transaction type, and effective dating attributes; however, the provided metadata documents only the surrogate PK as the enforced unique key. Additional descriptive and effective-date columns are understood to exist in the physical table but are not enumerated in the supplied metadata.

Common Use Cases and Queries

Typical reporting and integration scenarios involve retrieving rate set headers by product or transaction type, and traversing the self-referential lineage to identify how a rate set evolved. A representative query pattern is:

• Join OKL_LS_RT_FCTR_SETS_B to OKL_PRODUCTS on PDT_ID = PDT_ID to resolve product names for rate-card reporting.
• Join to OKL_TRX_TYPES_B on TRY_ID = TRY_ID to filter rate sets by transaction type.
• Self-join OKL_LS_RT_FCTR_SETS_B on ID = ORIG_RATE_SET_ID to trace derived or copied rate sets back to their source.

These patterns support pricing audits, rate-card maintenance reports, and reconciliation between rate set headers and their associated rate factor lines. The table is commonly the driving source for lease pricing validation during origination.

Related Objects

The most significant referencing and referenced objects are:

• OKL_PRODUCTS — joined via OKL_LS_RT_FCTR_SETS_B.PDT_ID; defines the product context for the rate set.
• OKL_TRX_TYPES_B — joined via OKL_LS_RT_FCTR_SETS_B.TRY_ID; defines the transaction type context.
• OKL_LS_RT_FCTR_SETS_B (self) — joined via OKL_LS_RT_FCTR_SETS_B.ORIG_RATE_SET_ID = OKL_LS_RT_FCTR_SETS_B.ID; captures rate set lineage and versioning.

Downstream rate factor line tables and OKL pricing APIs depend on the OKL_LS_RT_FCTR_SETS_PK key for referential integrity, making this header table the anchor point for all rate-card configuration within the Leasing and Finance Management module.