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_HOOKS

Line 261: , hr_api_hooks ahk

257: select hlk.meaning
258: , ahk.hook_package
259: , ahk.hook_procedure
260: from hr_lookups hlk
261: , hr_api_hooks ahk
262: where hlk.lookup_type = 'API_HOOK_TYPE'
263: and hlk.lookup_code = ahk.api_hook_type
264: and ahk.api_module_id = p_module_id
265: order by hlk.meaning;

Line 271: from hr_api_hooks;

267: -- Cursor to obtain the names of all the API hook packages
268: --
269: cursor cur_hooks is
270: select distinct hook_package
271: from hr_api_hooks;
272: --
273: -- Local variables to catch the values returned from
274: -- hr_general.describe_procedure
275: --

Line 418: -- database or the hook package name specified in the HR_API_HOOKS

414: -- Trap errors raised by hr_general.describe_procedure
415: when Package_Not_Exists then
416: -- Error: The hook package header source code cannot be found in the
417: -- database. Either the package header has not been loaded into the
418: -- database or the hook package name specified in the HR_API_HOOKS
419: -- table is incorrect. This API module will not execute until this
420: -- problem has been resolved.
421: hr_utility.set_message(800, 'HR_51960_AHK_HK_PKG_NOT_FOUND');
422: when Proc_Not_In_Package then

Line 513: from hr_api_hooks ahk

509: -- If there are no errors the hook package will not be listed.
510: --
511: cursor csr_hook_pkgs is
512: select distinct ahk.hook_package
513: from hr_api_hooks ahk
514: where ahk.api_module_id = p_api_module_id
515: and ( (ahk.encoded_error is not null)
516: or exists (select null
517: from hr_api_hook_calls ahc

Line 539: , hr_api_hooks ahk

535: ,p_hook_package varchar2) is
536: select hlk.meaning
537: , ahk.api_hook_id
538: from hr_lookups hlk
539: , hr_api_hooks ahk
540: where hlk.lookup_type = 'API_HOOK_TYPE'
541: and hlk.lookup_code = ahk.api_hook_type
542: and ahk.api_module_id = p_api_module_id
543: and ahk.hook_package = p_hook_package

Line 568: from hr_api_hooks

564: -- Cursor to obtain hook level application errors for one given hook
565: --
566: cursor cur_ahk_err (p_api_hook_id number) is
567: select encoded_error
568: from hr_api_hooks
569: where api_hook_id = p_api_hook_id
570: and encoded_error is not null;
571: --
572: -- Cursor to obtain hook call level application errors

Line 590: -- HR_API_HOOKS or

586: --
587: l_mod_name_output boolean default false; -- Indicates if the module name and
588: -- type has already been output.
589: l_encoded_error varchar2(2000); -- Encoded error message from
590: -- HR_API_HOOKS or
591: -- HR_API_HOOK_CALLS.
592: l_read_error varchar2(2000); -- A de-encrypted version of
593: -- l_encoded_error.
594: l_line varchar2(2000); -- Line of text for report.

Line 907: from hr_api_hooks;

903: -- Cursor to obtain the names of all the API hook packages
904: --
905: cursor cur_hooks is
906: select distinct hook_package
907: from hr_api_hooks;
908: --
909: -- Local variables
910: --
911: l_proc varchar2(72) := g_package||'create_hooks_all_modules';

Line 915: -- Create each hook package which is defined in the HR_API_HOOKS table

911: l_proc varchar2(72) := g_package||'create_hooks_all_modules';
912: begin
913: hr_utility.set_location('Entering:'|| l_proc, 10);
914: --
915: -- Create each hook package which is defined in the HR_API_HOOKS table
916: -- Commit after each package has been created to ensure any error
917: -- information written to the HR_API_HOOKS and HR_API_HOOK_CALLS tables
918: -- is kept.
919: --

Line 917: -- information written to the HR_API_HOOKS and HR_API_HOOK_CALLS tables

913: hr_utility.set_location('Entering:'|| l_proc, 10);
914: --
915: -- Create each hook package which is defined in the HR_API_HOOKS table
916: -- Commit after each package has been created to ensure any error
917: -- information written to the HR_API_HOOKS and HR_API_HOOK_CALLS tables
918: -- is kept.
919: --
920: for l_hook in cur_hooks loop
921: hr_api_user_hooks.create_package_body(l_hook.hook_package);

Line 949: from hr_api_hooks

945: -- Cursor to obtain the the API hook package names
946: --
947: cursor cur_hooks is
948: select distinct hook_package
949: from hr_api_hooks
950: where api_module_id = p_api_module_id;
951: --
952: -- Local variables
953: --

Line 966: -- HR_API_HOOKS table. Commit after each package has been created to

962: fetch cur_module into l_exists;
963: if cur_module%found then
964: --
965: -- For this API module, create each hook package defined in the
966: -- HR_API_HOOKS table. Commit after each package has been created to
967: -- ensure any error information written to the HR_API_HOOKS and
968: -- HR_API_HOOK_CALLS tables is kept.
969: --
970: for l_hook in cur_hooks loop

Line 967: -- ensure any error information written to the HR_API_HOOKS and

963: if cur_module%found then
964: --
965: -- For this API module, create each hook package defined in the
966: -- HR_API_HOOKS table. Commit after each package has been created to
967: -- ensure any error information written to the HR_API_HOOKS and
968: -- HR_API_HOOK_CALLS tables is kept.
969: --
970: for l_hook in cur_hooks loop
971: hr_api_user_hooks.create_package_body(l_hook.hook_package);