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.OKC_UTIL dependencies on FND_LOG_REPOSITORY

Line 2823: --to 1 by executing the fnd_log_repository.init procedure call,as done below.

2819: --
2820: --In the Non-apps mode the value of g_profile_log_level in the okc_debug API
2821: --is set to 0. However in the subsequent call to the Fnd_Log.test procedure
2822: --the value of G_CURRENT_RUNTIME_LEVEL is used.Hence we need to set its value
2823: --to 1 by executing the fnd_log_repository.init procedure call,as done below.
2824: --Also, when the okc_util.print_trace is called it DOESNOT go through the
2825: --looping in the set connection context procedure in the OKC_DEBUG package, so
2826: --g_profile_log_level is never set and it is defaulted to 0
2827: --

Line 2831: FND_LOG_REPOSITORY.INIT(OKC_DEBUG.g_session_id,l_user_id);

2827: --
2828:
2829: -- Initialize the current runtime level
2830:
2831: FND_LOG_REPOSITORY.INIT(OKC_DEBUG.g_session_id,l_user_id);
2832: -- Bug 1996039 Initializing aso debug
2833: aso_debug_pub.debug_on;
2834: aso_debug_pub.initialize;
2835: l_file :=aso_DEBUG_PUB.Set_Debug_Mode('FILE');

Line 2842: --fnd_log_repository.init procedure is invoked ,which sets the

2838: ELSE -- Apps mode
2839:
2840: --
2841: --In the apps mode,the profile values are explicitly set and the
2842: --fnd_log_repository.init procedure is invoked ,which sets the
2843: --G_CURRENT_RUNTIME_LEVEL (based on profile option values)
2844: --but since the set connection context is already
2845: --executed (to run apps_initialize) and has set up g_profile_log_level,
2846: --we need now to explicitly call fnd_log_repository.init to assign the

Line 2846: --we need now to explicitly call fnd_log_repository.init to assign the

2842: --fnd_log_repository.init procedure is invoked ,which sets the
2843: --G_CURRENT_RUNTIME_LEVEL (based on profile option values)
2844: --but since the set connection context is already
2845: --executed (to run apps_initialize) and has set up g_profile_log_level,
2846: --we need now to explicitly call fnd_log_repository.init to assign the
2847: --new value of G_CURRENT_RUNTIME_LEVEL, which is then used to initialize
2848: --g_profile_log_level value (p_level of okc_debug.log will be then greater
2849: --or equal to g_profile_log_level)
2850: --

Line 2859: FND_LOG_REPOSITORY.INIT(OKC_DEBUG.g_session_id,l_user_id);

2855: FND_PROFILE.PUT('AFLOG_ENABLED','Y');
2856: FND_PROFILE.PUT('AFLOG_LEVEL',1);
2857: FND_PROFILE.PUT('AFLOG_MODULE','OKC');
2858:
2859: FND_LOG_REPOSITORY.INIT(OKC_DEBUG.g_session_id,l_user_id);
2860:
2861: IF (l_debug = 'Y') THEN
2862: OKC_DEBUG.g_profile_log_level := Fnd_Log.G_CURRENT_RUNTIME_LEVEL;
2863: END IF;