Results for “lrg_lse_id”

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

Overview

OKL_OPT_RULES is a table in the OKL schema within Oracle E-Business Suite Lease and Finance Management (OKL). Its documented description is "Association of Rules with Option." The table maps contract options and option subclasses to the rule groups and rule definitions that govern how those options are validated, priced, or processed. It therefore acts as a configuration bridge between the options defined on a lease or financing contract (OKL_OPTIONS) and the reusable rule infrastructure maintained in the Oracle Contracts (OKC) modules.

Because a single row carries foreign-key relationships to several distinct parent entities (option, subclass rule definition, rule group, and defined rule) rather than describing the natural key of a single business entity, the heuristic Data Vault classification of OKL_OPT_RULES is satellite-leaning. In a dimensional or Data Vault-style model this would suggest treating it as a satellite of the option and rule-group hubs, with the composite unique key serving as the link anchor. This is a modeling suggestion only; the table is a standard EBS transactional configuration object.

Key Information Stored

The table is documented with fourteen columns. The most functionally significant are the key and relationship columns, supported by the standard EBS audit columns.

• ID — Surrogate primary key (OKL_OPT_RULES_PK), also enforced by unique index OKL_OPT_RULES_U1. It is the column referenced by the child table OKL_OPV_RULES.
• OPT_ID — Foreign key to OKL_OPTIONS; identifies the option to which the rule association applies.
• SRD_ID_FOR — Foreign key to OKC_SUBCLASS_RG_DEFS; identifies the subclass rule definition being associated with the option.
• RGR_RGD_CODE and RGR_RDF_CODE — Foreign key columns to OKC_RG_DEF_RULES, identifying the rule group definition and rule definition participating in the association.
• LRG_LSE_ID and LRG_SRD_ID — Foreign key columns to OKC_LSE_RULE_GROUPS, identifying the lease rule group.
• OVERALL_INSTRUCTIONS — Free-form instructions associated with the rule-to-option configuration.
• OBJECT_VERSION_NUMBER — 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 — Standard "Who" audit columns populated automatically by the EBS runtime.

The business-key candidate is the composite unique index OKL_OPT_RULES_U2, defined across OPT_ID, SRD_ID_FOR, RGR_RGD_CODE, RGR_RDF_CODE, LRG_LSE_ID, and LRG_SRD_ID. This composite uniqueness means an individual option may be linked to a given subclass rule definition and rule group definition only once, while still allowing many rows per option.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios resolve which rules apply to a contract option, or audit changes to rule associations over time. A representative query joins the option to its rule associations:

• Resolve rules for an option: SELECT o.OPT_ID, r.RGR_RGD_CODE, r.RGR_RDF_CODE, r.OVERALL_INSTRUCTIONS FROM OKL_OPT_RULES r JOIN OKL_OPTIONS o ON o.OPT_ID = r.OPT_ID WHERE r.OPT_ID = :p_option_id;
• Locate option-level rules for a rule definition: SELECT r.OPT_ID, r.SRD_ID_FOR FROM OKL_OPT_RULES r WHERE r.RGR_RGD_CODE = :p_rgd_code AND r.RGR_RDF_CODE = :p_rdf_code;
• Audit recent changes: SELECT r.ID, r.OPT_ID, r.LAST_UPDATED_BY, r.LAST_UPDATE_DATE FROM OKL_OPT_RULES r WHERE r.LAST_UPDATE_DATE >= :p_since ORDER BY r.LAST_UPDATE_DATE DESC;
• Rules tied to a rule group: SELECT r.OPT_ID, r.LRG_LSE_ID, r.LRG_SRD_ID FROM OKL_OPT_RULES r WHERE r.LRG_LSE_ID = :p_lse_id;
• Rule-value coverage: joining OKL_OPV_RULES back to OKL_OPT_RULES on ORL_ID = ID to confirm whether each option rule has associated rule values.

These patterns support configuration verification before contract processing, migration validation when moving rule setups between environments, and reconciliation of option behavior during troubleshooting.

Related Objects

The table participates in a well-defined foreign-key network across the OKL and OKC schemas.

• OKL_OPTIONS — Parent of the option being configured; joined on OPT_ID.
• OKC_LSE_RULE_GROUPS — Source of the lease rule group; joined on LRG_LSE_ID and LRG_SRD_ID.
• OKC_RG_DEF_RULES — Source of the rule group definition and rule definition; joined on RGR_RGD_CODE and RGR_RDF_CODE.
• OKC_SUBCLASS_RG_DEFS — Source of the subclass rule definition; joined on SRD_ID_FOR.
• OKL_OPV_RULES — Child table that references OKL_OPT_RULES.ID through ORL_ID, storing the rule values evaluated for each option rule association.

These relationships confirm that OKL_OPT_RULES is the operational junction between option configuration and the shared rule engine, and that its primary key is the anchor referenced by downstream rule-value records.