Search Results write_to_interfacetable

Overview

APPS.ERROR_HANDLER is the centralized error capture, translation, and reporting utility for the Oracle Bills of Material (BOM) business object APIs. The package body is delivered from source file BOMBOEHB.pls and carries a header revision of 120.5.12020000.3, dated 07-MAR-2013, which is the version shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. Its core purpose is to accumulate errors and warnings raised during BOM open-interface and Bill of Material processing, map internal tokens to user-facing messages, and route those messages to the appropriate output destinations.

The package is classified as OTHER, not as a public API, and is referenced by 186 other packages, confirming that it functions as shared infrastructure rather than an application entry point. The global G_ERROR_TABLE declared as Error_Handler.Error_Tbl_Type is the in-memory repository for the message list, and the global G_MSG_INDEX / G_Msg_Count pair tracks cursor position and total message volume. A G_BO_IDENTIFIER default of 'BOM' scopes the default message set to the BOM business object.

Key Procedures and Functions

• INITIALIZE and RESET — establish and clear the session state of the error table and message counters before a processing run.
• GET_MESSAGE_LIST, GET_MESSAGE, GET_ENTITY_MESSAGE, GET_MESSAGE_COUNT — read accessors that return accumulated messages, entity-specific messages, and the current count.
• DELETE_MESSAGE, DUMP_MESSAGE_LIST — remove a specific message or emit the entire list for diagnostic purposes.
• OPEN_DEBUG_SESSION, CLOSE_DEBUG_SESSION, WRITE_DEBUG — manage the debug-flag driven trace facility (g_debug_flag defaults to 'N').
• WRITE_TO_INTERFACETABLE, WRITE_TO_CONCURRENTLOG, WRITE_TO_DEBUGFILE — output routing procedures that direct messages to the interface errors table, the concurrent manager log, or a debug file.
• LOG_ERROR — the primary error-logging entry point; the header history records its addition in the Routing BO enhancement.
• ADD_MESSAGE, ADD_ERROR_MESSAGE, TRANSLATE_MESSAGE, TRANSLATE_AND_INSERT_MESSAGES — append messages, translate stored tokens into language-specific text, and insert translated rows.
• ADD_ERROR_TOKEN — registers a token and its substitution values so that the final rendered message can be assembled later.

Tables Accessed

• MTL_INTERFACE_ERRORS — target of WRITE_TO_INTERFACETABLE; persists interface failures for downstream review.
• MTL_SYSTEM_ITEMS_INTERFACE_S — the BOM open-interface staging object against which item-level errors are recorded.
• UTL_FILE — used by the debug file writer to produce diagnostic output.
• PLITBLM — the PL/SQL message table underlying translation of Message_Name values into formatted text.
• V$PARAMETER — read to determine database configuration such as the NLS language environment during translation.

Usage Notes

ERROR_HANDLER is not invoked directly by end users. It is called by BOM open-interface concurrent programs, by the BOM business object APIs (Bom_Bo_Pub), and by custom PL/SQL that processes bills, routings, and components. Callers typically invoke INITIALIZE, loop over records issuing ADD_MESSAGE or LOG_ERROR, then call TRANSLATE_AND_INSERT_MESSAGES and one of the WRITE_TO_* procedures. Debug tracing is enabled through OPEN_DEBUG_SESSION and WRITE_DEBUG. Because it is referenced 186 times, changes to its behavior can affect a broad range of BOM-related flows in both 12.1.1 and 12.2.2.