Search Results routing_class




Overview
Explore in AI Chat

Overview

The GMD_ROUTING_CLASS_TL table is a core translation table within the Oracle E-Business Suite Process Manufacturing (GMD) module, specifically for the Product Development sub-module. It stores language-specific descriptions for routing classes, which are foundational entities used to categorize and define the sequence of operations required to manufacture a product. This table enables the multi-language support (MLS) capability of Oracle EBS, allowing the same routing class to be represented in multiple languages within a single installation. Its primary role is to decouple the base routing class definition from its textual descriptions, facilitating international deployments by providing translated content based on a user's session language.

Key Information Stored

The table's structure is designed to hold translated text linked to a base routing class identifier and a language code. While the full column list is not detailed in the provided metadata, the primary key definition reveals the essential columns. The ROUTING_CLASS column stores the code that uniquely identifies a routing class, serving as the foreign key link to its base definition table (typically GMD_ROUTING_CLASS_B). The LANGUAGE column contains the ISO language code (e.g., 'US' for American English, 'F' for French) that identifies the translation's language. The most critical data column, implied by its function as a translation table, is the DESCRIPTION field, which holds the translated name or description of the routing class for the specified language. Other standard translation table columns, such as SOURCE_LANG and CREATION_DATE, are also typically present.

Common Use Cases and Queries

This table is primarily accessed by the application's MLS engine to display user-interface elements in the correct language. Common scenarios include generating localized reports on manufacturing processes, displaying routing class lists in forms, and supporting data migration for multi-national operations. A typical query to retrieve a translated description for a specific routing class would join this table with its base table, filtered by the user's session language.

  • Sample Query: SELECT rt.description FROM gmd_routing_class_tl rt, gmd_routing_class_b rb WHERE rb.routing_class = rt.routing_class AND rt.language = USERENV('LANG') AND rb.routing_class = :p_class_code;
  • Reporting Use Case: Creating a global process routing report that shows descriptions in both a base language and a target language for review by regional teams.

Related Objects

GMD_ROUTING_CLASS_TL has a direct and dependent relationship with its base table, GMD_ROUTING_CLASS_B, which stores the language-independent attributes of a routing class. The primary key, GMD_ROUTING_CLASS_TL_FK, enforces this relationship. This translation table is also referenced by any application form, report, or view that displays routing class descriptions in a multi-lingual context. Key APIs within the GMD product development suite, particularly those involved in defining and querying routing classes, will internally access this table to retrieve the appropriate translated text based on the session context.