Search Results create_failureset

Overview

APPS.EAM_FAILURESETS_PUB is the public application programming interface for managing Enterprise Asset Management (EAM) failure sets and their associations within Oracle E-Business Suite Releases 12.1.1 and 12.2.2. A failure set is a reusable collection of failure codes that can be linked to an asset, an asset group, or a maintenance work order so that technicians and planners can record standardized failure information during inspection, condition monitoring, and corrective maintenance activities.

The package is a thin public wrapper. It exposes a stable, versioned API surface and delegates all validation and data manipulation to the corresponding private package, EAM_FailureSets_PVT. The public layer performs standard Oracle Application Framework API housekeeping: call-compatibility checking through FND_API.Compatible_API_Call, message list initialization through FND_MSG_PUB.initialize, savepoint definition, message count retrieval, and rollback handling on unexpected errors. The header identifies the source as EAMPFSPB.pls, version 120.0, last revised 08-Mar-2006.

Key Procedures and Functions

The package declares five documented procedures, reflecting two distinct functional groupings: failure set definition and failure set association.

• CREATE_FAILURESET — Creates a new failure set record. The public procedure accepts the standard EAM API parameters (API version, initialization flag, commit flag, and a failure set record typed as EAM_FailureSets_PUB.eam_failureset_rec_type) and returns status, message count, message data, and the newly generated failure set identifier. Internally it invokes EAM_FailureSets_PVT.Setup_FailureSet with an action code of 'C' and passes the generated identifier back to the caller.
• UPDATE_FAILURESET — Modifies the attributes of an existing failure set. It mirrors the create procedure but operates on a failure set that already exists, delegating to the private package for validation and update logic.
• CREATE_ASSOCIATION — Establishes a link between a failure set and its target entity. This is the procedure that makes a failure set usable against a specific asset, asset group, or work order context.
• UPDATE_ASSOCIATION — Modifies the attributes of an existing failure set association, such as its effective dates or enabled status.
• DELETE_ASSOCIATION — Removes an existing failure set association. This is the procedure most frequently referenced in integration and decommissioning scenarios, because it allows an association to be detached without deleting the underlying failure set or its failure codes.

Tables Accessed

The ETRM metadata for this release does not enumerate the base tables accessed through APPS synonyms. Based on the functional scope of the API, the package operates on the EAM failure set definition and association tables, including the failure set header, the failure set line or code detail, and the association table that links a failure set to an asset, asset group, or work order context. The public package itself does not issue direct SQL; all inserts, updates, and deletes are executed by EAM_FailureSets_PVT against these tables.

Usage Notes

EAM_FAILURESETS_PUB is invoked when failure set data must be created or maintained programmatically rather than through the EAM HTML or forms user interface. Typical callers include Oracle-supplied and customer-developed integration routines, conversion programs that load legacy failure code hierarchies, and other PL/SQL packages that need to attach a failure set to an asset or work order. The API classification of PUB means it is the supported entry point; callers should never invoke EAM_FailureSets_PVT directly.

Standard calling conventions apply. Callers pass a compatible p_api_version and should set p_init_msg_list to FND_API.G_TRUE when a clean message stack is required. Commit control is transactional: the API does not implicitly commit unless p_commit is set to FND_API.G_TRUE, so callers can group failure set creation and association into a single logical unit of work. Because DELETE_ASSOCIATION is the only documented deletion procedure, removing a failure set itself is not exposed through this public API; detaching associations is the supported mechanism for retiring a failure set from active use. The package is referenced by one other package, indicating a small dependency footprint and limited internal coupling.