Search Results enable_debug_pvt

Overview

IBE_UTIL is a utility package body in the APPS schema that supports the Oracle iStore (IBE) application family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its API classification is UTIL, indicating that it is not a public business API but rather an internal helper library consumed by other iStore and Oracle Applications modules. The package consolidates cross-cutting services that many iStore components require: runtime debug instrumentation, authorization and permission checks against the JTF security model, installation metadata retrieval, NLS-aware number formatting, temporary-table data staging, and phone number presentation formatting.

The package holds a VALID status in the ETRM dictionary and exposes eighteen documented procedures and functions. Dependencies include FND_API, FND_GLOBAL, FND_PROFILE, FND_USER, FND_NUMBER, FND_INSTALLATION, APP_EXCEPTION, ASO_DEBUG_PUB, OE_DEBUG_PUB, UTL_FILE, and the JTF authorization tables. Notably, IBE_UTIL is not referenced by any other database object according to the ETRM record, though its own dependency footprint is broad.

Key Procedures and Functions

The eighteen documented entry points fall into four functional groups.

• Debug instrumentation: FILE_DEBUG, ENABLE_FILE_DEBUG, DISABLE_FILE_DEBUG, DEBUG, ENABLE_DEBUG, ENABLE_DEBUG_NEW, ENABLE_DEBUG_PVT, DISABLE_DEBUG, DISABLE_DEBUG_NEW, RESET_DEBUG, and DISABLE_DEBUG_PVT. These govern message logging, allowing developers to route diagnostic output to a file via UTL_FILE or to the standard debug stream, to toggle debug on and off at session or package level, and to reset debug state between operations. The private (PVT) variants support internal enable/disable logic invoked by the public wrappers.
• Environment and authorization: GET_INSTALL_INFO retrieves installation-level metadata using FND_INSTALLATION. CHECK_JTF_PERMISSION and CHECK_USER_PERMISSION validate whether the current user holds a required permission or is known to the application, drawing on the JTF authorization tables and FND_USER.
• Utility formatting and staging: NLS_NUMBER_FORMAT renders numeric values using the session's NLS conventions. FORMAT_PHONE standardizes telephone number presentation. INSERT_INTO_TEMP_TABLE and DELETE_FROM_TEMP_TABLE manage rows in the IBE_TEMP_TABLE staging area used to hold intermediate result sets.

Tables Accessed

Via APPS synonyms, IBE_UTIL reads FND_USER and HZ_PARTIES for identity context, and the JTF authorization set — JTF_AUTH_DOMAINS_B, JTF_AUTH_PERMISSIONS_B, JTF_AUTH_PRINCIPALS_B, JTF_AUTH_PRINCIPAL_MAPS, and JTF_AUTH_ROLE_PERMS — to resolve roles, permissions, and principal mappings during permission checks. IBE_TEMP_TABLE is written and read for transient data staging. UTL_FILE is used to support file-based debugging output. The documented dependency list additionally names FND_API, FND_GLOBAL, FND_PROFILE, FND_NUMBER, FND_INSTALLATION, APP_EXCEPTION, ASO_DEBUG_PUB, and OE_DEBUG_PUB as referenced package dependencies.

Usage Notes

Because IBE_UTIL is classified as a utility package and is not referenced by other database objects, it is primarily invoked from PL/SQL code paths internal to iStore — forms, concurrent programs, and other iStore packages that need debug toggling, permission validation, or formatting support. Customizations should treat these routines as internal helpers rather than supported public APIs. Debug-enabled calls should be used only during troubleshooting because they add logging overhead and may require file system privileges for UTL_FILE.