Search Results fun_rule_crit_params_tl

Overview

The FUN_RULE_CRIT_PARAMS_VL view is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite. It is delivered by the FND — Application Object Library product, which is the foundation layer that hosts the Oracle Application Framework, flexfields, and the rule engine infrastructure used across ETRM and other modules. The view exposes the parameter definitions that qualify criteria within E-Business Suite rule structures. Each row represents a criteria parameter, describing the data type, the flex value set (where applicable), the object it belongs to, and the user-facing label, description, and tooltip in the session's current language.

Because the view name ends in _VL, it is a language-sensitive ("translated") view. It joins the base table FUN_RULE_CRIT_PARAMS_B with the translation table FUN_RULE_CRIT_PARAMS_TL, filtering the translation rows to the language of the current session via USERENV('LANG'). This makes the view the appropriate interface for reporting, forms, OAF pages, and integrations that need localized labels rather than base-table values. In EBS 12.1.1 and 12.2.2, the object is documented as VALID and available to APPS.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed to APPS as synonyms:

• FUN_RULE_CRIT_PARAMS_B — the base (non-translatable) table holding parameter identifiers, technical names, data types, flex value set references, object version numbers, and standard WHO audit columns.
• FUN_RULE_CRIT_PARAMS_TL — the translation table holding the language-specific user parameter name, description, and tip text, keyed by criteria parameter ID and language.

The view text joins the two on CRITERIA_PARAM_ID and restricts rows to T.LANGUAGE = USERENV('LANG'), returning a single localized row per criteria parameter for the current session language. This is the standard EBS translated-view pattern: the _B table supplies the structural definition, and the _TL table supplies the user-facing text.

Key Columns

• ROW_ID — the ROWID of the underlying _B row; used internally and not generally meaningful to end users.
• CRITERIA_PARAM_ID — primary identifier for the criteria parameter; the join key between the _B and _TL tables.
• RULE_OBJECT_ID — the rule object to which this parameter belongs, linking the parameter to its owning rule definition.
• PARAM_NAME — the internal (developer-facing) parameter name used in code and configuration.
• DATA_TYPE — the expected data type of the parameter (for example, character, number, or date), governing validation and display.
• FLEX_VALUE_SET_ID — the key flexfield value set used to validate or source valid values for the parameter, where applicable.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning column for the underlying row.
• CREATED_BY_MODULE — identifies the module that created the row, useful for tracing ownership.
• USER_PARAM_NAME — the localized, user-facing name shown to end users.
• DESCRIPTION — localized descriptive text for the parameter.
• TIP_TEXT — localized tooltip or help text associated with the parameter.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting on rule configuration, building LOVs for criteria parameter selection, verifying that translations exist for all languages, and troubleshooting rule behavior where a parameter's data type or value set drives validation. The view is also the preferred source when localized labels are needed in custom reports or integrations.

List all criteria parameters for a given rule object with localized labels:

SELECT criteria_param_id,
       rule_object_id,
       param_name,
       user_param_name,
       data_type,
       flex_value_set_id
FROM   apps.fun_rule_crit_params_vl
WHERE  rule_object_id = :p_rule_object_id
ORDER  BY user_param_name;

Find parameters bound to a specific flex value set:

SELECT param_name, user_param_name, description
FROM   apps.fun_rule_crit_params_vl
WHERE  flex_value_set_id = :p_flex_value_set_id;

Inspect datatype and translation coverage for a parameter:

SELECT b.param_name,
       b.data_type,
       t.language,
       t.user_param_name
FROM   apps.fun_rule_crit_params_b b,
       apps.fun_rule_crit_params_tl t
WHERE  b.criteria_param_id = t.criteria_param_id
AND    b.criteria_param_id = :p_criteria_param_id;

Because the _VL view depends on USERENV('LANG'), ensure the reporting session language is initialized (for example, via FND_GLOBAL or a connected EBS session) so that translated columns resolve to the intended language.