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: --
199: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
200: hr_utility.set_location(' Leaving:'||l_proc, 15);
201: --
202: Exception
203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
206: pay_frr_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
206: pay_frr_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
211: pay_frr_shd.constraint_error
204: -- A check constraint has been violated
205: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
206: pay_frr_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
211: pay_frr_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
211: pay_frr_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
213: When Others Then
214: pay_frr_shd.g_api_dml := false; -- Unset the api dml status
215: Raise;
216: End dt_insert_dml;
477: );
478: --
479: exception
480: --
481: when hr_api.cannot_find_prog_unit then
482: --
483: hr_api.cannot_find_prog_unit_error
484: (p_module_name => 'PAY_FORMULA_RESULT_RULES_F'
485: ,p_hook_type => 'AI');
479: exception
480: --
481: when hr_api.cannot_find_prog_unit then
482: --
483: hr_api.cannot_find_prog_unit_error
484: (p_module_name => 'PAY_FORMULA_RESULT_RULES_F'
485: ,p_hook_type => 'AI');
486: --
487: end;
512: --
513: -- Post Failure:
514: -- The Lck process can fail for:
515: -- 1) When attempting to lock the row the row could already be locked by
516: -- another user. This will raise the HR_Api.Object_Locked exception.
517: -- 2) When attempting to the lock the parent which doesn't exist.
518: -- For the entity to be locked the parent must exist!
519: --
520: -- Developer Implementation Notes:
571: ,p_rec in out nocopy pay_frr_shd.g_rec_type
572: ) is
573: --
574: l_proc varchar2(72) := g_package||'ins';
575: l_datetrack_mode varchar2(30) := hr_api.g_insert;
576: l_validation_start_date date;
577: l_validation_end_date date;
578: --
579: Begin