Results for “eam_safety_associations”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EAM.EAM_SAFETY_ASSOCIATIONS is an Oracle Enterprise Asset Management (EAM) transactional table that stores work order and safety association information. It acts as a junction-style repository that links a source entity — typically an EAM work order or operation — to a target safety-related reference, such as a permit, hazard, safety procedure, or lockout/tagout definition. The table is owned by the EAM schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its 45-column physical footprint reflects the standard EBS pattern of a compact set of business columns followed by a 30-column ATTRIBUTE flexfield block and standard WHO audit columns.

The ETRM metadata classifies this object under a heuristic Data Vault model as standalone. In modeling terms, this suggests the table behaves primarily as a link between two entities (via SOURCE_ID and TARGET_REF_ID) with an attached descriptive satellite portion (association type, effective dating, enablement, comments). Practitioners designing a Data Vault or dimensional layer around EAM should treat EAM_SAFETY_ASSOCIATIONS as a link table rather than a hub, because its identity is defined by the relationship it expresses, not by an independent business concept.

Key Information Stored

• SAFETY_ASSOCIATION_ID — the surrogate primary key, enforced by EAM_SAFETY_ASSOCIATION_PK. This is the only documented unique key; no separate business-key unique index is identified in the metadata, so business uniqueness must be inferred from the combination of SOURCE_ID, TARGET_REF_ID, and ASSOCIATION_TYPE.
• SOURCE_ID — the identifier of the originating entity (for example, a work order or work order operation) that carries the safety requirement.
• TARGET_REF_ID — the identifier of the referenced safety object, such as a permit or procedure.
• ASSOCIATION_TYPE — the discriminator that classifies the nature of the link between source and target.
• ORGANIZATION_ID — the operating unit / inventory organization context, enabling multi-org filtered queries.
• EFFECTIVE_FROM and EFFECTIVE_TO — the validity window during which the association is active.
• ENABLED — a flag indicating whether the association is currently in force.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield block reserved for customer-defined extensions.
• COMMENTS — free-form notes describing the association.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO columns supporting audit and change tracking.

Common Use Cases and Queries

Typical reporting scenarios include identifying all safety requirements attached to open work orders, auditing expired associations, and validating that no active work order lacks a required permit. A common pattern joins the association back to the work order through SOURCE_ID:

SELECT sa.SAFETY_ASSOCIATION_ID, sa.SOURCE_ID, sa.TARGET_REF_ID, sa.ASSOCIATION_TYPE
FROM EAM.EAM_SAFETY_ASSOCIATIONS sa
WHERE sa.ORGANIZATION_ID = :org_id
AND sa.ENABLED = 'Y'
AND SYSDATE BETWEEN sa.EFFECTIVE_FROM AND NVL(sa.EFFECTIVE_TO, SYSDATE + 1);

Effective-dating queries should always apply NVL on EFFECTIVE_TO, since open-ended associations may leave the column null. Multi-org reporting must filter on ORGANIZATION_ID. Flexfield values in ATTRIBUTE1–ATTRIBUTE30 can be surfaced for client-specific reporting when an ATTRIBUTE_CATEGORY is populated.

Related Objects

The metadata documents no foreign keys, consistent with the standalone classification. However, functional relationships are expected with the following EAM objects:

• EAM_WORK_ORDERS — joined via SOURCE_ID = WORK_ORDER_ID when the source is a work order.
• EAM_WORK_ORDER_OPERATIONS — joined via SOURCE_ID when the association is scoped to an operation.
• EAM_WORK_REQUIREMENTS — relates safety constraints to work execution.
• EAM_PERMITS / permit-related EAM tables — likely targets of TARGET_REF_ID.
• EAM_SAFETY_PLANS and safety procedure definitions — candidate target references.
• FND_FLEX_VALUES — resolves ATTRIBUTE_CATEGORY and flexfield values.
• HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — resolves ORGANIZATION_ID.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY.

Because the source and target identifiers are polymorphic, joins must be conditioned on ASSOCIATION_TYPE to avoid mismatched entity resolution.