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.

[Home] [Help]

APPS.HR_API_USER_HOOKS dependencies on HR_API_HOOKS

Line 957: -- the HR_API_HOOKS table.

953: --
954: -- In Parameters:
955: -- Name Reqd Type Description
956: -- p_api_hook_id Yes number ID of the hook details from
957: -- the HR_API_HOOKS table.
958: -- p_legislation_package Yes varchar2 The legislation_package as
959: -- specified in the HR_API_HOOKS
960: -- table.
961: -- p_legislation_function Yes varchar2 The legislation_function as

Line 959: -- specified in the HR_API_HOOKS

955: -- Name Reqd Type Description
956: -- p_api_hook_id Yes number ID of the hook details from
957: -- the HR_API_HOOKS table.
958: -- p_legislation_package Yes varchar2 The legislation_package as
959: -- specified in the HR_API_HOOKS
960: -- table.
961: -- p_legislation_function Yes varchar2 The legislation_function as
962: -- specified in the HR_API_HOOKS
963: -- table.

Line 962: -- specified in the HR_API_HOOKS

958: -- p_legislation_package Yes varchar2 The legislation_package as
959: -- specified in the HR_API_HOOKS
960: -- table.
961: -- p_legislation_function Yes varchar2 The legislation_function as
962: -- specified in the HR_API_HOOKS
963: -- table.
964: -- p_number_of_parameters Yes number The number of parameters to
965: -- the hook package procedure.
966: -- p_hook_parameter_names Yes Table When the number of hook

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

1340: hr_utility.set_location(l_proc, 50);
1341: else
1342: -- Error: The legislation specific code cannot be called from this hook.
1343: -- The legislation package function has not been specified in the
1344: -- HR_API_HOOKS table, and the business_group_id value is not available
1345: -- at this hook. This API module will not execute until this problem has
1346: -- been resolved.
1347: hr_utility.set_message(800, 'HR_51967_AHK_LEG_NO_SPECIFIC');
1348: hr_utility.set_location(l_proc, 60);

Line 1375: -- the HR_API_HOOKS table.

1371: --
1372: -- In Parameters:
1373: -- Name Reqd Type Description
1374: -- p_api_hook_id Yes number ID of the hook details from
1375: -- the HR_API_HOOKS table.
1376: -- p_legislation_package Yes varchar2 The legislation_package as
1377: -- specified in the HR_API_HOOKS
1378: -- table.
1379: -- p_legislation_function Yes varchar2 The legislation_function as

Line 1377: -- specified in the HR_API_HOOKS

1373: -- Name Reqd Type Description
1374: -- p_api_hook_id Yes number ID of the hook details from
1375: -- the HR_API_HOOKS table.
1376: -- p_legislation_package Yes varchar2 The legislation_package as
1377: -- specified in the HR_API_HOOKS
1378: -- table.
1379: -- p_legislation_function Yes varchar2 The legislation_function as
1380: -- specified in the HR_API_HOOKS
1381: -- table.

Line 1380: -- specified in the HR_API_HOOKS

1376: -- p_legislation_package Yes varchar2 The legislation_package as
1377: -- specified in the HR_API_HOOKS
1378: -- table.
1379: -- p_legislation_function Yes varchar2 The legislation_function as
1380: -- specified in the HR_API_HOOKS
1381: -- table.
1382: -- p_number_of_parameters Yes number The number of parameters to
1383: -- the hook package procedure.
1384: -- p_hook_parameter_names Yes Table When the number of hook

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

1397: -- Post Failure:
1398: -- Comment text and invalid code is added to the hook package source code.
1399: -- Invalid code is deliberately included to ensure that the package body
1400: -- does not compile. This will force investigation and resolution of the
1401: -- problem. Details of the error are also written to the HR_API_HOOKS table.
1402: --
1403: -- Access Status:
1404: -- Internal Development Use Only.
1405: --

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

1456: --
1457: if not l_code_created then
1458: --
1459: -- The code to derive the legislation code could not be generated then
1460: -- place details of the error in the HR_API_HOOKS table.
1461: -- Also generate some invalid code in the hook package body to prevent
1462: -- the package from compiling. This will force somebody to investigate the
1463: -- problem and will prevent legislation specific logic from being
1464: -- by-passed.

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

1462: -- the package from compiling. This will force somebody to investigate the
1463: -- problem and will prevent legislation specific logic from being
1464: -- by-passed.
1465: --
1466: -- It is not necessary to clear hr_api_hooks.encoded_error, from previous
1467: -- generates because that will have already been done by the
1468: -- make_parameter_list procedure.
1469: --
1470: -- Create comment text in the package body source code

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

1482: add_to_source('-- Details of the error, in FND encoded format, can ');
1483: add_to_source('be obtained' || c_new_line);
1484: add_to_source('-- with the following sql statement:' || c_new_line);
1485: add_to_source('-- select h.encoded_error' || c_new_line);
1486: add_to_source('-- from hr_api_hooks h' || c_new_line);
1487: add_to_source('-- where h.api_hook_id = ' || to_char(p_api_hook_id));
1488: add_to_source(';' || c_new_line);
1489:
1490: add_to_source('-- The following invalid code has been deliberately ');

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

1493: add_to_source(c_new_line);
1494: add_to_source('INVALID_SEE_COMMENT_IN_SOURCE;' || c_new_line);
1495: hr_utility.set_location(l_proc, 40);
1496: --
1497: -- Write details of the error to the HR_API_HOOKS table
1498: --
1499: l_encoded_err_text := fnd_message.get_encoded;
1500: --
1501: -- Change the following update statement to

Line 1504: update hr_api_hooks

1500: --
1501: -- Change the following update statement to
1502: -- call the row handler, when it is available.
1503: --
1504: update hr_api_hooks
1505: set encoded_error = l_encoded_err_text
1506: where api_hook_id = p_api_hook_id;
1507: hr_utility.set_location(l_proc, 50);
1508: end if;

Line 1531: -- the HR_API_HOOKS table.

1527: --
1528: -- In Parameters:
1529: -- Name Reqd Type Description
1530: -- p_api_hook_id Yes number ID of the hook details from
1531: -- the HR_API_HOOKS table.
1532: -- p_legislation_package Yes varchar2 The legislation_package as
1533: -- specified in the HR_API_HOOKS
1534: -- table.
1535: -- p_legislation_function Yes varchar2 The legislation_function as

Line 1533: -- specified in the HR_API_HOOKS

1529: -- Name Reqd Type Description
1530: -- p_api_hook_id Yes number ID of the hook details from
1531: -- the HR_API_HOOKS table.
1532: -- p_legislation_package Yes varchar2 The legislation_package as
1533: -- specified in the HR_API_HOOKS
1534: -- table.
1535: -- p_legislation_function Yes varchar2 The legislation_function as
1536: -- specified in the HR_API_HOOKS
1537: -- table.

Line 1536: -- specified in the HR_API_HOOKS

1532: -- p_legislation_package Yes varchar2 The legislation_package as
1533: -- specified in the HR_API_HOOKS
1534: -- table.
1535: -- p_legislation_function Yes varchar2 The legislation_function as
1536: -- specified in the HR_API_HOOKS
1537: -- table.
1538: -- p_data_within_business_group Yes varchar2 Indicates if the data for
1539: -- this module is held within
1540: -- the context of a

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

1555: -- Creates source code to carry out legislation specific hook calls.
1556: --
1557: -- Post Failure:
1558: -- Any application errors and some system errors are written to the
1559: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.
1560: --
1561: -- Access Status:
1562: -- Internal Development Use Only.
1563: --

Line 1707: -- the HR_API_HOOKS table.

1703: --
1704: -- In Parameters:
1705: -- Name Reqd Type Description
1706: -- p_api_hook_id Yes number ID of the hook details from
1707: -- the HR_API_HOOKS table.
1708: -- p_number_of_parameters Yes number The number of parameters to
1709: -- the hook package procedure.
1710: -- p_hook_parameter_names Yes Table When the number of hook
1711: -- procedure parameters is

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

1720: -- Creates source code to carry out application specific hook calls.
1721: --
1722: -- Post Failure:
1723: -- Any application errors and some system errors are written to the
1724: -- corresponding row in the HR_API_HOOKS or HR_API_HOOK_CALLS tables.
1725: --
1726: -- Access Status:
1727: -- Internal Development Use Only.
1728: --

Line 1806: -- the HR_API_HOOKS table.

1802: --
1803: -- In Parameters:
1804: -- Name Reqd Type Description
1805: -- p_api_hook_id Yes number ID of the hook details from
1806: -- the HR_API_HOOKS table.
1807: -- p_number_of_parameters Yes number The number of parameters to
1808: -- the hook package procedure.
1809: -- p_hook_parameter_names Yes Table When the number of hook
1810: -- procedure parameters is

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

1989: -- ii) the pre-processor has successfully executed the hook call,
1990: -- from the latest version of the hook package body.
1991: --
1992: -- Prerequisites:
1993: -- This hook is known to exist in the HR_API_HOOKS table.
1994: --
1995: -- In Parameters:
1996: -- Name Reqd Type Description
1997: -- p_api_hook_id Yes number ID of the hook details from

Line 1998: -- the HR_API_HOOKS table.

1994: --
1995: -- In Parameters:
1996: -- Name Reqd Type Description
1997: -- p_api_hook_id Yes number ID of the hook details from
1998: -- the HR_API_HOOKS table.
1999: --
2000: -- Post Success:
2001: -- Updates all the rows in the HR_API_HOOK_CALLS table which match the
2002: -- api_hook_id and the enabled_flag is 'N'. Customer and legislation

Line 2067: -- the HR_API_HOOKS table.

2063: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2064: -- within the hook package.
2065: -- p_api_hook_type Yes varchar2 Type of Hook.
2066: -- p_api_hook_id Yes number ID of the hook details from
2067: -- the HR_API_HOOKS table.
2068: -- p_legislation_package Yes varchar2 The legislation_package as
2069: -- specified in the HR_API_HOOKS
2070: -- table.
2071: -- p_legislation_function Yes varchar2 The legislation_function as

Line 2069: -- specified in the HR_API_HOOKS

2065: -- p_api_hook_type Yes varchar2 Type of Hook.
2066: -- p_api_hook_id Yes number ID of the hook details from
2067: -- the HR_API_HOOKS table.
2068: -- p_legislation_package Yes varchar2 The legislation_package as
2069: -- specified in the HR_API_HOOKS
2070: -- table.
2071: -- p_legislation_function Yes varchar2 The legislation_function as
2072: -- specified in the HR_API_HOOKS
2073: -- table.

Line 2072: -- specified in the HR_API_HOOKS

2068: -- p_legislation_package Yes varchar2 The legislation_package as
2069: -- specified in the HR_API_HOOKS
2070: -- table.
2071: -- p_legislation_function Yes varchar2 The legislation_function as
2072: -- specified in the HR_API_HOOKS
2073: -- table.
2074: -- p_module_name Yes varchar2 API Module name from the
2075: -- HR_API_MODULES table.
2076: -- p_data_within_business_group Yes varchar2 Indicates if the data for

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

2093: -- Creates source code for the hook procedure in the source store.
2094: --
2095: -- Post Failure:
2096: -- Most application and some Oracle errors are written to the corresponding
2097: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2098: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2099: --
2100: -- Access Status:
2101: -- Internal Development Use Only.

Line 2164: , hr_api_hooks ahk_ap

2160: --
2161: cursor csr_ap_leg_call_exist is
2162: select 1
2163: from hr_api_hook_calls ahc
2164: , hr_api_hooks ahk_ap
2165: , hr_api_modules amk
2166: , hr_api_hooks ahk_bp
2167: where ahc.enabled_flag = 'Y'
2168: and ahc.legislation_code is not null

Line 2166: , hr_api_hooks ahk_bp

2162: select 1
2163: from hr_api_hook_calls ahc
2164: , hr_api_hooks ahk_ap
2165: , hr_api_modules amk
2166: , hr_api_hooks ahk_bp
2167: where ahc.enabled_flag = 'Y'
2168: and ahc.legislation_code is not null
2169: and ahc.api_hook_id = ahk_ap.api_hook_id
2170: and ahk_ap.api_hook_type = 'AP'

Line 2435: -- the HR_API_HOOKS table.

2431: -- p_hook_package Yes varchar2 Name of the hook package.
2432: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2433: -- within the hook package.
2434: -- p_api_hook_id Yes number ID of the hook details from
2435: -- the HR_API_HOOKS table.
2436: --
2437: -- Post Success:
2438: -- Creates the list of parameters in the source store.
2439: -- p_param_list_error is set to false. p_number_of_parameters is set to the

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

2441: -- p_number_of_parameters is greater than zero then p_hook_parameter_names
2442: -- is populated with the list of parameter names to hook package procedure.
2443: -- p_hook_parameter_datatypes is set to the corresponding parameter
2444: -- datatypes. The internal Oracle datatypes number codes are used, not the
2445: -- text string representations. hr_api_hooks.encoded_error is updated to
2446: -- null.
2447: --
2448: -- Post Failure:
2449: -- When a hook package procedure header or parameter error occurs the

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

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

Line 2457: -- hr_api_hooks.encoded_error.

2453: -- code to force the problem to be investigated and resolved. The
2454: -- p_number_of_parameters, p_hook_parameter_names and
2455: -- p_hook_parameter_datatypes parameters contain undefined values and no
2456: -- attempt should be made to use them. Details of the error are written to
2457: -- hr_api_hooks.encoded_error.
2458: --
2459: -- Access Status:
2460: -- Internal Development Use Only.
2461: --

Line 2508: -- the HR_API_HOOKS table.

2504: -- l_datatype number.
2505: l_param_code varchar2(20000) := null; -- The parameter list code.
2506: l_encoded_err_text varchar2(2000); -- Set to the encoded error text
2507: -- when an error is written to
2508: -- the HR_API_HOOKS table.
2509: l_proc varchar2(72) := g_package||'make_parameter_list';
2510: begin
2511: hr_utility.set_location('Entering:'|| l_proc, 10);
2512: --

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

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

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

2729: end if;
2730: hr_utility.set_location(l_proc, 150);
2731: --
2732: -- Set the out parameters for this procedure and update
2733: -- the error details in the hr_api_hooks table.
2734: --
2735: if not l_error then
2736: --
2737: -- Remember how many parameters exist to the hook package procedure

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

2740: -- Indicate that no hook package procedure or parameter list errors
2741: -- where found.
2742: p_param_list_error := false;
2743: --
2744: -- Ensure any error details placed in the HR_API_HOOKS table, from previous
2745: -- generates, are cleared. When the make_find_legislation procedure is
2746: -- executed, sometimes an error will be written to HR_API_HOOKS. In certain
2747: -- cases the 'clearing' update done here will be a waste of time. It is not
2748: -- possible to detect here when make_find_legislation will find an error.

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

2742: p_param_list_error := false;
2743: --
2744: -- Ensure any error details placed in the HR_API_HOOKS table, from previous
2745: -- generates, are cleared. When the make_find_legislation procedure is
2746: -- executed, sometimes an error will be written to HR_API_HOOKS. In certain
2747: -- cases the 'clearing' update done here will be a waste of time. It is not
2748: -- possible to detect here when make_find_legislation will find an error.
2749: -- Also make_find_legislation will not be called if there are any hook
2750: -- calls. So the 'clearing' update is always done here.

Line 2755: update hr_api_hooks

2751: --
2752: -- Change the following update statement to
2753: -- call the row handler, when it is available.
2754: --
2755: update hr_api_hooks
2756: set encoded_error = null
2757: where api_hook_id = p_api_hook_id;
2758: hr_utility.set_location(l_proc, 160);
2759: else

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

2758: hr_utility.set_location(l_proc, 160);
2759: else
2760: --
2761: -- The parameter list code for this hook procedure could not be generated
2762: -- due to an error. Write details of the error to the HR_API_HOOKS table.
2763: -- Also deliberately create some invalid code in the hook package body
2764: -- to prevent the package from compiling. This will force somebody to
2765: -- investigate the problem.
2766: --

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

2775: '-- an error. Details of the error, in FND encoded ' ||
2776: 'format, can be obtained' || c_new_line ||
2777: '-- with the following sql statement:' || c_new_line ||
2778: '-- select h.encoded_error' || c_new_line ||
2779: '-- from hr_api_hooks h' || c_new_line ||
2780: '-- where h.api_hook_id = ' || to_char(p_api_hook_id) ||
2781: ';' || c_new_line ||
2782: '-- The following invalid code has been deliberately ' ||
2783: 'created to force' || c_new_line ||

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

2785: c_new_line || 'INVALID_SEE_COMMENT_IN_SOURCE;' ||
2786: c_new_line;
2787: hr_utility.set_location(l_proc, 170);
2788: --
2789: -- Write details of the error to the HR_API_HOOKS table
2790: --
2791: l_encoded_err_text := fnd_message.get_encoded;
2792: --
2793: -- Change the following update statement to

Line 2796: update hr_api_hooks

2792: --
2793: -- Change the following update statement to
2794: -- call the row handler, when it is available.
2795: --
2796: update hr_api_hooks
2797: set encoded_error = l_encoded_err_text
2798: where api_hook_id = p_api_hook_id;
2799: hr_utility.set_location(l_proc, 180);
2800: end if;

Line 2829: -- the HR_API_HOOKS table.

2825: -- p_hook_procedure Yes varchar2 Name of the hook procedure
2826: -- within the hook package.
2827: -- p_api_hook_type Yes varchar2 Type of Hook.
2828: -- p_api_hook_id Yes number ID of the hook details from
2829: -- the HR_API_HOOKS table.
2830: -- p_legislation_package Yes varchar2 The legislation_package as
2831: -- specified in the HR_API_HOOKS
2832: -- table.
2833: -- p_legislation_function Yes varchar2 The legislation_function as

Line 2831: -- specified in the HR_API_HOOKS

2827: -- p_api_hook_type Yes varchar2 Type of Hook.
2828: -- p_api_hook_id Yes number ID of the hook details from
2829: -- the HR_API_HOOKS table.
2830: -- p_legislation_package Yes varchar2 The legislation_package as
2831: -- specified in the HR_API_HOOKS
2832: -- table.
2833: -- p_legislation_function Yes varchar2 The legislation_function as
2834: -- specified in the HR_API_HOOKS
2835: -- table.

Line 2834: -- specified in the HR_API_HOOKS

2830: -- p_legislation_package Yes varchar2 The legislation_package as
2831: -- specified in the HR_API_HOOKS
2832: -- table.
2833: -- p_legislation_function Yes varchar2 The legislation_function as
2834: -- specified in the HR_API_HOOKS
2835: -- table.
2836: -- p_module_name Yes varchar2 API Module name from the
2837: -- HR_API_MODULES table.
2838: -- p_data_within_business_group Yes varchar2 Indicates if the data for

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

2845: -- Creates source code for the hook procedure in the source store.
2846: --
2847: -- Post Failure:
2848: -- Most application and some Oracle errors are written to the corresponding
2849: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2850: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2851: --
2852: -- Access Status:
2853: -- Internal Development Use Only.

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

2958: -- p_hook_package Yes varchar2 Name of the hook package.
2959: --
2960: -- Post Success:
2961: -- Creates all the procedure bodies for the hook package. Only creates
2962: -- those procedures which have been listed in the the HR_API_HOOKS table.
2963: --
2964: -- Post Failure:
2965: -- Most application and some Oracle errors are written to the corresponding
2966: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application

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

2962: -- those procedures which have been listed in the the HR_API_HOOKS table.
2963: --
2964: -- Post Failure:
2965: -- Most application and some Oracle errors are written to the corresponding
2966: -- rows in the HR_API_HOOKS or HR_API_HOOK_CALLS tables. Some application
2967: -- or Oracle errors are raised from this procedure as PL/SQL exceptions.
2968: --
2969: -- Access Status:
2970: -- Internal Development Use Only.

Line 2989: , hr_api_hooks ahk

2985: , ahk.legislation_function
2986: , amd.module_name
2987: , amd.data_within_business_group
2988: from hr_api_modules amd
2989: , hr_api_hooks ahk
2990: where amd.api_module_id = ahk.api_module_id
2991: and ahk.hook_package = p_hook_package;
2992: --
2993: l_proc varchar2(72) := g_package||'create_procedures';

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

3036: -- Post Failure:
3037: -- If the text could not been found then an error is not raised here.
3038: -- When the hook package header does not exist in the database the
3039: -- 'make_parameter_list' procedure will raise an error and save the details
3040: -- to the HR_API_HOOKS table. The 'make_parameter_list' procedure is called
3041: -- as part of the 'create_procedures' work.
3042: --
3043: -- Access Status:
3044: -- Internal Development Use Only.

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

3166: --
3167: -- If the text could not been found then do not raise an error here.
3168: -- When the hook package header does not exist in the database the
3169: -- 'make_parameter_list' procedure will raise an error and save the
3170: -- details to the HR_API_HOOKS table. The 'make_parameter_list'
3171: -- procedure is called as part of the 'create_procedures' work.
3172: --
3173: if l_pkg_find_found then
3174: --