Search Results generate_lrf

Overview

OKL_LRF_INTERFACE_PVT is a private PL/SQL package body in the Oracle E-Business Suite Lease and Finance Management (OKL) module. It serves as the core interface processing engine for lease rate factors (LRF), the actuarial multipliers used to compute rental streams and residual values on a lease contract. The source header ($Header: OKLRLRIB.pls 120.3) confirms this is an internal implementation unit whose logic is exposed through a corresponding public specification. The package follows the standard ETRM private (PVT) API classification, meaning its procedures are intended for invocation by sibling packages, concurrent programs, or the LRF interface workflow rather than by external callers directly.

Its primary business purpose is to move lease rate factor data from a staging area into the operational tables that drive lease pricing: validating, converting, and committing set, entry, and translation rows so that rate factor lookups succeed at the point of lease booking.

Key Procedures and Functions

• PROCESS_RECORD — The central driver of the package. It accepts a single staging record, performs validation and uniqueness checks, resolves the parent rate factor set, and writes the corresponding rows into the operational LRF tables. This is the procedure most directly associated with the search term "process_record" and is the natural per-row workhorse called iteratively by a batch driver.
• PURGE_RECORD — Removes processed or obsolete rows associated with a given staging record, supporting idempotent, restartable interface runs. It allows a failed or re-executed batch to clear prior partial results before reprocessing.
• GENERATE_LRF — Produces or regenerates the lease rate factor output derived from the interface input, materializing the factor values that lease pricing logic subsequently consumes.

Several helper procedures appearing in the source—report_error, validate_lrt_id, Validate_Record, validate_term_in_months, validate_residual_val, and validate_lease_rate_factor—support these three public entry points. The Validate_Record function enforces the unique key on the combination of LRT_ID, TERM_IN_MONTHS, and RESIDUAL_VALUE_PERCENT; its cursor against OKL_LS_RT_FCTR_ENTS reflects this constraint, with LEASE_RATE_FACTOR comparison commented out in the shipped code.

Tables Accessed

• OKL_LRF_INTERFACE — The staging interface table; the source of records passed to PROCESS_RECORD and the target of PURGE_RECORD housekeeping.
• OKL_LS_RT_FCTR_SETS_B — Stores the base definitions of rate factor sets. validate_lrt_id queries this table to confirm the parent LRT_ID exists before processing.
• OKL_LS_RT_FCTR_SETS_TL — The translation table holding language-specific set descriptions, referenced when the interface must preserve or generate multilingual set text.
• OKL_LS_RT_FCTR_ENTS — Holds the individual rate factor entries keyed by LRT_ID, term in months, and residual value percent. It is both the uniqueness-check source during validation and the destination for GENERATE_LRF output.

Usage Notes

OKL_LRF_INTERFACE_PVT is documented as referenced by zero other packages, confirming it is a leaf-level implementation unit. It is typically invoked from the LRF interface concurrent program, whose driver reads rows from OKL_LRF_INTERFACE and calls PROCESS_RECORD per record within a batch loop, with PURGE_RECORD handling rollback of partial work. Custom extensions that need to load lease rate factors programmatically should call the public (PUB) wrapper rather than this package directly, preserving the documented private boundary. In 12.1.1 and 12.2.2, standard functionality migrates rate factor data through the same staging model, and the online lease pricing screens depend on the resulting rows in OKL_LS_RT_FCTR_ENTS being accurate and unique per term and residual combination.