Search Results add_warning

Overview

APPS.INV_ITEM_MSG is a shared message-handling and error-logging utility package used throughout the Oracle Inventory item interfaces in Oracle E-Business Suite 12.1.1 and 12.2.2. It is not a business API in the conventional sense; rather, it provides a centralised repository for the constants, message-level definitions, and helper routines that the item interface programs use to record, accumulate, and report validation and error conditions. The package is declared with AUTHID CURRENT_USER, so its unqualified references resolve against the calling schema's privileges, and it exposes a set of public constants — including g_MISS_CHAR, g_MISS_NUM, g_MISS_DATE, g_YES, g_NO, and the message-level values g_Level_Error, g_Level_Warning, g_Level_Event, g_Level_Procedure, g_Level_Statement, and g_Level_Unexpected — that standardise how the interface programs signal missing values, boolean flags, and severity.

The user search term g_next relates directly to a group of constants declared in the package specification: G_FIRST (-1), G_NEXT (-2), G_LAST (-3), and G_PREVIOUS (-4). These values are consumed by the WRITE_MESSAGE procedure (and its sibling WRITE_LIST) to control navigation through an accumulated message list. G_NEXT therefore instructs the package to advance to and emit the next message in the sequence, as opposed to G_FIRST, G_LAST, or G_PREVIOUS, which select the beginning, end, or preceding entry respectively.

Key Procedures and Functions

The documented interface comprises sixteen entry points. INITIALIZE and INITIALIZE_ERROR_HANDLER establish the package's session state and prepare the error stack. SET_MESSAGE_LEVEL and SET_MESSAGE_MODE govern which severity thresholds are captured and how messages are presented. ADD_MESSAGE, ADD_ERROR, ADD_WARNING, and ADD_UNEXPECTED_ERROR insert entries into the internal message collection at the appropriate severity, allowing callers to accumulate multiple problems before emission. DEBUG writes diagnostic output subject to the active message level. COUNT_MSG and COUNT_AND_GET report the size of the accumulated collection and retrieve its contents. WRITE_MESSAGE and WRITE_LIST emit buffered messages to the caller, with WRITE_MESSAGE accepting a navigation directive — the g_FIRST / g_NEXT / g_LAST / g_PREVIOUS constants — to walk the list. GET supplies access to stored message attributes. The Msg_Ctx_type record, holding Package_Name and Procedure_Name, allows each message to be attributed to its originating program unit.

Tables Accessed

Through APPS synonyms the package references MTL_INTERFACE_ERRORS, MTL_SYSTEM_ITEMS_INTERFACE_S, and PLITBLM. MTL_INTERFACE_ERRORS is the persistent landing table for item interface validation failures and is the natural target when accumulated errors are flushed. MTL_SYSTEM_ITEMS_INTERFACE_S is the interface staging table against which the item programs validate, and PLITBLM is the PL/SQL table-backed storage used internally for buffering the message list. The global g_Table_Name and g_Organization_Id variables indicate the package records the table and inventory organisation context for logged interface errors.

Usage Notes

INV_ITEM_MSG is typically invoked from the Inventory item interface concurrent programs (such as the Item Import and related open-interface workers) and from any custom PL/SQL that needs to report errors in the same format. Callers initialise the handler, add errors or warnings as validation proceeds, then iterate with WRITE_MESSAGE / WRITE_LIST using the g_* navigation constants to surface results. The package is referenced by eleven other packages, confirming its role as a shared, low-level utility rather than an application-facing API. Because it also stores session globals such as g_User_id, g_Login_id, g_Request_id, g_Prog_id, and g_Prog_appid, it should be initialised once per run before any logging call is made.