Results for “mtl_mvt_stats_rule_sets_b”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MTL_MVT_STATS_RULE_SETS_B is an Inventory (INV) module base table that stores rule set definitions used by Oracle's Movement Statistics feature to validate movement transactions. Movement Statistics captures physical movements of goods across organization boundaries for statistical and regulatory reporting purposes. Each rule set groups one or more validation rules that determine whether a movement transaction is acceptable — for example, enforcing that required attributes are populated, or that a valid alternate unit of measure has been supplied before a movement is recorded.
The table functions as the header-level definition of a rule set, referencing the individual rules in MTL_MVT_STATS_RULES and the translated descriptive text in MTL_MVT_STATS_RULE_SETS_TL. It is also the target of attribute-level and alternate UOM-level rule set assignments defined on MTL_STAT_TYPE_USAGES.
From a Data Vault modeling perspective, the metadata heuristic classifies this object as hub-leaning. The clean single-column primary key on RULE_SET_CODE, together with the absence of a natural composite business key aside from the seeded-flag and category columns, supports treating it as a hub of rule set entities, with the descriptive and audit columns modeled as an attached satellite.
Key Information Stored
The documented 10-column structure separates surrogate identity, business classification, and audit metadata as follows:
- RULE_SET_CODE — The primary key and the principal business identifier. Every rule, usage link, and translation row references this value.
- RULE_SET_TYPE — Classifies the purpose of the rule set (for example, distinguishing attribute validation rule sets from alternate UOM rule sets), which drives how consuming logic in
MTL_STAT_TYPE_USAGESapplies it. - SEEDED_FLAG — Indicates whether the rule set is an Oracle-seeded, out-of-the-box definition or a customer-created one; seeded rows are typically protected from deletion.
- CATEGORY_SET_ID — References an Oracle Inventory category set, allowing rules to be scoped to specific item categories rather than applying globally.
- ZD_EDITION_NAME — The editioning column supporting Oracle's E-Business Suite online patching model. Note the unique index
MTL_MVT_STATS_RULE_SETS_UKis defined on (RULE_SET_CODE,ZD_EDITION_NAME), which is the effective business-key candidate. - CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns recording row creation and last modification.
The intended naming convention is that _B holds language-independent columns while _TL holds translated descriptions, so text such as rule set names resides in the translation table rather than here.
Common Use Cases and Queries
Typical scenarios include reviewing which rule sets are seeded, identifying rule sets assigned to a given statistic type usage, and joining rule sets to their constituent rules for validation auditing.
-- Listing rule sets assigned to usages SELECT u.STAT_TYPE_CODE, u.ATTRIBUTE_RULE_SET_CODE, u.ALT_UOM_RULE_SET_CODE, r.RULE_SET_TYPE, r.SEEDED_FLAG FROM MTL_STAT_TYPE_USAGES u, MTL_MVT_STATS_RULE_SETS_B r WHERE u.ATTRIBUTE_RULE_SET_CODE = r.RULE_SET_CODE OR u.ALT_UOM_RULE_SET_CODE = r.RULE_SET_CODE;
-- Translating rule sets SELECT b.RULE_SET_CODE, t.RULE_SET_NAME, t.DESCRIPTION FROM MTL_MVT_STATS_RULE_SETS_B b, MTL_MVT_STATS_RULE_SETS_TL t WHERE b.RULE_SET_CODE = t.RULE_SET_CODE AND t.LANGUAGE = USERENV('LANG');
Reporting use cases include compliance audits of movement statistics configuration and impact analysis before modifying a seeded rule set.
Related Objects
- MTL_MVT_STATS_RULES — Child table holding individual rules; joined on
RULE_SET_CODE. - MTL_MVT_STATS_RULE_SETS_TL — Translation table providing name and description; joined on
RULE_SET_CODE. - MTL_STAT_TYPE_USAGES — Assigns rule sets to statistic types via
ATTRIBUTE_RULE_SET_CODEandALT_UOM_RULE_SET_CODE.
-
Movement Statistics table to store Rule Sets for validation rules.
-
Movement Statistics table to store Rule Sets for validation rules.
-
Multilingual view for Rule Sets tables.
APPS.MTL_MVT_STATS_RULE_SETS_VL·↳ MTL_MVT_STATS_RULE_SETS_B·↳ MTL_MVT_STATS_RULE_SETS_TL·Explore INV module →
-
Multilingual view for Rule Sets tables.
APPS.MTL_MVT_STATS_RULE_SETS_VL·↳ MTL_MVT_STATS_RULE_SETS_B·↳ MTL_MVT_STATS_RULE_SETS_TL·Explore INV module →
-
This table stores validation rules defined for movement statistics fields that belong to a rule set as defined in MTL_MVT_STATS_RULE_SETS_B table.Each row stores a rule that can determine a valid set of values for a field or an alternate u
-
Stores information which determines the statistical type data for each legal entity.
-
This table stores validation rules defined for movement statistics fields that belong to a rule set as defined in MTL_MVT_STATS_RULE_SETS_B table.Each row stores a rule that can determine a valid set of values for a field or an alternate u
-
Stores information which determines the statistical type data for each legal entity.
-
MTL_MVT_STATS_RULE_SET_TL is the corresponding transalation table for MTL_MVT_STATS_RULE_SET_B.This table contains one entry for every Rule Set Code and Language.Rule Set Code and Language uniquely identify a row.Rule Set Display Name iden
-
MTL_MVT_STATS_RULE_SET_TL is the corresponding transalation table for MTL_MVT_STATS_RULE_SET_B.This table contains one entry for every Rule Set Code and Language.Rule Set Code and Language uniquely identify a row.Rule Set Display Name iden
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1