Search Results eng_change_order_types_tl




Overview

ENG_CHANGE_ORDER_TYPES_TL is the translation (Multi-Language Support, MLS) table for Engineering Change Order types in Oracle E-Business Suite. It is owned by the ENG schema and is available in both 12.1.1 and 12.2.2. The base (non-translated) definition of each change order type resides in ENG_CHANGE_ORDER_TYPES, while this table stores the language-specific presentation attributes — the type name, description, and tab text rendered to users in their session language. In the Engineering module, change order types classify ECOs (Engineering Change Orders) for numbering, workflow, approval routing, and reporting, so the translated labels defined here drive what end users actually see on ECO entry and query screens.

The ETRM metadata classifies this object heuristically as standalone in Data Vault terms. In practice it behaves as a satellite: its grain is one row per change order type per language, it carries descriptive attributes (TYPE_NAME, DESCRIPTION, TAB_TEXT) rather than relationships, and it is anchored to the parent entity through CHANGE_ORDER_TYPE_ID. The single foreign key to ENG_CHANGE_ORDER_TYPES confirms this dependent, descriptive role.

Key Information Stored

The table contains 12 documented columns. The most significant are:

  • CHANGE_ORDER_TYPE_ID — surrogate identifier of the change order type; part of the foreign key to ENG_CHANGE_ORDER_TYPES and the leading column of the unique index. It is the join key back to the base table.
  • LANGUAGE — the NLS language code for the row (for example, US for English). Part of the composite business key; determines which translation is returned.
  • ZD_EDITION_NAME — the editioning column introduced with the 12.2 online patching architecture. It is part of the unique index and identifies the edition under which the row is visible. In 12.1.1 this column does not exist, so queries must be edition-aware only on 12.2.x.
  • TYPE_NAME — the translated change order type name displayed to users.
  • DESCRIPTION — the translated long description of the change order type.
  • TAB_TEXT — the translated tab label used on ECO entry forms.
  • SOURCE_LANG — the language from which the row was originally created, used by the translation (XLIFF) tooling.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The documented unique index ENG_CHANGE_ORDER_TYPES_TL_U1 on (CHANGE_ORDER_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) is the business-key candidate. The surrogate primary key is CHANGE_ORDER_TYPE_ID combined with LANGUAGE; ZD_EDITION_NAME is an EBS 12.2 infrastructural qualifier.

Common Use Cases and Queries

Typical reporting joins this table to its base table using the NLS view, which automatically filters to the session language. For example, to list change order types in English:

  • SELECT b.change_order_type_id, t.type_name, t.description FROM eng_change_order_types b, eng_change_order_types_tl t WHERE b.change_order_type_id = t.change_order_type_id AND t.language = USERENV('LANG');

Common scenarios include: populating LOVs on ECO entry forms, building multilingual reporting extracts, verifying translation completeness across LANGUAGES, and diagnosing missing tab or type labels after a patch. On 12.2.x, queries should reference the edition-aware synonym or use the NLS view so that ZD_EDITION_NAME resolution is handled by the editioning infrastructure rather than being hard-coded. Because this table is descriptive only, it is safe to query for read-only reporting without impacting the change order transaction tables.

Related Objects

  • ENG_CHANGE_ORDER_TYPES — the base table; joined on CHANGE_ORDER_TYPE_ID. It holds the language-independent attributes and the documented foreign key target.
  • ENG_CHANGE_ORDER_TYPES_VL / NLS view — the MLS view that joins base and translated rows, filtering by session language; the recommended query interface.
  • ENG_ECO_DEFINITION_TL and related ECO tables — definitional tables that reference change order types when numbering or routing ECOs.
  • FND_LANGUAGES — provides valid LANGUAGE codes and their installed/translated status.
  • FND_TERRITORIES / FND_LANGUAGE — supplementary NLS reference objects for language lookup.
  • XLIFF translation tooling — uses SOURCE_LANG and the composite key to manage translation upload/download.

Because the table is classified as standalone/satellite, the set of related objects is intentionally narrow: the dominant dependency is the parent ENG_CHANGE_ORDER_TYPES table via CHANGE_ORDER_TYPE_ID, with the NLS views providing the practical join layer for application and reporting use.