Search Results gmd_test_interval_plans_tl




Overview
Explore in AI Chat

Overview

GMD_TEST_INTERVAL_PLANS_TL is the translation (language-specific) table for test interval plans within the Oracle EBS Process Manufacturing Product Development module (GMD). It stores the language-dependent descriptive attributes of test interval plans, which define recurring quality or stability testing schedules applied to products or batches in process manufacturing environments. The base language-independent attributes reside in the companion table GMD_TEST_INTERVAL_PLANS_B, while this _TL table holds translated text keyed by language.

The ETRM metadata classifies this object heuristically as standalone from a Data Vault perspective. This is a modeling suggestion indicating that the table does not exhibit strong FK-driven hub or link characteristics; it functions effectively as a descriptive satellite attached to the underlying test interval plan entity, keyed by the plan identifier and language code. The object is documented as VALID and is owned by the GMD schema.

Key Information Stored

The table contains nine documented columns. The most important are:

  • TEST_INTERVAL_PLAN_ID — Surrogate identifier for the parent test interval plan. Part of the composite primary key.
  • LANGUAGE — Language code identifying the translation row. The second component of the composite primary key.
  • DESCRIPTION — The translated description of the test interval plan, the primary translated content of this table.
  • SOURCE_LANG — The source language from which the translation was derived, used for multilingual tracking.
  • CREATION_DATE, CREATED_BY — Audit columns capturing row creation metadata.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns recording the most recent modification details.

The composite primary key is enforced by the unique index GMD_TEST_INTRVL_PLANS_TL_PK (TEST_INTERVAL_PLAN_ID, LANGUAGE). This pair also serves as the business-key candidate, uniquely identifying one translation row per plan per language. There is no separate single-column surrogate key; the combination of plan ID and language constitutes the natural unique identifier for the _TL table.

Common Use Cases and Queries

Typical usage involves joining the _TL table to the base table or its view to retrieve plan descriptions in a user's session language. A standard reporting pattern selects translated descriptions filtered by language:

  • Retrieving a plan's description in the current language: SELECT description FROM gmd_test_interval_plans_tl WHERE test_interval_plan_id = :id AND language = USERENV('LANG');
  • Listing all available translations for a plan for multilingual audits: SELECT language, description, source_lang FROM gmd_test_interval_plans_tl WHERE test_interval_plan_id = :id;
  • Verifying completeness of translations by comparing available languages against the FND_LANGUAGES set.

Because TEST_INTERVAL_PLAN_ID and LANGUAGE form the access path, queries should always include both predicates for index efficiency. Reporting tools frequently join this table to the base table on TEST_INTERVAL_PLAN_ID to combine language-independent attributes with translated descriptions.

Related Objects

  • GMD_TEST_INTERVAL_PLANS_B — The base (language-independent) table; joined on TEST_INTERVAL_PLAN_ID.
  • GMD_TEST_INTERVAL_PLANS_VL — The multi-language view combining _B and _TL, commonly queried by forms and reports.
  • FND_LANGUAGES — Provides the LANGUAGE code values.
  • GMD_TEST_INTERVAL_PLANS_TL's PK index GMD_TEST_INTRVL_PLANS_TL_PK — enforces uniqueness of plan/language pairs.
  • Quality specification and testing setup entities in the GMD module that reference test interval plans as part of stability and sample testing workflows.

Because the metadata classifies the object as standalone with no documented foreign keys, joins to parent entities are driven functionally through the TEST_INTERVAL_PLAN_ID rather than by declared FK constraints.