Results for “okl_opt_values”

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

Overview

OKL_OPT_VALUES is a reference and configuration table within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It stores the discrete values that may be associated with an option defined in the lease or financing contract structure. In practical terms, each row represents a permissible value that can be attached to an option, allowing the application to present controlled, reusable selections rather than free-form entries during contract authoring, product configuration, and pricing.

The table sits within the OKL schema and is validated in both Oracle EBS 12.1.1 and 12.2.2. Based on the foreign key topology, the heuristic Data Vault classification for this object is hub-leaning. Modeled as a Data Vault construct, OKL_OPT_VALUES would function as a hub or reference entity, with OKL_OPTIONS and downstream rule and product tables acting as links or satellites that qualify or extend the option value.

Key Information Stored

The table comprises twelve documented columns. The most significant are:

• ID — Surrogate primary key (OKL_OPT_VALUES_PK) and the unique index OKL_OPT_VALUES_U1. It uniquely identifies each option value record and is referenced as a foreign key by downstream tables.
• OPT_ID — Foreign key to OKL_OPTIONS, linking each value to its parent option definition.
• VALUE — The actual option value text or code associated with the option.
• OPT_ID + VALUE — Composite unique index OKL_OPT_VALUES_U2, the strongest business-key candidate, ensuring the same value is not duplicated for a given option.
• DESCRIPTION — Human-readable description of the option value, used in list-of-values displays and reports.
• FROM_DATE and TO_DATE — Effective date range controlling when the option value is valid for selection.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns that capture audit and user attribution for each record.

Common Use Cases and Queries

Typical usage focuses on validating, reporting, and maintaining option values. A common pattern joins OKL_OPT_VALUES to OKL_OPTIONS to retrieve the values available for a given option:

• List active option values for an option: SELECT ove.value, ove.description FROM okl_opt_values ove, okl_options opt WHERE ove.opt_id = opt.id AND opt.id = :p_opt_id AND SYSDATE BETWEEN ove.from_date AND NVL(ove.to_date, SYSDATE + 1);
• Reporting configured option values by product: join through OKL_PDT_OPT_VALS to surface which option values are attached to a product definition.
• Detecting duplicate or overlapping effective-date configurations using the OPT_ID/VALUE business key.
• Data cleanup and audit queries leveraging the WHO columns to identify recent additions or modifications.

Related Objects

The foreign key relationships provided in the metadata define the key dependencies:

• OKL_OPTIONS — Parent table; joined via OKL_OPT_VALUES.OPT_ID = OKL_OPTIONS.ID.
• OKL_OPV_RULES — Child table referencing OKL_OPT_VALUES.OVE_ID; holds rules tied to a specific option value.
• OKL_PDT_OPT_VALS — Child table referencing OKL_OPT_VALUES.OVE_ID; links product definitions to permitted option values.

Together these relationships position OKL_OPT_VALUES as a central reference point between option definitions and the rules and product configurations that consume them.