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_HOOK_INTERNAL dependencies on HR_API

Line 1: Package hr_api_hook_internal AUTHID CURRENT_USER as

1: Package hr_api_hook_internal AUTHID CURRENT_USER as
2: /* $Header: peahkbsi.pkh 115.1 2002/12/03 16:28:52 apholt ship $ */
3: --
4: --
5: -- -------------------------------------------------------------------

Line 11: -- The HR_API_HOOKS table lists the points which are available in each API

7: -- -------------------------------------------------------------------
8: -- {Start Of Comments}
9: --
10: -- Description:
11: -- The HR_API_HOOKS table lists the points which are available in each API
12: -- module. It contains data sourced from the HR core Development team. If
13: -- legislation group/ partners and legislation vertical market groups
14: -- implement additional APIs which have user hooks they will also own rows
15: -- in the table. Each row is created using this procedure.

Line 18: -- the HR_API_MODULES table. The p_api_module_id acts as a foreign key to

14: -- implement additional APIs which have user hooks they will also own rows
15: -- in the table. Each row is created using this procedure.
16: --
17: -- Each row should be a child of a parent API module which already exists on
18: -- the HR_API_MODULES table. The p_api_module_id acts as a foreign key to
19: -- this table.
20: --
21: -- The hook package and hook procedure parms are both mandatory. An API
22: -- developer should not create two different hook points which call the same

Line 24: -- unique in HR_API_HOOKS.

20: --
21: -- The hook package and hook procedure parms are both mandatory. An API
22: -- developer should not create two different hook points which call the same
23: -- hook package. The combination of hook package and hook procedure should be
24: -- unique in HR_API_HOOKS.
25: --
26: -- The Legislation Code value should only be set if the API module contains at
27: -- least one user hook and will be maintained by a legislation group or a
28: -- legislation vertical market. Only the legislation group which created the

Line 119: -- This API deletes a row on the HR_API_HOOKS table.

115: -- ----------------------------------------------------------------
116: -- {Start Of Comments}
117: --
118: -- Description:
119: -- This API deletes a row on the HR_API_HOOKS table.
120: --
121: -- A hook cannot be deleted if it is reference by a row in the
122: -- HR_API_HOOK_CALLS. Only HR core development can delete a row where
123: -- LEGISLATION_CODE is null. Only the legislation group which created the

Line 122: -- HR_API_HOOK_CALLS. Only HR core development can delete a row where

118: -- Description:
119: -- This API deletes a row on the HR_API_HOOKS table.
120: --
121: -- A hook cannot be deleted if it is reference by a row in the
122: -- HR_API_HOOK_CALLS. Only HR core development can delete a row where
123: -- LEGISLATION_CODE is null. Only the legislation group which created the
124: -- row where legislation code is not not null can delete the row.
125: -- These two checks are not enforced by code.
126: --

Line 216: p_api_hook_type in varchar2 default hr_api.g_varchar2,

212: procedure update_api_hook
213: (p_validate in boolean default false,
214: p_effective_date in date,
215: p_api_hook_id in number,
216: p_api_hook_type in varchar2 default hr_api.g_varchar2,
217: p_hook_package in varchar2 default hr_api.g_varchar2,
218: p_hook_procedure in varchar2 default hr_api.g_varchar2,
219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2

Line 217: p_hook_package in varchar2 default hr_api.g_varchar2,

213: (p_validate in boolean default false,
214: p_effective_date in date,
215: p_api_hook_id in number,
216: p_api_hook_type in varchar2 default hr_api.g_varchar2,
217: p_hook_package in varchar2 default hr_api.g_varchar2,
218: p_hook_procedure in varchar2 default hr_api.g_varchar2,
219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2
221: );

Line 218: p_hook_procedure in varchar2 default hr_api.g_varchar2,

214: p_effective_date in date,
215: p_api_hook_id in number,
216: p_api_hook_type in varchar2 default hr_api.g_varchar2,
217: p_hook_package in varchar2 default hr_api.g_varchar2,
218: p_hook_procedure in varchar2 default hr_api.g_varchar2,
219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2
221: );
222: --

Line 219: p_legislation_package in varchar2 default hr_api.g_varchar2,

215: p_api_hook_id in number,
216: p_api_hook_type in varchar2 default hr_api.g_varchar2,
217: p_hook_package in varchar2 default hr_api.g_varchar2,
218: p_hook_procedure in varchar2 default hr_api.g_varchar2,
219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2
221: );
222: --
223: end hr_api_hook_internal;

Line 220: p_legislation_function in varchar2 default hr_api.g_varchar2

216: p_api_hook_type in varchar2 default hr_api.g_varchar2,
217: p_hook_package in varchar2 default hr_api.g_varchar2,
218: p_hook_procedure in varchar2 default hr_api.g_varchar2,
219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2
221: );
222: --
223: end hr_api_hook_internal;

Line 223: end hr_api_hook_internal;

219: p_legislation_package in varchar2 default hr_api.g_varchar2,
220: p_legislation_function in varchar2 default hr_api.g_varchar2
221: );
222: --
223: end hr_api_hook_internal;