DBA Data[Home] [Help]

APPS.PAY_PSD_INS dependencies on HR_API

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

112: --
113: -- If the datetrack_mode is not INSERT then we must populate the WHO
114: -- columns with the 'old' creation values and 'new' updated values.
115: --
116: If (p_datetrack_mode <> hr_api.g_insert) then
117: hr_utility.set_location(l_proc, 10);
118: --
119: -- Get the object version number for the insert
120: --

Line 229: When hr_api.check_integrity_violated Then

225: --
226: hr_utility.set_location(' Leaving:'||l_proc, 15);
227: --
228: Exception
229: When hr_api.check_integrity_violated Then
230: -- A check constraint has been violated
231: --
232: pay_psd_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

229: When hr_api.check_integrity_violated Then
230: -- A check constraint has been violated
231: --
232: pay_psd_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: pay_psd_shd.constraint_error

Line 234: When hr_api.unique_integrity_violated Then

230: -- A check constraint has been violated
231: --
232: pay_psd_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: pay_psd_shd.constraint_error
238: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: pay_psd_shd.constraint_error
238: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
239: When Others Then
240: --
241: Raise;
242: End dt_insert_dml;

Line 479: when hr_api.cannot_find_prog_unit then

475: );
476: --
477: exception
478: --
479: when hr_api.cannot_find_prog_unit then
480: --
481: hr_api.cannot_find_prog_unit_error
482: (p_module_name => 'PAY_PL_SII_DETAILS_F'
483: ,p_hook_type => 'AI');

Line 481: hr_api.cannot_find_prog_unit_error

477: exception
478: --
479: when hr_api.cannot_find_prog_unit then
480: --
481: hr_api.cannot_find_prog_unit_error
482: (p_module_name => 'PAY_PL_SII_DETAILS_F'
483: ,p_hook_type => 'AI');
484: --
485: end;

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

510: --
511: -- Post Failure:
512: -- The Lck process can fail for:
513: -- 1) When attempting to lock the row the row could already be locked by
514: -- another user. This will raise the HR_Api.Object_Locked exception.
515: -- 2) When attempting to the lock the parent which doesn't exist.
516: -- For the entity to be locked the parent must exist!
517: --
518: -- Developer Implementation Notes:

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

602: ,p_rec in out nocopy pay_psd_shd.g_rec_type
603: ) is
604: --
605: l_proc varchar2(72) := g_package||'ins';
606: l_datetrack_mode varchar2(30) := hr_api.g_insert;
607: l_validation_start_date date;
608: l_validation_end_date date;
609: --
610: Begin