Search Results eam_safety_usr_def_stat_tl_u2

Overview

EAM.EAM_SAFETY_USR_DEF_STATUSES_TL is the translation table for user-defined safety entity statuses within Oracle Enterprise Asset Management (EAM). In Oracle EBS 12.1.1 and 12.2.2, it stores the multilingual (MLS) representation of statuses defined for safety-related entities such as isolation, work clearance, and work permit records. Each row supplies the localized text for a given status in a specific language, enabling organizations operating in multiple locales to present safety workflow status descriptions in the user's preferred language.

The table belongs to the EAM schema and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its primary key, EAM_SAFETY_USR_DEF_STAT_TL_PK, is defined on (STATUS_ID, LANGUAGE). From a Data Vault modeling perspective, the structural metadata suggests this object is satellite-leaning, acting as a descriptive attribute satellite whose parent key is STATUS_ID. It carries no downstream dependencies and references EAM_WO_STATUSES_B via STATUS_ID, positioning it as a language-specific descriptive extension rather than a transactional or relationship entity.

Key Information Stored

The table holds 11 documented columns. The most significant are:

• STATUS_ID — Numeric identifier of the parent status; part of the primary key and foreign key to EAM_WO_STATUSES_B.
• LANGUAGE — The target language code for the translated text; part of the primary key.
• SOURCE_LANG — The language from which the translation was performed, supporting the MLS framework.
• USER_DEFINED_STATUS — The translated Work Order Status text (up to 240 characters).
• ENTITY_TYPE — Discriminator indicating the safety entity category: 1 = Isolation, 2 = Work Clearance, 3 = Work Permit.
• ZD_EDITION_NAME — Editioning column used for Online Patching (adopted in 12.2.x) to isolate changes across editions.
• Standard Who Columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit lineage.

Two unique indexes serve as business-key candidates. EAM_SAFETY_USR_DEF_STAT_TL_U1 enforces uniqueness on (STATUS_ID, LANGUAGE, ZD_EDITION_NAME), aligning with the primary key. EAM_SAFETY_USR_DEF_STAT_TL_U2 — the index referenced by the user's search term "eam_safety_usr_def_stat_tl_u2" — uniquely constrains (ENTITY_TYPE, USER_DEFINED_STATUS, LANGUAGE, ZD_EDITION_NAME), ensuring a given translated status name is unique per entity type and language. This distinction separates the surrogate identity (STATUS_ID) from the human-readable business key.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and integration where safety statuses must be resolved to display text in a target language. A common pattern joins the translation table to the base status table:

• Retrieving the translated status for a session language: SELECT STATUS_ID, USER_DEFINED_STATUS FROM EAM.EAM_SAFETY_USR_DEF_STATUSES_TL WHERE LANGUAGE = USERENV('LANG') AND ENTITY_TYPE = 1;
• Auditing translation coverage across languages for each entity type.
• Validating that no duplicate translated names exist per language, leveraging U2.
• Feeding downstream OAF pages and concurrent programs that render isolation/permit statuses.

Note that queries must account for ZD_EDITION_NAME in 12.2.2, since the editioning column participates in every unique key.

Related Objects

• EAM.EAM_WO_STATUSES_B — Base status table; join on STATUS_ID to obtain language-independent status attributes.
• EAM.EAM_SAFETY_USR_DEF_STATUSES_T# — Referencing object noted in dependency metadata.
• FND_LANGUAGES — Source of valid LANGUAGE and SOURCE_LANG codes.
• EAM_SAFETY_USR_DEF_STATUSES_TL (base/MLS views) — Supporting views that expose translated rows per session language.
• FND Design Data: EAM.EAM_SAFETY_USR_DEF_STATUSES_TL — Registers the table with the Application Object Library for seed and translation management.