Search Results oe_bulk_msg_pub




Overview
Explore in AI Chat

Overview

OE_BULK_MSG_PUB is a public PL/SQL package in the APPS schema that provides the message-handling framework for Oracle Order Management's bulk order import and processing infrastructure. Its central purpose is to accumulate, manage, and persist the diagnostic, warning, and error messages generated as the bulk processing engine validates, defaults, prices, schedules, and imports order data. Rather than allowing each processing utility to write messages independently, OE_BULK_MSG_PUB supplies a controlled API through which all stages of bulk processing register messages against a message stack, and subsequently retrieve or save them to the database for user review. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as a PUBLIC API (API classification: PUB), indicating that it is intended for supported external invocation as well as internal use by the Order Management application.

Key Procedures and Functions

The documented interface exposes twenty procedures and functions. The initialization and lifecycle routines — INITIALIZE, SET_PROCESS_ACTIVITY, SET_MSG_CONTEXT, RESET_MSG_CONTEXT, and UPDATE_MSG_CONTEXT — establish and manage the message context for the session or processing activity, binding messages to the appropriate request, process, or entity. COUNT_MSG and COUNT_AND_GET provide count and retrieval operations over the collected messages. The core collection routines are ADD, ADD_TEXT, and ADD_EXC_MSG, which register messages and free-text entries onto the stack. BUILD_EXC_MSG constructs an exception message payload, typically for use when raising or logging API-level errors. GET, RESET, DELETE_MSG, and CHECK_MSG_LEVEL manage retrieval, clearing, deletion, and severity-level interrogation of the accumulated stack. DUMP_MSG and DUMP_LIST provide diagnostic output of the message set, while SAVE_MESSAGES persists the accumulated stack to the database and TRANSFER_MSG_STACK moves messages between contexts. The package design follows the standard Oracle FND_API error-handling conventions, consistent with its documented dependency on APPS.FND_API.

Tables Accessed

OE_BULK_MSG_PUB references several tables through APPS synonyms. OE_PROCESSING_MSGS is the principal persistent store, holding the messages generated during a bulk processing run; SAVE_MESSAGES writes to this table and GET, COUNT_MSG, and DELETE_MSG read or purge from it. OE_MSG_ID_S is the sequence supplying surrogate message identifiers. FND_NEW_MESSAGES, a Foundation (FND) repository for message definitions and translations, is consulted to resolve message names and text. FND_APPLICATION is used to resolve the owning application identifier for message lookups. PLITBLM is an Oracle-supplied PL/SQL table type used internally for managing collections of message data.

Usage Notes

The package is invoked almost exclusively within the server-side bulk processing flow rather than directly from a form. It is used by Order Import concurrent programs and the bulk processing APIs, and by the wider set of Order Management utilities: the documented references include OE_BULK_ACK_PVT, OE_BULK_ORDER_IMPORT_PVT, OE_BULK_ORDER_PVT, OE_BULK_VALIDATE, OE_BULK_PRICE_PVT, OE_BULK_TAX_UTIL, OE_BULK_HOLDS_PVT, and OE_BULK_WF_UTIL, among a total of eighteen referencing packages. Custom code extending bulk order import should likewise call this API to register messages so that diagnostics appear through the standard Order Management message interface. Messages saved via SAVE_MESSAGES are surfaced to users through the Order Management message and error reporting views, making this package the single point of control for bulk processing feedback.