Results for “gmd_routings_tl”

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

Overview

GMD_ROUTINGS_TL is the translation (language-specific) child table for routing headers within the Oracle EBS Process Manufacturing Product Development module (GMD). In Oracle EBS 12.1.1 and 12.2.2, the "_TL" suffix denotes a translation table that stores the multilingual, user-facing descriptive text associated with a base (non-translated) entity. Because routings define the sequence of operations and resources used to manufacture a product, the descriptive text on a routing header frequently needs to be presented in the operator's or planner's own language. This table supplies that localized text without duplicating the operational routing definition itself.

The base routing header resides in GMD_ROUTINGS_B (the "_B" table holds language-independent attributes), while GMD_ROUTINGS_TL holds the translated description keyed by routing and language. The ETRM metadata classifies this object heuristically under the Data Vault model as standalone. In Data Vault terms it behaves as a satellite-like translation structure attached to the GMD_ROUTINGS_B hub, since it carries descriptive, language-dependent attributes keyed to the routing surrogate. It does not itself act as a hub or link; it is a dependent descriptive store. This classification should be treated as a modeling suggestion rather than a mandatory design.

Key Information Stored

The table contains nine documented columns in the 12.2.2 physical schema. The most significant are:

• ROUTING_ID — The surrogate foreign key linking back to the base routing header in GMD_ROUTINGS_B. It forms part of the composite primary key.
• LANGUAGE — The language code identifying the locale of the translated text. Together with ROUTING_ID it constitutes the composite primary key.
• SOURCE_LANG — The source language from which the translation originated, used for translation management and the "language of the source record" convention.
• ROUTING_DESC — The translated description text of the routing header. This is the primary business payload of the row (documented internally as ROUTING_DESC#1).
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO audit columns recording the most recent modification.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update.

The documented primary key is GMD_ROUTING_TL_PK, defined on (ROUTING_ID, LANGUAGE). This same constraint is the sole unique index identified, making the (ROUTING_ID, LANGUAGE) pair the business-key candidate. There is no separate single-column ROUTING_DESC column name beyond the ROUTING_DESC#1 designation reported in the metadata.

Common Use Cases and Queries

Typical usage centers on retrieving or reporting the localized routing description. A common query joins the translation to the base header, filtering to a specific language:

• Reporting the routing description in a chosen locale for a work-order or recipe document.
• Listing all languages for which a routing header has been translated.
• Identifying routing headers that lack a translation in a required language (missing-translation audits).

A representative pattern is: SELECT b.routing_id, t.routing_desc FROM gmd_routings_b b, gmd_routings_tl t WHERE b.routing_id = t.routing_id AND t.language = :lang. To detect gaps, an outer join from GMD_ROUTINGS_B with the LANGUAGE predicate in the WHERE clause yields the untranslated set. Multi-language reporting uses the LANGUAGE column directly rather than relying on session NLS settings, which is the recommended practice for translation tables.

Related Objects

• GMD_ROUTINGS_B — The base routing header table; joined on ROUTING_ID. This is the parent entity of the translation.
• GMD_ROUTING_TL_PK — The primary key constraint enforcing uniqueness on (ROUTING_ID, LANGUAGE).
• GMD_ROUTINGS_VL — The translated view layer that typically unions GMD_ROUTINGS_B and GMD_ROUTINGS_TL for user-facing inquiry.
• GMD_ROUTING_HEADERS — Related routing header definition objects depending on the routing identifier.
• GMD_OPERATIONS / GMD_ROUTING_OPERATIONS — Operation-level data that reference the routing, providing the operational context for the described header.
• FND_LANGUAGES — Reference table for validating the LANGUAGE and SOURCE_LANG values.

Because the object is classified as standalone in the mined relationship data, no additional foreign-key dependencies are documented beyond the ROUTING_ID association to the base routing header.