APPS.BEN_VEP_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 231: When hr_api.check_integrity_violated Then

227: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
228: hr_utility.set_location(' Leaving:'||l_proc, 15);
229: --
230: Exception
231: When hr_api.check_integrity_violated Then
232: -- A check constraint has been violated
233: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
234: ben_vep_shd.constraint_error
235: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

231: When hr_api.check_integrity_violated Then
232: -- A check constraint has been violated
233: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
234: ben_vep_shd.constraint_error
235: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
236: When hr_api.unique_integrity_violated Then
237: -- Unique integrity has been violated
238: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
239: ben_vep_shd.constraint_error

Line 236: When hr_api.unique_integrity_violated Then

232: -- A check constraint has been violated
233: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
234: ben_vep_shd.constraint_error
235: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
236: When hr_api.unique_integrity_violated Then
237: -- Unique integrity has been violated
238: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
239: ben_vep_shd.constraint_error
240: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

236: When hr_api.unique_integrity_violated Then
237: -- Unique integrity has been violated
238: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
239: ben_vep_shd.constraint_error
240: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
241: When Others Then
242: ben_vep_shd.g_api_dml := false; -- Unset the api dml status
243: Raise;
244: End dt_insert_dml;

Line 473: when hr_api.cannot_find_prog_unit then

469: );
470: --
471: exception
472: --
473: when hr_api.cannot_find_prog_unit then
474: --
475: hr_api.cannot_find_prog_unit_error
476: (p_module_name => 'BEN_VRBL_RT_ELIG_PRFL_F'
477: ,p_hook_type => 'AI');

Line 475: hr_api.cannot_find_prog_unit_error

471: exception
472: --
473: when hr_api.cannot_find_prog_unit then
474: --
475: hr_api.cannot_find_prog_unit_error
476: (p_module_name => 'BEN_VRBL_RT_ELIG_PRFL_F'
477: ,p_hook_type => 'AI');
478: --
479: end;

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

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

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

569: ,p_rec in out nocopy ben_vep_shd.g_rec_type
570: ) is
571: --
572: l_proc varchar2(72) := g_package||'ins';
573: l_datetrack_mode varchar2(30) := hr_api.g_insert;
574: l_validation_start_date date;
575: l_validation_end_date date;
576: --
577: Begin