Search Results g_debug_level_medium




Overview
Explore in AI Chat

Overview

JTM_HOOK_UTIL_PKG is a shared utility package in the Oracle E-Business Suite APPS schema that supports the Oracle TeleSales / Field Service (JTM) family of applications. Its responsibilities are twofold: it provides a standardized debug and logging framework used by dependent packages throughout the module, and it supplies common lookup and maintenance routines for application context (ACC) records and resource resolution. The package is installed as a specification-only interface in the form shown (header revision 120.1, 2005), and it is referenced by sixty-one other packages, which makes it one of the more widely consumed utility artifacts in the JTM codebase.

The debug framework is exposed through a discrete set of numeric constants. Level 0 suppresses all output, level 1 logs errors only, level 2 adds functional and replication messages, level 3 adds SQL statements, and level 4 provides full debug output including procedure entry and exit tracing. The constant g_debug_level_full is the highest of these and corresponds to the value 4.

Key Procedures and Functions

ETRM documents twelve callable units in this package, of which the principal ones are described below. Parameter lists are intentionally omitted here; the documented signatures run to as many as fourteen arguments for the ACC routines.

  • GET_DEBUG_LEVEL — Returns the currently effective debug level as a number. Callers use the returned value to decide whether to emit error, informational, or SQL trace messages, comparing it against the g_debug_level_* constants.
  • ISMOBILEFSRESOURCE — Accepts a resource identifier and returns a Boolean indicating whether that resource represents a mobile Field Service or laptop resource. This is used to branch behavior for disconnected or field-based users.
  • GET_RESOURCE_ID — Resolves and returns the resource identifier associated with a supplied client name.
  • GET_USER_ID — Resolves and returns the FND user identifier associated with a supplied client name.
  • GET_ACC_ID — Retrieves the ACC identifier for a given ACC table, resource, and up to three primary key columns whose values may be numeric, character, or date typed. This general-purpose key handling allows the routine to serve many ACC tables.
  • UPDATE_ACC and DELETE_ACC — Maintain application context records, updating or removing entries identified through the same flexible primary-key convention used by GET_ACC_ID.
  • Additional documented units support publication item list typing and related internal helpers.

Tables Accessed

The package works against several APPS synonyms. FND_USER and ASG_USER provide user identity resolution, while ASG_USER_PUB_RESPS supplies publication responsibility data used to determine which publication items a user or resource may access. JTF_RS_RESOURCE_EXTNS is the resource extension table consulted by the resource and mobile-resource routines. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES are read to derive profile-driven behavior, including debug level settings. PLITBLM is used for PL/SQL index-by table handling, and DBMS_SQL is referenced for dynamic SQL execution against ACC tables whose names and key columns are supplied at runtime.

Usage Notes

This package is not an end-user-facing API. It is invoked from other PL/SQL packages, from Oracle Forms-based JTM screens, and from concurrent programs that require consistent logging or ACC lookup. The most common pattern involves calling GET_DEBUG_LEVEL once and caching the result, then comparing it to g_debug_level_full or the lower constants to gate diagnostic output. Because sixty-one packages depend on it, changes to the package specification should be treated as high-impact; new overloads are safer than signature changes. Debug output should be enabled only in non-production environments or during targeted troubleshooting, since level 4 tracing carries measurable performance cost.