Search Results parent_flex_value_high




Overview

FND_FLEX_VALUE_RULES_VL is a bilingual (MLS) view owned by the APPS schema in Oracle E-Business Suite. It is part of the FND — Application Object Library product and is classified as a VIEW with VALID status across EBS 12.1.1 and 12.2.2. The view presents human-readable definitions of Flex Value Rules, the security construct that restricts which key flexfield segment values a responsibility or user may access. In the Oracle EBS security architecture, a value rule is associated with a flex value set and defines a range of permitted parent values (from a low boundary to a high boundary). The view joins the rule definition stored in the base table with its translated descriptive columns, exposing a single localized row per rule matching the session language. Because it exposes the rule name, the target value set, range boundaries, and an error message, it is the standard reference for reporting on flexfield security rule configuration, for validating rule assignments, and for integration or reconciliation extracts that must resolve rule names to their underlying identifiers.

Underlying Base Objects

The view is defined over two documented base objects, each referenced as a synonym in the APPS schema:

  • FND_FLEX_VALUE_RULES — the transactional base table holding the rule identifier, name, owning flex value set, parent flex value low/high boundaries, and standard WHO audit columns (creation and last-update metadata).
  • FND_FLEX_VALUE_RULES_TL — the translation table holding language-specific attributes, notably ERROR_MESSAGE and DESCRIPTION.

The join is performed on FLEX_VALUE_RULE_ID between the base table (aliased B) and the translation table (aliased T), filtered by T.LANGUAGE = USERENV('LANG'). The _VL suffix indicates that the view returns the current session language row, so a user running under a Japanese language setting sees the localized description and error message rather than the base-language values. The view also projects the base table ROWID as ROW_ID.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing security rule coverage by value set, reconciling rule names with their ranges for migration or integration, and reporting localized descriptions for multi-language deployments.

SELECT flex_value_rule_name,
       flex_value_set_id,
       parent_flex_value_low,
       parent_flex_value_high,
       description
FROM   apps.fnd_flex_value_rules_vl
WHERE  flex_value_set_id = :p_value_set_id
ORDER  BY flex_value_rule_name;

To resolve rule names for a specific rule identifier returned by the flexfield security APIs:

SELECT flex_value_rule_name, description, error_message
FROM   apps.fnd_flex_value_rules_vl
WHERE  flex_value_rule_id = :p_rule_id;

Because the view enforces the USERENV('LANG') filter, callers should not add their own LANGUAGE predicate against the translation table; doing so against the view is unnecessary and may exclude valid rows.