Search Results psp_message_s




Overview
Explore in AI Chat

Overview

PSP_MESSAGE_S is a server-side PL/SQL package body in the APPS schema that provides a centralized message-handling utility for Oracle E-Business Suite components belonging to the Payables and Payments product family (the PSP prefix). Its business function is to standardize how application code stores, retrieves, and displays informational and error messages to the end user. Rather than embedding literal text or ad-hoc exception handling in every business process, dependent packages call PSP_MESSAGE_S to register a message together with a success or error context, and later to fetch that message for display in a form, a concurrent program log, or a notification. The object is documented in ETRM as object type PACKAGE BODY, owner APPS, status VALID, with an API classification of OTHER. This classification indicates that the package is intended primarily for internal consumption within the EBS application stack rather than as a publicly supported extension API, though it remains a stable and widely reused utility.

Key Procedures and Functions

The package body exposes six documented procedures and functions. Together they form a simple register-then-retrieve pattern for messages.

  • GET — Retrieves a stored message value, serving as the base accessor for message content registered by callers.
  • INSERT_ERROR — Registers an error condition and its associated message text so it can be surfaced later through the standard EBS messaging stack.
  • PRINT_ERROR — Writes the current error message to the output destination (for example, the concurrent manager log or a report), providing a consistent error-reporting format.
  • PRINT_SUCCESS — Writes the success message to the same output destination, completing the informational side of the message lifecycle.
  • GET_ERROR_MESSAGE — Returns the currently held error message, allowing calling code to inspect or relay it.
  • GET_SUCCESS_MESSAGE — Returns the currently held success message for the same purpose.

No parameter lists are reproduced here; the names and purposes above reflect the documented procedure inventory.

Tables Accessed

The ETRM metadata for this package body does not list any directly referenced application tables. This is consistent with a utility whose persistence and message formatting are delegated to the Oracle Application Object Library. PSP_MESSAGE_S references FND_MESSAGE, FND_MSG_PUB, FND_API, and FND_FILE rather than base tables, using these APIs to manage the message dictionary and the FND message stack. Any persistent message definitions reside in the FND message tables maintained by FND_MSG_PUB and FND_MESSAGE, not in a dedicated PSP table.

Usage Notes

PSP_MESSAGE_S depends on FND_API, FND_FILE, FND_MESSAGE, and FND_MSG_PUB, all core EBS application foundation packages, and on the STANDARD package supplied by SYS. These dependencies explain its role: it prepares message text through the message dictionary, propagates it onto the FND message stack, and emits it to concurrent output via FND_FILE. According to ETRM, the package body is referenced by seventeen other packages, confirming that it is invoked broadly across the PSP product family rather than from a single entry point. It is not referenced by any database object outside those packages, and it is not designed to be called directly from a form or via a public interface. In practice, developers and support personnel encounter it indirectly — as the messaging layer behind payment and payables processes, concurrent programs, and error notifications. Custom extensions should call the supported FND messaging APIs directly rather than depending on this internal utility, since it is classified as OTHER and offers no public API guarantee.