Search Results eam_isolations_u01

Overview

EAM.EAM_ISOLATIONS is the Oracle Enterprise Asset Management (eAM) table that stores safety Isolation Definitions. In EBS 12.1.1 and 12.2.2, an isolation definition describes a physical or logical energy-isolation boundary — such as a lockout/tagout point, electrical disconnect, valve, or permit-controlled work zone — that must be applied before maintenance work proceeds on an asset. The table is owned by the EAM schema and is registered in FND Design Data as EAM.EAM_ISOLATIONS with a status of VALID. Its physical storage resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its unique index EAM_ISOLATIONS_U01 is stored in APPS_TS_TX_IDX.

The table exposes 48 documented columns, comprising the core isolation attributes plus a standard 30-column descriptive flexfield block and Oracle's WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN). Its primary key is EAM_ISOLATIONS_PK on ISOLATION_ID. A heuristic Data Vault classification mined from the FK structure places this object as a standalone structure — effectively a hub-style reference entity with no documented foreign-key dependencies. Modeling guidance therefore treats ISOLATION_ID as the durable business key of a hub, with descriptive and status-bearing fields treated as hub attributes or as a satellite if history tracking is required.

Key Information Stored

The most operationally significant columns are:

• ISOLATION_ID — numeric surrogate primary key and the column behind both EAM_ISOLATIONS_PK and the unique index EAM_ISOLATIONS_U01. It is the sole documented business-key candidate.
• ISOLATION_NAME — the user-facing name of the isolation definition, up to 240 characters.
• ISOLATION_TYPE — numeric discriminator classifying the isolation (for example, lockout versus permit-based boundaries).
• DESCRIPTION — free-text explanation of the isolation, up to 240 characters.
• ORGANIZATION_ID — the inventory organization that owns the definition, enabling multi-org partitioning.
• PENDING_FLAG — indicates whether the isolation record is awaiting release or approval before it becomes active.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the isolation definition is valid.
• APPROVED_BY — the application user who approved the isolation definition.
• USER_DEFINED_STATUS_ID / STATUS_TYPE — link the record to a user-defined status value and its status category.
• PERMIT_REQUIRED_FLAG — flags whether a work permit must accompany the isolation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the descriptive flexfield context and segment values used for customer-specific extensions.

Common Use Cases and Queries

Typical usage includes validating whether an isolation is still effective before a work order is released, reporting on isolations that require permits, and auditing approval activity. The most common access path is a lookup by primary key through EAM_ISOLATIONS_U01:

• SELECT isolation_id, isolation_name, isolation_type, description, permit_required_flag FROM eam.eam_isolations WHERE isolation_id = :p_id;
• ... WHERE organization_id = :org_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);
• ... WHERE pending_flag = 'Y' AND approved_by IS NULL; — identify definitions awaiting approval.
• ... WHERE permit_required_flag = 'Y'; — drive permit-control reporting.

Flexfield reporting should query ATTRIBUTE_CATEGORY first to resolve the context, then select only the relevant ATTRIBUTE columns for that context.

Related Objects

The mined relationship data classifies EAM_ISOLATIONS as standalone, so no foreign keys are documented from this table. Nevertheless, it participates logically in the eAM safety and work-management model, and the following objects are the most significant consumers or companions:

• EAM_WORK_ORDERS / EAM_WO_OPERATIONS — work orders reference the isolations that must be applied before execution begins.
• EAM_WO_ISOLATIONS — the association table linking isolation definitions to specific work orders, joined on ISOLATION_ID.
• EAM_ASSETS / EAM_ASSET_ACTIVITIES — assets and their activities provide the physical context for an isolation boundary.
• EAM_PERMIT_DEFINITIONS — permit definitions reconcile with PERMIT_REQUIRED_FLAG on this table.
• FND_LOOKUP_VALUES — resolves lookup-coded values such as pending and permit flags.
• FND_USER (via APPROVED_BY, CREATED_BY, LAST_UPDATED_BY) — supplies user names for approval and audit reporting.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE_TL — describe the DFF segments mapped to ATTRIBUTE1 through ATTRIBUTE30.

Any PL/SQL or concurrent program accessing this table should reference it with the EAM schema prefix and honor ORGANIZATION_ID when running under a multi-org context.