Results for “pon_id”

50+ results




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

Overview

OKL_LA_PDT_OPTS_VALS_UV is an APPS-owned database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the OKL – Leasing and Finance Management product family. It is a user interface (UI) view, not a reporting or interface view in the conventional sense: its documented purpose is to drive the product option values list of values (LOV) page within the Oracle Lease and Finance Management application. When a user attaches a product to a lease or loan contract and then selects a product option, this view supplies the set of valid option values that may be chosen for that option in the context of that product.

Because it is a UI-support view, its semantics are tightly bound to the contracting flow. It filters simultaneously on effective dating at two levels — the option value itself and the product-to-option association — so that only currently effective combinations are presented to the user. The view does not expose the contract identifier directly, but the parameter implicitly captured by the LOV is the product option identifier, referenced in the user's search as PON_ID.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to the APPS schema through synonyms:

  • OKL_OPT_VALUES — the option value master, holding the permissible values and their descriptions for a given option, together with effective start and end dates.
  • OKL_PDT_OPT_VALS — the product option value assignment, associating a specific option value with a product option, and carrying its own effective dating columns.

The join condition is OPT_VALS.ID = PDT_OPT_VALS.OVE_ID, linking each product-level option value row to its master option value definition. The view therefore sits one level above the product option and requires the caller to filter by product option identifier, supplied through the PON_ID column of OKL_PDT_OPT_VALS, in order to return the values relevant to a single option on a single product.

Key Columns

  • VALUE — the option value code sourced from OKL_OPT_VALUES.VALUE. This is the stored value that would be written to the contract.
  • DESCRIPTION — the user-facing, translatable description from OKL_OPT_VALUES.DESCRIPTION, displayed in the LOV.
  • ID — the surrogate identifier from OKL_PDT_OPT_VALS.ID, uniquely identifying the product option value assignment row.
  • PON_ID — the product option identifier from OKL_PDT_OPT_VALS.PON_ID. This is the key correlation column and the value a caller must constrain to obtain the option values belonging to a specific product option.

Two effective-dating filters are applied in the view text. For the master option value: TRUNC(NVL(OPT_VALS.FROM_DATE, SYSDATE)) <= TRUNC(SYSDATE) and TRUNC(NVL(OPT_VALS.TO_DATE, SYSDATE+1)) > TRUNC(SYSDATE). For the product option value: the equivalent predicates on PDT_OPT_VALS.FROM_DATE and PDT_OPT_VALS.TO_DATE. Null start dates default to the current day and null end dates default to the following day, which makes open-ended records permanently effective under the strict "greater than" comparison.

Common Use Cases and Queries

The primary use case is populating the product option values LOV during contract entry. Because the view is already date-filtered, no additional effective-date predicate is required at the call site. A typical query constrains by PON_ID:

  • SELECT value, description, id FROM okl_la_pdt_opts_vals_uv WHERE pon_id = :p_pon_id ORDER BY description;

The same statement can be used in a reporting or reconciliation query when auditing which option values were available for a given product option on a given date, remembering that the view resolves against the database server's SYSDATE and therefore reflects only currently effective rows. Historical validation of what a user could have selected on a prior date is not supported by this view as written; such analysis requires querying OKL_PDT_OPT_VALS and OKL_OPT_VALUES directly with explicit date bounds. Performance is generally acceptable because lookups are driven by the indexed PON_ID and ID keys, but broad unfiltered queries return the full effective option value population and should be avoided.