Search Results get_user_role

Overview

APPS.AHL_UTIL_PKG is the core utility package body within the Oracle E-Business Suite Enterprise Asset Management (EAM) and Asset Lifecycle (AHL) application family. It consolidates miscellaneous helper routines that are required across the AHL product modules, providing standardized services for message translation, profile and installation checks, user-role resolution, and EAM/WIP class type retrieval. The package body is classified as OTHER in the ETRM metadata, indicating it is a general-purpose library rather than a business API with a formal API-level contract. It resides in the APPS schema and is documented as VALID in both EBS 12.1.1 and 12.2.2.

The body depends on several Oracle Application Object Library components, including FND_API, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, and FND_FUNCTION, as well as AHL_DEBUG_PUB and WIP_CONSTANTS. These dependencies confirm that AHL_UTIL_PKG acts as a bridge between the AHL application logic and the standard EBS foundation layer, leveraging the FND message stack and profile infrastructure rather than reimplementing that functionality.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• ERR_MESG_TO_TABLE — Transfers error messages from the FND message stack into an internal table structure so that callers can process, display, or forward them in bulk.
• IS_PM_INSTALLED — Determines whether Oracle Preventive Maintenance (PM) is installed in the current environment, allowing AHL logic to branch on the presence of that module.
• GET_APPLN_USAGE — Returns usage information for the application, typically used to confirm the operating context or feature-usage configuration.
• GET_USER_ROLE — Resolves the role associated with the current user, supporting role-based behavior and access decisions.
• GET_WIP_EAM_CLASS_TYPE — Retrieves the WIP/EAM class type, enabling AHL asset logic to align with work-in-process EAM class definitions held in WIP_CONSTANTS.
• GET_MESSAGE_STRING — Returns the formatted text for a message, typically by interrogating FND_MESSAGE and returning the resolved string to the caller.
• IS_USER_ALLOWED_FOR_FUNC — Evaluates whether the current user is permitted to execute a given function, using the FND_FUNCTION/security model to return an authorization result.

Tables Accessed

The ETRM metadata records no direct table references via APPS synonyms for this package body; its data access is instead mediated through the FND and WIP foundation packages. Message text and stack operations flow through FND_MESSAGE and FND_MSG_PUB, profile values are read through FND_PROFILE, and function security checks are resolved through FND_FUNCTION. WIP class type information is sourced from the WIP_CONSTANTS package rather than by direct SQL against WIP tables.

Usage Notes

AHL_UTIL_PKG is not referenced by any database object directly, but the ETRM documentation records that it is referenced by nineteen other packages. It is therefore invoked primarily from within the AHL package layer, supporting forms, concurrent programs, and custom extensions that require message handling, installation checks, or authorization tests. Because the routines are generic helpers, they are safe to call from custom code, provided the FND message stack is properly initialized by the caller. The documented metadata provides no parameter lists, so callers should consult the deployed source via the EBS "show dependent code" facility before invoking any routine.