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.FEM_GL_POST_PROCESS_PKG dependencies on DBMS_UTILITY

Line 345: pv_callstack := dbms_utility.format_call_stack;

341: ------------------------------------------------------------------
342: -- Unexpected exceptions
343: ------------------------------------------------------------------
344: pv_sqlerrm := SQLERRM;
345: pv_callstack := dbms_utility.format_call_stack;
346:
347: x_completion_code := 2;
348:
349: -- Log the call stack and the Oracle error message to

Line 689: pv_callstack := dbms_utility.format_call_stack;

685: --------------------------------------------------------------------
686: x_completion_code := 2;
687:
688: pv_sqlerrm := SQLERRM;
689: pv_callstack := dbms_utility.format_call_stack;
690:
691: -- Log the call stack and the Oracle error message to
692: -- FND_LOG with the "unexpected exception" severity level.
693:

Line 1078: pv_callstack := dbms_utility.format_call_stack;

1074: ------------------------------------------------------------------
1075: -- Unexpected exceptions
1076: ------------------------------------------------------------------
1077: pv_sqlerrm := SQLERRM;
1078: pv_callstack := dbms_utility.format_call_stack;
1079:
1080: -- Log the call stack and the Oracle error message to
1081: -- FND_LOG with the "unexpected exception" severity level.
1082:

Line 1395: pv_callstack := dbms_utility.format_call_stack;

1391: ------------------------------------------------------------------
1392: -- Unexpected exceptions
1393: ------------------------------------------------------------------
1394: pv_sqlerrm := SQLERRM;
1395: pv_callstack := dbms_utility.format_call_stack;
1396:
1397: -- Log the call stack and the Oracle error message to
1398: -- FND_LOG with the "unexpected exception" severity level.
1399:

Line 2441: pv_callstack := dbms_utility.format_call_stack;

2437: -- Unexpected exception
2438: -- ------------------------
2439:
2440: pv_sqlerrm := SQLERRM;
2441: pv_callstack := dbms_utility.format_call_stack;
2442: pv_proc_name := 'get_dim_ids';
2443:
2444: RAISE;
2445:

Line 2579: pv_callstack := dbms_utility.format_call_stack;

2575:
2576: -- In case it's an unexpected exception
2577:
2578: pv_sqlerrm := SQLERRM;
2579: pv_callstack := dbms_utility.format_call_stack;
2580:
2581: -- For all exceptions:
2582:
2583: pv_proc_name := 'validate_budget';

Line 2808: pv_callstack := dbms_utility.format_call_stack;

2804: WHEN OTHERS THEN
2805: -- In case it's an unexpected exception
2806:
2807: pv_sqlerrm := SQLERRM;
2808: pv_callstack := dbms_utility.format_call_stack;
2809:
2810: -- For all exceptions:
2811:
2812: pv_proc_name := 'validate_cal_period';

Line 2931: pv_callstack := dbms_utility.format_call_stack;

2927:
2928: -- In case it's an unexpected exception
2929:
2930: pv_sqlerrm := SQLERRM;
2931: pv_callstack := dbms_utility.format_call_stack;
2932:
2933: -- For all exceptions:
2934:
2935: pv_proc_name := 'validate_dataset';

Line 3075: pv_callstack := dbms_utility.format_call_stack;

3071:
3072: -- In case it's an unexpected exception
3073:
3074: pv_sqlerrm := SQLERRM;
3075: pv_callstack := dbms_utility.format_call_stack;
3076:
3077: -- For all exceptions:
3078:
3079: pv_proc_name := 'validate_ds_bal_type';

Line 3215: pv_callstack := dbms_utility.format_call_stack;

3211:
3212: -- In case it's an unexpected exception
3213:
3214: pv_sqlerrm := SQLERRM;
3215: pv_callstack := dbms_utility.format_call_stack;
3216:
3217: -- For all exceptions:
3218:
3219: pv_proc_name := 'validate_encumbrance_type';

Line 3586: pv_callstack := dbms_utility.format_call_stack;

3582:
3583: -- In case it's an unexpected exception
3584:
3585: pv_sqlerrm := SQLERRM;
3586: pv_callstack := dbms_utility.format_call_stack;
3587:
3588: -- For all exceptions:
3589:
3590: pv_proc_name := 'validate_ledger';

Line 3802: pv_callstack := dbms_utility.format_call_stack;

3798:
3799: -- In case it's an unexpected exception
3800:
3801: pv_sqlerrm := SQLERRM;
3802: pv_callstack := dbms_utility.format_call_stack;
3803:
3804: -- For all exceptions:
3805:
3806: pv_proc_name := 'validate_object_def_id';

Line 4499: pv_callstack := dbms_utility.format_call_stack;

4495: ------------------------------------------------------------------
4496: IF pv_proc_name = 'validate_engine_parameters' THEN
4497:
4498: pv_sqlerrm := SQLERRM;
4499: pv_callstack := dbms_utility.format_call_stack;
4500:
4501: END IF;
4502:
4503: -- Log the call stack and the Oracle error message to

Line 5951: pv_callstack := dbms_utility.format_call_stack;

5947:
5948: IF pv_proc_name = 'validate_ogl_eng_parameters'
5949: THEN
5950: pv_sqlerrm := SQLERRM;
5951: pv_callstack := dbms_utility.format_call_stack;
5952: END IF;
5953:
5954: -- Log the call stack and the Oracle error message to
5955: -- FND_LOG with the "unexpected exception" severity level.

Line 7143: pv_callstack := dbms_utility.format_call_stack;

7139: -- <<< Unexpected database exceptions >>>
7140: x_completion_code := 2; -- Indicating fatal error
7141:
7142: pv_sqlerrm := SQLERRM;
7143: pv_callstack := dbms_utility.format_call_stack;
7144:
7145: -- Log the call stack and the Oracle error message to
7146: -- FND_LOG with the "unexpected exception" severity level.
7147: FEM_ENGINES_PKG.Tech_Message

Line 7700: pv_callstack := dbms_utility.format_call_stack;

7696: EXCEPTION
7697: WHEN OTHERS THEN
7698: -- <<< Unexpected database exceptions >>>
7699: pv_sqlerrm := SQLERRM;
7700: pv_callstack := dbms_utility.format_call_stack;
7701:
7702: -- Log the call stack and the Oracle error message to
7703: -- FND_LOG with the "unexpected exception" severity level.
7704: FEM_ENGINES_PKG.Tech_Message