DBA Data[Home] [Help]

APPS.PAY_PPD_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 209: When hr_api.check_integrity_violated Then

205: --
206: hr_utility.set_location(' Leaving:'||l_proc, 15);
207: --
208: Exception
209: When hr_api.check_integrity_violated Then
210: -- A check constraint has been violated
211: --
212: pay_ppd_shd.constraint_error
213: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

209: When hr_api.check_integrity_violated Then
210: -- A check constraint has been violated
211: --
212: pay_ppd_shd.constraint_error
213: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
214: When hr_api.unique_integrity_violated Then
215: -- Unique integrity has been violated
216: --
217: pay_ppd_shd.constraint_error

Line 214: When hr_api.unique_integrity_violated Then

210: -- A check constraint has been violated
211: --
212: pay_ppd_shd.constraint_error
213: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
214: When hr_api.unique_integrity_violated Then
215: -- Unique integrity has been violated
216: --
217: pay_ppd_shd.constraint_error
218: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

214: When hr_api.unique_integrity_violated Then
215: -- Unique integrity has been violated
216: --
217: pay_ppd_shd.constraint_error
218: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
219: When Others Then
220: --
221: Raise;
222: End dt_insert_dml;

Line 439: when hr_api.cannot_find_prog_unit then

435: );
436: --
437: exception
438: --
439: when hr_api.cannot_find_prog_unit then
440: --
441: hr_api.cannot_find_prog_unit_error
442: (p_module_name => 'PAY_PL_PAYE_DETAILS_F'
443: ,p_hook_type => 'AI');

Line 441: hr_api.cannot_find_prog_unit_error

437: exception
438: --
439: when hr_api.cannot_find_prog_unit then
440: --
441: hr_api.cannot_find_prog_unit_error
442: (p_module_name => 'PAY_PL_PAYE_DETAILS_F'
443: ,p_hook_type => 'AI');
444: --
445: end;

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

470: --
471: -- Post Failure:
472: -- The Lck process can fail for:
473: -- 1) When attempting to lock the row the row could already be locked by
474: -- another user. This will raise the HR_Api.Object_Locked exception.
475: -- 2) When attempting to the lock the parent which doesn't exist.
476: -- For the entity to be locked the parent must exist!
477: --
478: -- Developer Implementation Notes:

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

564: ,p_rec in out nocopy pay_ppd_shd.g_rec_type
565: ) is
566: --
567: l_proc varchar2(72) := g_package||'ins';
568: l_datetrack_mode varchar2(30) := hr_api.g_insert;
569: l_validation_start_date date;
570: l_validation_end_date date;
571: --
572: Begin