Results for “interest_calculation_meaning”

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

Overview

OKL_PRODUCT_PARAMETERS_V is a reporting view owned by the APPS schema in Oracle Lease and Finance Management (OKL), the ETRM module of Oracle E-Business Suite. The view consolidates the key business parameters defined for each lease and finance product configured on OKL_PRODUCTS into a single denormalized result set. Rather than requiring callers to join the product table to multiple quality/value tables and resolve lookup codes themselves, the view performs those joins and lookup translations in advance, exposing human-readable meanings alongside raw codes. Its primary role is to support configuration review, reporting, and integration scenarios in which downstream processes must determine how a product behaves — for example, its deal type, tax ownership treatment, revenue recognition method, and interest calculation basis.

The view is available in both release 12.1.1 and 12.2.2 and is documented as VALID in the ETRM repository. The presence of OBJECT_VERSION_NUMBER among the projected columns reflects the optimistic locking convention standard to ETRM 12.x tables, which is useful when the view output is used to drive update logic in adjacent product maintenance forms.

Underlying Base Objects

The view text is defined entirely within the OKL schema family and draws on seven documented base objects:

• OKL_PRODUCTS — the master product definition table, aliased as PDT, and self-joined as PDT1 to resolve REPORTING_PDT_ID into the reporting product name.
• OKL_AE_TMPT_SETS — aliased AES, supplied through a non-outer join to bring in the template set name and organization identifier.
• OKL_PDT_QUALITYS — the product quality (parameter group) table, joined repeatedly as PQY, PQY1, PQY2, and PQY3.
• OKL_PDT_PQY_VALS — the product-to-quality-value association table, aliased PQV, PQV1, PQV2, and PQV3.
• OKL_PQY_VALUES — the quality value table supplying LEASE and TAXOWNER selections, aliased QVE and QVE1.
• OKL_PQY_VALUES_V — a related view supplying the revenue recognition and interest calculation values, aliased QVE2 and QVE3.
• OKL_ACCOUNTING_UTIL — a package whose GET_LOOKUP_MEANING function converts OKL lookup codes into their descriptive meanings.

Filter predicates are anchored on PQY.NAME = 'LEASE' and PQY1.NAME = 'TAXOWNER', so the row is driven by products that have those two quality assignments populated.

Key Columns

• ID, NAME, DESCRIPTION, VERSION, FROM_DATE, TO_DATE — core product identity and effective dating attributes.
• PRODUCT_SUBCLASS — the product subclass name from OKL_PDT_QUALITYS.
• DEAL_TYPE / DEAL_TYPE_MEANING / DEAL_TYPE_DESCRIPTION — the LEASE quality value and its decoded meaning.
• TAX_OWNER, TAX_OWNER_MEANING, TAX_OWNER_DESCRIPTION — the TAXOWNER quality value and lookup translation.
• PRODUCT_STATUS_CODE — the status code stored on OKL_PRODUCTS for the product (the column of interest to users searching on this term), paired with PRODUCT_STATUS_MEANING, resolved through OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING using lookup type OKL_PRODUCT_STATUS.
• REVENUE_RECOGNITION_METHOD / REVENUE_RECOGNITION_MEANING and INTEREST_CALCULATION_BASIS / INTEREST_CALCULATION_MEANING — behavioral parameters decoded from OKL_REVENUE_RECOGNITION_METHOD and OKL_INTEREST_CALCULATION_BASIS lookups respectively.
• REPORTING_PDT_ID / REPORTING_PRODUCT — self-referencing pointer to the product used for external reporting.
• AES_ID, AES_NAME, AES_ORG_ID — template set and owning organization context.
• OBJECT_VERSION_NUMBER, LEGACY_PRODUCT_YN, PTL_ID — concurrency and migration-related attributes.

Common Use Cases and Queries

A frequent requirement is to report all active products together with their decoded status. Because the view already resolves the lookup, no additional join to FND_LOOKUP_VALUES is necessary:

• SELECT id, name, product_status_code, product_status_meaning FROM okl_product_parameters_v WHERE product_status_code = 'ACTIVE';
• SELECT name, deal_type_meaning, tax_owner_meaning, revenue_recognition_meaning FROM okl_product_parameters_v ORDER BY name;
• SELECT name, product_status_meaning, aes_name, aes_org_id FROM okl_product_parameters_v WHERE aes_org_id = :org_id;
• SELECT name, from_date, to_date, version FROM okl_product_parameters_v WHERE SYSDATE BETWEEN from_date AND NVL(to_date, SYSDATE + 1);

Typical consumers include integration extracts that feed a pricing or contract-booking engine needing a product's deal type and tax owner, configuration audits comparing status codes across environments, and custom concurrent programs that must validate a product is active before allowing lease origination. When reporting on large product populations, filtering on PRODUCT_STATUS_CODE or AES_ORG_ID is advisable, since the multiple quality joins in the view definition are not themselves constrained by bind parameters in the underlying SQL.