Search Results mtl_mvt_stats_rule_pk
Overview
The MTL_MVT_STATS_RULES table is a core data structure within the Oracle E-Business Suite (EBS) Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It functions as the repository for individual validation rules that govern movement statistics data. Movement statistics track the flow of items within an organization, and this table stores the discrete logic rules that define valid sets of values for specific statistics fields or their alternate units of measure. These rules are not standalone; they are grouped into rule sets defined in the related MTL_MVT_STATS_RULE_SETS_B table. The primary role of this table is to enforce data integrity and business logic for inventory movement analytics and reporting.
Key Information Stored
Each row in MTL_MVT_STATS_RULES represents a single validation rule. While the full column list is not detailed in the provided metadata, the structure is defined by its primary and foreign keys. The RULE_NUMBER column serves as the unique identifier for each rule within the table, forming the primary key (MTL_MVT_STATS_RULE_PK). A critical foreign key column is RULE_SET_CODE, which links each rule to its parent rule set in the MTL_MVT_STATS_RULE_SETS_B table. Other columns would typically store the rule's operational data, such as the specific movement statistics field it validates, the operator (e.g., equals, between), and the permissible value or range of values. The table enables the system to determine whether a given piece of movement data is valid according to the configured business policies.
Common Use Cases and Queries
The primary use case is the validation of inventory transaction data for statistical purposes. When movement statistics are generated or reviewed, the application references the rules stored here to ensure data quality. From a reporting and administrative perspective, common queries involve listing all rules within a specific rule set or identifying which rules apply to a particular field. A developer or analyst might use SQL patterns such as:
SELECT * FROM INV.MTL_MVT_STATS_RULES WHERE RULE_SET_CODE = '<SET_CODE>' ORDER BY RULE_NUMBER;
to audit a rule set's configuration. Another typical query joins to the rule sets table to get a comprehensive view:
SELECT r.*, s.RULE_SET_NAME FROM INV.MTL_MVT_STATS_RULES r, INV.MTL_MVT_STATS_RULE_SETS_B s WHERE r.RULE_SET_CODE = s.RULE_SET_CODE;
This is essential for troubleshooting data validation issues or during implementation to verify rule setup.
Related Objects
The MTL_MVT_STATS_RULES table has a direct and documented foreign key relationship with the MTL_MVT_STATS_RULE_SETS_B table. This is a master-detail relationship where the rule set is the master.
- Foreign Key Relationship: The RULE_SET_CODE column in MTL_MVT_STATS_RULES references the corresponding column in MTL_MVT_STATS_RULE_SETS_B. This enforces that every validation rule must belong to a predefined rule set.
-
Table: MTL_MVT_STATS_RULES
12.2.2
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_MVT_STATS_RULES, object_name:MTL_MVT_STATS_RULES, status:VALID, product: INV - Inventory , description: 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 , implementation_dba_data: INV.MTL_MVT_STATS_RULES ,
-
Table: MTL_MVT_STATS_RULES
12.1.1
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_MVT_STATS_RULES, object_name:MTL_MVT_STATS_RULES, status:VALID, product: INV - Inventory , description: 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 , implementation_dba_data: INV.MTL_MVT_STATS_RULES ,
-
eTRM - INV Tables and Views
12.2.2
-
eTRM - INV Tables and Views
12.1.1
-
eTRM - INV Tables and Views
12.1.1
-
eTRM - INV Tables and Views
12.2.2