Results for “ove_id”

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

Overview

OKL_PDT_OPT_VALS is a transactional configuration table owned by the OKL schema within the Oracle E-Business Suite Lease and Finance Management (OKL) module. Its documented purpose is the association of option values with a product. In practice, the table acts as the intersection between a product option definition and the discrete option values that may be selected for that option when a product is used to originate or administer a lease contract.

Under a heuristic Data Vault classification mined from its foreign key structure, OKL_PDT_OPT_VALS is satellite-leaning. This suggests it is best modeled as an attribute-bearing structure attached to the product option hub, rather than as an independent hub or a pure link. The table carries effective-dating columns and standard EBS audit columns, which is consistent with a satellite carrying descriptive, time-versioned attributes. This classification is a modeling suggestion derived from the relationship metadata, not a documented ETRM designation.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• ID — the system-generated surrogate primary key, enforced by OKL_PDT_OPT_VALS_PK. It uniquely identifies each option-value-to-product association row.
• OVE_ID — foreign key to OKL_OPT_VALUES, identifying the specific option value being associated.
• PON_ID — foreign key to OKL_PDT_OPTS, identifying the product option to which the value is attached.
• FROM_DATE and TO_DATE — effective-dating range governing when the association is valid for the product configuration.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-columns capturing creation and last-modification audit information.

Two unique indexes are documented. OKL_PDT_OPT_VALS_U1 enforces uniqueness on the surrogate ID. OKL_PDT_OPT_VALS_U2 enforces a composite business key on (OVE_ID, PON_ID), guaranteeing that any given option value is associated with a given product option at most once. In Data Vault terms, U2 is the natural business key candidate, while ID remains the technical surrogate.

Common Use Cases and Queries

The primary use case is resolving which option values are valid for a given product option, supporting product setup validation, lease origination, and configuration reporting. A typical join enumerates valid values for a product option:

• Join OKL_PDT_OPT_VALS to OKL_OPT_VALUES on OVE_ID and to OKL_PDT_OPTS on PON_ID, filtering by FROM_DATE and TO_DATE to return only currently effective associations.
• Query by PON_ID to list all option values attached to a product option; query by OVE_ID to find every product option that references a given value.
• Reconcile selections back to configuration: join OKL_SLCTD_OPTNS.POV_ID to OKL_PDT_OPT_VALS.ID to determine which configured option-value association a selected option originated from.
• Audit queries using CREATION_DATE, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER to trace configuration changes over time.

Reporting typically targets product configuration completeness, orphaned option values, and effectivity gaps where FROM_DATE/TO_DATE ranges leave a product option with no active values.

Related Objects

• OKL_OPT_VALUES — referenced via OKL_PDT_OPT_VALS.OVE_ID; supplies the option value definition.
• OKL_PDT_OPTS — referenced via OKL_PDT_OPT_VALS.PON_ID; the product option definition.
• OKL_SLCTD_OPTNS — references this table through OKL_SLCTD_OPTNS.POV_ID, linking actual contract selections back to the configured association.

Together these objects form the option configuration chain: product option definition (OKL_PDT_OPTS), permitted values (OKL_OPT_VALUES), the association itself (OKL_PDT_OPT_VALS), and the runtime selection (OKL_SLCTD_OPTNS).