Search Results fnd_flex_val_rule_stats_pk

Overview

FND_FLEX_VALIDATION_RULE_STATS is an APPLSYS-owned table in the Oracle E-Business Suite FND (Application Object Library) product. It stores aggregate statistics describing the number of key flexfield cross-validation rules defined against a given key flexfield structure. Cross-validation rules constrain the combinations of segment values that a user may enter when building a key flexfield combination, and this table summarizes how many such rules exist for each structure.

The table is scoped by three identifying columns — APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM — which together identify a specific key flexfield structure. A fourth column, ZD_EDITION_NAME, participates in the unique index and supports edition-based online patching introduced in EBS 12.2. Because the table holds derived counts keyed to a parent structure rather than serving as an independent business entity, the mined Data Vault classification is satellite-leaning; in a Data Vault model it is best treated as a satellite attached to the key flexfield structure hub.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

• APPLICATION_ID — identifies the application that owns the key flexfield.
• ID_FLEX_CODE — the short code of the key flexfield (for example, GL#).
• ID_FLEX_NUM — the structure number of the key flexfield.
• RULE_COUNT — the number of cross-validation rules defined for the structure.
• INCLUDE_LINE_COUNT — the count of include lines across those rules.
• EXCLUDE_LINE_COUNT — the count of exclude lines across those rules.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who last changed the row and when.
• CREATION_DATE, CREATED_BY — standard creation audit columns.
• ZD_EDITION_NAME — the edition identifier supporting EBS 12.2 online patching.

The primary key is FND_FLEX_VAL_RULE_STATS_PK, defined on (APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM). The unique index FND_FLEX_VAL_RULE_STATS_U1 extends that business key with ZD_EDITION_NAME, confirming that a structure may carry one statistics row per edition. The primary key is therefore both the physical surrogate and the natural business key; there is no separate meaningless surrogate column.

Common Use Cases and Queries

This table supports reporting and diagnostics around key flexfield validation rule volume, without requiring the expensive aggregation of rule and line detail tables. Typical uses include inventorying how many cross-validation rules exist per structure, identifying structures with excessive include or exclude lines, and verifying that rule statistics are consistent after a rule migration or patch.

• Listing rule counts for all General Ledger structures: SELECT id_flex_code, id_flex_num, rule_count FROM fnd_flex_validation_rule_stats WHERE id_flex_code = 'GL#';
• Identifying structures with the highest rule complexity: SELECT * FROM fnd_flex_validation_rule_stats ORDER BY rule_count DESC, include_line_count DESC;
• Joining to the structure definition for descriptive names: SELECT v.*, s.id_flex_structure_name FROM fnd_flex_validation_rule_stats v, fnd_id_flex_structures s WHERE v.application_id = s.application_id AND v.id_flex_code = s.id_flex_code AND v.id_flex_num = s.id_flex_num;

Related Objects

The dominant relationship is the foreign key from this table's (APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM) to FND_ID_FLEX_STRUCTURES, which defines every key flexfield structure. Other significant objects in the surrounding model include FND_FLEX_VALIDATION_RULES, FND_FLEX_VALIDATION_RULE_LINES, and FND_FLEX_VALIDATION_RULE_SETS, which hold the rule and line detail summarized here; FND_ID_FLEX_SEGMENTS and FND_FLEX_VALUES / FND_FLEX_VALUE_SETS, which define the segments and values validated by those rules; and the Application Object Library concurrent programs and forms used to define and maintain cross-validation rules.