APPS.PAY_OPM_INS dependencies on HR_API

Line 124: If (p_datetrack_mode <> hr_api.g_insert) then

120: --
121: -- If the datetrack_mode is not INSERT then we must populate the WHO
122: -- columns with the 'old' creation values and 'new' updated values.
123: --
124: If (p_datetrack_mode <> hr_api.g_insert) then
125: hr_utility.set_location(l_proc, 10);
126: --
127: -- Select the 'old' created values
128: --

Line 290: When hr_api.check_integrity_violated Then

286: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
287: hr_utility.set_location(' Leaving:'||l_proc, 15);
288: --
289: Exception
290: When hr_api.check_integrity_violated Then
291: -- A check constraint has been violated
292: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
293: pay_opm_shd.constraint_error
294: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

290: When hr_api.check_integrity_violated Then
291: -- A check constraint has been violated
292: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
293: pay_opm_shd.constraint_error
294: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
295: When hr_api.unique_integrity_violated Then
296: -- Unique integrity has been violated
297: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
298: pay_opm_shd.constraint_error

Line 295: When hr_api.unique_integrity_violated Then

291: -- A check constraint has been violated
292: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
293: pay_opm_shd.constraint_error
294: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
295: When hr_api.unique_integrity_violated Then
296: -- Unique integrity has been violated
297: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
298: pay_opm_shd.constraint_error
299: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

295: When hr_api.unique_integrity_violated Then
296: -- Unique integrity has been violated
297: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
298: pay_opm_shd.constraint_error
299: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
300: When Others Then
301: pay_opm_shd.g_api_dml := false; -- Unset the api dml status
302: Raise;
303: End dt_insert_dml;

Line 614: when hr_api.cannot_find_prog_unit then

610: );
611: --
612: exception
613: --
614: when hr_api.cannot_find_prog_unit then
615: --
616: hr_api.cannot_find_prog_unit_error
617: (p_module_name => 'PAY_ORG_PAYMENT_METHODS_F'
618: ,p_hook_type => 'AI');

Line 616: hr_api.cannot_find_prog_unit_error

612: exception
613: --
614: when hr_api.cannot_find_prog_unit then
615: --
616: hr_api.cannot_find_prog_unit_error
617: (p_module_name => 'PAY_ORG_PAYMENT_METHODS_F'
618: ,p_hook_type => 'AI');
619: --
620: end;

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

645: --
646: -- Post Failure:
647: -- The Lck process can fail for:
648: -- 1) When attempting to lock the row the row could already be locked by
649: -- another user. This will raise the HR_Api.Object_Locked exception.
650: -- 2) When attempting to the lock the parent which doesn't exist.
651: -- For the entity to be locked the parent must exist!
652: --
653: -- Developer Implementation Notes:

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

704: ,p_rec in out nocopy pay_opm_shd.g_rec_type
705: ) is
706: --
707: l_proc varchar2(72) := g_package||'ins';
708: l_datetrack_mode varchar2(30) := hr_api.g_insert;
709: l_validation_start_date date;
710: l_validation_end_date date;
711: --
712: Begin