APPS.FND_DEBUG_UTIL dependencies on FND_DEBUG_RULE_EXECUTIONS

Line 204: -- It updates the request_id in fnd_debug_rule_executions table as

200: -- STOP_PLSQL_PROFILER
201: -- Description:
202: -- This procedure will stop PLSQL profiler by calling FND_TRACE
203: -- and submit concurrent request to generate profiler output.
204: -- It updates the request_id in fnd_debug_rule_executions table as
205: -- log_request_id.
206:
207: procedure stop_plsql_profiler is
208: sql_str varchar2(500);

Line 222: -- update fnd_debug_rule_executions table with request_id

218: sql_str := 'begin :1 := fnd_trace.submit_profiler_report; end; ';
219:
220: execute immediate sql_str using out req_id;
221:
222: -- update fnd_debug_rule_executions table with request_id
223: update fnd_debug_rule_executions
224: set log_request_id = req_id
225: where transaction_id = fnd_log.g_transaction_context_id
226: and debug_option_name = 'PLSQL_PROFILER';

Line 223: update fnd_debug_rule_executions

219:
220: execute immediate sql_str using out req_id;
221:
222: -- update fnd_debug_rule_executions table with request_id
223: update fnd_debug_rule_executions
224: set log_request_id = req_id
225: where transaction_id = fnd_log.g_transaction_context_id
226: and debug_option_name = 'PLSQL_PROFILER';
227: