Search Results eng_change_order_types_tl_n1

Overview

The ENG.ENG_CHANGE_ORDER_TYPES_TL table is the multi-language (MLS) translation table for Engineering Change Order (ECO) types in Oracle E-Business Suite. It stores the language-dependent attributes of each change order type, including translated type names, descriptions, and tab text, for every installed or licensed language in the EBS instance. The base table, ENG.ENG_CHANGE_ORDER_TYPES, holds the language-independent definition, while this companion table supplies the displayable text rendered to users according to their session language.

Change order types are the classification mechanism that Oracle Engineering uses to group ECOs and control access to engineering items and engineering bills of material. Because ECO types are seeded reference data, the table resides in the APPS_TS_SEED tablespace, which is consistent with its role as a low-volume, high-stability configuration object rather than a transactional one.

From a data modeling perspective, the documented foreign key from CHANGE_ORDER_TYPE_ID to ENG_CHANGE_ORDER_TYPES classifies this object heuristically as a satellite. The parent change order type identifier represents the business hub/key, and this table carries the descriptive, language-dependent attributes that qualify it. It is worth noting that this classification is a modeling suggestion inferred from FK structure rather than a declared Data Vault design.

Key Information Stored

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

• CHANGE_ORDER_TYPE_ID — the internal numeric identifier of the change order type; the foreign key to ENG_CHANGE_ORDER_TYPES and the primary component of the unique key.
• LANGUAGE — the NLS language code for the translation row.
• SOURCE_LANG — the base (source) language of the seed data, used by the MLS framework to track translation origin.
• ZD_EDITION_NAME — the editioning discriminator used in EBS 12.2 online patching; participates in the unique key.
• TYPE_NAME — the translated name of the change order type (up to 80 characters); indexed and commonly used for lookups.
• DESCRIPTION — the translated long description (up to 240 characters).
• TAB_TEXT — the translated label used for tab-style navigation or display groupings (up to 80 characters).
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The surrogate identifier for a row is CHANGE_ORDER_TYPE_ID combined with LANGUAGE; the unique index ENG_CHANGE_ORDER_TYPES_TL_U1 enforces uniqueness across CHANGE_ORDER_TYPE_ID, LANGUAGE, and ZD_EDITION_NAME, effectively defining the business key. A non-unique index, ENG_CHANGE_ORDER_TYPES_TL_N1, supports searches by TYPE_NAME and LANGUAGE.

Common Use Cases and Queries

Typical uses include LOV lookups for ECO type selection, reporting on the set of configured change types and their translations, and verification of MLS seed data consistency after patching or upgrades. When querying, the current session language should generally be supplied to retrieve the correct translated row; falling back to the source language handles missing translations.

• Retrieve the translated name for a known type: query by CHANGE_ORDER_TYPE_ID and LANGUAGE.
• List all types in a given language: filter on LANGUAGE and order by TYPE_NAME.
• Audit translations: join to ENG_CHANGE_ORDER_TYPES_TL grouped by CHANGE_ORDER_TYPE_ID to identify missing languages.
• Compare source and translated text: compare SOURCE_LANG rows with target-language rows.

A representative join is:

SELECT t.TYPE_NAME, t.DESCRIPTION
FROM   ENG.ENG_CHANGE_ORDER_TYPES_TL t
WHERE  t.CHANGE_ORDER_TYPE_ID = :type_id
AND    t.LANGUAGE = USERENV('LANG');

Because the table is keyed by CHANGE_ORDER_TYPE_ID, reports joining to ENG_CHANGE_ORDER_TYPES should always include the LANGUAGE predicate to prevent row multiplication across languages.

Related Objects

• ENG.ENG_CHANGE_ORDER_TYPES — the base table; joined on CHANGE_ORDER_TYPE_ID. This is the primary parent.
• ENG.ENG_CHANGE_ORDER_TYPES_TL# — the editioning companion object used in 12.2 online patching operations.
• Engineering ECO transaction tables (such as ENG_ECN and related change order headers) that carry CHANGE_ORDER_TYPE_ID as a classifying attribute.
• Engineering item and BOM access-control objects that resolve permissions by change order type.
• MLS translation utilities and the FND language tables used to resolve LANGUAGE codes.

The dominant dependency remains the parent ENG_CHANGE_ORDER_TYPES table via the documented foreign key on CHANGE_ORDER_TYPE_ID.