Results for “okl_interest_calculation_basis”

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

Overview

APPS.OKL_PRODUCT_PARAMETERS_V is a reporting and integration view within the Oracle E-Business Suite Lease and Finance Management (OKL/ETRM) module. It presents a denormalized, business-friendly representation of lease product definitions by resolving the flexible attribute-value model used by the product quality and product parameter tables into readable, named columns. Rather than exposing raw foreign keys and lookup codes, the view joins product records to their associated quality values and translates stored lookup codes into their descriptive meanings using the OKL_ACCOUNTING_UTIL.Get_Lookup_Meaning function.

The view is particularly significant because it surfaces the Revenue_Recognition_Method attribute directly by name, along with its decoded meaning. Users searching for "revenue_recognition_method" are typically looking to determine which revenue recognition convention is assigned to a given lease product. This view answers that question without requiring the caller to traverse the underlying OKL_PDT_QUALITYS, OKL_PDT_PQY_VALS, and OKL_PQY_VALUES tables manually.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_PRODUCTS (synonym) — the core product master, aliased as PDT, and self-joined as PDT1 to resolve the reporting product name.
• OKL_PDT_QUALITYS (synonym) — joins products to their assigned qualities; aliased PQY, PQY1, PQY2, PQY3.
• OKL_PDT_PQY_VALS (synonym) — stores the value assigned to each product/quality pair; aliased PQV, PQV1, PQV2, PQV3.
• OKL_PQY_VALUES (synonym) — the list of valid values for a given quality; aliased QVE, QVE1.
• OKL_PQY_VALUES_V (view) — the value list source used specifically for revenue recognition and interest calculation; aliased QVE2, QVE3.
• OKL_AE_TMPT_SETS (synonym) — the accounting template set, aliased AES.
• OKL_ACCOUNTING_UTIL (package) — supplies the Get_Lookup_Meaning function used to decode lookup codes.

The WHERE clause pins named qualities: 'LEASE' for deal type, 'TAXOWNER' for tax owner, and 'REVENUE_RECOGNITION_METHOD' for revenue recognition. This structure exposes a single row per qualifying product with the key parameters flattened into discrete columns.

Key Columns

• ID, NAME — product identifier and name.
• PRODUCT_SUBCLASS — the product subclass derived from the quality name.
• Deal_Type / Deal_Type_meaning / Deal_Type_description — lease deal classification and its decoded meaning (OKL_BOOK_CLASS lookup).
• Tax_Owner / Tax_owner_meaning — tax owner code and meaning (OKL_TAX_OWNER lookup).
• REPORTING_PRODUCT, PTL_ID, VERSION, DESCRIPTION, FROM_DATE, TO_DATE — product reporting and versioning metadata.
• AES_ID, aes_name, aes_org_id — associated accounting template set and its organization.
• PRODUCT_STATUS_CODE / PRODUCT_STATUS_meaning — lifecycle status and meaning (OKL_PRODUCT_STATUS lookup).
• Revenue_Recognition_Method / Revenue_Recognition_meaning — the revenue recognition convention assigned to the product, decoded via the OKL_REVENUE_RECOGNITION_METHOD lookup.
• Interest_Calculation_Basis / Interest_Calculation_meaning — interest basis and meaning (OKL_INTEREST_CALCULATION_BASIS lookup).
• LEGACY_PRODUCT_YN, OBJECT_VERSION_NUMBER — migration flag and optimistic-locking version.

Common Use Cases and Queries

Typical uses include reporting on product setup, validating revenue recognition assignments, and driving downstream accounting integration. A frequent query returns the revenue recognition method for all active products:

• SELECT name, Revenue_Recognition_Method, Revenue_Recognition_meaning FROM apps.okl_product_parameters_v WHERE PRODUCT_STATUS_CODE = 'ACTIVE' ORDER BY NAME;
• SELECT name, Deal_Type_meaning, Tax_owner_meaning, Interest_Calculation_meaning FROM apps.okl_product_parameters_v WHERE name = :product_name;
• SELECT name, aes_name FROM apps.okl_product_parameters_v WHERE Revenue_Recognition_Method = :method_code;

Because the view performs dictionary decoding through OKL_ACCOUNTING_UTIL, queries should ideally constrain on the product ID or name to limit the row set. The view is read-only and should be treated as a reporting interface rather than a maintenance path; product parameter changes must be made through the underlying OKL_PDT_PQY_VALS and related setup forms.