Results for “gmd_sampling_plans_tl”

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

Overview

GMD_SAMPLING_PLANS_TL is the translation (TL) table for OPM Quality Sampling Plans within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It stores language-specific, translatable descriptive text for sampling plans defined in Oracle Process Manufacturing. In a multi-language EBS deployment, the base table (QA_SAMPLING_PLANS) holds the operational definition of a sampling plan, while GMD_SAMPLING_PLANS_TL holds the language-dependent description rows keyed by both the sampling plan identifier and a language code. This separation follows the standard Oracle EBS MLS (Multi-Language Support) pattern, where translatable attributes are isolated from the base transactional definition to allow independent translation per installed language.

From a data modeling perspective, the ETRM heuristic Data Vault classification for this object is standalone, based on its mined foreign key structure. As a modeling suggestion, this reflects that the table is primarily a language/description attribute carrier tied to a single business parent rather than a junction resolving multiple independent hubs; in Data Vault terms it behaves most like a satellite supplying descriptive context rather than a hub or link.

Key Information Stored

The documented physical schema for release 12.2.2 contains nine columns owned by the GMD schema. The most significant are:

• SAMPLING_PLAN_ID — Surrogate foreign key referencing QA_SAMPLING_PLANS.SAMPLING_PLAN_ID. In combination with LANGUAGE, this forms the effective composite key that uniquely identifies a translation row for a given sampling plan. This column is not the standalone primary key; uniqueness is achieved through the pairing with the language column.
• SAMPLING_PLAN_DESC — The translated description of the sampling plan. This is the primary translatable business attribute and the reason the TL table exists.
• LANGUAGE — The language code identifying which installed EBS language this translation row serves. Combined with SAMPLING_PLAN_ID it constitutes the business/unique key of the table.
• SOURCE_LANG — The source language from which the translation was derived, supporting the MLS language-mapping and audit conventions used across EBS TL tables.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the translation row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the most recent modification timestamp, the updating user, and the login context of the update.

The surrogate/business distinction is important: SAMPLING_PLAN_ID is the referential surrogate tied to the base plan, whereas the true uniqueness constraint is the (SAMPLING_PLAN_ID, LANGUAGE) business key combination.

Common Use Cases and Queries

Typical use cases center on retrieving language-specific descriptions for reporting, exports, and integration extracts. A common pattern joins the TL table to the base plan table:

• Reporting the translated plan description alongside the base sampling plan identifier for a chosen language.
• Auditing which sampling plans have translations for which languages, and identifying plans missing a translation for a target language.
• Comparing SOURCE_LANG against LANGUAGE to track translation provenance.

Illustrative SQL:

• SELECT sp.sampling_plan_id, tl.sampling_plan_desc, tl.language FROM qa_sampling_plans sp, gmd_sampling_plans_tl tl WHERE sp.sampling_plan_id = tl.sampling_plan_id AND tl.language = USERENV('LANG');
• Missing-translation detection: filter base rows where no TL row exists for a given language via an outer join or NOT EXISTS.
• Audit extract selecting LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently retranslated plans.

Related Objects

The documented foreign key relationship defines the primary dependency:

• QA_SAMPLING_PLANS — Referenced by GMD_SAMPLING_PLANS_TL.SAMPLING_PLAN_ID. This is the base (non-translated) sampling plan table and the essential join partner.
• Related Process Manufacturing quality tables within the GMD/QMD family (such as sampling plan associations and quality specification objects) depend on the same SAMPLING_PLAN_ID business identifier and may be joined indirectly through QA_SAMPLING_PLANS.
• The OPM Quality/Product Development APIs and DML operations that maintain sampling plans typically populate this TL row as part of MLS-conformant insert logic keyed by plan and language.

Because the metadata classifies this object as standalone, no additional foreign keys beyond the QA_SAMPLING_PLANS reference are documented. All joins should be driven through SAMPLING_PLAN_ID and, where language filtering matters, through the LANGUAGE column.