Results for “rule_set_description”

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

Overview

MTL_MVT_STATS_RULE_SETS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2, delivered under the INV – Inventory product. Its documented purpose is to expose the Rule Sets tables in a language-aware form, joining the base and translation tables of the movement statistics rule set entity and resolving descriptive attributes according to the session language.

Movement statistics rule sets govern how transaction movement data is grouped, categorised, and reported for statistical reporting (for example, intrastat-style movement reporting). Because rule set names and descriptions are translatable, the descriptive columns are not stored in a single base table; they reside in a translation table keyed by language. The VL view therefore provides the application and any integration layer with a stable, translatable presentation of rule sets, allowing concurrent users in different language environments to see descriptions in their own session language.

The view is central to any reporting or interface logic that needs to list, validate, or resolve movement statistics rule sets by descriptive name rather than by code alone. This is directly relevant to searches on the RULE_SET_DESCRIPTION column, since that column is exposed only through this language-resolved view, not through the underlying base table.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• MTL_MVT_STATS_RULE_SETS_B – the base table holding the language-independent attributes of a rule set, including the primary code, type, category set, seeded flag, and standard WHO audit columns.
• MTL_MVT_STATS_RULE_SETS_TL – the translation table holding the language-dependent display name and description, keyed by rule set code and language.

The join predicate links the two on RULE_SET_CODE, with the translation side restricted by TL.LANGUAGE = USERENV('LANG'). This restriction resolves the translation row to the language of the current database session, so each query returns exactly one row per rule set for the running user. The view selects B.ROWID as ROW_ID, preserving the base table row identifier for the language-independent record and supporting updatable or identifying behaviour against the base record.

Key Columns

• ROW_ID – ROWID of the row in MTL_MVT_STATS_RULE_SETS_B; unique identifier of the underlying base rule set record.
• RULE_SET_CODE – the language-independent unique code of the rule set; the join key between the base and translation tables.
• RULE_SET_DISPLAY_NAME – the translated, user-facing name of the rule set for the session language.
• RULE_SET_DESCRIPTION – the translated description of the rule set; the descriptive attribute most often targeted by ad hoc queries and reporting.
• RULE_SET_TYPE – classification of the rule set, determining the movement statistics context in which the rule set applies.
• CATEGORY_SET_ID – foreign key to the category set associated with the rule set, defining the item category structure used for grouping.
• SEEDED_FLAG – indicates whether the rule set was delivered as seeded Oracle data or created by a user.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical scenarios include listing all rule sets with their translated names for a configuration or setup report, searching for rule sets by description text, and joining rule sets to their category sets for movement statistics analysis. Because the view already resolves the session language, no explicit language predicate is required in the calling SQL.

• Retrieve all rule sets: SELECT rule_set_code, rule_set_display_name, rule_set_description, rule_set_type FROM apps.mtl_mvt_stats_rule_sets_vl ORDER BY rule_set_display_name;
• Search by description: SELECT rule_set_code, rule_set_display_name, rule_set_description FROM apps.mtl_mvt_stats_rule_sets_vl WHERE UPPER(rule_set_description) LIKE '%MOVEMENT%';
• Identify user-defined rule sets: SELECT rule_set_code, rule_set_display_name FROM apps.mtl_mvt_stats_rule_sets_vl WHERE seeded_flag = 'N';
• Link rule sets to category sets: SELECT v.rule_set_code, v.rule_set_description, c.category_set_name FROM apps.mtl_mvt_stats_rule_sets_vl v, apps.mtl_category_sets_vl c WHERE v.category_set_id = c.category_set_id;

In all cases the results are filtered implicitly to the language of USERENV('LANG'); a row is only returned where a matching translation row exists for that language.