DBA Data[Home] [Help]

APPS.PAY_ISB_INS dependencies on HR_API

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

99: --
100: -- If the datetrack_mode is not INSERT then we must populate the WHO
101: -- columns with the 'old' creation values and 'new' updated values.
102: --
103: If (p_datetrack_mode <> hr_api.g_insert) then
104: hr_utility.set_location(l_proc, 10);
105: --
106: -- Select the 'old' created values
107: --

Line 187: When hr_api.check_integrity_violated Then

183: --
184: hr_utility.set_location(' Leaving:'||l_proc, 15);
185: --
186: Exception
187: When hr_api.check_integrity_violated Then
188: -- A check constraint has been violated
189: --
190: pay_isb_shd.constraint_error
191: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

187: When hr_api.check_integrity_violated Then
188: -- A check constraint has been violated
189: --
190: pay_isb_shd.constraint_error
191: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
192: When hr_api.unique_integrity_violated Then
193: -- Unique integrity has been violated
194: --
195: pay_isb_shd.constraint_error

Line 192: When hr_api.unique_integrity_violated Then

188: -- A check constraint has been violated
189: --
190: pay_isb_shd.constraint_error
191: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
192: When hr_api.unique_integrity_violated Then
193: -- Unique integrity has been violated
194: --
195: pay_isb_shd.constraint_error
196: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

192: When hr_api.unique_integrity_violated Then
193: -- Unique integrity has been violated
194: --
195: pay_isb_shd.constraint_error
196: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
197: When Others Then
198: --
199: Raise;
200: End dt_insert_dml;

Line 385: when hr_api.cannot_find_prog_unit then

381: );
382: --
383: exception
384: --
385: when hr_api.cannot_find_prog_unit then
386: --
387: hr_api.cannot_find_prog_unit_error
388: (p_module_name => 'PAY_IE_SOCIAL_BENEFITS_F'
389: ,p_hook_type => 'AI');

Line 387: hr_api.cannot_find_prog_unit_error

383: exception
384: --
385: when hr_api.cannot_find_prog_unit then
386: --
387: hr_api.cannot_find_prog_unit_error
388: (p_module_name => 'PAY_IE_SOCIAL_BENEFITS_F'
389: ,p_hook_type => 'AI');
390: --
391: end;

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

416: --
417: -- Post Failure:
418: -- The Lck process can fail for:
419: -- 1) When attempting to lock the row the row could already be locked by
420: -- another user. This will raise the HR_Api.Object_Locked exception.
421: -- 2) When attempting to the lock the parent which doesn't exist.
422: -- For the entity to be locked the parent must exist!
423: --
424: -- Developer Implementation Notes:

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

478: ,p_rec in out nocopy pay_isb_shd.g_rec_type
479: ) is
480: --
481: l_proc varchar2(72) := g_package||'ins';
482: l_datetrack_mode varchar2(30) := hr_api.g_insert;
483: l_validation_start_date date;
484: l_validation_end_date date;
485: --
486: Begin