eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_SECURITY_INTERNAL dependencies on FND_GLOBAL

Line 3069: -- fnd_global.apps_initialise call.

3065: -- Check whether the local cached version of the session context
3066: -- differs to the AOL session context.
3067: -- This is the most aggressive form of session change identification
3068: -- as the session_context should increment for each
3069: -- fnd_global.apps_initialise call.
3070: --
3071: -- This procedure is used primarily for ADF applications, where database
3072: -- sessions (and therefore cached PL/SQL values) are pooled and can
3073: -- be reused by a user that may have entirely different security permissions

Line 3083: fnd_global.session_context IS NULL OR

3079: -- No debug output is added here because this is called in each
3080: -- iteration of the secure view.
3081: --
3082: IF g_session_context IS NULL OR
3083: fnd_global.session_context IS NULL OR
3084: g_session_context <> fnd_global.session_context THEN
3085: RETURN TRUE;
3086: ELSE
3087: RETURN FALSE;

Line 3084: g_session_context <> fnd_global.session_context THEN

3080: -- iteration of the secure view.
3081: --
3082: IF g_session_context IS NULL OR
3083: fnd_global.session_context IS NULL OR
3084: g_session_context <> fnd_global.session_context THEN
3085: RETURN TRUE;
3086: ELSE
3087: RETURN FALSE;
3088: END IF;

Line 3104: g_session_context := fnd_global.session_context;

3100:
3101: --
3102: -- Cache the AOL session context locally.
3103: --
3104: g_session_context := fnd_global.session_context;
3105:
3106: END sync_session_context;
3107: --
3108: -- ----------------------------------------------------------------------------