Results for “fnd_flex_value_rules_tl”

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

Overview

FND_FLEX_VALUE_RULES_TL is the translation table for FND_FLEX_VALUE_RULES in Oracle E-Business Suite, owned by the APPLSYS schema and belonging to the FND – Application Object Library product. A flex value rule defines a security rule over key flexfield segment values, determining which value ranges a given responsibility, user, or application may access. The base table FND_FLEX_VALUE_RULES stores the language-independent definition of each rule, while FND_FLEX_VALUE_RULES_TL stores the language-dependent descriptive text. In a multilingual EBS deployment, this separation allows a single rule definition to carry a translated name and description for every installed language.

Under the heuristic Data Vault classification derived from the foreign-key structure, this table is characterized as satellite-leaning. In Data Vault modeling terms, it behaves as a satellite attached to the FND_FLEX_VALUE_RULES hub: the rule identifier is inherited from the parent, and the descriptive attributes vary by language and edition without introducing new business entities. This classification is a modeling suggestion rather than a physical constraint, since the table itself functions as a standard EBS translation (TL) entity.

Key Information Stored

The documented physical schema for release 12.2.2 contains eleven columns. The most significant are listed below.

• FLEX_VALUE_RULE_ID – surrogate identifier inherited from the parent FND_FLEX_VALUE_RULES record; part of the composite primary key and the join column back to the base table.
• LANGUAGE – the NLS language code for the translated row; the second component of the primary key.
• DESCRIPTION – the translated description of the flex value rule, the primary user-facing text stored here.
• SOURCE_LANG – the language in which the row was originally authored, used by the translation synchronization process.
• ZD_EDITION_NAME – editioning column that participates in the unique index FND_FLEX_VALUE_RULES_TL_U1; it supports the adopted "editions" feature of Release 12.2, allowing multiple edition copies of the same row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – the standard EBS "Who" audit columns applied to every row.
• ERROR_MESSAGE – an internal column used by the translation upload and validation utilities.

The primary key is documented as FND_FLEX_VALUE_RULES_TL_PK on (FLEX_VALUE_RULE_ID, LANGUAGE). A second unique index, FND_FLEX_VALUE_RULES_TL_U1, is defined on (FLEX_VALUE_RULE_ID, LANGUAGE, ZD_EDITION_NAME) and represents the business-key candidate once editioning is taken into account. Note that the natural business key of the rule itself resides in the parent table; this table carries only translated attributes.

Common Use Cases and Queries

The most frequent requirement is to report rule descriptions in the session or base language rather than displaying the raw rule identifier. A typical query joins the TL table to the base table and filters by language:

SELECT r.flex_value_rule_id,
       r.flex_value_rule_name,
       tl.description
FROM   fnd_flex_value_rules r,
       fnd_flex_value_rules_tl tl
WHERE  r.flex_value_rule_id = tl.flex_value_rule_id
AND    tl.language = USERENV('LANG');

Because a row exists per installed language, reports that omit the LANGUAGE predicate will return duplicate rule rows. A second common pattern is a translation-gap audit, identifying rules that lack a row for a target language:

SELECT r.flex_value_rule_id, r.flex_value_rule_name
FROM   fnd_flex_value_rules r
WHERE  NOT EXISTS
       (SELECT 1
        FROM   fnd_flex_value_rules_tl tl
        WHERE  tl.flex_value_rule_id = r.flex_value_rule_id
        AND    tl.language = 'FR');

In Release 12.2 environments, queries against seeded or editioned rows should account for ZD_EDITION_NAME to avoid returning stale edition copies. Reporting extracts for security-rule inventories typically select the rule name and translated description alongside the segment-value ranges held in the associated range tables.

Related Objects

• FND_FLEX_VALUE_RULES – the parent base table; joined on FLEX_VALUE_RULE_ID. This is the sole documented foreign key and the source of the rule's language-independent definition.
• FND_FLEX_VALUE_RULE_LINES – stores the include and exclude range lines that make up each rule.
• FND_FLEX_VALUE_RULE_USAGES – records where a rule is assigned, linking rules to responsibilities, users, or applications.
• FND_FLEX_VALUES and FND_FLEX_VALUES_TL – the flexfield values evaluated by the rule ranges; FND_FLEX_VALUES_TL follows the same translation pattern documented here.
• FND_FLEX_VALUE_SETS – defines the value set against which a rule's ranges are validated.
• FND_ID_FLEX_STRUCTURES – identifies the key flexfield structure and owning application for the segments secured by the rule.

These objects together form the flexfield security-rule model: rules are defined in FND_FLEX_VALUE_RULES, translated here, composed of ranges in the rule-lines table, evaluated against flex values, and assigned to users or responsibilities through the usage table.