APPS.CZ_DIAGNOSTICS_PVT dependencies on CZ_DB_LOGS

Line 9: --p_debug_flag if 1, writes the detailed message log to cz_db_logs, otherwise just

5: --first encountered problem. It does not continue after the first problems because most
6: --errors in explosion will induce other errors, which would go away after the first one
7: --is corrected.
8: --
9: --p_debug_flag if 1, writes the detailed message log to cz_db_logs, otherwise just
10: -- returns one error message in the output parameter x_msg_data.
11: --
12: --p_fix_extra_flag in case when extra records are found the procedure can be requested
13: -- to automatically delete them with this parameter set to 1.

Line 91: INSERT INTO cz_db_logs (run_id, logtime, message, caller, message_id)

87: BEGIN
88:
89: IF(p_debug_flag = 1)THEN
90:
91: INSERT INTO cz_db_logs (run_id, logtime, message, caller, message_id)
92: VALUES (x_run_id, SYSDATE, inMessage, 'CZ_DIAGNOSTICS_PVT.VERIFY_STRUCTURE', g_message_id);
93:
94: g_message_id := g_message_id + 1;
95:

Line 548: -- SELECT message FROM cz_db_logs WHERE run_id = ORDER BY message_id;

544: --Example if use:
545: -- SET SERVEROUTPUT ON
546: -- BEGIN DBMS_OUTPUT.PUT_LINE(cz_diagnostics_pvt.fast_debug(623160)); END;
547: -- /
548: -- SELECT message FROM cz_db_logs WHERE run_id = ORDER BY message_id;
549:
550: FUNCTION fast_debug(p_devl_project_id IN NUMBER) RETURN NUMBER
551: IS
552: