Search Results fnd_flex_sec_rule_allowed_vals

Overview

FND_FLEX_SEC_RULE_ALLOWED_VALS is a table owned by the APPLSYS schema within the FND - Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a supporting object for Oracle Flexfields security rules, specifically storing the discrete set of flexfield values that are permitted (or denied, depending on rule configuration) under a given value rule definition. This table sits directly beneath the security rule header defined in FND_FLEX_VALUE_RULES, providing the row-level granular allow-list entries that constrain access to Key and Descriptive Flexfield segment values.

From a data modeling perspective, the ETRM heuristic classifies this object as standalone, with a single foreign key relationship pointing to FND_FLEX_VALUE_RULES. As a modeling suggestion, the table behaves as a link-style construct bridging a rule definition to permitted value-set members, though the absence of a second outgoing FK to a value-set-rows table justifies its standalone classification. In a Data Vault model, this payload-heavy association table would more naturally be treated as a link with descriptive attributes.

Key Information Stored

The table contains seven documented columns. The most significant are:

• FLEX_VALUE_RULE_ID — Foreign key referencing FND_FLEX_VALUE_RULES. Identifies the parent security rule to which each permitted value belongs. This is the primary business-key driver.
• FLEX_VALUE_SET_ID — Identifies the value set within which the permitted value resides.
• FLEX_VALUE — The actual low-level segment value string that the rule qualifies for inclusion.
• LAST_UPDATE_DATE — Audit timestamp of the most recent modification.
• LAST_UPDATED_BY — User identifier of the last modifier.
• CREATION_DATE — Audit timestamp for row insertion.
• CREATED_BY — User identifier of the row creator.

The composite (FLEX_VALUE_RULE_ID, FLEX_VALUE_SET_ID, FLEX_VALUE) effectively acts as the business key ensuring uniqueness per rule/value combination. No dedicated surrogate primary key column is documented; the composite governs uniqueness.

Common Use Cases and Queries

Administrators and reporting analysts query this table to audit which flexfield values are explicitly permitted under each security rule, to reconcile rule definitions against value-set membership, and to diagnose user access issues in segment value security. A typical query enumerating permitted values for a given rule follows:

• SELECT rule_id, flex_value_set_id, flex_value FROM fnd_flex_sec_rule_allowed_vals WHERE flex_value_rule_id = :rule_id;
• Join to FND_FLEX_VALUE_RULES to resolve the rule name and owning value set.
• Join to FND_FLEX_VALUES (via FLEX_VALUE and FLEX_VALUE_SET_ID) to retrieve descriptive flexfield value descriptions for reporting.
• Audit queries comparing CREATION_DATE/LAST_UPDATE_DATE across rules to detect recently modified security scope.

Reporting use cases include security post-implementation reviews, segregation-of-duties audits, and reconciliation of allow-list rules against denied-list rules.

Related Objects

The following objects are most significant in relation to this table:

• FND_FLEX_VALUE_RULES — Parent table; join on FLEX_VALUE_RULE_ID = FLEX_VALUE_RULE_ID. Defines the security rule header.
• FND_FLEX_VALUES — Provides descriptive attributes for FLEX_VALUE within FLEX_VALUE_SET_ID.
• FND_FLEX_VALUE_SETS — Resolves the owning value set identified by FLEX_VALUE_SET_ID.
• FND_FLEX_VALUE_RULE_LINES — Sibling rule-detail table for range-based rather than value-based qualifications.
• FND_FLEX_VALIDATION_TABLES — Provides context for value validation logic used by rules.

Together these objects constitute the Flexfield value security subsystem within Application Object Library, with this table supplying the row-level allowed-value payload consumed by the flexfield security engine at runtime.