Results for “qcassy_typ_id”

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

Overview

GMD_TESTS_TL is a translation (TL) table in the GMD schema, owned by the Oracle Process Manufacturing Product Development module. It stores language-specific descriptive text for quality test definitions used in process manufacturing quality control. Each base record in the associated test entity is represented by one row per installed language, allowing the same test to carry translated descriptions across a multi-language EBS deployment.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This suggests it is best modeled independently — not as a strict hub, link, or satellite — because the documented foreign-key structure does not reveal upstream parent dependencies within the extracted relationship set. Practitioners building a warehouse layer may nonetheless treat the combination of QCASSY_TYP_ID and LANGUAGE as a natural composite business key, with descriptive attributes (such as ASSAY_DESC) behaving like satellite payload columns.

Key Information Stored

The table exposes 10 documented columns. The most significant include:

• QCASSY_TYP_ID — the quality assay (test) type identifier. This is the business-key component that ties the translation row back to its parent test definition, and it participates in the primary key.
• LANGUAGE — the language code for the translated row; the second component of the composite primary key.
• ASSAY_DESC — the translated description of the assay/test, the primary textual payload of this table.
• SOURCE_LANG — indicates the source language from which the translation originated, typically used to identify the base language row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each row and when.
• MIGRATION_STATUS — a status flag often used during data migration or upgrade processes to track record readiness.

The primary key is GMD_TESTS_TL_PK, defined on the composite of QCASSY_TYP_ID and LANGUAGE. Because the surrogate identity is composite rather than a single generated sequence, the business key (QCASSY_TYP_ID + LANGUAGE) effectively serves as the row identifier here; there is no separately documented single-column surrogate key.

Common Use Cases and Queries

This table is queried primarily when rendering test descriptions in a user's session language, joining translations to their base test records. A typical pattern filters to a single language to avoid duplicate rows:

• Retrieve the translated description for a given test: SELECT assay_desc FROM gmd_tests_tl WHERE qcassy_typ_id = :id AND language = USERENV('LANG');
• List all available translations for a test: SELECT language, assay_desc FROM gmd_tests_tl WHERE qcassy_typ_id = :id ORDER BY language;
• Identify untranslated records by comparing against SOURCE_LANG, useful for translation-completeness reporting.
• Audit reporting on recently modified translations using LAST_UPDATE_DATE.

Because the object is a TL table, reports should always constrain LANGUAGE to prevent Cartesian-style duplication when joining to base test tables.

Related Objects

GMD_TESTS_TL relates to the base (non-translated) test entity through the shared QCASSY_TYP_ID business key. Reported join columns and dependencies include:

• GMD_TESTS_B (base table) — joined on QCASSY_TYP_ID, providing language-independent test attributes.
• GMD_QC_ASSYS / assay-type definitions — the underlying test/assay master referenced by QCASSY_TYP_ID.
• FND_LANGUAGES — joined on LANGUAGE to resolve language names for reporting.
• GMD_TESTS_TL_PK — the primary key constraint enforced on (QCASSY_TYP_ID, LANGUAGE).

As the metadata documents a standalone classification, no authoritative foreign-key parents were extracted; joins to base test tables should therefore be validated against the specific GMD schema version in use.