Search Results set_search_name




Overview
Explore in AI Chat

Overview

FND_MSG_PUB is the Oracle E-Business Suite public message-handling package owned by APPS and classified as a PUB API. It provides the centralized mechanism by which every other EBS product, form, concurrent program, and custom extension manages the message stack exposed to users. Rather than hard-coding error text or populating fields directly, developers call FND_MSG_PUB to add, retrieve, count, reset, and format messages held in a session-level global table (G_msg_tbl). The package also applies the message-level profile option threshold, ensuring only messages at or above the site-configured severity are surfaced. Because it is the single funnel for user-facing diagnostics, it is referenced by 6,173 other packages, making it one of the most widely depended-upon APIs in the EBS application schema.

Key Procedures and Functions

  • INITIALIZE — Clears the global message table and resets its associated global variables; the message level threshold is preserved across the call. Typically invoked at the start of a transaction or form block.
  • COUNT_MSG — Returns the number of messages currently held in the global list (G_msg_count).
  • COUNT_AND_GET — Shortcut that counts messages and, when exactly one exists, retrieves it in a single call, avoiding a separate count, check, and fetch sequence. Supports encoded or translated output in the data buffer.
  • ADD — Appends a message to the global message table.
  • DELETE_MSG — Removes a message from the global list.
  • GET — Retrieves a message using direction constants (G_FIRST, G_NEXT, G_LAST, G_PREVIOUS) to navigate the stack.
  • RESET — Reinitializes message state, discarding accumulated messages.
  • CHECK_MSG_LEVEL — Compares a message against the level threshold profile option to determine whether it should be reported.
  • BUILD_EXC_MSG — Constructs a formatted exception message string.
  • ADD_EXC_MSG — Builds and adds an exception message to the stack in one operation.
  • DUMP_MSG and DUMP_LIST — Diagnostic utilities that output a single message or the entire message list, used for debugging.
  • ADD_DETAIL and GET_DETAIL — Manage supplementary detail text attached to a message.
  • NO_ALL_INCLUSIVE_ERROR, NO_EXCLUSIVE_ERROR, NO_ERROR_MESSAGE — Validation helpers that produce or suppress standard messages depending on inclusive/exclusive logic and whether an error exists.
  • SET_SEARCH_NAME, SET_SEARCH_TOKEN — Establish the search name and token context used when resolving messages.
  • CHANGE_MSG — Modifies an existing message already held in the global list, allowing its text or attributes to be adjusted in place before display.

Tables Accessed

The package reads the PLITBLM table (accessed through an APPS synonym), which stores the message repository that underlies the FND_MESSAGE infrastructure. Message definitions and translations are resolved from this table when a message is retrieved or encoded/decoded. All other state is held in memory within the G_msg_tbl global structure, so the package's database footpright is limited to message lookup rather than transactional data.

Usage Notes

FND_MSG_PUB is invoked primarily from Oracle Forms (via the FND Message libraries), from server-side PL/SQL in concurrent programs and APIs, and from custom code that needs to raise user-visible errors or warnings. The standard pattern is to call INITIALIZE, perform work while invoking ADD or ADD_EXC_MSG, then use COUNT_AND_GET or GET to surface the results. Developers searching for change_msg are typically looking to alter a message already on the stack — for example, customizing text before display — and should use CHANGE_MSG rather than re-adding a duplicate. Because it is a public API, direct DML against PLITBLM is discouraged; message changes should flow through the documented procedures to preserve encoding, translation, and level-threshold behavior.