Results for “gmd_spec_tests_tl”

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

Overview

GMD_SPEC_TESTS_TL is the translation table for OPM Specification tests within the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. In EBS 12.1.1 and 12.2.2, Oracle stores translatable descriptive text in paired tables: a base table (GMD_SPEC_TESTS_B) holding language-independent attributes and a "_TL" table holding the language-dependent display text. GMD_SPEC_TESTS_TL holds the multilingual display names of the tests attached to quality specifications, allowing the same specification test to appear in different languages based on the session's language setting. The object is owned by the GMD schema and carries a VALID status in the data dictionary.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone, meaning it participates in no outbound FK relationships within the documented metadata. As a modeling suggestion, a translation table of this kind behaves most like a satellite attached to the specification-test business key, since it carries descriptive, language-qualified attributes (TEST_DISPLAY) that vary by language rather than by transactional event.

Key Information Stored

The table's documented physical schema contains ten columns. The composite primary key, enforced by GMD_SPEC_TESTS_TL_PK, consists of LANGUAGE, SPEC_ID, and TEST_ID. These three columns also form the unique business-key candidate (the unique index is documented as SPEC_ID, TEST_ID, LANGUAGE). SPEC_ID identifies the parent quality specification, TEST_ID identifies the specific test defined against that specification, and LANGUAGE (the ISO language code, typically sourced from the session's NLS_LANG) determines which translation row is returned.

The principal payload column is TEST_DISPLAY, which holds the translated, user-facing name of the specification test. SOURCE_LANG records the original language in which the test display text was authored, which Oracle Translation (XLIFF) workflows use to determine what requires re-translation. The remaining columns are standard "Who" audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Note that this table stores descriptive text only; the numeric test results, units, and validity ranges live in the base test tables, not here.

Common Use Cases and Queries

Typical reporting and integration scenarios include:

• Multilingual test listing: Selecting TEST_DISPLAY for a given language to render specification tests on Quality Management reports or custom OAF pages.
• Translation gap analysis: Finding tests whose SOURCE_LANG differs from a target LANGUAGE, indicating untranslated or stale display text.
• Data validation and migration: Verifying that base test records (from the _B table) have a matching _TL row before loading or interface processing.

A representative query joining the base table to the translation for the current session language:

SELECT b.spec_id, b.test_id, t.test_display
FROM   gmd_spec_tests_b b,
       gmd_spec_tests_tl t
WHERE  b.spec_id = t.spec_id
AND    b.test_id = t.test_id
AND    t.language = USERENV('LANG');

Related Objects

Although the mined metadata classifies this object as standalone, its functional relationships follow the standard OPM translation pattern. The most significant dependents and peers are:

• GMD_SPEC_TESTS_B — the base table; joins on SPEC_ID and TEST_ID.
• GMD_SPEC_TESTS_VL / GMD_SPEC_TESTS_V — the language-aware view typically created over the B/TL pair.
• GMD_SPECIFICATIONS_B / _TL — the parent specification header, joined via SPEC_ID.
• GMD_SPEC_TESTS_TL_PK — the enforcing primary-key constraint/index.
• Translation (XLIFF) extraction processes in the Application Object Library, which read SOURCE_LANG and TEST_DISPLAY.

Because no FK constraints are documented from this object, referential integrity between specification tests and their parent specifications is enforced at the application and package layer rather than by the database.