Search Results failure_code_required

Overview

The APPS.EAM_FAILURE_SET_ASSOCIATIONS_V view is a reporting and integration object within the Oracle Enterprise Asset Management (EAM) module. Its stated purpose, as documented in the ETRM, is to query all active Failure Set – Item associations. A Failure Set in Oracle EAM groups a collection of failure codes (problem, cause, and resolution codes) that can be applied to an asset or an inventory item during work order and maintenance execution. The association records define which items are linked to a given failure set and whether the entry of a failure code is mandatory when that item is serviced.

The view is owned by the APPS schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its principal value lies in exposing only associations that are currently effective, filtering out rows whose EFFECTIVE_END_DATE has passed. This makes it a convenient source for reports, concurrent programs, Oracle Discoverer worksheets, OBIEE extracts, and integration interfaces that must reflect the present state of failure set configuration without applying their own date logic.

Underlying Base Objects

The view is defined over a single documented base object: the synonym EAM_FAILURE_SET_ASSOCIATIONS, which resolves to the underlying EAM base table of the same name. The view does not join to MTL_SYSTEM_ITEMS_B or to any failure set header table; it therefore returns the INVENTORY_ITEM_ID and SET_ID as raw identifiers, and consumers must join outward to MTL_SYSTEM_ITEMS_B or the corresponding EAM failure set definition objects to resolve item numbers, descriptions, or failure set names.

The view text applies a date predicate of TRUNC(NVL(EFFECTIVE_END_DATE, SYSDATE+1)) > TRUNC(SYSDATE). Rows with a null end date are treated as open-ended and therefore active, while rows whose end date is on or before the current system date are excluded. All audit columns from the base table are passed through unchanged.

Key Columns

• SET_ID – Identifier of the failure set to which the item association belongs.
• INVENTORY_ITEM_ID – Identifier of the associated inventory item in MTL_SYSTEM_ITEMS_B.
• FAILURE_CODE_REQUIRED – Flag indicating whether a failure code must be captured for this item when it is used in an EAM work order; this is the column most frequently referenced by users searching for "failure_code_required".
• EFFECTIVE_END_DATE – Date on which the association ceases to be effective; a null value denotes an open-ended association.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Oracle Who columns providing audit trail information.

Common Use Cases and Queries

Typical scenarios include auditing which items enforce failure code entry, validating configuration before a maintenance rollout, and feeding external systems that mirror EAM failure set associations. A representative query listing active associations with item and failure set context follows:

SELECT v.SET_ID,
       v.INVENTORY_ITEM_ID,
       msib.SEGMENT1       AS ITEM_NUMBER,
       msib.DESCRIPTION    AS ITEM_DESCRIPTION,
       v.FAILURE_CODE_REQUIRED,
       v.EFFECTIVE_END_DATE
FROM   APPS.EAM_FAILURE_SET_ASSOCIATIONS_V v,
       APPS.MTL_SYSTEM_ITEMS_B msib
WHERE  v.INVENTORY_ITEM_ID = msib.INVENTORY_ITEM_ID
AND    msib.ORGANIZATION_ID = :org_id
ORDER  BY msib.SEGMENT1;

To isolate only those associations where a failure code is mandatory, the predicate FAILURE_CODE_REQUIRED = 'Y' is added. Because the view already restricts output to effective rows, no additional date filtering is necessary. The view is read-only and should not be used as a DML target; updates to associations must be performed against the base table through the EAM application or supported APIs.