Search Results okl_lse_scs_rules_v




Overview
Explore in AI Chat

Overview

OKL_LSE_SCS_RULES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. The view exposes rule information required for a product, combining line style, subclass, rule group, and rule definitions into a single denormalized result set. In ETRM (Enterprise Tax, Revenue, and Trade Management) documentation for release 12.2.2, the object is listed with a status of VALID and is documented as a reporting and lookup helper rather than a transaction-processing entity.

Within Oracle EBS 12.1.1 and 12.2.2, the view serves as a lightweight bridge between the OKC (Oracle Contracts) rule-definition tables and the OKL leasing accounting engine. It allows reporting tools, concurrent programs, and integration layers to resolve which accounting rules apply to a given subclass without navigating multiple parent-child relationships. The view is not a base table and holds no data of its own; every row is derived at query time from the underlying rule configuration.

Underlying Base Objects

The documented ETRM metadata confirms the view is defined over three referenced objects:

The two OKC tables are joined on RGD_CODE. The view text applies a fixed filter restricting results to four specific rule-group and rule combinations: AMTEOC/AMBPOC, AMTFOC/AMBPOC, LAEVEL/LAEVEL, and LAIIND/LAINTP. Consequently, the view intentionally returns a narrow, curated subset of the rule configuration rather than every row present in the base tables.

Key Columns

  • SRD_ID – Identifier from OKC_SUBCLASS_RG_DEFS for the subclass/rule-group definition row.
  • SUBCLASS – The subclass code (SCS_CODE) to which the rule applies.
  • RULE_GROUP – The rule group (RGD_CODE) associated with the subclass.
  • RULE – The individual rule code (RDF_CODE) within the rule group.
  • CONCATENATED_RULE – A composite key formed as RULE || '.' || RULE_GROUP || '.' || SUBCLASS, useful for building unique lookup keys in reports and interfaces.
  • START_DATE / END_DATE – Effective dating for the subclass/rule-group definition, enabling date-aware filtering.
  • MEANING – The descriptive text returned by OKL_ACCOUNTING_UTIL.GET_RULE_MEANING, providing a user-facing label for the rule.
  • LSE_ID, LINE_STYLE, LINE_TYPE, PARENT_ID – Exposed as NULL literals in the view text; they are placeholders that preserve a consistent column shape for callers, or for potential set operations and future extension.

Common Use Cases and Queries

Typical uses include validating rule configuration for leasing products, populating LOVs or reference data in custom reports, and resolving rule meanings during accounting reconciliation. Because the placeholder columns are always NULL, queries should rely on SUBCLASS, RULE_GROUP, and RULE.

Return all configured rules with their meanings:

  • SELECT subclass, rule_group, rule, meaning FROM okl_lse_scs_rules_v;

Retrieve rules effective on a specific date:

  • SELECT concatenated_rule, meaning FROM okl_lse_scs_rules_v WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Filter to a specific subclass for a product setup check:

  • SELECT rule, meaning FROM okl_lse_scs_rules_v WHERE subclass = :subclass_code ORDER BY rule_group, rule;

Because the view depends on OKC rule definitions and the OKL_ACCOUNTING_UTIL package, changes to rule setup in Oracle Contracts are reflected immediately on the next query, making the view suitable for real-time validation logic in custom concurrent programs and 12.1.1/12.2.2 integrations.