Search Results eam_safety_usr_def_statuses_tl




Overview
Explore in AI Chat

Overview

EAM_SAFETY_USR_DEF_STATUSES_TL is a translation table in the Oracle E-Business Suite Enterprise Asset Management (EAM) schema. It stores the language-specific, user-visible text for user-defined safety statuses that can be assigned to safety entities within the EAM module. The "_TL" suffix in Oracle EBS naming conventions denotes a translation table, meaning the rows stored here hold the multilingual display strings rather than the base (language-independent) definition. The base definition and the language-independent attributes of each status reside in the companion table EAM_SAFETY_USR_DEF_STATUSES_B, a relationship consistent with the standard Oracle EBS _B / _TL table pair pattern.

Heuristically, the Data Vault classification of this object is satellite-leaning. In Data Vault terms, a translation table behaves like a descriptive satellite attached to the status definition hub: its primary key of (STATUS_ID, LANGUAGE) combines the business key of the parent entity with the language discriminator, and it carries descriptive text attributes rather than introducing new relationships. This classification is a modeling suggestion only and should not be treated as an architectural directive.

Key Information Stored

The table is defined with a composite primary key and two unique business-key candidates. The most significant columns are described below.

  • STATUS_ID — The surrogate and foreign key that identifies the base status record in the parent table. It is part of the primary key and part of both unique indexes.
  • LANGUAGE — The language code for the translated row. It forms the second half of the primary key and the language discriminator in each unique index.
  • USER_DEFINED_STATUS — The user-facing, language-specific description text for the defined status. This is the primary descriptive attribute of the translation row.
  • ENTITY_TYPE — Identifies the type of safety entity to which the status applies. It participates in unique index U2.
  • SOURCE_LANG — The source (base) language from which the translation was derived.
  • ZD_EDITION_NAME — The editioning column supporting Oracle EBS online patching/editioning. It appears in both unique indexes, which is characteristic of the 12.2.x editioning model.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns capturing the last modification audit trail.
  • CREATION_DATE, CREATED_BY — Standard EBS who-columns capturing creation audit information.

The surrogate primary key EAM_SAFETY_USR_DEF_STAT_TL_PK (STATUS_ID, LANGUAGE) and the duplicate extended key EAM_SAFETY_USR_DEF_STA_TL_PK should be distinguished from the business-key candidates: unique index EAM_SAFETY_USR_DEF_STAT_TL_U1 (STATUS_ID, LANGUAGE, ZD_EDITION_NAME) and EAM_SAFETY_USR_DEF_STAT_TL_U2 (ENTITY_TYPE, USER_DEFINED_STATUS, LANGUAGE, ZD_EDITION_NAME). The U2 index additionally enforces uniqueness across the entity type and the translated status text.

Common Use Cases and Queries

Typical usage resolves the translated status text for a given language while joining back to the base status definition. A representative pattern:

  • Reporting the human-readable name of each user-defined safety status: SELECT t.STATUS_ID, t.USER_DEFINED_STATUS FROM EAM_SAFETY_USR_DEF_STATUSES_TL t WHERE t.LANGUAGE = USERENV('LANG').
  • Cross-language validation, listing all available translations for a status by filtering on STATUS_ID and enumerating LANGUAGE values.
  • Joining to the parent base table to retrieve non-translated attributes, and joining to EAM_WO_STATUSES_B to reconcile status definitions used across work order and safety flows.
  • Data-quality checks to confirm every base-status row has a corresponding translation row for each active language, which supports multilingual safety reporting and compliance documentation.

Related Objects

The most significant related objects are described below, grounded in the documented foreign key and key relationships.

  • EAM_WO_STATUSES_B — Referenced by the foreign key on STATUS_ID. The translation rows depend on this base status definition table.
  • EAM_SAFETY_USR_DEF_STATUSES_B — The companion base table holding the language-independent status definition; the natural _B/_Tl join partner.
  • EAM_SAFETY_USR_DEF_STAT_TL_PK / EAM_SAFETY_USR_DEF_STA_TL_PK — The primary key constraints enforcing row uniqueness on STATUS_ID and LANGUAGE.
  • EAM_SAFETY_USR_DEF_STAT_TL_U1 / EAM_SAFETY_USR_DEF_STAT_TL_U2 — The unique indexes enforcing business-key and entity-type/status-text uniqueness.
  • EAM_SAFETY_USR_DEF_STATUSES_VL — Where present, the translated view that unions base and translation rows to present a single language-resolved record.