Search Results maintenance_object_source_pk

Overview

The EAM.EAM_ENABLE_WORKFLOW table is a configuration-level reference object within the Oracle Enterprise Asset Management (EAM) module. Its documented purpose is to store the various maintenance object source values for which Oracle Workflow is either enabled or disabled. In practice, this table acts as a control switch: when a maintenance activity is created against a given source object, the EAM application queries this table to determine whether that source type participates in the workflow-driven approval or notification process. The object resides in the EAM schema, carries a VALID status, and is documented with eight physical columns under ETRM 12.2.2.

From a Data Vault modeling perspective, the mined relationship data classifies this table as standalone, with no foreign key dependencies to other tables. Applying the heuristic classification, it is best modeled as a satellite of the maintenance object source business key, or alternatively as a small hub-plus-satellite construct in which MAINTENANCE_OBJECT_SOURCE serves as the natural business key and ENABLE_WORKFLOW is the descriptive attribute. Because the table is reference data rather than transactional data, the satellite interpretation is the more practical modeling suggestion.

Key Information Stored

The table is compact, and the columns that carry functional meaning are limited to the following:

• MAINTENANCE_OBJECT_SOURCE_PK — the documented primary key. It is the surrogate identifier for each row and is functionally dependent on MAINTENANCE_OBJECT_SOURCE.
• MAINTENANCE_OBJECT_SOURCE — the business-key candidate. This column holds the name of the maintenance object source (for example, the source type of a work order or maintenance activity) whose workflow participation is being configured. It is the leading column of the unique index EAM_ENABLE_WORKFLOW_U1 (MAINTENANCE_OBJECT_SOURCE, ZD_EDITION_NAME).
• ENABLE_WORKFLOW — the descriptive flag indicating whether workflow is enabled or disabled for the corresponding maintenance object source. This is the principal attribute consumed by application logic.
• ZD_EDITION_NAME — the editioning column that, combined with MAINTENANCE_OBJECT_SOURCE, forms the documented unique business-key index. It reflects the Edition-Based Redefinition (EBR) architecture introduced in EBS 12.2.

The remaining auditable columns — CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — are standard Oracle EBS "Who" columns that record row provenance and change history. They are not functionally significant but are routinely referenced in audit and reconciliation queries.

Common Use Cases and Queries

The most common use case is troubleshooting workflow behavior: determining whether a particular maintenance object source is configured to trigger workflow. A typical lookup query is:

• SELECT maintenance_object_source, enable_workflow FROM eam.eam_enable_workflow WHERE enable_workflow = 'Y';

A second scenario is security and administration auditing, verifying which users created or last modified configuration rows:

• SELECT maintenance_object_source, last_updated_by, last_update_date FROM eam.eam_enable_workflow ORDER BY last_update_date DESC;

Reporting use cases include validating that workflow is enabled for all required sources prior to go-live, and extracting the complete enabled-source list for documentation or migration scripts. Because the table is small and stable, queries typically run without performance concerns, and an index on ENABLE_WORKFLOW is generally unnecessary given the low cardinality of the flag.

Related Objects

The mined relationship data classifies this table as standalone, with no documented foreign keys to other EAM objects. Consequently, joins to related objects are driven by the MAINTENANCE_OBJECT_SOURCE value rather than by referential constraints. The most significant related objects are those that supply the maintenance object source domain:

• EAM_MAINTENANCE_OBJECT_SOURCES (or the equivalent lookup of source values) — provides the domain against which MAINTENANCE_OBJECT_SOURCE is matched.
• EAM_WORK_ORDERS and EAM_WORK_REQUESTS — the transactional entities whose source values are evaluated against this configuration.
• EAM_WORKFLOW_* Workflow process and notification definitions — the objects whose activation depends on ENABLE_WORKFLOW.
• FND_LOOKUPS — frequently referenced when the maintenance object source list is validated or displayed.
• EAM_OBJECTS — may reference source definitions that align with rows in this configuration table.

Because no foreign keys are documented, developers should validate joins through application logic and the EAM configuration setup rather than assuming database-enforced integrity.