Results for “okl_opv_rules”

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

Overview

OKL.OKL_OPV_RULES is a transactional configuration table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It stores the association between Option Values and Option Rules, and is consumed by the Option Value Rule Template during Product Setup. In practical terms, this table defines which option values are permitted, or required, for a given option rule, and under which organizational and asset-book context that association holds. Because product configuration drives contract generation, pricing, and option execution downstream, OKL_OPV_RULES acts as a pivotal junction between reusable rule definitions and the concrete values available to end users at contract entry.

From a Data Vault modeling perspective, the documented foreign key topology suggests a satellite-leaning classification. The table carries descriptive and context-bearing attributes (COPY_OR_ENTER_FLAG, INDIVIDUAL_INSTRUCTIONS, and multiple CONTEXT_* columns) rather than acting as a pure many-to-many link, though its dual foreign keys to OKL_OPT_RULES and OKL_OPT_VALUES give it a strongly associative character. Modelers should treat it as a context-bearing satellite attached to the option rule and option value hubs, with the organizational context columns supplying the grain refinement.

Key Information Stored

The table contains 15 documented columns. The most significant are summarized below.

• ID — Surrogate primary key, enforced by OKL_OPV_RULES_PK and unique index OKL_OPV_RULES_U1. This is the internal system identifier and carries no business meaning.
• OVE_ID — Foreign key to OKL_OPT_VALUES. Identifies the specific option value being associated.
• ORL_ID — Foreign key to OKL_OPT_RULES. Identifies the governing option rule.
• CONTEXT_INTENT — Intent qualifier that scopes the association, typically distinguishing whether the value is offered, default, or mandatory within a given intent.
• CONTEXT_ORG — Operating unit or organization context in which the rule-value association applies.
• CONTEXT_INV_ORG — Inventory organization context, relevant where the option relates to tangible leased assets.
• CONTEXT_ASSET_BOOK — Asset book context, aligning the association to a specific depreciation or accounting book.
• COPY_OR_ENTER_FLAG — Indicates whether the option value is copied from a template or entered manually during setup.
• INDIVIDUAL_INSTRUCTIONS — Free-text or reference instructions applied when the value is presented to the user.
• 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 audit trail columns recording who created and last modified each row.

The composite unique index OKL_OPV_RULES_U2 covers OVE_ID, ORL_ID, CONTEXT_INTENT, CONTEXT_ORG, CONTEXT_INV_ORG, and CONTEXT_ASSET_BOOK. This is the true business key, guaranteeing that a given option value is associated with a given option rule only once per context combination.

Common Use Cases and Queries

The primary functional use case is diagnosing product setup behavior: identifying why a particular option value does not appear for an option rule in a specific organization. A representative query joins the three core tables:

• List all values attached to a rule: SELECT r.ID, v.NAME, r.CONTEXT_ORG FROM OKL_OPV_RULES r, OKL_OPT_VALUES v WHERE r.OVE_ID = v.ID AND r.ORL_ID = :rule_id;
• Check for gaps against the composite key: query OKL_OPV_RULES_U2 columns to confirm no duplicate context combinations exist after a data migration.
• Audit changes: report on LAST_UPDATED_BY and LAST_UPDATE_DATE within a date range to trace product setup modifications.
• Impact analysis: retrieve all rows referencing a value before retiring that value from OKL_OPT_VALUES.

Reporting consumers typically extract this table into a data warehouse alongside the option rule and value masters to support configuration governance and regression testing of product templates.

Related Objects

• OKL_OPT_RULES — Referenced through ORL_ID; the parent rule definition.
• OKL_OPT_VALUES — Referenced through OVE_ID; the parent value definition.
• OKL_OVD_RUL_TMLS — References this table via OVD_ID; the Option Value Rule Template that consumes these associations during Product Setup.
• OKL_OPV_RULES_PK / OKL_OPV_RULES_U1 / OKL_OPV_RULES_U2 — Supporting constraints and indexes that enforce identity and business uniqueness.

These four dependencies constitute the complete documented relationship set, making OKL_OPV_RULES a tightly scoped and well-bounded configuration object within the OKL schema.