APPS.PAY_RFM_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 217: When hr_api.check_integrity_violated Then

213: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
214: hr_utility.set_location(' Leaving:'||l_proc, 15);
215: --
216: Exception
217: When hr_api.check_integrity_violated Then
218: -- A check constraint has been violated
219: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
220: pay_rfm_shd.constraint_error
221: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

217: When hr_api.check_integrity_violated Then
218: -- A check constraint has been violated
219: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
220: pay_rfm_shd.constraint_error
221: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
222: When hr_api.unique_integrity_violated Then
223: -- Unique integrity has been violated
224: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
225: pay_rfm_shd.constraint_error

Line 222: When hr_api.unique_integrity_violated Then

218: -- A check constraint has been violated
219: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
220: pay_rfm_shd.constraint_error
221: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
222: When hr_api.unique_integrity_violated Then
223: -- Unique integrity has been violated
224: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
225: pay_rfm_shd.constraint_error
226: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

222: When hr_api.unique_integrity_violated Then
223: -- Unique integrity has been violated
224: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
225: pay_rfm_shd.constraint_error
226: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
227: When Others Then
228: pay_rfm_shd.g_api_dml := false; -- Unset the api dml status
229: Raise;
230: End dt_insert_dml;

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

477: --
478: -- Post Failure:
479: -- The Lck process can fail for:
480: -- 1) When attempting to lock the row the row could already be locked by
481: -- another user. This will raise the HR_Api.Object_Locked exception.
482: -- 2) When attempting to the lock the parent which doesn't exist.
483: -- For the entity to be locked the parent must exist!
484: --
485: -- Developer Implementation Notes:

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

536: ,p_rec in out nocopy pay_rfm_shd.g_rec_type
537: ) is
538: --
539: l_proc varchar2(72) := g_package||'ins';
540: l_datetrack_mode varchar2(30) := hr_api.g_insert;
541: l_validation_start_date date;
542: l_validation_end_date date;
543: --
544: Begin