Search Results eam_failuresets_pvt




Overview
Explore in AI Chat

Overview

EAM_FAILURESETS_PUB is the public API package within the Oracle Enterprise Asset Management (eAM) module of Oracle E-Business Suite. It governs the creation and maintenance of failure sets, which are structured collections of failure codes organised into parent-child hierarchies. Failure sets provide the taxonomic backbone used during maintenance work order closeout, equipment failure entry, and reliability analysis. When a technician records a failure against an asset, the failure set determines which failure code combinations are valid and how they roll up for reporting.

The package is classified as a PUB (public) API, meaning it forms part of the supported programmatic interface for eAM and is intended for invocation by external consumers rather than internal-only use. It is owned by the APPS schema and holds VALID status in ETRM 12.2.2. The naming convention indicates a companion private package, EAM_FAILURESETS_PVT, which contains the implementation logic; the PUB layer performs validation, standardisation, and error handling before delegating to the private layer. The package depends on FND_API, the Oracle Application Object Library API utility package that supplies the standard fnd_api.g_ret_sts_success, fnd_api.g_ret_sts_error, and fnd_api.g_ret_sts_unexp_error constants and the fnd_msg_pub message stack used throughout Oracle's PL/SQL APIs.

Key Procedures and Functions

The documented interface exposes five procedures, covering failure set headers, failure set associations, and their lifecycle:

  • CREATE_FAILURESET — Creates a new failure set header record, establishing the top-level identity and descriptive attributes of the failure set.
  • UPDATE_FAILURESET — Modifies an existing failure set header, allowing changes to its descriptive attributes.
  • CREATE_ASSOCIATION — Creates an association between a failure set and its constituent failure codes, building the hierarchical structure of the failure set.
  • UPDATE_ASSOCIATION — Updates an existing failure set-to-failure code association, enabling adjustments to the hierarchy without recreating the parent failure set.
  • DELETE_ASSOCIATION — Removes an association between a failure set and a failure code, allowing entries to be pruned from the hierarchy.

All procedures follow the standard Oracle API convention of accepting a p_api_version, an optional p_init_msg_list flag, and returning x_return_status and x_msg_count/x_msg_data. Error conditions are surfaced through the FND message stack rather than raised exceptions, so callers must inspect the return status after every invocation.

Tables Accessed

The ETRM excerpt for this object does not enumerate the underlying base tables directly; documentation lists the dependencies at the package level. In practice, EAM_FAILURESETS_PUB and its private counterpart operate against the eAM failure set tables, principally the failure set header table and the failure set association table that link a failure set to the failure codes it contains. Writes to these tables maintain both the header record and the ordered parent-child relationships that define the hierarchy. All table access is performed through APPS synonyms, consistent with Oracle's schema separation between the APPS code layer and the underlying application tables.

Usage Notes

EAM_FAILURESETS_PUB is the supported entry point for any operation that creates or modifies failure sets or their associated failure codes: setup screens in the eAM responsibility, concurrent programs that load failure set data, and custom extensions or interfaces that populate failure sets from legacy or third-party systems. Direct DML against the underlying failure set tables is not supported and bypasses the validation and message handling implemented in the package.

Callers should initialise the FND message stack, supply a valid API version, commit explicitly after a successful return (the API does not commit internally unless documented), and always check x_return_status. The dependency listing shows the package is referenced by itself and by EAM_FAILURESETS_PVT, confirming the PUB-to-PVT delegation pattern. Because the PUB package is referenced by only one other package in the documented metadata, it should be treated as a foundational, low-level API that other eAM components and customer code build upon rather than one invoked indirectly through many layers.