Results for “okl_options”

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

Overview

OKL_OPTIONS is a core configuration table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The table stores the master definition of contract options — the configurable attributes that characterize a lease or loan contract, such as purchase options, termination options, renewal terms, and other contractual elections that drive pricing and lifecycle behavior. Because options are defined once and then associated to products and contracts, OKL_OPTIONS acts as a reference or setup entity rather than a transactional table.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. The presence of a single-column surrogate primary key (ID), a stable business key (NAME), and no upstream foreign key dependencies suggests OKL_OPTIONS functions as a hub from which rules, values, and product associations descend. This is a modeling suggestion: the option definition itself is a durable, non-volatile list of business concepts, while the satellite-like descriptive and audit columns (dates, attributes, who-columns) travel alongside it.

Key Information Stored

The table contains 27 documented columns in the OKL schema. The most significant are:

• ID — surrogate primary key defined by OKL_OPTIONS_PK and reinforced by unique index OKL_OPTIONS_U1. This is the internal identifier used by all child tables.
• NAME — the business-key candidate, enforced by unique index OKL_OPTIONS_U2. This is how users and most reports identify an option.
• DESCRIPTION — free-text explanation of the option's purpose and behavior.
• FROM_DATE and TO_DATE — effective dating that governs when the option definition is valid and available for selection.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OKL APIs and concurrent programs.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, allowing customers to extend the option definition without customization.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit columns that record provenance and support change tracking.

The distinction between ID and NAME matters operationally: ID is the referential anchor for all downstream tables, while NAME is the human-readable key used in setup screens and ad hoc reporting. Any integration that loads or reconciles options should key on NAME for matching but persist ID for joins.

Common Use Cases and Queries

Typical scenarios include setup validation, functional reporting on available options, and impact analysis before disabling an option.

• List active options: select ID, NAME, DESCRIPTION from OKL_OPTIONS where trunc(sysdate) between FROM_DATE and TO_DATE order by NAME.
• Locate an option by business key: select ID from OKL_OPTIONS where NAME = :name.
• Impact check before deactivation: join to OKL_PDT_OPTS on OPT_ID to find products currently offering the option, and to OKL_OPT_VALUES on OPT_ID to find permitted values.
• DFF-driven reporting: select NAME, ATTRIBUTE_CATEGORY, ATTRIBUTE1 from OKL_OPTIONS where ATTRIBUTE_CATEGORY = :category.

Because OKL_OPTIONS is a low-volume setup table, queries against it are inexpensive; the tuning concern lies in the child tables, which should be joined via indexed OPT_ID.

Related Objects

Three tables reference OKL_OPTIONS through the OPT_ID foreign key column:

• OKL_OPT_RULES (OKL_OPT_RULES.OPT_ID → OKL_OPTIONS) — rules governing how and when the option may be exercised.
• OKL_OPT_VALUES (OKL_OPT_VALUES.OPT_ID → OKL_OPTIONS) — the valid value list for a given option.
• OKL_PDT_OPTS (OKL_PDT_OPTS.OPT_ID → OKL_OPTIONS) — the association of options to lease products, which determines which options appear on contracts generated from a product.

In practice, OKL_OPTIONS sits at the top of a small family of related tables: products link options via OKL_PDT_OPTS, and each option's permitted values and rules are held in OKL_OPT_VALUES and OKL_OPT_RULES respectively. Reporting and integration work should treat this group as a unit when extracting option configuration for downstream systems.