Search Results fnd_oam_mets_tl_u1

Overview

APPLSYS.FND_OAM_METS_TL is the translation (TL) table for Oracle E-Business Suite's OAM (Oracle Applications Manager) Dashboard Metrics. It stores the language-specific display names and textual descriptions associated with each metric defined in the base OAM metrics repository. In Oracle EBS 12.1.1 and 12.2.2, this table supports the multilingual rendering of the OAM Dashboard, allowing administrators and end users to view metric labels and help text in their configured session language rather than a single base language.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, with no foreign key dependencies on other database objects. The heuristic classification suggests treating it as a satellite-style descriptive table: the metric identifier and language together identify the parent context, while the display name, description, and audit columns represent the descriptive payload. This aligns with the standard EBS pattern in which a base table holds language-independent attributes and a companion _TL table holds translatable text.

Key Information Stored

The table's structure reflects a classic EBS translation design. The most significant columns are:

• METRIC_SHORT_NAME (VARCHAR2(30)) — the internal, language-independent identifier for the metric. This is the business key that links back to the base metrics definition.
• LANGUAGE (VARCHAR2) — the language code in which the following descriptive fields are stored.
• METRIC_DISPLAY_NAME (VARCHAR2(256)) — the user-facing label for the metric, rendered on dashboards and reports.
• DESCRIPTION (VARCHAR2(1024)) — a short explanatory description of what the metric measures.
• SOURCE_LANG (VARCHAR2) — identifies the source language from which the translation originates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns providing audit traceability.
• ZD_EDITION_NAME — the editioning column introduced in 12.2 to support Online Patching (Edition-Based Redefinition), permitting multiple editions of the row to coexist during patching cycles.

The documented dependent key is FND_OAM_METS_TL_PK1 on (METRIC_SHORT_NAME, LANGUAGE). Two unique indexes are documented: FND_OAM_METS_TL_U1, which the user searched for, and a second unique index that extends the key with ZD_EDITION_NAME. In 12.2.2 the edition-aware unique index (METRIC_SHORT_NAME, LANGUAGE, ZD_EDITION_NAME) is the operative business-key candidate, ensuring that within any given edition a metric-language pair is unique. The ETRM 12.1.1 documentation lists only METRIC_SHORT_NAME and LANGUAGE for FND_OAM_METS_TL_U1, reflecting the pre-editioning schema.

Common Use Cases and Queries

Typical usage centers on retrieving localized metric labels for dashboards, OAM reports, and custom monitoring pages. A common query joins the base metric table to this translation table filtered by the session language:

• Look up the display name for a specific metric in a specific language: SELECT METRIC_DISPLAY_NAME, DESCRIPTION FROM APPLSYS.FND_OAM_METS_TL WHERE METRIC_SHORT_NAME = :metric AND LANGUAGE = USERENV('LANG');
• Audit which metrics have translations in a given language, or identify gaps where no translated row exists.
• Verify the uniqueness enforced by FND_OAM_METS_TL_U1 when diagnosing duplicate or missing label issues on the OAM Dashboard.
• In 12.2, filter by ZD_EDITION_NAME to confirm the correct edition row is returned during patching.

Related Objects

The metadata records that FND_OAM_METS_TL does not reference any other database objects, but it is referenced by the synonym or view APPS.FND_OAM_METS_TL. The primary logical relationship is to the base metrics definition table (FND_OAM_METS), joined on METRIC_SHORT_NAME, where language-independent metric attributes reside. Related OAM objects include the dashboard registration and metric history structures that consume the same metric identifiers. Because the table is standalone at the database level, joins are enforced logically through METRIC_SHORT_NAME rather than by declared foreign keys.