Search Results eng_subjects_tl_u1

Overview

ENG.ENG_SUBJECTS_TL is the multi-language (MLS) translation table for engineering subjects within the Oracle E-Business Suite ENG schema. It stores the language-specific attributes of subject records, specifically the translated subject name, keyed by subject identifier and language. The table is registered in FND Design Data as ENG.ENG_SUBJECTS_TL and resides in the APPS_TS_SEED tablespace, which is typical for seed and reference data used across multiple EBS modules.

The "_TL" suffix denotes a translation table in Oracle's Multi-Language Support (MLS) architecture. Such tables hold one row per language for a given base entity, allowing application users to view reference data in their session language. The base (non-translated) attributes of a subject are held in the corresponding base table, ENG_SUBJECTS_B or equivalent, while this table carries the descriptive text.

From a Data Vault modeling perspective, the heuristic classification of this object is standalone, indicating that no foreign keys reference other documented tables directly within the mined relationship set. In a dimensional or Data Vault model, ENG_SUBJECTS_TL functions effectively as a language-dependent satellite attached to the subject hub, holding descriptive attributes that vary by language and edition. Because the record set is small and stable, it is often treated as static reference data rather than transactional data.

Key Information Stored

The table contains ten documented columns, of which the most significant are listed below. The composite unique key, backed by index ENG_SUBJECTS_TL_U1, consists of SUBJECT_ID, LANGUAGE, and ZD_EDITION_NAME. This triple defines the business-key candidate and enforces a single translation row per subject per language per edition.

• SUBJECT_ID (NUMBER) — Surrogate/internal identifier for the subject. Part of the unique index and the primary join key to the base subject definition.
• LANGUAGE (VARCHAR2) — The language code for the translation row. Part of the unique index; determines which session language retrieves this record.
• ZD_EDITION_NAME (VARCHAR2, 30) — The edition name used by EBS Edition-Based Redefinition (EBR). Part of the unique index; separates online patching editions at 12.2.x.
• SOURCE_LANG (VARCHAR2) — The base language from which the translation originated.
• SUBJECT_NAME (VARCHAR2, 80) — The translated human-readable name of the subject. This is the primary business-facing attribute.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update provenance and timestamps.

Note that LANGUAGE and ZD_EDITION_NAME are structural components of the key rather than descriptive business data, and SUBJECT_ID is the linking surrogate. SUBJECT_NAME is the only purely descriptive translated column.

Common Use Cases and Queries

The most common requirement is retrieving the correct subject name for the user's session language. A typical query joins the translation table filtered by LANGUAGE and the active EBR edition:

SELECT t.subject_id, t.subject_name
FROM eng.eng_subjects_tl t
WHERE t.language = USERENV('LANG')
  AND t.zd_edition_name = SYS_CONTEXT('USERENV','EBR_EDITION');

Reporting scenarios include producing a multi-language listing of all subjects, comparing translations across languages to identify missing or truncated names, and auditing translation coverage for a given edition. Administrators validating seed data frequently count rows grouped by language to confirm that every subject has a translation in each installed language. Because the table is small and read-mostly, it is commonly referenced in concurrent report definitions and value-set validation queries rather than high-volume transactional workloads.

Related Objects

Relationship metadata indicates that ENG_SUBJECTS_TL is referenced by the view or synonym ENG_SUBJECTS_TL#, the EBR editioned object variant used during online patching. A documented foreign-key relationship links SUBJECT_ID to the table IGS_UC_COM_EBL_SUBJ, which supplies the subject master record the translation describes. The base subject table (without the _TL suffix) complements the translation rows and supplies language-independent attributes. Downstream consumers include engineering and scientific reference data setup forms that display the subject name from this table, plus any FND value sets or lookups built on the ENG_SUBJECTS domain. When tracing subject data lineage, the significant objects are therefore the base ENG_SUBJECTS table, the EBR editioned object ENG_SUBJECTS_TL#, and IGS_UC_COM_EBL_SUBJ as the parent identifier source.