Results for “okl_revenue_recognition_method”

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

Overview

APPS.OKL_PRODUCT_PARAMETERS_ALL_V is a reporting and integration view in the Oracle E-Business Suite Lease Management (OKL) module, part of the Enterprise Transaction and Revenue Management (ETRM) family of applications. It presents a denormalized, human-readable picture of lease product definitions by joining each product header record in OKL_PRODUCTS to the quality values that qualify it, and then resolving the coded values into their descriptive lookup meanings. The view answers a recurring question for implementers and analysts: for a given lease product, which business attributes control its behavior — deal type, tax ownership, revenue recognition method, and interest calculation basis — and what do the underlying codes actually mean?

The name suffix "_ALL" reflects multi-organization (multi-org) awareness via the AES_ID column and its join to OKL_AE_TMPT_SETS_ALL, the asset/entity template sets table. This makes the view suitable for use in multi-org reporting where the operating unit or entity context matters. The user search term "okl_revenue_recognition_method" maps directly to the OKL_REVENUE_RECOGNITION_METHOD lookup type exposed through the Revenue_Recognition_Method and Revenue_Recognition_meaning columns of this view.

Underlying Base Objects

The view is defined over the following documented base objects, all owned by APPS:

• OKL_PRODUCTS — aliased twice as PDT and PDT1; PDT supplies the primary product row, PDT1 is outer-joined through reporting_pdt_id to resolve the parent reporting product name.
• OKL_PDT_QUALITYS — the product quality definitions (aliased PQY, PQY1, PQY2, PQY3); the names used in the joins are 'LEASE', 'TAXOWNER', 'REVENUE_RECOGNITION_METHOD', and the interest calculation quality.
• OKL_PDT_PQY_VALS — the product-to-quality-value assignments (aliased PQV, PQV1, PQV2, PQV3).
• OKL_PQY_VALUES — the quality value master (aliased QVE, QVE1).
• OKL_PQY_VALUES_V — a validation view over quality values (aliased QVE2, QVE3), used specifically for the revenue recognition and interest calculation qualities.
• OKL_AE_TMPT_SETS_ALL — the entity template set, aliased AES, providing aes_name and aes_org_id.
• OKL_ACCOUNTING_UTIL — the package whose Get_Lookup_Meaning function translates stored lookup codes into descriptive meanings.

Key Columns

The view exposes product-identifying columns (ID, NAME, VERSION, DESCRIPTION, FROM_DATE, TO_DATE, PRODUCT_STATUS_CODE and its meaning), organizational context (AES_ID, aes_name, aes_org_id), and a set of quality-derived attributes:

• Deal_Type / Deal_Type_meaning — derived from the 'LEASE' quality and looked up against OKL_BOOK_CLASS.
• Tax_Owner / Tax_owner_meaning — derived from the 'TAXOWNER' quality against OKL_TAX_OWNER.
• Revenue_Recognition_Method / Revenue_Recognition_meaning — derived from the 'REVENUE_RECOGNITION_METHOD' quality against OKL_REVENUE_RECOGNITION_METHOD. This is the column referenced by the user's search term.
• Interest_Calculation_Basis / Interest_Calculation_meaning — derived from the corresponding quality against OKL_INTEREST_CALCULATION_BASIS.
• PRODUCT_SUBCLASS, REPORTING_PDT_ID, REPORTING_PRODUCT, PTL_ID, LEGACY_PRODUCT_YN, OBJECT_VERSION_NUMBER — classification and versioning attributes.

Common Use Cases and Queries

Typical uses include auditing which products use a given revenue recognition method, validating setup consistency across operating units, and feeding downstream revenue schedules or integration extracts.

• Find lease products by revenue recognition method:

SELECT id, name, revenue_recognition_method, revenue_recognition_meaning
FROM   apps.okl_product_parameters_all_v
WHERE  revenue_recognition_meaning = 'Straight Line'
AND    SYSDATE BETWEEN from_date AND NVL(to_date, SYSDATE);

• Audit all quality-based parameters for a single product:

SELECT name, deal_type_meaning, tax_owner_meaning,
       revenue_recognition_meaning, interest_calculation_meaning
FROM   apps.okl_product_parameters_all_v
WHERE  name = 'MY_LEASE_PRODUCT';

• Cross-check revenue recognition rules by operating unit:

SELECT aes_org_id, revenue_recognition_meaning, COUNT(*)
FROM   apps.okl_product_parameters_all_v
GROUP  BY aes_org_id, revenue_recognition_meaning;

Because the view resolves codes to meanings via OKL_ACCOUNTING_UTIL.Get_Lookup_Meaning and joins several quality tables, queries should always filter on active date ranges and, where needed, aes_org_id to avoid row duplication from historical quality values.