Search Results wms_rules_tl




Overview
Explore in AI Chat

Overview

The WMS_RULES_TL table is a translation table within the Oracle E-Business Suite Warehouse Management (WMS) module. Its primary role is to store multilingual translations for the descriptive, user-facing text associated with warehouse rules defined in the system. These rules govern various warehouse operations such as putaway, picking, and replenishment logic. The table supports the global deployment of Oracle EBS by enabling the presentation of rule names and descriptions in a user's preferred language, as specified by their application session. It is a critical component for maintaining a single, language-independent rule definition in the base table while supporting multiple linguistic representations.

Key Information Stored

The table stores translated text for warehouse rules, keyed by the rule identifier and language. Based on standard Oracle translation table architecture and the provided metadata, its essential columns include:

  • RULE_ID: The unique identifier for the warehouse rule. This column is a foreign key to the WMS_RULES_B base table, linking the translation to the core rule definition.
  • LANGUAGE: The language code (e.g., 'US' for American English, 'ES' for Spanish) for the translated text.
  • SOURCE_LANG: A column typically present in TL tables that indicates the original language in which the record was created.
  • NAME and DESCRIPTION: The most common translatable columns, holding the user-visible name and explanatory text for the rule in the specified language.

The primary key constraint WMS_RULES_TL_PK is defined on the combination of LANGUAGE and RULE_ID, ensuring a unique translation per language for each rule.

Common Use Cases and Queries

This table is primarily accessed by the Oracle application's multilingual engine to display translated content. Common practical scenarios include generating user reports in a specific language or auditing translation coverage. A typical query to retrieve all Spanish translations for active rules would join to the base table.

Sample SQL Pattern:
SELECT b.RULE_ID, tl.NAME, tl.DESCRIPTION, tl.LANGUAGE
FROM WMS.WMS_RULES_B b,
WMS.WMS_RULES_TL tl
WHERE b.RULE_ID = tl.RULE_ID
AND tl.LANGUAGE = 'ES'
AND b.ENABLED_FLAG = 'Y';

For reporting or data fixes, administrators may query for rules missing translations in a target language or directly update the NAME/DESCRIPTION for a specific RULE_ID and LANGUAGE combination, ensuring SOURCE_LANG is correctly maintained.

Related Objects

The WMS_RULES_TL table has a direct, foundational relationship with several key WMS objects.

  • WMS_RULES_B: This is the base table containing the core, language-independent attributes of a warehouse rule. The foreign key from WMS_RULES_TL.RULE_ID to WMS_RULES_B enforces this relationship. All translatable rules must have a corresponding entry here.
  • WMS_RULES_VL: A common view in Oracle EBS that performs a join between the _B and _TL tables to present a complete, language-sensitive record based on the user's session language. This is typically the view used by application forms and standard reports.
  • Rule Definition Forms (FND): The application interfaces for defining and maintaining warehouse rules (such as the Rules Manager) will read from and write to the _TL table via the _VL view or corresponding APIs to manage translations.