Search Results eam_execution_jsp




Overview
Explore in AI Chat

Overview

EAM_EXECUTION_JSP is a PL/SQL package body owned by the APPS schema that supports the Oracle Enterprise Asset Management (EAM) work execution functionality exposed through the EAM self-service JSP-based user interface. In Oracle EBS 12.1.1 and 12.2.2, EAM provides maintenance organizations with the ability to create, schedule, and execute work orders against assets. The execution portion of that flow — where a technician or maintenance user navigates eAM work order and operation screens in a browser — relies on server-side JavaServer Page logic that in turn calls back into PL/SQL helper packages such as this one. EAM_EXECUTION_JSP therefore acts as a server-side utility layer that supplies the JSP front end with organization context, message text, and other supporting data required to render and validate the execution pages.

The package is classified as OTHER in the ETRM API classification, indicating it is not a published public API intended for customer extension, but rather an internal implementation dependency of the EAM execution UI. Its status is VALID, and it is referenced by eight other database objects while itself depending on standard EBS foundation packages.

Key Procedures and Functions

Six documented procedures and functions are defined in the package body:

  • GETORGID — Retrieves the organization identifier used to scope the EAM execution context. This allows the JSP layer to determine which maintenance organization's data should be displayed.
  • GETORGNAME — Returns the descriptive name of the organization, typically for display on the execution page header or selection context.
  • TO_TIME_STRING — Converts a time value into a formatted string representation suitable for presentation in the JSP user interface.
  • GET_ENCODED_MSG — Produces an encoded form of a message, used to convey message text safely through the web layer.
  • GET_MESSAGES — Retrieves pending or accumulated messages, most likely from the FND message stack, for display to the user.
  • ADD_MESSAGE — Adds a message to the message stack or collection so that it can subsequently be surfaced by GET_MESSAGES.

These routines together form the plumbing that connects JSP presentation logic to the EBS message and organization frameworks. No parameter lists are documented here, and none should be assumed.

Tables Accessed

The documented table reference for this package is limited to DUAL via an APPS synonym, which is consistent with utility routines that evaluate expressions, perform lookups, or normalize values rather than querying business data directly. Organization information is obtained indirectly through the dependency on HR_ORGANIZATION_UNITS, which supplies the organization units used by GETORGID and GETORGNAME. Message handling is delegated to the FND foundation packages — FND_MESSAGE and FND_MSG_PUB — rather than through direct table access.

Usage Notes

EAM_EXECUTION_JSP is invoked from the EAM self-service JSP execution flow and is not intended to be called directly from SQL*Plus or custom concurrent programs. Its dependencies on FND_API, FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB indicate that it relies on the standard EBS application context (initialized via FND_GLOBAL) and the standard message dictionary. Because it is referenced by eight other packages and references none of its own callers, it functions as a lower-level helper in the EAM execution call stack. Customizations should avoid modifying this package body; instead, the supported approach is to extend behavior through the documented EAM and FND public APIs. Administrators troubleshooting EAM work execution screens may encounter this package when tracing message rendering or organization context errors.