Search Results eam_work_permit_u1

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 definition of permits that authorize specific maintenance or hazardous activities against assets and work orders. Each row represents a distinct permit, capturing its identity, validity window, type, and approval and completion state. Permits are defined once in this table and then associated to work orders, providing the safety governance layer that controls when and under what conditions work may proceed.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and its unique index EAM_WORK_PERMIT_U1 (the object referenced in the search term) is created on the PERMIT_ID column in the APPS_TS_TX_IDX tablespace. The documented physical schema comprises 48 columns. Based on the heuristic Data Vault classification derived from the foreign key structure, this object is modeled as a standalone entity, which in Data Vault terms suggests a hub-like construct — the PERMIT_ID business entity anchor without documented dependent links or satellites in the supplied metadata.

Key Information Stored

The table’s primary key is EAM_PERMIT_PK, defined on PERMIT_ID, which is the surrogate unique identifier for each permit. The unique index EAM_WORK_PERMIT_U1 also enforces uniqueness on PERMIT_ID, making it the single documented business-key candidate; no composite natural key is defined in the metadata.

• PERMIT_ID — Surrogate primary key and unique identifier for the permit.
• PERMIT_NAME — Descriptive name of the permit (VARCHAR2 240).
• DESCRIPTION — Text description of the permit’s purpose.
• ORGANIZATION_ID — Identifies the inventory organization owning the permit.
• PERMIT_TYPE — Classifies the permit category.
• VALID_FROM / VALID_TO — The date range during which the permit is active.
• STATUS_TYPE — Numeric status of the permit.
• USER_DEFINED_STATUS_ID — References a user-defined permit status.
• APPROVED_BY — The user who approved the permit.
• COMPLETION_DATE — Date the permit was completed.
• PENDING_FLAG — Indicates whether the permit is pending.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield structure and segment columns for extensibility.
• Audit columns — LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and CREATED_BY support standard EBS auditing.

Common Use Cases and Queries

Typical reporting includes listing active permits for an organization, identifying permits nearing expiry, and auditing approval and completion activity. A representative query retrieves active permits within a validity window:

• SELECT permit_id, permit_name, permit_type, valid_from, valid_to FROM eam.eam_work_permits WHERE organization_id = :org_id AND TRUNC(SYSDATE) BETWEEN valid_from AND NVL(valid_to, SYSDATE) AND pending_flag IS NULL;
• SELECT permit_id, permit_name, approved_by, completion_date FROM eam.eam_work_permits WHERE status_type = :status;
• SELECT COUNT(*) FROM eam.eam_work_permits WHERE valid_to < TRUNC(SYSDATE);

Related Objects

The metadata documents this object as standalone, meaning no foreign key relationships were mined to parent or child tables. In practice, EAM_WORK_PERMITS is referenced by work order permit association entities that link permits to work orders, and ORGANIZATION_ID logically relates to ORG_ORGANIZATION_DEFINITIONS, while USER_DEFINED_STATUS_ID relates to the user-defined status lookup. APPROVED_BY and CREATED_BY reference FND_USER. Because the documented relationship data does not enumerate explicit FK constraints, join columns such as PERMIT_ID to the work order permit association table should be verified against the ETRM relationship model for the specific EBS release before use in production queries.