Search Results get_msg_context

Overview

APPS.OE_MSG_PUB is the public message-handling API for the Oracle Order Management (OM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a centralized, in-memory repository through which Order Management APIs, forms, concurrent programs, and external integration code accumulate, retrieve, persist, and display validation and processing messages. Rather than returning errors directly, Order Management APIs write messages into the OE_MSG_PUB context; the calling program then retrieves them in a controlled sequence (first, next, last, previous) using the G_FIRST, G_NEXT, G_LAST, and G_PREVIOUS global constants. A message-level threshold, held in G_msg_level_threshold and derived from a profile option, allows callers to filter messages by severity. Because the package declares AUTHID CURRENT_USER and runs under the APPS schema, it operates with the privileges of the connected user while relying on APPS synonyms for its underlying tables.

The package also manages message context. The record type G_MSG_CONTEXT_REC_TYPE captures the entity, order header, line, order source, original system document references, shipment references, change sequence, attribute, constraint, and processing activity associated with each message. A PL/SQL table of this record type, G_msg_context_tbl, together with G_msg_context_count and G_msg_context_index, holds the context stack used to scope messages to the correct transactional entity during nested processing.

Key Procedures and Functions

• INITIALIZE — Initializes the package state, clearing the message and context collections before a new processing cycle.
• ADD / ADD_TEXT — Appends a message or free-text message to the in-memory message store.
• COUNT_MSG / COUNT_AND_GET — Returns the number of messages currently held, optionally retrieving messages as they are counted.
• GET / RESET — Retrieves a message according to the requested position (first, next, last, previous) and resets package state.
• DELETE_MSG — Removes an individual message from the collection.
• SET_PROCESS_ACTIVITY — Assigns the processing activity identifier associated with subsequent messages.
• SET_MSG_CONTEXT / RESET_MSG_CONTEXT / UPDATE_MSG_CONTEXT / GET_MSG_CONTEXT — Manage the message context stack, establishing, replacing, reading, or clearing the entity, header, line, and source document references that qualify messages.
• CHECK_MSG_LEVEL — Evaluates a message against the configured level threshold to determine whether it should be surfaced to the caller.
• BUILD_EXC_MSG / ADD_EXC_MSG — Construct and append exception messages derived from Oracle errors.
• DUMP_MSG / DUMP_LIST — Emit the accumulated messages for debugging and diagnostics.
• SAVE_MESSAGES / INSERT_MESSAGE — Persist the in-memory messages into the Order Management processing message tables.

Tables Accessed

OE_MSG_PUB reads and writes OE_PROCESSING_MSGS and OE_PROCESSING_MSGS_TL, the base and translated message tables that store persisted Order Management messages. It obtains the next message identifier from the sequence OE_MSG_ID_S. Validation and lookup logic references OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL to confirm header and line context, and FND_NEW_MESSAGES, FND_APPLICATION, and FND_LANGUAGES for message text and multilingual resolution. It also references DUAL, the PL/SQL table type PLITBLM, and DBMS_SQL for dynamic processing. All references are made through APPS synonyms.

Usage Notes

OE_MSG_PUB is invoked from Order Management forms, concurrent programs, and custom PL/SQL integration code whenever Order Management APIs are called and their messages must be captured. A typical cycle calls INITIALIZE, sets the processing activity and message context, invokes the OM business API, then loops through GET or COUNT_AND_GET to read messages, filtering by CHECK_MSG_LEVEL and persisting them with SAVE_MESSAGES. GET_MSG_CONTEXT is the accessor used to read the current context record, which is essential when messages span multiple headers or lines in a single processing run. Because the package is referenced by 482 other packages, modifications to its behavior have broad impact and should be validated against all dependent Order Management flows.