Search Results eam_work_permits




Overview

EAM.EAM_WORK_PERMITS is the master definition table for safety work permits within the Oracle Enterprise Asset Management (EAM) module. In Oracle EBS 12.1.1 and 12.2.2, this table stores the permit templates and permit records that authorize personnel to perform specific maintenance activities under controlled safety conditions. Once a permit is defined here, it must be associated to Work Orders before maintenance execution can proceed against the governed asset. The table resides in the EAM schema and is classified as VALID with 48 documented columns.

From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is standalone. This suggests the table can be modeled as an independent hub with its own business key rather than as a dependent link or satellite. Modelers should treat the permit as a durable business concept rather than a transactional edge between two other entities.

Key Information Stored

The table's surrogate primary key is PERMIT_ID, enforced by the constraint EAM_PERMIT_PK and also covered by the unique index EAM_WORK_PERMIT_U1. This makes PERMIT_ID the strongest business-key candidate documented for the entity.

Common Use Cases and Queries

Typical reporting use cases include retrieving all active permits for an organization, tracking permits approaching expiration, and identifying permits awaiting approval. A representative query follows:

SELECT permit_id, permit_name, permit_type, status_type,
       valid_from, valid_to, approved_by
FROM   eam.eam_work_permits
WHERE  organization_id = :org_id
AND    TRUNC(SYSDATE) BETWEEN valid_from AND valid_to
AND    pending_flag = 'N';

Auditors frequently query permits joined to work orders to verify that governed maintenance tasks had valid authorization at execution time. Dashboards can aggregate permits by STATUS_TYPE and PERMIT_TYPE to report safety compliance metrics.

Related Objects

Because the table is classified as standalone, it does not expose outgoing foreign keys in the mined metadata. Its practical relationships are realized logically through the EAM work order framework and reference the following objects: