Search Results cause_code




Overview
Explore in AI Chat

Overview

EAM_FAILUREINFO_V is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Enterprise Asset Management (EAM) product family and presents failure information recorded against a discrete work order. The view consolidates failure, cause, and resolution data captured through the EAM asset failure framework, joining it to the associated WIP discrete job and EAM work order details, and resolving the applicable failure set for the affected item or asset group.

Because the underlying failure records are transactional and spread across multiple normalized tables, the view serves as the primary denormalized access point for failure analysis. Query tools such as OBIEE, Discoverer, BI Publisher, and third-party reporting layers typically reference EAM_FAILUREINFO_V rather than the base tables directly. The view text embeds scalar subqueries that derive the failure set and set name dynamically using EAM_FAILURE_SET_ASSOCIATIONS and EAM_FAILURE_SETS, so results reflect the failure set in effect at query time, based on the current system date.

Underlying Base Objects

The documented base objects referenced by the view are EAM_ASSET_FAILURES, EAM_ASSET_FAILURE_CODES, EAM_CAUSE_CODES, EAM_FAILURE_CODES, EAM_FAILURE_SETS, EAM_FAILURE_SET_ASSOCIATIONS, EAM_RESOLUTION_CODES, EAM_WORK_ORDER_DETAILS, and WIP_DISCRETE_JOBS. All are surfaced as APPS synonyms. The join logic is built as follows:

  • WIP_DISCRETE_JOBS is joined to EAM_WORK_ORDER_DETAILS on WIP_ENTITY_ID, establishing the work order context.
  • EAM_WORK_ORDER_DETAILS is outer-joined to EAM_ASSET_FAILURES on WIP_ENTITY_ID as SOURCE_ID, so work orders without reported failures are still returned.
  • EAM_ASSET_FAILURES is outer-joined to EAM_ASSET_FAILURE_CODES on FAILURE_ID.
  • EAM_FAILURE_CODES, EAM_CAUSE_CODES, and EAM_RESOLUTION_CODES are outer-joined to provide human-readable descriptions for the coded failure, cause, and resolution values.
  • EAM_FAILURE_SET_ASSOCIATIONS and EAM_FAILURE_SETS are accessed through scalar subqueries to determine the active failure set for the item or asset group.

The outer joins ensure the view reports work orders even where failure coding is incomplete, which is important because EAM_WORK_ORDER_DETAILS carries a FAILURE_CODE_REQUIRED flag indicating whether failure coding was mandated for that work order.

Key Columns

  • WIP_ENTITY_ID — Identifier of the discrete job / work order against which the failure is reported.
  • FAILURE_ID / FAILURE_ENTRY_ID — Keys for the failure record and its coded failure entry.
  • FAILURE_DATE — The date on which the failure was reported, sourced from EAM_ASSET_FAILURES. This is the column most frequently used for time-based failure trending.
  • FAILURE_CODE / FAILURE_DESCRIPTION — The coded failure and its description, resolved via NVL against EAM_FAILURE_CODES.
  • CAUSE_CODE / CAUSE_DESCRIPTION — The coded cause of failure and its resolved description.
  • RESOLUTION_CODE / RESOLUTION_DESCRIPTION — The coded resolution and its resolved description.
  • FAILURE_CODE_REQUIRED — Flag from EAM_WORK_ORDER_DETAILS indicating whether failure coding was required for the work order.
  • COMMENTS — Free-text comments recorded on the failure entry.
  • INVENTORY_ITEM_ID — Derived as NVL(REBUILD_ITEM_ID, ASSET_GROUP_ID) from the discrete job, identifying the item or asset group.
  • SET_ID / SET_NAME — The failure set associated with the inventory item and currently in effect.
  • STATUS_TYPE / CREATION_DATE — Status and creation timestamp of the discrete job.

Common Use Cases and Queries

Typical scenarios include failure trending by date, Pareto analysis of failure and cause codes, mean-time-between-failure measurement, and compliance checks for work orders where failure coding was required but omitted.

Sample query listing recent failures with resolved codes:

  • SELECT WIP_ENTITY_ID, FAILURE_DATE, FAILURE_CODE, FAILURE_DESCRIPTION, CAUSE_DESCRIPTION, RESOLUTION_DESCRIPTION FROM APPS.EAM_FAILUREINFO_V WHERE FAILURE_DATE >= SYSDATE - 90 ORDER BY FAILURE_DATE DESC;

Sample query counting failures by code for a trending report:

  • SELECT FAILURE_CODE, FAILURE_DESCRIPTION, COUNT(*) FAILURE_COUNT FROM APPS.EAM_FAILUREINFO_V WHERE FAILURE_DATE BETWEEN :start_date AND :end_date GROUP BY FAILURE_CODE, FAILURE_DESCRIPTION ORDER BY FAILURE_COUNT DESC;

Sample query identifying work orders requiring but lacking failure detail:

  • SELECT WIP_ENTITY_ID, FAILURE_CODE_REQUIRED, FAILURE_ID, FAILURE_DATE FROM APPS.EAM_FAILUREINFO_V WHERE FAILURE_CODE_REQUIRED = 'Y' AND FAILURE_ID IS NULL;

Because FAILURE_DATE is resolved from the underlying EAM_ASSET_FAILURES record, date-filtered extracts should filter on this column rather than on CREATION_DATE to reflect reporting period accurately.