Results for “eam_wo_statuses_tl_u2”

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

Overview

EAM.EAM_WO_STATUSES_TL is the translation-enabled (TL) table that stores the user-facing, language-specific labels for Work Order Statuses in Oracle Enterprise Asset Management (EAM). It is a core reference object within the EAM schema, sitting alongside its base table EAM_WO_STATUSES_B, which holds the language-independent attributes and internal configuration for each status. The "_TL" suffix indicates that this table participates in Oracle's Multi-Language Support (MLS) architecture, where one row exists per installed language for each status record. The table resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, and is registered under FND Design Data as EAM.EAM_WO_STATUSES_TL. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the heuristic Data Vault classification of this object is satellite-leaning. This means the table is best understood as a descriptive satellite attached to the Work Order Status hub represented by the base table's identifier (STATUS_ID). It carries descriptive, translatable attributes rather than relationships or independent business events, so it is not a hub or a link. Analysts building a Data Vault or star-schema layer on top of EAM should treat EAM_WO_STATUSES_TL as a translation attribute satellite joined to the status hub on STATUS_ID and LANGUAGE.

Key Information Stored

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

• STATUS_ID (NUMBER) — the unique identifier for the work order status. Together with LANGUAGE it forms the table's primary key, EAM_WO_STATUSES_TL_PK. This is the surrogate key linking back to the base status record.
• USER_DEFINED_STATUS (VARCHAR2, 80) — the display label (Work Order Status) shown to users in the selected language. This is the primary business-key candidate because it is part of the unique index EAM_WO_STATUSES_TL_U2.
• LANGUAGE (VARCHAR2) — the target language into which the record is translated; the second component of both the primary key and the unique indexes.
• SOURCE_LANG (VARCHAR2) — the source language from which the translation originates, used by MLS tooling to track translation provenance.
• ZD_EDITION_NAME (VARCHAR2, 30) — an editioning column present in 12.2.2 that supports Online Patching (ADOP) edition-based redefinition, allowing multiple editions of the definition to coexist.

The remaining columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — are standard Who columns managed automatically by the EBS framework for audit and concurrency purposes. Two unique indexes are documented: EAM_WO_STATUSES_TL_U1 (STATUS_ID, LANGUAGE, ZD_EDITION_NAME) and EAM_WO_STATUSES_TL_U2 (USER_DEFINED_STATUS, LANGUAGE, ZD_EDITION_NAME), both seeded in APPS_TS_TX_IDX. The second unique index enforces that a given user-defined status label is unique per language, which is the business-key candidate a search for "eam_wo_statuses_tl_u2" typically surfaces.

Common Use Cases and Queries

This table is most often queried to resolve a STATUS_ID to a human-readable status name in a specific language, for reporting, operational dashboards, and Work Order workflow validation. A typical translation lookup joins the TL table to the base or to a Work Order table:

SELECT t.status_id, t.user_defined_status, t.language
FROM eam.eam_wo_statuses_tl t
WHERE t.language = USERENV('LANG')
ORDER BY t.status_id;

Because EAM_WO_STATUSES_TL_U2 enforces uniqueness on (USER_DEFINED_STATUS, LANGUAGE, ZD_EDITION_NAME), a frequent diagnostic is checking whether a proposed custom status name already exists before insertion, or verifying that no duplicate label has been introduced across languages. Administrators also use the table to audit which defined statuses have been translated into which languages by comparing SOURCE_LANG and LANGUAGE values. Multi-org and multi-language reporting extracts rely on this table to present status descriptions alongside work order transaction data.

Related Objects

The table is a dependent reference object; per the documented metadata it references no other database objects, but it is referenced by other EAM entities. The most significant related objects are the base table EAM_WO_STATUSES_B (joined on STATUS_ID), which holds the non-translated status attributes and controls the definitions that this table localizes; the EAM Work Order entity (EAM_WO_HEADERS or the work order interface tables) that carries a STATUS_ID foreign key resolving through to these labels; and the MLS/FND language administration views (FND_LANGUAGES) used to validate the LANGUAGE and SOURCE_LANG values. The intersection view EAM_WO_STATUSES_VL is the standard MLS view that joins the _B and _TL tables for application-layer access, and the seed/index EAM_WO_STATUSES_TL_U2 is the unique constraint most relevant to status-name integrity. The tablespace-level dependencies on APPS_TS_TX_DATA and APPS_TS_TX_IDX complete the documented object footprint. In short, EAM_WO_STATUSES_TL functions as the multilingual descriptive satellite of the EAM work order status definition, and any integration or reporting layer must join it through STATUS_ID and LANGUAGE to recover localized status labels.