DBA Data[Home] [Help]

APPS.BEN_QIG_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 255: When hr_api.check_integrity_violated Then

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

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

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

Line 260: When hr_api.unique_integrity_violated Then

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

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

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

Line 533: when hr_api.cannot_find_prog_unit then

529: );
530: --
531: exception
532: --
533: when hr_api.cannot_find_prog_unit then
534: --
535: hr_api.cannot_find_prog_unit_error
536: (p_module_name => 'BEN_QUA_IN_GR_RT_F'
537: ,p_hook_type => 'AI');

Line 535: hr_api.cannot_find_prog_unit_error

531: exception
532: --
533: when hr_api.cannot_find_prog_unit then
534: --
535: hr_api.cannot_find_prog_unit_error
536: (p_module_name => 'BEN_QUA_IN_GR_RT_F'
537: ,p_hook_type => 'AI');
538: --
539: end;

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

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

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

626: ,p_rec in out nocopy ben_qig_shd.g_rec_type
627: ) is
628: --
629: l_proc varchar2(72) := g_package||'ins';
630: l_datetrack_mode varchar2(30) := hr_api.g_insert;
631: l_validation_start_date date;
632: l_validation_end_date date;
633: --
634: Begin