Search Results inv_all_sql_error




Overview
Explore in AI Chat

Overview

INV_MOBILE_HELPER_FUNCTIONS is a utility package body in the Oracle Inventory (INV) application, owned by the APPS schema. It provides shared error-handling, diagnostic tracing, and message-assembly routines consumed by Inventory mobile (handheld / RF) transaction processing and related PL/SQL modules. Its API classification is OTHER, reflecting a low-level helper role rather than a business-entity API. The package is referenced by 85 other packages, making it a widely used dependency within the Inventory stack, particularly for mobile receiving, picking, and move-order processing where consistent error reporting and stacked-message retrieval are required across many callers. The header comment ($Header: INVMTXHB.pls 120.1 2005/06/17) indicates the source file has been stable since 2005, and the same code ships in both EBS 12.1.1 and 12.2.2 with no functional change.

Key Procedures and Functions

The package exposes three documented procedures:

  • TRACELOG — Logs a diagnostic trace message. It reads the INV_DEBUG_TRACE profile option and only forwards messages to the consolidated INV_LOG_UTIL.TRACE API when tracing is enabled. Accepts a message, a module name, and a trace level (default 9).
  • SQL_ERROR — Formats and registers a standardized database error message. It uses FND_MESSAGE to build the INV/INV_ALL_SQL_ERROR message, setting tokens for the routine name, location, and the SQLERRM text for the supplied error code, then adds the message to the stack via FND_MSG_PUB.ADD. The exception handler swallows any failure so error reporting never masks the original error.
  • GET_STACKED_MESSAGES — Returns a single concatenated string of all pending FND messages, joining multiple messages with a pipe delimiter and truncating to 2000 characters, then deleting the message stack via FND_MSG_PUB.DELETE_MSG. This allows mobile callers to surface a complete error picture to the device or user.

Tables Accessed

The only documented referenced object is the UTL_FILE synonym (the Oracle PL/SQL file I/O built-in), declared as a global file type for optional file-based tracing. No Inventory base tables, interface tables, or FND tables are documented as directly read or written; message handling is performed through the FND_MESSAGE and FND_MSG_PUB APIs rather than direct SQL against message tables. The INV_DEBUG_TRACE profile option is read via FND_PROFILE.VALUE to gate trace output.

Usage Notes

This package is not invoked directly by end users or standard concurrent programs. It is called programmatically from other PL/SQL packages and mobile transaction APIs — as evidenced by its 85 referencing packages — typically from exception blocks where a failing DML or validation must produce a formatted, user-visible message. In EBS 12.1.1 and 12.2.2 the behavior is identical; the 12.2.2 online patching (adop) model does not alter the package's runtime semantics, though the file may be patched via ADPATCH when an Inventory patchset touches it. When diagnosing an unexpected "sql_err" message on a mobile screen, the INV_DEBUG_TRACE profile should be enabled to 1 to capture TRACELOG output, and the message text produced by SQL_ERROR should be correlated with the routine and location tokens it passes to FND_MESSAGE. Because GET_STACKED_MESSAGES deletes the message stack after retrieval, callers must persist or display the returned string before invoking any further FND message API.