DBA Data[Home] [Help]

APPS.BEN_OTP_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 239: When hr_api.check_integrity_violated Then

235: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
236: hr_utility.set_location(' Leaving:'||l_proc, 15);
237: --
238: Exception
239: When hr_api.check_integrity_violated Then
240: -- A check constraint has been violated
241: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
242: ben_otp_shd.constraint_error
243: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

239: When hr_api.check_integrity_violated Then
240: -- A check constraint has been violated
241: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
242: ben_otp_shd.constraint_error
243: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
244: When hr_api.unique_integrity_violated Then
245: -- Unique integrity has been violated
246: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
247: ben_otp_shd.constraint_error

Line 244: When hr_api.unique_integrity_violated Then

240: -- A check constraint has been violated
241: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
242: ben_otp_shd.constraint_error
243: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
244: When hr_api.unique_integrity_violated Then
245: -- Unique integrity has been violated
246: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
247: ben_otp_shd.constraint_error
248: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

244: When hr_api.unique_integrity_violated Then
245: -- Unique integrity has been violated
246: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
247: ben_otp_shd.constraint_error
248: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
249: When Others Then
250: ben_otp_shd.g_api_dml := false; -- Unset the api dml status
251: Raise;
252: End dt_insert_dml;

Line 489: when hr_api.cannot_find_prog_unit then

485: );
486: --
487: exception
488: --
489: when hr_api.cannot_find_prog_unit then
490: --
491: hr_api.cannot_find_prog_unit_error
492: (p_module_name => 'BEN_OPTIP_F'
493: ,p_hook_type => 'AI');

Line 491: hr_api.cannot_find_prog_unit_error

487: exception
488: --
489: when hr_api.cannot_find_prog_unit then
490: --
491: hr_api.cannot_find_prog_unit_error
492: (p_module_name => 'BEN_OPTIP_F'
493: ,p_hook_type => 'AI');
494: --
495: end;

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

520: --
521: -- Post Failure:
522: -- The Lck process can fail for:
523: -- 1) When attempting to lock the row the row could already be locked by
524: -- another user. This will raise the HR_Api.Object_Locked exception.
525: -- 2) When attempting to the lock the parent which doesn't exist.
526: -- For the entity to be locked the parent must exist!
527: --
528: -- Developer Implementation Notes:

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

588: ,p_rec in out nocopy ben_otp_shd.g_rec_type
589: ) is
590: --
591: l_proc varchar2(72) := g_package||'ins';
592: l_datetrack_mode varchar2(30) := hr_api.g_insert;
593: l_validation_start_date date;
594: l_validation_end_date date;
595: --
596: Begin