Search Results eam_error_message_pvt




Overview
Explore in AI Chat

Overview

EAM_ERROR_MESSAGE_PVT is a private PL/SQL package body in the APPS schema that provides the centralized error handling and diagnostic messaging infrastructure for the Enterprise Asset Management (EAM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to capture, translate, store, retrieve, and expose error and informational messages generated by EAM business logic, particularly the work order processing APIs (EAM_PROCESS_WO_PUB and EAM_PROCESS_WO_PVT). The package acts as an EAM-specific layer built on top of the Oracle Application Object Library messaging framework (FND_MSG_PUB and FND_MESSAGE), allowing EAM transactions to register errors against a business object, attach tokens for contextual substitution, and later retrieve a consolidated message list for display in Forms, concurrent program logs, or OAF pages. Because it is classified as a PVT (private) package, it is not intended as a public integration API but rather as an internal service consumed by EAM processing routines.

Key Procedures and Functions

The documented ETRM metadata exposes 21 procedures and functions organized around message lifecycle management and debug tracing:

Tables Accessed

The metadata lists three referenced objects, all accessed through APPS synonyms rather than base tables: UTL_FILE, PLITBLM, and V$PARAMETER.

  • UTL_FILE — used by LOG_ERROR and WRITE_DEBUG to write diagnostic output to server-side files when a debug session is active.
  • PLITBLM — supplies the PL/SQL character-mapping facility supporting token substitution and text handling.
  • V$PARAMETER — typically queried to determine database parameters such as the user_dump_dest or background_dump_dest location used for debug file output.

Messages themselves are not persisted in EAM tables; they reside in the FND_MSG_PUB global message stack and in the package’s internal PL/SQL collections.

Usage Notes

EAM_ERROR_MESSAGE_PVT is invoked indirectly. The ETRM metadata records that it is referenced by 79 other database objects, and it is directly referenced by EAM_PROCESS_WO_PUB, EAM_PROCESS_WO_PVT, and ERROR_HANDLER. Typical call paths include work order and asset maintenance concurrent programs, EAM Forms, and service/OAF flows that call the EAM work order processing APIs. A caller normally executes INITIALIZE, invokes EAM business logic, then calls GET_MESSAGE_LIST or GET_ENTITY_MESSAGE to surface errors to the user or to the concurrent manager log. During troubleshooting, developers enable OPEN_DEBUG_SESSION so that LOG_ERROR and WRITE_DEBUG emit trace output to a UTL_FILE destination identified from V$PARAMETER. The package is not documented as being referenced by external applications, so custom code should prefer the public EAM APIs rather than calling EAM_ERROR_MESSAGE_PVT directly, as its signature is private and subject to change across patch levels.