DBA Data[Home] [Help]

APPS.BEN_CTY_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 257: When hr_api.check_integrity_violated Then

253: --
254: hr_utility.set_location(' Leaving:'||l_proc, 15);
255: --
256: Exception
257: When hr_api.check_integrity_violated Then
258: -- A check constraint has been violated
259: --
260: ben_cty_shd.constraint_error
261: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

257: When hr_api.check_integrity_violated Then
258: -- A check constraint has been violated
259: --
260: ben_cty_shd.constraint_error
261: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
262: When hr_api.unique_integrity_violated Then
263: -- Unique integrity has been violated
264: --
265: ben_cty_shd.constraint_error

Line 262: When hr_api.unique_integrity_violated Then

258: -- A check constraint has been violated
259: --
260: ben_cty_shd.constraint_error
261: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
262: When hr_api.unique_integrity_violated Then
263: -- Unique integrity has been violated
264: --
265: ben_cty_shd.constraint_error
266: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

262: When hr_api.unique_integrity_violated Then
263: -- Unique integrity has been violated
264: --
265: ben_cty_shd.constraint_error
266: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
267: When Others Then
268: --
269: Raise;
270: End dt_insert_dml;

Line 537: when hr_api.cannot_find_prog_unit then

533: );
534: --
535: exception
536: --
537: when hr_api.cannot_find_prog_unit then
538: --
539: hr_api.cannot_find_prog_unit_error
540: (p_module_name => 'BEN_COMPTNCY_RT_F'
541: ,p_hook_type => 'AI');

Line 539: hr_api.cannot_find_prog_unit_error

535: exception
536: --
537: when hr_api.cannot_find_prog_unit then
538: --
539: hr_api.cannot_find_prog_unit_error
540: (p_module_name => 'BEN_COMPTNCY_RT_F'
541: ,p_hook_type => 'AI');
542: --
543: end;

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

568: --
569: -- Post Failure:
570: -- The Lck process can fail for:
571: -- 1) When attempting to lock the row the row could already be locked by
572: -- another user. This will raise the HR_Api.Object_Locked exception.
573: -- 2) When attempting to the lock the parent which doesn't exist.
574: -- For the entity to be locked the parent must exist!
575: --
576: -- Developer Implementation Notes:

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

630: ,p_rec in out nocopy ben_cty_shd.g_rec_type
631: ) is
632: --
633: l_proc varchar2(72) := g_package||'ins';
634: l_datetrack_mode varchar2(30) := hr_api.g_insert;
635: l_validation_start_date date;
636: l_validation_end_date date;
637: --
638: Begin