Search Results build_exc_msg

Overview

PV_MSG_PUB is a public PL/SQL API belonging to the Oracle EBS Process Manufacturing (Process Manufacturing / OPM) message handling framework. It is owned by APPS and classified as a PUB interface in the ETRM 12.2.2 repository, meaning it is intended for direct invocation by external callers, concurrent programs, forms, and custom extensions. The package provides a centralized mechanism for accumulating, retrieving, filtering, and formatting error, warning, and informational messages generated during process manufacturing transactions.

The package manages a global in-memory message table (G_msg_tbl) that callers populate through the Add family of procedures and subsequently interrogate through the Get and Count routines. A message-level threshold profile option value is cached in the global variable G_msg_level_threshold, which governs whether a given message is retained based on its severity level. This design allows client APIs to build a complete message stack across multiple processing steps and then present the result to end users in a single, consolidated response.

Key Procedures and Functions

• Initialize — Clears the global message table and resets all associated global variables, with the exception of the message level threshold. API callers invoke this at the start of processing to guarantee a clean message state.
• Count_Msg — Returns the current count of messages held in the global message list.
• Count_And_Get — A convenience cover routine that calls Count_Msg and, when exactly one message exists, automatically retrieves that message. It reduces the calling sequence from count-check-get to a single invocation.
• Add — Appends a message to the global message table.
• Delete_Msg — Removes a previously stored message from the global message table.
• Get — Retrieves a message from the global table. Positional constants G_FIRST, G_NEXT, G_LAST, and G_PREVIOUS drive traversal through the message list. An encoded option controls whether the message is returned in raw encoded form or translated.
• Reset — Reinitializes message-related state, comparable in purpose to Initialize.
• Check_Msg_Level — Evaluates a message against the configured message level threshold to determine whether it should be surfaced.
• Build_Exc_Msg — Constructs a formatted exception message string from accumulated message data, typically for raising or displaying as a single concatenated error.
• Add_Exc_Msg — Adds an exception-oriented message entry to the global message table.
• Dump_Msg — Writes the contents of the message table for debugging and diagnostic purposes.
• Dump_List — Outputs the message list, supporting developer-level troubleshooting.

Thirteen documented entry points are exposed in total. The package is declared AUTHID CURRENT_USER.

Tables Accessed

The ETRM metadata documents a single underlying table reference: PLITBLM, accessed through APPS synonyms. This table stores message text and translation data consumed by the Get routine when translated output is requested (p_encoded set to FALSE). All other message state is maintained in PL/SQL global memory structures rather than persistent tables, which explains why the documented table footprint is minimal.

Usage Notes

PV_MSG_PUB is referenced by zero other packages in the ETRM repository, indicating that it is a leaf-level utility consumed directly by forms, concurrent programs, and custom code rather than by other public APIs. The canonical invocation pattern is: call Initialize, execute the business logic while calling Add or Add_Exc_Msg for each condition encountered, then call Count_And_Get or Count_Msg followed by Get to present results. When an exception must be raised, Build_Exc_Msg assembles the accumulated messages into a single displayable string. Developers should observe the encoded parameter on Get and Count_And_Get to control whether messages are returned translated for end-user display or left encoded for programmatic handling. Dump_Msg and Dump_List are intended strictly for development and diagnostic scenarios and should not appear in production execution paths.