Search Results eam_enable_workflow_u1




Overview
Explore in AI Chat

Overview

The EAM.EAM_ENABLE_WORKFLOW table is a configuration control object within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite. It governs whether Oracle Workflow-based approval and notification functionality is activated for a given maintenance object source. Each row represents a distinct source value, allowing Oracle EAM and other product teams to selectively enable or disable workflow processing for work orders and related maintenance transactions originating from different systems, integrations, or originating modules.

The table documents eight physical columns and is owned by the EAM schema, stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its status is VALID in releases 12.1.1 and 12.2.2. Oracle seeds a single row for Maintenance Object Source value 1 for EAM itself; other product teams are expected to insert additional rows to extend work order workflow functionality.

From a dimensional or Data Vault modeling perspective, the mined relationship data classifies this object as standalone — it references no other database object. In Data Vault terms it is best treated as a small reference or configuration hub, keyed on MAINTENANCE_OBJECT_SOURCE, with ENABLE_WORKFLOW acting as a descriptive attribute. It is not a transaction satellite; it is a setup/reference entity whose cardinality remains low.

Key Information Stored

The table’s business content is concentrated in a small number of columns:

  • MAINTENANCE_OBJECT_SOURCE — Numeric identifier of the maintenance object source for which workflow is enabled or disabled. This is the documented primary key and the leading column of the unique index EAM_ENABLE_WORKFLOW_U1.
  • ENABLE_WORKFLOW — VARCHAR2 flag indicating whether workflow is enabled for the associated source.
  • ZD_EDITION_NAME — Editioning column introduced with the 12.2.x Online Patching (ADOP) architecture; it participates with MAINTENANCE_OBJECT_SOURCE in the unique index EAM_ENABLE_WORKFLOW_U1.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns recording audit and row-level accountability.

The primary key is documented as MAINTENANCE_OBJECT_SOURCE_PK on MAINTENANCE_OBJECT_SOURCE. The business-key candidate is the composite unique index EAM_ENABLE_WORKFLOW_U1 over MAINTENANCE_OBJECT_SOURCE and ZD_EDITION_NAME — the edition name is included because editioned objects maintain separate logical copies per edition.

Common Use Cases and Queries

Typical scenarios include verifying whether workflow is active before submitting a work order, auditing which sources have workflow extended, and supporting integration teams that register new sources.

  • Checking the workflow flag for a given source: 
    SELECT MAINTENANCE_OBJECT_SOURCE, ENABLE_WORKFLOW
FROM   EAM.EAM_ENABLE_WORKFLOW
WHERE  MAINTENANCE_OBJECT_SOURCE = :source;
  • Confirming the seeded EAM row (source = 1) is present and enabled.
  • Reporting on all sources with workflow disabled for governance review.
  • Validating edition scope via ZD_EDITION_NAME in a 12.2.x environment during patching cycles.

Related Objects

The relationship metadata states that EAM.EAM_ENABLE_WORKFLOW does not reference any database object and is a standalone entity. It is referenced by the editioning view EAM_ENABLE_WORKFLOW#. Functionally, it is consumed alongside the Oracle EAM work order and Oracle Workflow infrastructure — for example the work order and work request entities in EAM, the Oracle Workflow runtime/definition tables, and the FND Design Data definition EAM.EAM_ENABLE_WORKFLOW. Because the table holds only a source identifier and a flag, joins should be driven by MAINTENANCE_OBJECT_SOURCE against the corresponding source lookup used by the calling application.