Search Results eam_establishment_details

Overview

EAM_ESTABLISHMENT_DETAILS is an Oracle Enterprise Asset Management (EAM) table that stores safety establishment records. Within Oracle EBS Release 12.1.1 and 12.2.2, this object supports the safety and lockout/tagout (LOTO) workflow that governs maintenance execution — associating an establishment of safety conditions (such as lockout devices, safety tags, and tag positions) with a source transaction, a maintenance object, and optionally a resource, department, or resource instance. The table is owned by the EAM schema and is documented with 52 physical columns in ETRM 12.2.2, with a primary key constraint named EAM_ESTABLISHMENT_DETAILS_PK on ESTABLISHMENT_ID.

The ETRM documentation classifies this table as standalone at the Data Vault level, meaning the mined foreign-key structure does not identify a dependent hub/link/satellite relationship to another EAM entity. Modeling it as an independent hub (or as a satellite of the establishment source entity, if a natural business key is inferred from ESTABLISHMENT_SOURCE and ESTABLISHMENT_SOURCE_ID) is a reasonable heuristic suggestion rather than a documented constraint.

Key Information Stored

The table's most operationally significant columns include:

• ESTABLISHMENT_ID — surrogate primary key (EAM_ESTABLISHMENT_DETAILS_PK).
• ESTABLISHMENT_SOURCE and ESTABLISHMENT_SOURCE_ID — together identify the originating business entity (for example, a work order or permit) that the safety establishment is derived from; these are the strongest business-key candidates.
• SEQUENCE_TYPE and SEQUENCE_NUMBER — order and category the establishment steps within its source.
• DESCRIPTION — free-text description of the establishment.
• ORGANIZATION_ID — the operating unit / organization context, enabling multi-org access control.
• MAINTENANCE_OBJECT_ID, RESOURCE_ID, DEPT_ID, RES_INSTANCE_ID — the assets, resources, departments, and resource instances to which the establishment applies.
• SAFETY_TAG, TAG_POSITION, LOCKOUT_DEVICE, LOCK_NUMBER — the physical safety controls and identifiers used in the tagout/lockout procedure.
• COMPLETION_DATE — when the establishment was completed.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle DFF flexfield, used for client-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard "Who" audit columns.

Common Use Cases and Queries

Typical uses are compliance reporting on LOTO activity, listing all establishments for a maintenance object, and reconciling completed vs. open establishments for a work order. A representative query joins the establishment to its source:

• Filter by organization for multi-org reporting: SELECT ESTABLISHMENT_ID, DESCRIPTION, SAFETY_TAG, LOCK_NUMBER, COMPLETION_DATE FROM EAM.EAM_ESTABLISHMENT_DETAILS WHERE ORGANIZATION_ID = :org_id;
• Locate all establishments for a maintenance object: ... WHERE MAINTENANCE_OBJECT_ID = :object_id ORDER BY SEQUENCE_NUMBER;
• Trace the source of an establishment: ... WHERE ESTABLISHMENT_SOURCE = :source AND ESTABLISHMENT_SOURCE_ID = :source_id;
• Audit stale or uncompleted records: ... WHERE COMPLETION_DATE IS NULL;

Reporting views built on this table should honor the ORGANIZATION_ID column and the standard security profile to enforce operating-unit restrictions.

Related Objects

Because ETRM classes the table as standalone, few direct FK dependencies are documented. However, business linkage exists through the following objects (join on the indicated columns):

• EAM_ESTABLISHMENTS — the header/principal record; join on ESTABLISHMENT_SOURCE / ESTABLISHMENT_SOURCE_ID or, in some implementations, ESTABLISHMENT_ID.
• EAM_MAINTENANCE_OBJECTS — join on MAINTENANCE_OBJECT_ID.
• EAM_RESOURCES / EAM_RESOURCE_INSTANCES — join on RESOURCE_ID and RES_INSTANCE_ID.
• EAM_WORK_ORDERS / WIP entities — where ESTABLISHMENT_SOURCE references a work order.
• PER_DEPARTMENTS — join on DEPT_ID.
• HR_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — join on ORGANIZATION_ID for organization names.
• FND_USER — join CREATED_BY and LAST_UPDATED_BY for audit identity.
• Standard EBS security and flexfield views for ATTRIBUTE_CATEGORY and ATTRIBUTE1–30.

No documented public API is named in the ETRM excerpt; integrations should treat the table as EAM-internal and access it read-only for reporting.