Results for “eam_wo_statuses_b_u1”

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

Overview

EAM.EAM_WO_STATUSES_B is a foundational configuration table in the Oracle Enterprise Asset Management (EAM) module, delivered under the EAM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the set of user-defined work order statuses together with their association to the underlying Work in Process (WIP) system statuses. It is the base (non-translated) table in the EAM work order status model, holding the language-independent definition of each status. Every status visible to an EAM user — whether Oracle-seeded or created by the implementation team — originates as a row in this table. All seeded records carry ENABLED_FLAG = Y and SEEDED_FLAG = Y, while user-defined statuses carry SEEDED_FLAG = N or null. From a Data Vault modeling perspective, the mined relationship structure classifies this object heuristically as a standalone hub-like entity: it owns its own primary key (EAM_WO_STATUSES_B_PK on STATUS_ID) and is not dependent on a parent entity for identity, functioning as a reference/conformed dimension rather than a transactional satellite or link.

Key Information Stored

The table contains ten documented columns. The elements of greatest analytical and functional importance are:

• STATUS_ID — A NUMBER surrogate primary key that uniquely identifies each work order status. It is also the leading column of the unique business index EAM_WO_STATUSES_B_U1.
• SEEDED_FLAG — VARCHAR2 flag storing Y for Oracle-seeded statuses and N or null for customer-defined statuses. This distinguishes out-of-the-box configuration from implementation-specific extensions.
• SYSTEM_STATUS — The numeric WIP system status identifier to which the user-defined status maps. Documented as mapping to LOOKUP_CODE for the WIP_JOB_STATUS lookup, this is the critical link between EAM status presentation and WIP processing semantics.
• ENABLED_FLAG — Indicates whether the status is active (Y) or disabled (N or null). Disabled statuses remain in the table but are not available for new work order assignment.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the audit trail and enable incremental extraction and change-data-capture reporting.

The physical table is stored in tablespace APPS_TS_TX_DATA with PCTFREE 10; its unique index resides in APPS_TS_TX_IDX. In 12.2.x multi-tenant (Online Patching) environments the ETRM physical schema additionally documents ZD_EDITION_NAME, and the unique index EAM_WO_STATUSES_B_U1 is defined over (STATUS_ID, ZD_EDITION_NAME) to support edition-based redefinition.

Common Use Cases and Queries

The primary use case is reporting and validation of EAM work order status configuration. Common patterns include:

• Listing all enabled statuses available for work order creation:
  SELECT status_id, system_status FROM eam.eam_wo_statuses_b WHERE enabled_flag = 'Y';
• Separating seeded from customer-defined configuration:
  SELECT status_id, seeded_flag FROM eam.eam_wo_statuses_b WHERE NVL(seeded_flag,'N') = 'N';
• Joining to the WIP_JOB_STATUS lookup to obtain the meaningful status name for each mapped system status.
• Identifying statuses disabled by the implementation, to explain missing values in order-entry list of values.
• Incremental extracts keyed on LAST_UPDATE_DATE and LAST_UPDATED_BY for configuration audit reporting.

Because the table is standalone, queries typically traverse outward to the translation table and to the WIP lookup for descriptive text rather than joining to dependent children.

Related Objects

The documented dependency data records that EAM_WO_STATUSES_B references no other database object but is itself referenced by the APPS synonym EAM_WO_STATUSES_B. In practice, the most significant related objects are:

• EAM_WO_STATUSES_TL — The translation (MLS) table joined on STATUS_ID, supplying the language-specific status name and description.
• EAM_WO_STATUSES_VL — The multi-language view presenting both base and translated attributes.
• FND_LOOKUPS (WIP_JOB_STATUS) — Supplies the lookup meaning for SYSTEM_STATUS via the LOOKUP_CODE column.
• EAM_WORK_ORDERS / WIP_DISCRETE_JOBS — Consumer entities whose status values reference the configured set of STATUS_IDs.
• WIP_JOB_STATUS / WIP status codes — The WIP-side definitions to which EAM statuses are mapped through SYSTEM_STATUS.

Together these objects reconcile the EAM user-facing status model with the WIP execution model, and they should be queried as a unit for any status configuration audit.