Search Results rule_values

Overview

XDO_DGF_RULE_CATALOG_VL is a validation view owned by the APPS schema in Oracle E-Business Suite, categorized under FND — Application Object Library. The view exposes the Data Gathering Framework (DGF) rule catalog used by the XML Publisher / BI Publisher engine (XDO) to define conditional rules evaluated during report execution and post-processing. In ETRM 12.1.1 and 12.2.2, the view is documented as VALID and serves as the translation-aware, read-only interface through which rule metadata is queried, reported on, and consumed by integration layers.

The suffix "_VL" denotes a "view with language" pattern standard in EBS: the view joins a base table that stores language-independent data with a translation table that holds language-specific descriptions, filtered by the session language. This allows reporting tools and APIs to retrieve a single row per rule in the user's current language without writing explicit translation joins. The view is primarily a reporting and integration surface; DML is performed against the underlying base and translation tables by the DGF setup forms rather than through the view.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• XDO_DGF_RULE_CATALOG_B — the base (language-independent) table storing rule identifiers, context bindings, operators, arguments, and audit columns. Aliased as XRG in the view definition.
• XDO_DGF_RULE_CATALOG_TL — the translation table storing language-specific rule values and descriptions. Aliased as XRL and joined on RULE_CATALOG_ID, restricted by XRL.LANGUAGE = USERENV('LANG').

The join is an inner join on RULE_CATALOG_ID between the two tables. The view therefore returns exactly one row for every base record that has a translation row in the session language, projecting all columns from the base table plus the translatable RULE_VALUES and RULE_DESCRIPTION from the TL table.

Key Columns

• RULE_CATALOG_ID — the primary identifier for a DGF rule; the central search key for the catalog.
• BLOCK_CONTEXT_ID — identifies the data block or context against which the rule is evaluated.
• RULE_SHORT_NAME, RULE_TYPE, RULE_VARIABLE, RULE_OPERATOR — define the rule's identity and comparison logic.
• RULE_VALUES, RULE_DESCRIPTION — sourced from the translation table; text is language-dependent.
• RULE_VALUES_DATATYPE, DB_FUNCTION, ARG_NUMBER — control the datatype and the database function invoked when the rule fires.
• ARG01–ARG10 and ARG01_TYPE–ARG10_TYPE — up to ten positional argument values and their datatypes passed to the rule's DB function.
• OBJECT_VERSION_NUMBER, ATTRIBUTE1–ATTRIBUTE15 — DFF and optimistic locking support.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage includes auditing rule definitions, migrating DGF rules between environments, and joining rule data to report definitions for documentation.

• Retrieve all rules for a given context:
  SELECT rule_catalog_id, rule_short_name, rule_operator, rule_values FROM xdo_dgf_rule_catalog_vl WHERE block_context_id = :p_context_id;
• Search directly by the identifier the user queried:
  SELECT * FROM xdo_dgf_rule_catalog_vl WHERE rule_catalog_id = :p_rule_catalog_id;
• List rules invoking a specific database function:
  SELECT rule_short_name, db_function, rule_description FROM xdo_dgf_rule_catalog_vl WHERE db_function = :p_function;

Because the view filters on USERENV('LANG'), any extraction or migration must account for language context to avoid missing translation rows for the target locale.