APPS.PAY_UCI_INS dependencies on HR_API

Line 125: If (p_datetrack_mode <> hr_api.g_insert) then

121: --
122: -- If the datetrack_mode is not INSERT then we must populate the WHO
123: -- columns with the 'old' creation values and 'new' updated values.
124: --
125: If (p_datetrack_mode <> hr_api.g_insert) then
126: hr_utility.set_location(l_proc, 10);
127: --
128: -- Select the 'old' created values
129: --

Line 193: When hr_api.check_integrity_violated Then

189: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
190: hr_utility.set_location(' Leaving:'||l_proc, 15);
191: --
192: Exception
193: When hr_api.check_integrity_violated Then
194: -- A check constraint has been violated
195: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
196: pay_uci_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

193: When hr_api.check_integrity_violated Then
194: -- A check constraint has been violated
195: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
196: pay_uci_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
201: pay_uci_shd.constraint_error

Line 198: When hr_api.unique_integrity_violated Then

194: -- A check constraint has been violated
195: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
196: pay_uci_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
201: pay_uci_shd.constraint_error
202: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 202: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
201: pay_uci_shd.constraint_error
202: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
203: When Others Then
204: pay_uci_shd.g_api_dml := false; -- Unset the api dml status
205: Raise;
206: End dt_insert_dml;

Line 463: when hr_api.cannot_find_prog_unit then

459: );
460: --
461: exception
462: --
463: when hr_api.cannot_find_prog_unit then
464: --
465: hr_api.cannot_find_prog_unit_error
466: (p_module_name => 'PAY_USER_COLUMN_INSTANCES_F'
467: ,p_hook_type => 'AI');

Line 465: hr_api.cannot_find_prog_unit_error

461: exception
462: --
463: when hr_api.cannot_find_prog_unit then
464: --
465: hr_api.cannot_find_prog_unit_error
466: (p_module_name => 'PAY_USER_COLUMN_INSTANCES_F'
467: ,p_hook_type => 'AI');
468: --
469: end;

Line 498: -- another user. This will raise the HR_Api.Object_Locked exception.

494: --
495: -- Post Failure:
496: -- The Lck process can fail for:
497: -- 1) When attempting to lock the row the row could already be locked by
498: -- another user. This will raise the HR_Api.Object_Locked exception.
499: -- 2) When attempting to the lock the parent which doesn't exist.
500: -- For the entity to be locked the parent must exist!
501: --
502: -- Developer Implementation Notes:

Line 560: l_datetrack_mode varchar2(30) := hr_api.g_insert;

556: ,p_rec in out nocopy pay_uci_shd.g_rec_type
557: ) is
558: --
559: l_proc varchar2(72) := g_package||'ins';
560: l_datetrack_mode varchar2(30) := hr_api.g_insert;
561: l_validation_start_date date;
562: l_validation_end_date date;
563: --
564: Begin