Search Results gmd_storage_plans_tl




Overview
Explore in AI Chat

Overview

GMD_STORAGE_PLANS_TL is the translation table for Stability Study Storage Plans within the Oracle EBS Process Manufacturing Product Development (GMD) module. In Oracle EBS, multilingual support is implemented through a pair of tables: a base table (GMD_STORAGE_PLANS_B) that holds language-independent attributes, and a translation table (GMD_STORAGE_PLANS_TL) that stores the language-dependent, translatable text attributes for each defined language. As the "_TL" suffix indicates, this table carries the descriptive content that must be presented in the user's session language, while the base table carries the structural and operational data.

The table resides in the GMD schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to hold the translated descriptive text associated with stability study storage plans. From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. This classification should be treated as a modeling suggestion: because the table is a pure translation satellite keyed by both its parent identifier and a language code, it functions conceptually as a descriptive satellite hanging off the storage plan hub, without participating in many-to-many link structures of its own.

Key Information Stored

The documented physical schema contains nine columns. The most significant are described below, with primary key and business-key roles distinguished per the ETRM metadata.

  • STORAGE_PLAN_ID — The identifier of the parent storage plan. Together with LANGUAGE it forms the composite primary key GMD_STORAGE_PLANS_TL_PK.
  • LANGUAGE — The language code identifying the translation. This is the second component of the composite primary key and the discriminator that makes this a translation table.
  • DESCRIPTION — The translated descriptive text for the storage plan, the principal language-dependent payload of the row.
  • SOURCE_LANG — The source language from which the translation was derived, supporting multilingual content management and the standard EBS translation workflow.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the translation row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification context.

The composite unique index GMD_STORAGE_PLANS_TL_PK on (STORAGE_PLAN_ID, LANGUAGE) is the documented business-key candidate, guaranteeing one translation row per storage plan per language. STORAGE_PLAN_ID is a foreign-key-style reference to the base table, while LANGUAGE is a business discriminator rather than a surrogate. There is no single-column surrogate key; the composite key serves both identity and uniqueness.

Common Use Cases and Queries

The predominant use case is retrieving the correctly translated description for a storage plan in the user's session language, falling back to the base language when no translation exists. Reporting queries typically join this table to the base table on STORAGE_PLAN_ID and filter by LANGUAGE.

SELECT b.storage_plan_id,
       t.description
FROM   gmd_storage_plans_b b,
       gmd_storage_plans_tl t
WHERE  b.storage_plan_id = t.storage_plan_id
AND    t.language = USERENV('LANG');

Multilingual audits frequently count the number of translations per plan to detect missing or incomplete translations, using a GROUP BY on STORAGE_PLAN_ID with HAVING COUNT(*) comparisons against the number of installed languages. Data-conversion and migration scripts insert rows here after creating the base record, populating SOURCE_LANG and DESCRIPTION while stamping the audit columns. Administrators diagnosing display issues inspect this table to confirm whether a translation exists for a given language before escalating to the base table.

Related Objects

The following objects are most significant in relation to this translation table. Join columns are stated where documented.

  • GMD_STORAGE_PLANS_B — The base (language-independent) storage plan table. Joined on STORAGE_PLAN_ID; it is the parent of every translation row.
  • GMD_STORAGE_PLANS_TL_PK — The composite primary key index on (STORAGE_PLAN_ID, LANGUAGE) enforcing uniqueness.
  • GMD_STORAGE_PLANS_VL / _V — The standard multilingual views that union base and translation content, presenting a single logical row per plan in the session language; they reference this table internally.
  • FND_LANGUAGES — The language definition table against which the LANGUAGE column is conceptually validated to determine installed and enabled languages.
  • Stability study and storage condition configuration tables — Storage plans are consumed by stability study setup, so dependent configuration objects reference the plan through STORAGE_PLAN_ID when describing storage conditions in the user's language.

Because the ETRM metadata classifies this object as standalone, no additional foreign-key relationships are documented beyond the implicit parent linkage to the base plan table.