Results for “rgd_code”

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

Overview

OKL_VP_RULE_GROUPS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is shipped as part of the OKL product family, Oracle Lease and Finance Management, and is classified in the ETRM repository with a status of VALID. The view serves as a presentation-layer abstraction over the lease subclass rule-group configuration data that underpins OKL accounting rule derivation.

Rather than exposing raw code values, the view resolves the stored rule-group definition code (RGD_CODE) into a human-readable meaning using the OKL_ACCOUNTING_UTIL package. This makes it suitable for reporting, diagnostics, and integration scenarios where a descriptive label is required without embedding lookup translation logic into the consuming query. Because it is a view rather than a table, no DML is possible through this object; it is intended strictly for query access.

The object name does not appear independently in general OKL documentation, and users frequently reach it while searching for the underlying configuration object OKC_RULE_GROUP_DEF, which this view references indirectly through its lookup call. This association is the primary reason the view surfaces in searches for rule-group configuration metadata.

Underlying Base Objects

According to documented ETRM 12.2.2 metadata, OKL_VP_RULE_GROUPS_UV is defined over the following referenced objects:

• OKC_SUBCLASS_RG_DEFS (SYNONYM) — supplies the rule-group definition rows, including RGD_CODE, SCS_CODE, and the effective date range for each definition.
• OKC_SUBCLASSES_B (SYNONYM) — supplies the subclass master rows, including CODE and the subclass effective date range used to filter active subclasses.
• OKL_ACCOUNTING_UTIL (PACKAGE) — invoked in the SELECT list to translate the rule-group definition code into a lookup meaning.

The view text joins OKC_SUBCLASS_RG_DEFS (aliased SRDV) to OKC_SUBCLASSES_B (aliased SCSV) on SRDV.SCS_CODE = SCSV.CODE. Both sides are constrained by an effective-date predicate: SYSDATE must fall between START_DATE and NVL(END_DATE, SYSDATE), so only currently effective subclasses and rule-group definitions are returned. The lookup meaning is obtained via OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING with a lookup type of OKC_RULE_GROUP_DEF, the RGD_CODE value, and the parameters 510 and 0.

Key Columns

• MEANING — The decoded, user-facing description of the rule-group definition. It is produced by GET_LOOKUP_MEANING against the OKC_RULE_GROUP_DEF lookup type and is the principal reason for querying the view.
• RGD_CODE — The rule-group definition code as stored in OKC_SUBCLASS_RG_DEFS. This is the raw identifier used by the application's rule engine and is the join key to that base table.
• SCS_CODE — The subclass code from OKC_SUBCLASSES_B. It identifies the lease subclass to which the rule-group definition is attached and is the join key back to the subclass master data.

Common Use Cases and Queries

The view is typically used to validate which rule groups are currently active for a given subclass, to produce reporting extracts that display descriptive rule-group names, and to diagnose discrepancies between configuration and expected accounting behavior. A straightforward listing of all currently effective mappings can be obtained as follows:

• SELECT meaning, rgd_code, scs_code FROM apps.okl_vp_rule_groups_uv ORDER BY scs_code, rgd_code;
• SELECT meaning, rgd_code FROM apps.okl_vp_rule_groups_uv WHERE scs_code = :subclass_code;
• SELECT scs_code, COUNT(*) FROM apps.okl_vp_rule_groups_uv GROUP BY scs_code;

Because effective dates are already applied inside the view definition, no additional date filtering is required by callers seeking current configuration. Reports needed for historical (non-current) rule-group assignments must query OKC_SUBCLASS_RG_DEFS directly, since the view intentionally restricts output to rows valid as of the current SYSDATE.