Search Results oe_msg_id_s




Overview
Explore in AI Chat

Overview

APPS.OE_BULK_MSG_PUB is a public PL/SQL package in the Oracle Order Management (OE) module that provides a centralized, bulk-oriented message stack for Order Management processing. Rather than raising individual messages at each point of failure or validation during order import, order capture, or processing, callers accumulate messages in an in-memory PL/SQL collection (g_msg_tbl) that can be flushed, retrieved, or archived as a set. This design supports high-volume Order Management flows where hundreds or thousands of messages may be generated per batch, and where the overhead of immediate, per-message error handling is prohibitive.

The package is classified as public (API classification PUB) and is owned by APPS. It is referenced by 18 other Oracle EBS packages, making it a foundational utility within the Order Management message infrastructure. In the 12.1.1 and 12.2.2 code lines the package body (OEBUMSGB.pls) is stable, and its collection is heavily denormalized: each stack entry carries message text, entity identifiers (header, line, shipment references), source document references, attribute and constraint identifiers, processing activity, notification flag, and change sequence. This wide row shape allows downstream consumers to reconstruct exactly which order, line, or source document triggered a message and in which processing activity.

Key Procedures and Functions

  • INITIALIZE — Sets up the package state, including any global message table and context globals, prior to message accumulation.
  • SET_PROCESS_ACTIVITY — Records the current processing activity into the message context. This is the procedure most commonly associated with the search term "set_process_activity," and it tags subsequently collected messages with the activity (for example, an order import or processing phase) that produced them.
  • SET_MSG_CONTEXT / RESET_MSG_CONTEXT / UPDATE_MSG_CONTEXT — Manage the contextual attributes (entity, document, or activity identifiers) applied to messages as they are added.
  • COUNT_MSG / COUNT_AND_GET — Report the number of stacked messages; COUNT_AND_GET returns the count and populates an OUT collection.
  • ADD / ADD_TEXT — Append a new message (ADD) or append descriptive text (ADD_TEXT) to the stack.
  • ADD_EXC_MSG / BUILD_EXC_MSG — Add and construct exception-derived messages, integrating PL/SQL error handling into the stack.
  • GET — Retrieves stacked messages into output structures for inspection or persistence.
  • DELETE_MSG — Removes messages from the stack, either selectively or in full.
  • RESET — Clears the stack and context, restoring the package to an initial state.
  • CHECK_MSG_LEVEL — Evaluates the configured message severity or level to control whether processing continues or aborts.
  • DUMP_MSG / DUMP_LIST — Emit the stack contents for diagnostic and debugging output.
  • SAVE_MESSAGES — Persists stacked messages to the OE_PROCESSING_MSGS repository.
  • TRANSFER_MSG_STACK — Moves or merges messages between stack instances, supporting nested or delegated processing.

Tables Accessed

  • OE_PROCESSING_MSGS — The primary persistence target for SAVE_MESSAGES, storing processed messages for later inquiry and reconciliation.
  • OE_MSG_ID_S — Sequence used to generate unique message identifiers.
  • FND_NEW_MESSAGES — Oracle Application Object Library messages used to resolve message names and text.
  • FND_APPLICATION — Application registration data used to resolve application context.
  • PLITBLM — The standard Applications generic character table (used for resolving message text and related lookups).

Usage Notes

OE_BULK_MSG_PUB is typically invoked from Order Management processing code rather than directly from end-user forms. Because it is referenced by 18 packages, callers usually INITIALIZE the stack, SET_PROCESS_ACTIVITY and related context once per processing phase, ADD or ADD_EXC_MSG messages as issues arise, query the stack with COUNT_MSG or CHECK_MSG_LEVEL, and finally SAVE_MESSAGES to OE_PROCESSING_MSGS. Custom code extending Order Import or Order Management processing should follow the same pattern, calling SET_PROCESS_ACTIVITY before adding messages so that each message carries an accurate activity tag. Because the collection is a package global, it is not session-safe across concurrent contexts; callers should RESET the stack between logical batches. In 12.1.1 and 12.2.2 the package is unchanged in behavior, and it remains the recommended public interface for bulk message handling in Order Management customizations.