Search Results add_sql_error

Overview

FA_SRVR_MSG is a server-side message-handling utility package in the Oracle E-Business Suite Fixed Assets (OFA) module. Its principal business function is to provide a standardized, centralized mechanism for constructing, stacking, and retrieving user-facing messages generated during Fixed Assets server-side processing. Rather than allowing individual packages to build error text ad hoc, FA_SRVR_MSG centralizes the interaction with the Oracle Application Object Library message dictionary (FND_MESSAGE) and the FND logging framework. This ensures consistent message formatting, uniform severity classification, and coherent error stacks that are surfaced to the user through the Fixed Assets forms and concurrent managers.

The package is deeply embedded in the Fixed Assets technical stack: the documented metadata indicates it is referenced by 189 other packages, confirming its role as a foundational infrastructure component rather than an end-user feature. Its particular relevance to the search term add_sql_error stems from the ADD_SQL_ERROR procedure, which is the designated entry point for capturing unexpected Oracle database errors and pushing them onto the message stack alongside a translated message from the message dictionary.

Key Procedures and Functions

• INIT_SERVER_MESSAGE — Initializes the server-side message stack, establishing a clean state before Fixed Assets processing begins. Internally it delegates to FND_MSG_PUB.INITIALIZE.
• RESET_SERVER_MESSAGE — Resets the message stack so that stale messages from prior processing are discarded. It likewise calls FND_MSG_PUB.INITIALIZE.
• ADD_SQL_ERROR — Captures an Oracle database error (SQLERRM) and adds it to the stack. It resets the global FA_ERROR_LEVEL to 1, loads the seeded message FA_SHARED_ORACLE_ERR from the OFA application with the ORACLE_ERR token bound to SQLERRM, conditionally writes an UNEXPECTED-level entry to the FND log, adds the message to the stack via FND_MSG_PUB.ADD, and records the calling function name for traceability.
• ADD_MESSAGE — The general-purpose message-stacking routine. It accepts a calling function name plus an optional message name and up to two token/value pairs, allowing callers to compose messages from the message dictionary or from literal tokens.
• GET_MESSAGE — Retrieves messages previously placed on the stack, supporting the presentation layer in surfacing accumulated errors.
• SET_MESSAGE_LEVEL — Establishes or adjusts the message severity level used when messages are added, aligning logging and user-visible severity.
• DUMP_API_MESSAGES — Emits the contents of the API message stack, typically for diagnostic purposes.
• WRITE_MSG_LOG — Writes message information to the FND log, integrating stack activity with the standard logging infrastructure.

Tables Accessed

The documented metadata lists no direct table references through APPS synonyms. In practice, FA_SRVR_MSG does not perform conventional DML against Fixed Assets business tables. Its data interactions occur through the AOL message dictionary (FND_MESSAGE) and the FND logging tables, which are managed by the FND_MESSAGE and FND_LOG APIs it invokes. The message text for ADD_SQL_ERROR is sourced from the seeded message FA_SHARED_ORACLE_ERR registered under the OFA application in the message dictionary.

Usage Notes

FA_SRVR_MSG is invoked from Fixed Assets PL/SQL packages, forms, and concurrent programs whenever server-side processing must report status, warnings, or errors to the user. A typical pattern is for a processing package to call INIT_SERVER_MESSAGE at the outset, perform its work, invoke ADD_SQL_ERROR inside exception handlers to capture SQLERRM, and then retrieve results through GET_MESSAGE. Because the package is referenced by 189 other packages, customizations that call it should preserve its calling conventions and avoid modifying the shared message stack outside the supported API surface. The global variables for logging levels, print-debug flag, and release number tie the package's behavior to the runtime logging configuration and the current Fixed Assets schema release, as reflected in the conditional logging guard in ADD_SQL_ERROR.