Results for “fnd_flex_value_rules”

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

Overview

FND_FLEX_VALUE_RULES is the Oracle E-Business Suite table that stores security rules (also called value security rules) applied to flexfield value sets. Owned by the APPLSYS schema and belonging to the FND — Application Object Library product, it is the definition repository for the intersection of a key flexfield (KFF) or descriptive flexfield (DFF) value set with a hierarchical parent-child value range. Each row defines a rule header: a named rule mapped to a specific value set and constrained by a parent value low/high range. The actual included or excluded value ranges are held in child tables, making this object the parent anchor of a small, purpose-built security model.

In data-vault terms, the heuristic classification of this object is hub-leaning. FND_FLEX_VALUE_RULES behaves like a hub: it carries a stable surrogate key (FLEX_VALUE_RULE_ID) and is referenced by several dependent tables. Descriptive attributes attached to a rule, plus translations and line memberships, are carried in satellite- or link-style child tables, so this table is best modelled as the business core of the value-security domain.

Key Information Stored

The table is physically documented with 11 columns. The most significant are:

• FLEX_VALUE_RULE_ID — surrogate primary key (FND_FLEX_VALUE_RULES_PK) and the value propagated to every child table.
• FLEX_VALUE_RULE_NAME — user-visible rule name; part of the business-key candidate FND_FLEX_VALUE_RULES_U2.
• FLEX_VALUE_SET_ID — foreign key to FND_FLEX_VALUE_SETS; identifies the value set the rule secures.
• PARENT_FLEX_VALUE_LOW — low end of the parent value range governed by the rule; also a member of FND_FLEX_VALUE_RULES_U2.
• PARENT_FLEX_VALUE_HIGH — high end of the parent value range.
• ZD_EDITION_NAME — edition discriminator used by Oracle’s data-model editioning; present in both unique indexes (U1 and U2).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns supporting change tracking and reconciliation.

Two unique indexes serve as business-key candidates: FND_FLEX_VALUE_RULES_U1 (FLEX_VALUE_RULE_ID, ZD_EDITION_NAME) and FND_FLEX_VALUE_RULES_U2 (FLEX_VALUE_RULE_NAME, FLEX_VALUE_SET_ID, PARENT_FLEX_VALUE_LOW, ZD_EDITION_NAME). The unique combination of name, value set and parent low value confirms that a rule is uniquely identified within its secured value set.

Common Use Cases and Queries

Typical scenarios include auditing which rules secure a given value set, tracing which users or responsibilities inherit a rule, and validating that value ranges do not overlap. A frequently used join pattern lists rules alongside their value set:

• SELECT r.FLEX_VALUE_RULE_ID, r.FLEX_VALUE_RULE_NAME, r.FLEX_VALUE_SET_ID, s.FLEX_VALUE_SET_NAME FROM FND_FLEX_VALUE_RULES r, FND_FLEX_VALUE_SETS s WHERE r.FLEX_VALUE_SET_ID = s.FLEX_VALUE_SET_ID;
• Rule memberships are expanded through FND_FLEX_VALUE_RULE_LINES, joined on FLEX_VALUE_RULE_ID, to return the individual include/exclude value ranges.
• Assignment of rules to users or responsibilities is obtained via FND_FLEX_VALUE_RULE_USAGES, again joined on FLEX_VALUE_RULE_ID.
• Multilingual names and descriptions are retrieved from FND_FLEX_VALUE_RULES_TL, joined on FLEX_VALUE_RULE_ID, filtered by the session LANGUAGE.

Reporting use cases include security-rule inventories for SOX or internal audit, gap analysis of unprotected value sets, and reconciliation of rule counts by value set and edition.

Related Objects

The most significant related objects, based on documented referential relationships, are:

• FND_FLEX_VALUE_SETS — parent of the foreign key FND_FLEX_VALUE_RULES.FLEX_VALUE_SET_ID; the value set each rule secures.
• FND_FLEX_VALUE_RULES_TL — translation table referencing FLEX_VALUE_RULE_ID.
• FND_FLEX_VALUE_RULE_LINES — line detail (include/exclude ranges) referencing FLEX_VALUE_RULE_ID.
• FND_FLEX_VALUE_RULE_USAGES — usage/assignment records referencing FLEX_VALUE_RULE_ID.

These three referencing tables, together with the value set parent, form the complete value-security model anchored on FND_FLEX_VALUE_RULES.