DBA Data[Home] [Help]

APPS.BEN_BER_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 195: When hr_api.check_integrity_violated Then

191: --
192: hr_utility.set_location(' Leaving:'||l_proc, 15);
193: --
194: Exception
195: When hr_api.check_integrity_violated Then
196: -- A check constraint has been violated
197: --
198: ben_ber_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

195: When hr_api.check_integrity_violated Then
196: -- A check constraint has been violated
197: --
198: ben_ber_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: --
203: ben_ber_shd.constraint_error

Line 200: When hr_api.unique_integrity_violated Then

196: -- A check constraint has been violated
197: --
198: ben_ber_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: --
203: ben_ber_shd.constraint_error
204: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: --
203: ben_ber_shd.constraint_error
204: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
205: When Others Then
206: --
207: Raise;
208: End dt_insert_dml;

Line 411: when hr_api.cannot_find_prog_unit then

407: );
408: --
409: exception
410: --
411: when hr_api.cannot_find_prog_unit then
412: --
413: hr_api.cannot_find_prog_unit_error
414: (p_module_name => 'BEN_ELIG_RSLT_F'
415: ,p_hook_type => 'AI');

Line 413: hr_api.cannot_find_prog_unit_error

409: exception
410: --
411: when hr_api.cannot_find_prog_unit then
412: --
413: hr_api.cannot_find_prog_unit_error
414: (p_module_name => 'BEN_ELIG_RSLT_F'
415: ,p_hook_type => 'AI');
416: --
417: end;

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

442: --
443: -- Post Failure:
444: -- The Lck process can fail for:
445: -- 1) When attempting to lock the row the row could already be locked by
446: -- another user. This will raise the HR_Api.Object_Locked exception.
447: -- 2) When attempting to the lock the parent which doesn't exist.
448: -- For the entity to be locked the parent must exist!
449: --
450: -- Developer Implementation Notes:

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

504: ,p_rec in out nocopy ben_ber_shd.g_rec_type
505: ) is
506: --
507: l_proc varchar2(72) := g_package||'ins';
508: l_datetrack_mode varchar2(30) := hr_api.g_insert;
509: l_validation_start_date date;
510: l_validation_end_date date;
511: --
512: Begin