Search Results csl_imobile

Overview

APPS.JTM_PROFILE_UTL_PKG is a utility package within the Oracle E-Business Suite that centralizes the resolution of application-level profile option values for the JTM (mobile field service / iMobile) product family. Its principal design objective is to enforce a hierarchical enablement model: the value of the JTM_MOB_APPS_ENABLED profile option at the JTM application level acts as a master switch, and when that switch is not set to 'Y', every dependent mobile application profile is treated as disabled regardless of its own setting. The package therefore provides a single, reusable point of control for determining whether a given mobile application, responsibility, or user context should be considered "enabled." The package body header indicates a version at 120.1 dated 2005, reflecting its longstanding role as a foundational utility in the JTM stack rather than a feature-specific API.

Key Procedures and Functions

• GET_APP_LEVEL_PROFILE_VALUE — Retrieves the value of a named profile option as set specifically at the application level for a given application short name. It resolves the application identifier from FND_APPLICATION and delegates to the standard profile facility using fnd_profile.VALUE_SPECIFIC. If the application cannot be resolved or an error occurs, the function returns NULL.
• GET_APP_ENABLE_FLAG — Returns the enablement flag for an application identified by its short name. It first reads the JTM-level value of JTM_MOB_APPS_ENABLED; if the caller is JTM itself, that value is returned directly. Otherwise, if the JTM value is NULL or not 'Y', the flag is propagated as disabled. Only when JTM is explicitly enabled does it resolve the requested application's own profile value.
• GET_APP_ENABLE_FLAG (responsibility overload) — A variant that determines enablement in the context of a specific responsibility and application identifier, supporting responsibility-scoped enablement decisions. The body excerpt begins this overload at line 70 but is truncated; documented metadata confirms its existence.
• GET_ENABLE_FLAG_AT_RESP — Documented as the responsibility-level counterpart, resolving the enablement flag at responsibility granularity. It relies on responsibility metadata to determine the applicable context.

Tables Accessed

• FND_APPLICATION — Read to translate an application short name into an APPLICATION_ID, which is the key required by fnd_profile.VALUE_SPECIFIC. This lookup makes the package tolerant of callers passing human-readable short names rather than numeric identifiers.
• FND_RESPONSIBILITY — Read to support the responsibility-scoped enablement functions, providing the responsibility-to-application and profile-context relationship needed to evaluate the flag for a given responsibility.

Usage Notes

This package is referenced by fourteen other packages in the ETRM schema, indicating that it is invoked indirectly by mobile application framework code rather than by end users directly. Typical callers are JTM forms, mobile server-side components, and concurrent or batch routines that must decide whether to expose mobile functionality to a user or responsibility. When integrating custom code, the master-switch behavior should be preserved: callers should treat a NULL or non-'Y' JTM profile value as a global disablement. Because all functions trap WHEN OTHERS and return NULL on error, calling programs must interpret NULL as "not enabled" rather than as an exceptional condition.