Results for “lang_id”

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

Overview

MTH_TRANSLATED_MESSAGE is a table owned by the MTH schema, which supports Oracle Manufacturing Operations Center (MOC), a manufacturing intelligence application that ships as part of the Oracle E-Business Suite technology stack. In Oracle EBS 12.1.1 and 12.2.2, the object holds a status of VALID and is documented in ETRM as a repository used to store seeding data for translation. In practical terms, the table acts as a lightweight message catalog: each row associates a language identifier with a message number and the corresponding translated message text. This enables MOC components — dashboards, plant operator screens, and shop-floor reports — to display user-facing strings in the session language without hard-coding text into forms or JSP pages.

From a data modeling perspective, the mined FK structure classifies MTH_TRANSLATED_MESSAGE heuristically as a standalone object within the Data Vault sense. It is best treated as a reference or lookup satellite rather than a transactional hub or link. The table carries no downstream dependents in the documented FK graph, which is consistent with a leaf-level, read-mostly reference data set that is seeded at implementation time and rarely modified afterward.

Key Information Stored

The documented physical schema for 12.2.2 lists only three columns, so the entire business payload of the table is represented here:

• LANG_ID — The language identifier. This is the only documented foreign key, referencing MTH_TRANSLATED_MESSAGE.LANG_ID → AD_PATCH_DRIVER_LANGS. It binds each message to a specific installed language and is the primary partitioning dimension for lookups.
• MSG_NUM — The numeric (or coded) message identifier. Together with LANG_ID this forms the natural business key: a message number is unique within a language. Application code resolves a message by supplying a language and message number.
• MSG_TEXT — The translated message text itself, stored as the displayable string returned to the UI or report layer.

No surrogate primary key column is documented in the ETRM excerpt, and no unique index columns are listed. The LANG_ID + MSG_NUM combination is the practical business-key candidate for uniqueness; DBAs should confirm the actual constraint definition in the target instance before relying on it for merge or upsert logic.

Common Use Cases and Queries

Typical usage centers on message-resolution lookups and translation completeness reporting. A runtime lookup resembles:

• SELECT MSG_TEXT FROM MTH.MTH_TRANSLATED_MESSAGE WHERE LANG_ID = :p_lang AND MSG_NUM = :p_msg_num;
• Translation coverage audit — comparing rows per MSG_NUM across languages to find gaps: SELECT MSG_NUM, COUNT(DISTINCT LANG_ID) FROM MTH.MTH_TRANSLATED_MESSAGE GROUP BY MSG_NUM HAVING COUNT(DISTINCT LANG_ID) < :expected_lang_count;
• Duplicate detection on the business key prior to seeding or patching.
• Extract of all strings for a language for external review by translation vendors.
• Regression comparisons between environments after a patch or upgrade, verifying that seeded text was not overwritten.

Because the table is seeded rather than user-maintained, direct DML is generally discouraged; corrections should be applied through supported patching or the MOC configuration utilities.

Related Objects

The documented relationship set is narrow, reflecting the standalone classification:

• AD_PATCH_DRIVER_LANGS — referenced via MTH_TRANSLATED_MESSAGE.LANG_ID, providing the authoritative list of languages into which messages are seeded. Joining to this table validates that a LANG_ID is properly installed.
• FND_LANGUAGES — the standard EBS language repository; commonly joined on the language code to translate LANG_ID into a readable language name for reports.
• MTH_* application objects — MOC UI and reporting components that consume the resolved MSG_TEXT at runtime. These are consumers rather than FK dependents and therefore do not appear in the mined relationship graph.
• AD_PATCH_DRIVER_* family — related patching/seed driver tables that govern how translation seed rows are delivered and applied.

No child tables reference MTH_TRANSLATED_MESSAGE, confirming its role as a terminal reference object in the MTH schema.