Search Results opt_name




Overview
Explore in AI Chat

Overview

OKL_PRODUCT_OPTIONS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKL (Lease and Finance Management) product family and carries a VALID status in the ETRM 12.2.2 data dictionary. The view presents the complete association between lease products and the options configured against those products, joining three base tables — OKL_PDT_OPTS, OKL_PRODUCTS, and OKL_OPTIONS — into a single denormalized result set. Its primary purpose is to expose product-to-option mappings in a form that is convenient for reporting, concurrent programs, and integration interfaces without forcing the caller to write multi-table joins. The name suffix "UV" conventionally indicates a user view, meaning it is intended as a supported query surface rather than an internal implementation object. Because the view is defined in APPS and references synonyms of the underlying OKL tables, it respects the standard EBS multi-org and security model applied to the OKL schema.

Underlying Base Objects

The documented base objects referenced by OKL_PRODUCT_OPTIONS_UV are OKL_PDT_OPTS, OKL_PRODUCTS, and OKL_OPTIONS, all accessed through synonyms in the APPS schema. OKL_PDT_OPTS is the association table that records which options attach to which products, and it supplies the ID, OPTIONAL_YN, PDT_ID, OPT_ID, OBJECT_VERSION_NUMBER, FROM_DATE, and TO_DATE columns. OKL_PRODUCTS supplies the product definition, contributing PDT.NAME as PDT_NAME. OKL_OPTIONS supplies the option master, contributing OPT.NAME as OPT_NAME and OPT.DESCRIPTION as OPT_DESCRIPTION. The join conditions are explicit and equality-based: PON.PDT_ID = PDT.ID and PON.OPT_ID = OPT.ID. This inner-join construction means a row is returned only when the product option association resolves to existing product and option records, which is consistent with expected referential integrity in the OKL data model.

Key Columns

  • ID — Surrogate identifier of the product option association row from OKL_PDT_OPTS.
  • OPTIONAL_YN — Flag indicating whether the option is optional (Y) or mandatory (N) for the product.
  • PDT_ID — Foreign key to the product record in OKL_PRODUCTS.
  • PDT_NAME — Descriptive name of the product, useful for reporting without an additional join.
  • OPT_ID — Foreign key to the option record in OKL_OPTIONS.
  • OPT_NAME — Name of the option; this is the column most commonly used when searching for a specific option such as an "opt_name" lookup.
  • OPT_DESCRIPTION — Free-text description of the option.
  • OBJECT_VERSION_NUMBER — Optimistic locking version number for the association row.
  • FROM_DATE / TO_DATE — Effective date range governing when the product-option association is active.

Common Use Cases and Queries

Typical usage includes validating which options are attached to a lease product, filtering mandatory versus optional options, and driving configuration or pricing interfaces that consume option metadata. A direct search on the option name is the most frequent pattern:

  • SELECT pdt_name, opt_name, optional_yn FROM okl_product_options_uv WHERE opt_name = 'YOUR_OPTION';
  • SELECT opt_name, opt_description FROM okl_product_options_uv WHERE pdt_id = :product_id ORDER BY opt_name;
  • SELECT pdt_name, COUNT(*) FROM okl_product_options_uv WHERE optional_yn = 'Y' GROUP BY pdt_name;
  • SELECT * FROM okl_product_options_uv WHERE TRUNC(SYSDATE) BETWEEN from_date AND to_date;

Because the view performs the join internally, report developers avoid duplicating product and option lookups in custom SQL and reduce the risk of inconsistent join logic across OKL reporting assets.