Search Results concatenated_rule




Overview
Explore in AI Chat

Overview

OKL_OPT_RULES_UV is a VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management product family. It exposes option-level accounting rule definitions in a flattened, report-ready form. The view is a denormalized presentation layer over the option rule tables and their associated subclass rule group definitions, joining OKL_OPT_RULES to OKC_SUBCLASS_RG_DEFS and invoking OKL_ACCOUNTING_UTIL to derive a rule description. Its purpose is to give reporting, inquiry, and integration components a single, stable projection of rule data without requiring the caller to reconstruct joins, decode subclass identifiers, or resolve rule meanings programmatically.

The defining characteristic of the view is that it restricts output to option-level rules only: the WHERE clause enforces ORL.LRG_LSE_ID IS NULL, which excludes lease-level rule rows. Consequently, every row returned represents a rule scoped to an option or product construct rather than a lease. This design is why the LSE_ID and LINE_STYLE columns are projected as literal NULLs — they exist in the view's column list to preserve a uniform column signature across the OKL rule views family, even though they carry no data here. The view also computes CONCATENATED_RULE, a composite key formed from the rule code, the rule group code, and the subclass code, which is the element most frequently requested by users searching for that term.

Underlying Base Objects

The view is defined over two synonym-referenced base objects plus one package. OKL_OPT_RULES (synonym) is the driving table; it supplies the rule identifier ID, the option identifier OPT_ID, the subclass reference SRD_ID_FOR, the rule group code RGR_RGD_CODE, the rule code RGR_RDF_CODE, the overall instructions text, and the standard audit columns. OKC_SUBCLASS_RG_DEFS (synonym) supplies the subclass definition joined on SRD.ID = ORL.SRD_ID_FOR, contributing SCS_CODE (the subclass code), START_DATE, and END_DATE. OKL_ACCOUNTING_UTIL (package) is called through the function GET_RULE_MEANING, which accepts the stored rule code and returns a human-readable MEANING value. The join is an inner join, so an option rule without a matching subclass rule group definition will not appear in the result set, and the effective date window of the subclass definition governs the START_DATE and END_DATE columns presented.

Key Columns

  • ID – Primary identifier of the option rule row, inherited from OKL_OPT_RULES.ID.
  • OPT_ID – Identifier of the owning option; the principal filter for option-scoped queries.
  • LSE_ID / LINE_STYLE – Always NULL in this view; retained for column compatibility with the broader rule view family.
  • SRD_ID – Foreign key to the subclass rule group definition (OKC_SUBCLASS_RG_DEFS.ID).
  • SUBCLASS – The subclass code (SCS_CODE) from the joined definition.
  • RULE_GROUP – The rule group code (RGR_RGD_CODE).
  • RULE – The rule code (RGR_RDF_CODE).
  • CONCATENATED_RULE – Composite key built as RGR_RDF_CODE || '.' || RGR_RGD_CODE || '.' || SCS_CODE. This is the fully qualified rule reference used for lookup and cross-referencing.
  • MEANING – Descriptive text returned by OKL_ACCOUNTING_UTIL.GET_RULE_MEANING for the rule code.
  • OVERALL_INSTRUCTIONS – Free-text guidance stored against the rule.
  • START_DATE / END_DATE – Effective dating inherited from the subclass rule group definition.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns.

Common Use Cases and Queries

Typical uses include rule inquiry forms, accounting rule validation reports, migration and reconciliation extracts, and integration payloads that must publish option rule assignments with their effective dates. When debugging, the CONCATENATED_RULE column is the most direct search target, since it uniquely identifies a rule within its group and subclass.

List all option rules for a given option:

  • SELECT rule_group, rule, subclass, concatenated_rule, meaning FROM okl_opt_rules_uv WHERE opt_id = :p_opt_id;

Resolve a rule from its concatenated identifier:

  • SELECT opt_id, rule_group, rule, subclass, meaning, overall_instructions FROM okl_opt_rules_uv WHERE concatenated_rule = :p_concatenated_rule;

Retrieve rules effective as of a date, with audit traceability:

  • SELECT concatenated_rule, meaning, start_date, end_date, last_updated_by, last_update_date FROM okl_opt_rules_uv WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Because the view performs a table-to-table join and a PL/SQL function call per row, queries should always be restricted by OPT_ID, SRD_ID, or CONCATENATED_RULE rather than scanned in full, particularly in high-volume reporting environments.