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_API_USER_HOOKS_UTILITY dependencies on HR_API_USER_HOOK_REPORTS

Line 16: -- Inserts one row to the HR_API_USER_HOOK_REPORTS table.

12: -- ----------------------------------------------------------------------------
13: -- {Start Of Comments}
14: --
15: -- Description:
16: -- Inserts one row to the HR_API_USER_HOOK_REPORTS table.
17: --
18: -- Prerequisites:
19: -- None.
20: --

Line 26: -- One row is inserted into the HR_API_USER_HOOK_REPORTS table. No commit

22: -- Name Reqd Type Description
23: -- p_text Yes varchar2 Text to insert
24: --
25: -- Post success:
26: -- One row is inserted into the HR_API_USER_HOOK_REPORTS table. No commit
27: -- is issued.
28: --
29: -- Post Failure:
30: -- An Oracle error is raised. No application specific errors as raised from

Line 47: insert into hr_api_user_hook_reports

43: hr_utility.set_location('Entering:'|| l_proc, 10);
44: --
45: -- Insert into reports table
46: --
47: insert into hr_api_user_hook_reports
48: (session_id,
49: line,
50: text)
51: values

Line 67: -- Creates a translated report title in the HR_API_USER_HOOK_REPORTS table.

63: -- ----------------------------------------------------------------------------
64: -- {Start Of Comments}
65: --
66: -- Description:
67: -- Creates a translated report title in the HR_API_USER_HOOK_REPORTS table.
68: --
69: -- Prerequisites:
70: -- The message name must exist in the message dictionary.
71: --

Line 80: -- The title is created in the HR_API_USER_HOOK_REPORTS table.

76: -- which contains the title for
77: -- this report.
78: --
79: -- Post success:
80: -- The title is created in the HR_API_USER_HOOK_REPORTS table.
81: --
82: -- Post Failure:
83: -- An exception error is raised and no rows are created in the
84: -- HR_API_USER_HOOK_REPORTS table.

Line 84: -- HR_API_USER_HOOK_REPORTS table.

80: -- The title is created in the HR_API_USER_HOOK_REPORTS table.
81: --
82: -- Post Failure:
83: -- An exception error is raised and no rows are created in the
84: -- HR_API_USER_HOOK_REPORTS table.
85: --
86: -- Access Status:
87: -- Internal Development Use Only.
88: --

Line 100: from hr_api_user_hook_reports

96: -- been started for the current session
97: --
98: cursor csr_report_started is
99: select count(*)
100: from hr_api_user_hook_reports
101: where session_id = userenv('SESSIONID');
102: --
103: -- Local variables
104: --

Line 456: -- HR_API_USER_HOOK_REPORTS.

452: -- {Start Of Comments}
453: --
454: -- Description:
455: -- Writes the hook error details, for one API module, to the
456: -- HR_API_USER_HOOK_REPORTS.
457: --
458: -- This procedure has been designed to be called from the
459: -- write_all_errors_report and write_one_errors_report procedures in
460: -- this package.

Line 482: -- be written to the HR_API_USER_HOOK_REPORTS table.

478: -- included in the report out
479: --
480: -- Post success:
481: -- Details of any hook package compilation and application errors will
482: -- be written to the HR_API_USER_HOOK_REPORTS table.
483: --
484: -- Post Failure:
485: -- An error is raised.
486: --

Line 836: from hr_api_user_hook_reports

832: -- Cursor to find other sessions
833: --
834: cursor csr_oth_ses is
835: select distinct session_id
836: from hr_api_user_hook_reports
837: where session_id <> userenv('SESSIONID');
838: --
839: -- Cursor to find if a specific session is active
840: --

Line 854: delete from hr_api_user_hook_reports

850: hr_utility.set_location('Entering:'|| l_proc, 10);
851: --
852: -- Delete rows in the report table for this session
853: --
854: delete from hr_api_user_hook_reports
855: where session_id = userenv('SESSIONID');
856: --
857: -- Delete rows from the report table for any sessions
858: -- which no longer exist. (Clean-up to ensure unwanted

Line 865: -- delete from hr_api_user_hook_reports a

861: -- Note: Due to wwbug 854170, deliberately using a cursor
862: -- loop instead of an join or sub-query between a
863: -- standard table and a v$ view. These separate cursors
864: -- and PL/SQL code are providing the same result as:
865: -- delete from hr_api_user_hook_reports a
866: -- where not exists (select null
867: -- from v$session s
868: -- where s.audsid = a.session_id);
869: --

Line 876: -- rows from hr_api_user_hook_reports

872: open csr_v_ses(l_oth_ses.session_id);
873: fetch csr_v_ses into l_exists;
874: if csr_v_ses%notfound then
875: -- Session is not active so remove corresponding
876: -- rows from hr_api_user_hook_reports
877: delete from hr_api_user_hook_reports
878: where session_id = l_oth_ses.session_id;
879: end if;
880: close csr_v_ses;

Line 877: delete from hr_api_user_hook_reports

873: fetch csr_v_ses into l_exists;
874: if csr_v_ses%notfound then
875: -- Session is not active so remove corresponding
876: -- rows from hr_api_user_hook_reports
877: delete from hr_api_user_hook_reports
878: where session_id = l_oth_ses.session_id;
879: end if;
880: close csr_v_ses;
881: --