Search Results eam_safety_usr_def_statuses_b




Overview
Explore in AI Chat

Overview

EAM_SAFETY_USR_DEF_STATUSES_B is a base table in the Oracle E-Business Suite Enterprise Asset Management (EAM) module, owned by the EAM schema and classified as VALID in Oracle EBS 12.1.1 and 12.2.2. It serves as the definition repository for user-defined safety statuses, allowing organizations to extend the standard safety status set with codes specific to their maintenance safety workflows. This table underpins the safety status lookup mechanism used across EAM safety plans, work permits, and related safety records.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is modeled as a standalone table — effectively a hub candidate. The absence of documented foreign keys to other hubs or links suggests it functions as an independent reference/master entity whose rows are referenced by satellite-style transactional tables (such as safety status assignments) rather than aggregating codes from other sources. In practice, this positions the table as a foundational definition entity rather than a relationship or history table.

Key Information Stored

The table carries 11 documented columns. The most significant include:

  • STATUS_ID — the surrogate primary key, enforced by the EAM_SAFETY_USR_DEF_STATUS_B_PK constraint. This numeric identifier uniquely identifies each user-defined safety status record and is the value carried into dependent tables.
  • ZD_EDITION_NAME — the editioning column introduced in Oracle EBS 12.2.2 multi-tenant architecture. It participates in the unique index EAM_SAFETY_USR_DEF_STAT_B_U1 (STATUS_ID, ZD_EDITION_NAME), which acts as the business-key candidate for edition-aware access. In 12.1.1 this column does not exist.
  • SEEDED_FLAG — distinguishes Oracle-seeded statuses from customer-defined ones, a critical filter in upgrade and support scenarios.
  • ENTITY_TYPE — identifies which EAM safety entity (e.g., permit, plan) the user-defined status applies to.
  • SYSTEM_STATUS — maps the user-defined code to an underlying system status used internally by EAM processing logic.
  • ENABLED_FLAG — controls whether the status is available for selection in EAM safety forms.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking creation and modification of each status definition.

Common Use Cases and Queries

Typical use cases include validating active user-defined statuses for a given entity type, auditing seeded versus customer statuses, and joining status definitions to safety transaction records for reporting.

  • Enumerating enabled customer statuses: SELECT status_id, entity_type, system_status FROM eam.eam_safety_usr_def_statuses_b WHERE enabled_flag = 'Y' AND seeded_flag = 'N';
  • Auditing status usage: join STATUS_ID to dependent safety assignment tables for volume and distribution reports.
  • Edition-aware access on 12.2.2: SELECT * FROM eam.eam_safety_usr_def_statuses_b WHERE zd_edition_name = 'SET1';
  • Tracking changes: filter by LAST_UPDATE_DATE to report recently modified status definitions.

Related Objects

Because the mined classification is standalone, relationships are primarily inferred from the primary key rather than documented foreign keys. Relevant associated objects include: