Search Results routing_class_desc

Overview

GMD_ROUTING_CLASS_VL is a seeded APPS view within the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. It serves as the user-facing, language-aware presentation layer for routing classes, which are the classification entities used to group and organize routings in process manufacturing environments. The view consolidates the base (non-translated) attributes of a routing class with its translated description, exposing a single logical record per routing class for the session's active language.

In 12.1.1 and 12.2.2 the view is delivered with a VALID status and is a standard component of the Process Manufacturing Product Development schema. Its practical role is to bridge the technical base table, which holds language-independent data such as units of measure and audit columns, with the translation table that stores the descriptive text used on forms and reports. Because it resolves the translated description automatically via the session language, it is a preferred data source for reports, concurrent programs, and integration interfaces that must present routing class information in the user's language without performing their own translation joins.

Underlying Base Objects

The view is defined over two synonym-referenced base tables: GMD_ROUTING_CLASS_B and GMD_ROUTING_CLASS_TL. The "_B" suffix denotes the base table, which stores language-independent routing class data, including the primary routing class identifier, unit of measure attributes, and standard WHO audit columns. The "_TL" suffix denotes the translation table, which stores language-specific descriptive text keyed by routing class and language.

The join condition links the two tables on the ROUTING_CLASS column, guaranteeing that every returned row carries the correct translated description. The translation side is additionally filtered by the condition T.LANGUAGE = USERENV('LANG'), which restricts the result set to the language of the current database session. This mechanism is characteristic of Oracle's MLS (Multi-Language Support) design, in which the "_VL" view is expected to return exactly one row per entity for the active language. The view text also selects B.ROWID, exposing a row identifier from the base table for downstream update or reference processing.

Key Columns

• ROUTING_CLASS: The primary identifier and business key of the routing class; the join column between the base and translation tables.
• ROUTING_CLASS_DESC: The translated description of the routing class, retrieved from GMD_ROUTING_CLASS_TL for the session language. This is the column most commonly sought in reporting queries, including searches on "routing_class_desc".
• TEXT_CODE: The text code associated with the routing class, used for code-based lookups and reference.
• UOM and ROUTING_CLASS_UOM: Unit of measure attributes defined for the routing class, governing how quantities associated with the class are expressed.
• ROW_ID: The ROWID of the base table row, used as a unique row identifier within the view.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO audit tracking inherited from the base table.
• TRANS_CNT and DELETE_MARK: Internal Oracle columns supporting translation/migration counters and logical deletion respectively; these are not intended for end-user reporting.

Common Use Cases and Queries

The view is typically queried to retrieve a routing class description for display or for joining to routing-related entities. A straightforward lookup by routing class is the most frequent pattern:

• SELECT routing_class, routing_class_desc FROM apps.gmd_routing_class_vl WHERE routing_class = :p_routing_class;
• SELECT routing_class, routing_class_desc FROM apps.gmd_routing_class_vl ORDER BY routing_class_desc; to produce a language-appropriate list of values.
• Integration and reporting queries often join the view to routing tables using ROUTING_CLASS as the key, relying on ROUTING_CLASS_DESC to label output in the user's language.

Because the view filters on USERENV('LANG'), the description returned reflects the session language; passing a different language requires querying the translation table directly. For listings that must include classes regardless of translation availability, a LEFT OUTER JOIN to GMD_ROUTING_CLASS_TL is preferred over the view, since the view's inner join excludes base rows lacking a translation for the active language.