Search Results get_encoded_msg

Overview

APPS.EAM_EXECUTION_JSP is a PL/SQL package belonging to the Oracle Enterprise Asset Management (EAM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its role is to support the execution-side Java Server Pages (JSP) user interface used by maintenance technicians and supervisors to record and manage work order execution activities. The package is compiled with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owner, which is typical of EAM packages designed for use across multiple application schemas and middle-tier JSP calls.

The package blends two categories of utility: organization resolution helpers and message-handling wrappers. Additionally, a block of global variables captures standard "WHO" audit columns — last updated by, created by, last update login, concurrent request ID, program application ID, and concurrent program ID — sourcing them from FND_GLOBAL at package initialization. These globals standardize audit stamping for records manipulated during EAM execution flows.

Key Procedures and Functions

• GetOrgId — Accepts an organization name and returns the corresponding organization ID. If no matching organization record exists, it returns NULL. The function carries a RESTRICT_REFERENCES pragma (WNDS, WNPS), confirming it does not write database state or package state.
• GetOrgName — The inverse of GetOrgId: accepts an organization ID and returns the organization name, or NULL when no matching record is found. It also carries the WNDS/WNPS pragma.
• to_time_string — A temporary utility that converts a DATE value into a formatted time string. The source comments explicitly label this as temporary.
• Get_Encoded_Msg — This is the object most directly associated with the user's search term "get_encoded_msg." As documented, it is a wrapper around the standard function FND_MSG_PUB.Get, provided specifically so that client Oracle Forms can invoke the message-retrieval call. It is implemented as a procedure rather than a function, which is the convention required for Forms-to-database invocation of encoded message retrieval.
• Get_Messages — A companion routine that retrieves a message set from the FND message stack and returns both the message data and an output message index. It supports an encoded flag and index/count inputs, allowing callers to walk the message stack one entry at a time.
• Add_Message — Records or registers a message, applied in the same message-handling context as the two procedures above.

Tables Accessed

The only table documented as referenced through APPS synonyms is DUAL. This is consistent with a utility package whose organization lookups and message operations are primarily delegated to underlying FND APIs and views. The organization-name and organization-ID conversions are logically resolved against organization definition data, but the ETRM metadata records only DUAL as a directly referenced table, indicating the package relies on external API calls or views for the substantive data access.

Usage Notes

Get_Encoded_Msg exists explicitly to bridge PL/SQL and Oracle Forms, so its primary invocation path is from EAM execution forms that need to display Oracle Applications-standard messages generated during transaction processing. The comments in the source confirm this intent, describing it as a wrapper needed to access FND_MSG_PUB.Get from client Forms.

GetMessages and Add_Message are typically used alongside FND_API-style error handling to accumulate and replay messages across an API call boundary, particularly where a JSP page or form must surface all errors and warnings from a multi-step operation. The message-encoding convention matches the standard EBS API pattern: messages are encoded into a single delimited string that the caller decodes using the message stack APIs.

The package is referenced by eight other packages within the EAM schema, underscoring its role as a shared internal utility rather than an end-user-facing API. Customizations should treat it as an internal implementation package; direct calls are viable but not supported as a public interface, and any custom code relying on Get_Encoded_Msg should mirror the standard FND message-handling pattern for forward compatibility across 12.1.1 and 12.2.2.