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 dependencies on HR_API_HOOKS

Line 964: -- the HR_API_HOOKS table.

960: --
961: -- In Parameters:
962: -- Name Reqd Type Description
963: -- p_api_hook_id Yes number ID of the hook details from
964: -- the HR_API_HOOKS table.
965: -- p_legislation_package Yes varchar2 The legislation_package as
966: -- specified in the HR_API_HOOKS
967: -- table.
968: -- p_legislation_function Yes varchar2 The legislation_function as

Line 966: -- specified in the HR_API_HOOKS

962: -- Name Reqd Type Description
963: -- p_api_hook_id Yes number ID of the hook details from
964: -- the HR_API_HOOKS table.
965: -- p_legislation_package Yes varchar2 The legislation_package as
966: -- specified in the HR_API_HOOKS
967: -- table.
968: -- p_legislation_function Yes varchar2 The legislation_function as
969: -- specified in the HR_API_HOOKS
970: -- table.

Line 969: -- specified in the HR_API_HOOKS

965: -- p_legislation_package Yes varchar2 The legislation_package as
966: -- specified in the HR_API_HOOKS
967: -- table.
968: -- p_legislation_function Yes varchar2 The legislation_function as
969: -- specified in the HR_API_HOOKS
970: -- table.
971: -- p_number_of_parameters Yes number The number of parameters to
972: -- the hook package procedure.
973: -- p_hook_parameter_names Yes Table When the number of hook

Line 1351: -- HR_API_HOOKS table, and the business_group_id value is not available

1347: hr_utility.set_location(l_proc, 50);
1348: else
1349: -- Error: The legislation specific code cannot be called from this hook.
1350: -- The legislation package function has not been specified in the
1351: -- HR_API_HOOKS table, and the business_group_id value is not available
1352: -- at this hook. This API module will not execute until this problem has
1353: -- been resolved.
1354: hr_utility.set_message(800, 'HR_51967_AHK_LEG_NO_SPECIFIC');
1355: hr_utility.set_location(l_proc, 60);

Line 1382: -- the HR_API_HOOKS table.

1378: --
1379: -- In Parameters:
1380: -- Name Reqd Type Description
1381: -- p_api_hook_id Yes number ID of the hook details from
1382: -- the HR_API_HOOKS table.
1383: -- p_legislation_package Yes varchar2 The legislation_package as
1384: -- specified in the HR_API_HOOKS
1385: -- table.
1386: -- p_legislation_function Yes varchar2 The legislation_function as

Line 1384: -- specified in the HR_API_HOOKS

1380: -- Name Reqd Type Description
1381: -- p_api_hook_id Yes number ID of the hook details from
1382: -- the HR_API_HOOKS table.
1383: -- p_legislation_package Yes varchar2 The legislation_package as
1384: -- specified in the HR_API_HOOKS
1385: -- table.
1386: -- p_legislation_function Yes varchar2 The legislation_function as
1387: -- specified in the HR_API_HOOKS
1388: -- table.

Line 1387: -- specified in the HR_API_HOOKS

1383: -- p_legislation_package Yes varchar2 The legislation_package as
1384: -- specified in the HR_API_HOOKS
1385: -- table.
1386: -- p_legislation_function Yes varchar2 The legislation_function as
1387: -- specified in the HR_API_HOOKS
1388: -- table.
1389: -- p_number_of_parameters Yes number The number of parameters to
1390: -- the hook package procedure.
1391: -- p_hook_parameter_names Yes Table When the number of hook

Line 1408: -- problem. Details of the error are also written to the HR_API_HOOKS table.

1404: -- Post Failure:
1405: -- Comment text and invalid code is added to the hook package source code.
1406: -- Invalid code is deliberately included to ensure that the package body
1407: -- does not compile. This will force investigation and resolution of the
1408: -- problem. Details of the error are also written to the HR_API_HOOKS table.
1409: --
1410: -- Access Status:
1411: -- Internal Development Use Only.
1412: --

Line 1467: -- place details of the error in the HR_API_HOOKS table.

1463: --
1464: if not l_code_created then
1465: --
1466: -- The code to derive the legislation code could not be generated then
1467: -- place details of the error in the HR_API_HOOKS table.
1468: -- Also generate some invalid code in the hook package body to prevent
1469: -- the package from compiling. This will force somebody to investigate the
1470: -- problem and will prevent legislation specific logic from being
1471: -- by-passed.

Line 1473: -- It is not necessary to clear hr_api_hooks.encoded_error, from previous

1469: -- the package from compiling. This will force somebody to investigate the
1470: -- problem and will prevent legislation specific logic from being
1471: -- by-passed.
1472: --
1473: -- It is not necessary to clear hr_api_hooks.encoded_error, from previous
1474: -- generates because that will have already been done by the
1475: -- make_parameter_list procedure.
1476: --
1477: -- Create comment text in the package body source code

Line 1493: add_to_source('-- from hr_api_hooks h' || c_new_line);

1489: add_to_source('-- Details of the error, in FND encoded format, can ');
1490: add_to_source('be obtained' || c_new_line);
1491: add_to_source('-- with the following sql statement:' || c_new_line);
1492: add_to_source('-- select h.encoded_error' || c_new_line);
1493: add_to_source('-- from hr_api_hooks h' || c_new_line);
1494: add_to_source('-- where h.api_hook_id = ' || to_char(p_api_hook_id));
1495: add_to_source(';' || c_new_line);
1496:
1497: add_to_source('-- The following invalid code has been deliberately ');

Line 1504: -- Write details of the error to the HR_API_HOOKS table

1500: add_to_source(c_new_line);
1501: add_to_source('INVALID_SEE_COMMENT_IN_SOURCE;' || c_new_line);
1502: hr_utility.set_location(l_proc, 40);
1503: --
1504: -- Write details of the error to the HR_API_HOOKS table
1505: --
1506: l_encoded_err_text := fnd_message.get_encoded;
1507: --
1508: -- Change the following update statement to

Line 1511: update hr_api_hooks

1507: --
1508: -- Change the following update statement to
1509: -- call the row handler, when it is available.
1510: --
1511: update hr_api_hooks
1512: set encoded_error = l_encoded_err_text
1513: where api_hook_id = p_api_hook_id;
1514: hr_utility.set_location(l_proc, 50);
1515: end if;

Line 1538: -- the HR_API_HOOKS table.

1534: --
1535: -- In Parameters:
1536: -- Name Reqd Type Description
1537: -- p_api_hook_id Yes number ID of the hook details from
1538: -- the HR_API_HOOKS table.
1539: -- p_legislation_package Yes varchar2 The legislation_package as
1540: -- specified in the HR_API_HOOKS
1541: -- table.
1542: -- p_legislation_function Yes varchar2 The legislation_function as

Line 1540: -- specified in the HR_API_HOOKS

1536: -- Name Reqd Type Description
1537: -- p_api_hook_id Yes number ID of the hook details from
1538: -- the HR_API_HOOKS table.
1539: -- p_legislation_package Yes varchar2 The legislation_package as
1540: -- specified in the HR_API_HOOKS
1541: -- table.
1542: -- p_legislation_function Yes varchar2 The legislation_function as
1543: -- specified in the HR_API_HOOKS
1544: -- table.

Line 1543: -- specified in the HR_API_HOOKS

1539: -- p_legislation_package Yes varchar2 The legislation_package as
1540: -- specified in the HR_API_HOOKS
1541: -- table.
1542: -- p_legislation_function Yes varchar2 The legislation_function as
1543: -- specified in the HR_API_HOOKS
1544: -- table.
1545: -- p_data_within_business_group Yes varchar2 Indicates if the data for
1546: -- this module is held within
1547: -- the context of a

Line 1566: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.

1562: -- Creates source code to carry out legislation specific hook calls.
1563: --
1564: -- Post Failure:
1565: -- Any application errors and some system errors are written to the
1566: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.
1567: --
1568: -- Access Status:
1569: -- Internal Development Use Only.
1570: --

Line 1714: -- the HR_API_HOOKS table.

1710: --
1711: -- In Parameters:
1712: -- Name Reqd Type Description
1713: -- p_api_hook_id Yes number ID of the hook details from
1714: -- the HR_API_HOOKS table.
1715: -- p_number_of_parameters Yes number The number of parameters to
1716: -- the hook package procedure.
1717: -- p_hook_parameter_names Yes Table When the number of hook
1718: -- procedure parameters is

Line 1731: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.

1727: -- Creates source code to carry out application specific hook calls.
1728: --
1729: -- Post Failure:
1730: -- Any application errors and some system errors are written to the
1731: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.
1732: --
1733: -- Access Status:
1734: -- Internal Development Use Only.
1735: --

Line 1813: -- the HR_API_HOOKS table.

1809: --
1810: -- In Parameters:
1811: -- Name Reqd Type Description
1812: -- p_api_hook_id Yes number ID of the hook details from
1813: -- the HR_API_HOOKS table.
1814: -- p_number_of_parameters Yes number The number of parameters to
1815: -- the hook package procedure.
1816: -- p_hook_parameter_names Yes Table When the number of hook
1817: -- procedure parameters is

Line 2000: -- This hook is known to exist in the HR_API_HOOKS table.

1996: -- ii) the pre-processor has successfully executed the hook call,
1997: -- from the latest version of the hook package body.
1998: --
1999: -- Prerequisites:
2000: -- This hook is known to exist in the HR_API_HOOKS table.
2001: --
2002: -- In Parameters:
2003: -- Name Reqd Type Description
2004: -- p_api_hook_id Yes number ID of the hook details from

Line 2005: -- the HR_API_HOOKS table.

2001: --
2002: -- In Parameters:
2003: -- Name Reqd Type Description
2004: -- p_api_hook_id Yes number ID of the hook details from
2005: -- the HR_API_HOOKS table.
2006: --
2007: -- Post Success:
2008: -- Updates all the rows in the HR_API_HOOK_CALLS table which match the
2009: -- api_hook_id and the enabled_flag is 'N'. Customer and legislation

Line 2074: -- the HR_API_HOOKS table.

2070: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2071: -- within the hook package.
2072: -- p_api_hook_type Yes varchar2 Type of Hook.
2073: -- p_api_hook_id Yes number ID of the hook details from
2074: -- the HR_API_HOOKS table.
2075: -- p_legislation_package Yes varchar2 The legislation_package as
2076: -- specified in the HR_API_HOOKS
2077: -- table.
2078: -- p_legislation_function Yes varchar2 The legislation_function as

Line 2076: -- specified in the HR_API_HOOKS

2072: -- p_api_hook_type Yes varchar2 Type of Hook.
2073: -- p_api_hook_id Yes number ID of the hook details from
2074: -- the HR_API_HOOKS table.
2075: -- p_legislation_package Yes varchar2 The legislation_package as
2076: -- specified in the HR_API_HOOKS
2077: -- table.
2078: -- p_legislation_function Yes varchar2 The legislation_function as
2079: -- specified in the HR_API_HOOKS
2080: -- table.

Line 2079: -- specified in the HR_API_HOOKS

2075: -- p_legislation_package Yes varchar2 The legislation_package as
2076: -- specified in the HR_API_HOOKS
2077: -- table.
2078: -- p_legislation_function Yes varchar2 The legislation_function as
2079: -- specified in the HR_API_HOOKS
2080: -- table.
2081: -- p_module_name Yes varchar2 API Module name from the
2082: -- HR_API_MODULES table.
2083: -- p_data_within_business_group Yes varchar2 Indicates if the data for

Line 2104: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application

2100: -- Creates source code for the hook procedure in the source store.
2101: --
2102: -- Post Failure:
2103: -- Most application and some Oracle errors are written to the corresponding
2104: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2105: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2106: --
2107: -- Access Status:
2108: -- Internal Development Use Only.

Line 2171: , hr_api_hooks ahk_ap

2167: --
2168: cursor csr_ap_leg_call_exist is
2169: select 1
2170: from hr_api_hook_calls ahc
2171: , hr_api_hooks ahk_ap
2172: , hr_api_modules amk
2173: , hr_api_hooks ahk_bp
2174: where ahc.enabled_flag = 'Y'
2175: and ahc.legislation_code is not null

Line 2173: , hr_api_hooks ahk_bp

2169: select 1
2170: from hr_api_hook_calls ahc
2171: , hr_api_hooks ahk_ap
2172: , hr_api_modules amk
2173: , hr_api_hooks ahk_bp
2174: where ahc.enabled_flag = 'Y'
2175: and ahc.legislation_code is not null
2176: and ahc.api_hook_id = ahk_ap.api_hook_id
2177: and ahk_ap.api_hook_type = 'AP'

Line 2442: -- the HR_API_HOOKS table.

2438: -- p_hook_package Yes varchar2 Name of the hook package.
2439: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2440: -- within the hook package.
2441: -- p_api_hook_id Yes number ID of the hook details from
2442: -- the HR_API_HOOKS table.
2443: --
2444: -- Post Success:
2445: -- Creates the list of parameters in the source store.
2446: -- p_param_list_error is set to false. p_number_of_parameters is set to the

Line 2452: -- text string representations. hr_api_hooks.encoded_error is updated to

2448: -- p_number_of_parameters is greater than zero then p_hook_parameter_names
2449: -- is populated with the list of parameter names to hook package procedure.
2450: -- p_hook_parameter_datatypes is set to the corresponding parameter
2451: -- datatypes. The internal Oracle datatypes number codes are used, not the
2452: -- text string representations. hr_api_hooks.encoded_error is updated to
2453: -- null.
2454: --
2455: -- Post Failure:
2456: -- When a hook package procedure header or parameter error occurs the

Line 2458: -- Details of the error are written to the hr_api_hooks.encoded_error

2454: --
2455: -- Post Failure:
2456: -- When a hook package procedure header or parameter error occurs the
2457: -- parameter list is not constructed. p_param_list_error is set to true.
2458: -- Details of the error are written to the hr_api_hooks.encoded_error
2459: -- column. A comment and invalid code is deliberately added to the source
2460: -- code to force the problem to be investigated and resolved. The
2461: -- p_number_of_parameters, p_hook_parameter_names and
2462: -- p_hook_parameter_datatypes parameters contain undefined values and no

Line 2464: -- hr_api_hooks.encoded_error.

2460: -- code to force the problem to be investigated and resolved. The
2461: -- p_number_of_parameters, p_hook_parameter_names and
2462: -- p_hook_parameter_datatypes parameters contain undefined values and no
2463: -- attempt should be made to use them. Details of the error are written to
2464: -- hr_api_hooks.encoded_error.
2465: --
2466: -- Access Status:
2467: -- Internal Development Use Only.
2468: --

Line 2515: -- the HR_API_HOOKS table.

2511: -- l_datatype number.
2512: l_param_code varchar2(20000) := null; -- The parameter list code.
2513: l_encoded_err_text varchar2(2000); -- Set to the encoded error text
2514: -- when an error is written to
2515: -- the HR_API_HOOKS table.
2516: l_proc varchar2(72) := g_package||'make_parameter_list';
2517: begin
2518: hr_utility.set_location('Entering:'|| l_proc, 10);
2519: --

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

2543: exception
2544: when Package_Not_Exists then
2545: -- Error: The hook package header source code cannot be found in the
2546: -- database. Either the package header has not been loaded into the
2547: -- database or the hook package name specified in the HR_API_HOOKS
2548: -- table is incorrect. This API module will not execute until this
2549: -- problem has been resolved.
2550: hr_utility.set_message(800, 'HR_51960_AHK_HK_PKG_NOT_FOUND');
2551: l_error := true;

Line 2743: -- the error details in the hr_api_hooks table.

2739: end if;
2740: hr_utility.set_location(l_proc, 150);
2741: --
2742: -- Set the out parameters for this procedure and update
2743: -- the error details in the hr_api_hooks table.
2744: --
2745: if not l_error then
2746: --
2747: -- Remember how many parameters exist to the hook package procedure

Line 2754: -- Ensure any error details placed in the HR_API_HOOKS table, from previous

2750: -- Indicate that no hook package procedure or parameter list errors
2751: -- where found.
2752: p_param_list_error := false;
2753: --
2754: -- Ensure any error details placed in the HR_API_HOOKS table, from previous
2755: -- generates, are cleared. When the make_find_legislation procedure is
2756: -- executed, sometimes an error will be written to HR_API_HOOKS. In certain
2757: -- cases the 'clearing' update done here will be a waste of time. It is not
2758: -- possible to detect here when make_find_legislation will find an error.

Line 2756: -- executed, sometimes an error will be written to HR_API_HOOKS. In certain

2752: p_param_list_error := false;
2753: --
2754: -- Ensure any error details placed in the HR_API_HOOKS table, from previous
2755: -- generates, are cleared. When the make_find_legislation procedure is
2756: -- executed, sometimes an error will be written to HR_API_HOOKS. In certain
2757: -- cases the 'clearing' update done here will be a waste of time. It is not
2758: -- possible to detect here when make_find_legislation will find an error.
2759: -- Also make_find_legislation will not be called if there are any hook
2760: -- calls. So the 'clearing' update is always done here.

Line 2765: update hr_api_hooks

2761: --
2762: -- Change the following update statement to
2763: -- call the row handler, when it is available.
2764: --
2765: update hr_api_hooks
2766: set encoded_error = null
2767: where api_hook_id = p_api_hook_id;
2768: hr_utility.set_location(l_proc, 160);
2769: else

Line 2772: -- due to an error. Write details of the error to the HR_API_HOOKS table.

2768: hr_utility.set_location(l_proc, 160);
2769: else
2770: --
2771: -- The parameter list code for this hook procedure could not be generated
2772: -- due to an error. Write details of the error to the HR_API_HOOKS table.
2773: -- Also deliberately create some invalid code in the hook package body
2774: -- to prevent the package from compiling. This will force somebody to
2775: -- investigate the problem.
2776: --

Line 2789: '-- from hr_api_hooks h' || c_new_line ||

2785: '-- an error. Details of the error, in FND encoded ' ||
2786: 'format, can be obtained' || c_new_line ||
2787: '-- with the following sql statement:' || c_new_line ||
2788: '-- select h.encoded_error' || c_new_line ||
2789: '-- from hr_api_hooks h' || c_new_line ||
2790: '-- where h.api_hook_id = ' || to_char(p_api_hook_id) ||
2791: ';' || c_new_line ||
2792: '-- The following invalid code has been deliberately ' ||
2793: 'created to force' || c_new_line ||

Line 2799: -- Write details of the error to the HR_API_HOOKS table

2795: c_new_line || 'INVALID_SEE_COMMENT_IN_SOURCE;' ||
2796: c_new_line;
2797: hr_utility.set_location(l_proc, 170);
2798: --
2799: -- Write details of the error to the HR_API_HOOKS table
2800: --
2801: l_encoded_err_text := fnd_message.get_encoded;
2802: --
2803: -- Change the following update statement to

Line 2806: update hr_api_hooks

2802: --
2803: -- Change the following update statement to
2804: -- call the row handler, when it is available.
2805: --
2806: update hr_api_hooks
2807: set encoded_error = l_encoded_err_text
2808: where api_hook_id = p_api_hook_id;
2809: hr_utility.set_location(l_proc, 180);
2810: end if;

Line 2839: -- the HR_API_HOOKS table.

2835: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2836: -- within the hook package.
2837: -- p_api_hook_type Yes varchar2 Type of Hook.
2838: -- p_api_hook_id Yes number ID of the hook details from
2839: -- the HR_API_HOOKS table.
2840: -- p_legislation_package Yes varchar2 The legislation_package as
2841: -- specified in the HR_API_HOOKS
2842: -- table.
2843: -- p_legislation_function Yes varchar2 The legislation_function as

Line 2841: -- specified in the HR_API_HOOKS

2837: -- p_api_hook_type Yes varchar2 Type of Hook.
2838: -- p_api_hook_id Yes number ID of the hook details from
2839: -- the HR_API_HOOKS table.
2840: -- p_legislation_package Yes varchar2 The legislation_package as
2841: -- specified in the HR_API_HOOKS
2842: -- table.
2843: -- p_legislation_function Yes varchar2 The legislation_function as
2844: -- specified in the HR_API_HOOKS
2845: -- table.

Line 2844: -- specified in the HR_API_HOOKS

2840: -- p_legislation_package Yes varchar2 The legislation_package as
2841: -- specified in the HR_API_HOOKS
2842: -- table.
2843: -- p_legislation_function Yes varchar2 The legislation_function as
2844: -- specified in the HR_API_HOOKS
2845: -- table.
2846: -- p_module_name Yes varchar2 API Module name from the
2847: -- HR_API_MODULES table.
2848: -- p_data_within_business_group Yes varchar2 Indicates if the data for

Line 2859: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application

2855: -- Creates source code for the hook procedure in the source store.
2856: --
2857: -- Post Failure:
2858: -- Most application and some Oracle errors are written to the corresponding
2859: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2860: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2861: --
2862: -- Access Status:
2863: -- Internal Development Use Only.

Line 2972: -- those procedures which have been listed in the the HR_API_HOOKS table.

2968: -- p_hook_package Yes varchar2 Name of the hook package.
2969: --
2970: -- Post Success:
2971: -- Creates all the procedure bodies for the hook package. Only creates
2972: -- those procedures which have been listed in the the HR_API_HOOKS table.
2973: --
2974: -- Post Failure:
2975: -- Most application and some Oracle errors are written to the corresponding
2976: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application

Line 2976: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application

2972: -- those procedures which have been listed in the the HR_API_HOOKS table.
2973: --
2974: -- Post Failure:
2975: -- Most application and some Oracle errors are written to the corresponding
2976: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2977: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2978: --
2979: -- Access Status:
2980: -- Internal Development Use Only.

Line 2999: , hr_api_hooks ahk

2995: , ahk.legislation_function
2996: , amd.module_name
2997: , amd.data_within_business_group
2998: from hr_api_modules amd
2999: , hr_api_hooks ahk
3000: where amd.api_module_id = ahk.api_module_id
3001: and ahk.hook_package = p_hook_package;
3002: --
3003: l_proc varchar2(72) := g_package||'create_procedures';

Line 3050: -- to the HR_API_HOOKS table. The 'make_parameter_list' procedure is called

3046: -- Post Failure:
3047: -- If the text could not been found then an error is not raised here.
3048: -- When the hook package header does not exist in the database the
3049: -- 'make_parameter_list' procedure will raise an error and save the details
3050: -- to the HR_API_HOOKS table. The 'make_parameter_list' procedure is called
3051: -- as part of the 'create_procedures' work.
3052: --
3053: -- Access Status:
3054: -- Internal Development Use Only.

Line 3180: -- details to the HR_API_HOOKS table. The 'make_parameter_list'

3176: --
3177: -- If the text could not been found then do not raise an error here.
3178: -- When the hook package header does not exist in the database the
3179: -- 'make_parameter_list' procedure will raise an error and save the
3180: -- details to the HR_API_HOOKS table. The 'make_parameter_list'
3181: -- procedure is called as part of the 'create_procedures' work.
3182: --
3183: if l_pkg_find_found then
3184: --