Search Results mtl_mvt_stats_rule_sets_tl




Overview
Explore in AI Chat

Overview

The MTL_MVT_STATS_RULE_SETS_TL table is a core Inventory (INV) module object in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the translation table for its base table, MTL_MVT_STATS_RULE_SETS_B. This design is a standard Oracle Applications pattern for supporting multilingual implementations. The table's primary role is to store language-specific, user-facing text—specifically the display name—for Movement Statistics Rule Sets. These rule sets are configurations used within Inventory to define the criteria for generating movement statistics, which track the flow of items. Each unique combination of a Rule Set Code and a Language is stored as a distinct row, enabling the EBS user interface to present localized terminology based on the user's session language.

Key Information Stored

The table stores translated attributes for movement statistics rule sets. Its structure is defined by a composite primary key and descriptive columns. The most critical columns, as indicated by the metadata, are:

  • RULE_SET_CODE: A foreign key column linking directly to the RULE_SET_CODE in the base table MTL_MVT_STATS_RULE_SETS_B. It identifies the specific rule set being described.
  • LANGUAGE: The language code (e.g., 'US' for American English) for the translation. Together with RULE_SET_CODE, this forms the table's primary key (RULE_SET_PK).
  • RULE_SET_DISPLAY_NAME: The user-facing, translated name for the rule set as it should appear in forms and reports for the specified language.

Standard translation table columns like CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are also present to track data maintenance.

Common Use Cases and Queries

This table is primarily accessed by the Oracle application runtime to display localized content. Common operational and reporting scenarios include generating user interface labels and auditing rule set translations. A typical query retrieves the display name for a specific rule set in the current session language, which is fundamental for any form or report displaying rule set information. For example: SELECT rule_set_display_name FROM inv.mtl_mvt_stats_rule_sets_tl WHERE rule_set_code = '&RULE_SET_CODE' AND language = USERENV('LANG');. Another common use case is administrative reporting to list all available translations for rule sets, aiding in implementation support and gap analysis for new language deployments: SELECT rule_set_code, language, rule_set_display_name FROM inv.mtl_mvt_stats_rule_sets_tl ORDER BY 1, 2;.

Related Objects

MTL_MVT_STATS_RULE_SETS_TL has a direct and essential relationship with its base table. The primary related objects are:

  • MTL_MVT_STATS_RULE_SETS_B: This is the base table that holds the primary, language-independent definition of the movement statistics rule set. The TL table's RULE_SET_CODE is a foreign key referencing this table, establishing a one-to-many relationship where one base rule set can have multiple translated names.
  • Views and APIs: While not specified in the metadata, standard EBS practice dictates that application logic typically accesses this data through published views (which often have a suffix like '_VL' joining the _B and _TL tables) or via public Inventory APIs, rather than through direct table queries, to ensure integrity and support future upgrades.