Results for “rule_set_code”

50+ results




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

Overview

MTL_MVT_STATS_RULES is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual validation rules applied to movement statistics fields. Movement statistics are used to report the movement of goods across borders for statistical and customs purposes, and each rule in this table defines either a valid set of values for a movement statistics field or an alternate value substitution. Rules are organized into rule sets, which are defined in the parent table MTL_MVT_STATS_RULE_SETS_B and referenced here through the RULE_SET_CODE foreign key.

From a dimensional modeling perspective, the documented foreign key structure suggests a satellite-leaning classification. The table carries descriptive and contextual attributes—source type, attribute codes, lookup types, and commodity codes—that qualify and extend the parent rule set entity. In a Data Vault model, this would typically be implemented as a satellite attached to the MTL_MVT_STATS_RULE_SETS_B hub, with RULE_SET_CODE acting as the link to the parent business key. Analysts building a warehouse layer should treat this as descriptive metadata rather than an independent hub.

Key Information Stored

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

  • RULE_NUMBER — The surrogate primary key (MTL_MVT_STATS_RULE_PK) that uniquely identifies each rule row. This is the column most frequently referenced in the user's search.
  • RULE_SET_CODE — The foreign key to MTL_MVT_STATS_RULE_SETS_B, identifying the rule set to which this rule belongs.
  • SOURCE_TYPE — Defines the origin or category of movement statistics data to which the rule applies.
  • ATTRIBUTE_CODE — Identifies the specific movement statistics field or attribute governed by the rule.
  • ATTRIBUTE_PROPERTY_CODE — Specifies the property of the attribute being validated or substituted.
  • ATTRIBUTE_LOOKUP_TYPE — References the Oracle lookup type that supplies the valid value list for the attribute.
  • COMMODITY_CODE — The commodity classification associated with the rule, enabling rules to vary by traded good.
  • ZD_EDITION_NAME — The editioning column used in 12.2.2 online patching (Edition-Based Redefinition) to isolate editions of the data.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns that record who created and last modified each rule and when.

The documented unique index MTL_MVT_STATS_RULES_UK covers (RULE_NUMBER, RULE_SET_CODE, ZD_EDITION_NAME), making these the business-key candidates for uniqueness. RULE_NUMBER is separately designated as the primary key.

Common Use Cases and Queries

Typical use cases include auditing which validation rules exist within a rule set, tracing rules for a specific commodity or attribute, and supporting movement statistics reporting and customs declarations. Reporting queries frequently join this table to its parent and to lookup tables. Representative SQL patterns include:

  • Selecting all rules in a set: SELECT * FROM INV.MTL_MVT_STATS_RULES WHERE RULE_SET_CODE = :rule_set_code;
  • Retrieving a single rule: SELECT * FROM INV.MTL_MVT_STATS_RULES WHERE RULE_NUMBER = :rule_number;
  • Joining to the parent rule set: SELECT r.RULE_NUMBER, r.RULE_SET_CODE, s.RULE_SET_DESCRIPTION FROM INV.MTL_MVT_STATS_RULES r, INV.MTL_MVT_STATS_RULE_SETS_B s WHERE r.RULE_SET_CODE = s.RULE_SET_CODE;

Analysts should always filter on ZD_EDITION_NAME when querying in a 12.2.2 environment to avoid returning rows from multiple editions.

Related Objects

The following objects are most relevant to MTL_MVT_STATS_RULES:

  • MTL_MVT_STATS_RULE_SETS_B — The parent table referenced via RULE_SET_CODE; defines the rule sets that group rules.
  • MTL_MVT_STATS_RULE_SETS_TL — The translation table providing language-specific descriptions of rule sets.
  • FND_LOOKUP_TYPES / FND_LOOKUP_VALUES — Referenced through ATTRIBUTE_LOOKUP_TYPE to resolve valid attribute values.
  • MTL_COMMODITIES_B / related commodity tables — Provide context for COMMODITY_CODE.
  • Movement statistics reporting APIs and concurrent programs in the INV module that consume rule definitions to validate and substitute values during statistics generation.

Together, these objects form the rule-definition layer that supports movement statistics validation and reporting in Oracle EBS Inventory.