Results for “equipment_gen_object_id”

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

Overview

EAM_ASSET_LOG is a transactional table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It records the operational status history of assets, capturing events that affect whether an asset is operable, down, or otherwise unavailable. The table serves as the analytical backbone for asset availability reporting, mean-time-between-failure (MTBF) calculations, and downtime root-cause analysis. Each row represents a discrete status event associated with an asset instance, referenced by context columns such as INSTANCE_ID and REF_ID.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests the table functions primarily as a satellite-like event log without a strong hub-and-link topology of its own; the two documented foreign keys to PSB_EMPLOYEES and BOM_DEPARTMENTS attach descriptive context rather than forming a shared business hub. Modelers should treat EAM_ASSET_LOG as an append-oriented fact/event structure keyed by LOG_ID.

Key Information Stored

The surrogate primary key is LOG_ID. Business-key candidates are not explicitly documented, but EVENT_ID combined with EVENT_TYPE, ORGANIZATION_ID, and INSTANCE_ID form a natural candidate for uniquely identifying a status transition within an operating unit.

• LOG_ID — surrogate primary key for the log entry.
• EVENT_DATE — timestamp of the operational status event; the primary axis for time-series analysis.
• EVENT_TYPE — classification of the event (for example, down, up, or status change).
• EVENT_ID — identifier of the originating event or source transaction.
• ORGANIZATION_ID — inventory/asset organization owning the record.
• INSTANCE_ID — the asset instance whose status is being logged.
• REFERENCE / REF_ID — external or internal cross-reference to the related business document.
• OPERABLE — flag indicating whether the asset is operable at the time of the event.
• DOWN_CODE / REASON_CODE — coded reasons for downtime or status change.
• RESOURCE_ID / RESOURCE_SERIAL_NUMBER — the specific resource and its serial number.
• EXPECTED_UP_DATE — projected restoration date for down assets.
• SOURCE_LOG_ID — self-referencing link to a prior log entry.
• EMPLOYEE_ID — foreign key to PSB_EMPLOYEES; the person reporting or responsible.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS; the responsible department.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — descriptive flexfield storage.

Common Use Cases and Queries

Typical reporting includes asset downtime duration, availability percentages, and failure frequency by organization, department, or resource. A representative query computes total downtime per resource:

• Filter by ORGANIZATION_ID and EVENT_DATE range to isolate a reporting period.
• Join RESOURCE_ID to asset master views to resolve asset names and categories.
• Aggregate OPERABLE = 'N' events by DOWN_CODE to rank root causes.
• Join EMPLOYEE_ID to PSB_EMPLOYEES and DEPARTMENT_ID to BOM_DEPARTMENTS for responsibility reporting.
• Use SOURCE_LOG_ID self-joins to trace chained status transitions.

Related Objects

• PSB_EMPLOYEES — joined on EAM_ASSET_LOG.EMPLOYEE_ID = PSB_EMPLOYEES.EMPLOYEE_ID.
• BOM_DEPARTMENTS — joined on EAM_ASSET_LOG.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID.
• EAM_ASSET_LOG (self) — joined on SOURCE_LOG_ID to LOG_ID for event chains.
• Asset instance / resource master tables in the EAM schema, referenced via INSTANCE_ID and RESOURCE_ID.
• EAM work order and maintenance objects, cross-referenced through REFERENCE and REF_ID.