DBA Data[Home] [Help]

APPS.PAY_PGA_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 199: When hr_api.check_integrity_violated Then

195: --
196: hr_utility.set_location(' Leaving:'||l_proc, 15);
197: --
198: Exception
199: When hr_api.check_integrity_violated Then
200: -- A check constraint has been violated
201: --
202: pay_pga_shd.constraint_error
203: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

199: When hr_api.check_integrity_violated Then
200: -- A check constraint has been violated
201: --
202: pay_pga_shd.constraint_error
203: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
204: When hr_api.unique_integrity_violated Then
205: -- Unique integrity has been violated
206: --
207: pay_pga_shd.constraint_error

Line 204: When hr_api.unique_integrity_violated Then

200: -- A check constraint has been violated
201: --
202: pay_pga_shd.constraint_error
203: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
204: When hr_api.unique_integrity_violated Then
205: -- Unique integrity has been violated
206: --
207: pay_pga_shd.constraint_error
208: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

204: When hr_api.unique_integrity_violated Then
205: -- Unique integrity has been violated
206: --
207: pay_pga_shd.constraint_error
208: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
209: When Others Then
210: --
211: Raise;
212: End dt_insert_dml;

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

413: --
414: -- Post Failure:
415: -- The Lck process can fail for:
416: -- 1) When attempting to lock the row the row could already be locked by
417: -- another user. This will raise the HR_Api.Object_Locked exception.
418: -- 2) When attempting to the lock the parent which doesn't exist.
419: -- For the entity to be locked the parent must exist!
420: --
421: -- Developer Implementation Notes:

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

492: ,p_rec in out nocopy pay_pga_shd.g_rec_type
493: ) is
494: --
495: l_proc varchar2(72) := g_package||'ins';
496: l_datetrack_mode varchar2(30) := hr_api.g_insert;
497: l_validation_start_date date;
498: l_validation_end_date date;
499: --
500: Begin