APPS.PAY_PGR_INS dependencies on HR_API

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

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

Line 216: When hr_api.check_integrity_violated Then

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

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

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

Line 221: When hr_api.unique_integrity_violated Then

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

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

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

Line 483: when hr_api.cannot_find_prog_unit then

479: );
480: --
481: exception
482: --
483: when hr_api.cannot_find_prog_unit then
484: --
485: hr_api.cannot_find_prog_unit_error
486: (p_module_name => 'PAY_GRADE_RULES_F'
487: ,p_hook_type => 'AI');

Line 485: hr_api.cannot_find_prog_unit_error

481: exception
482: --
483: when hr_api.cannot_find_prog_unit then
484: --
485: hr_api.cannot_find_prog_unit_error
486: (p_module_name => 'PAY_GRADE_RULES_F'
487: ,p_hook_type => 'AI');
488: --
489: end;

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

514: --
515: -- Post Failure:
516: -- The Lck process can fail for:
517: -- 1) When attempting to lock the row the row could already be locked by
518: -- another user. This will raise the HR_Api.Object_Locked exception.
519: -- 2) When attempting to the lock the parent which doesn't exist.
520: -- For the entity to be locked the parent must exist!
521: --
522: -- Developer Implementation Notes:

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

573: ,p_rec in out nocopy pay_pgr_shd.g_rec_type
574: ) is
575: --
576: l_proc varchar2(72) := g_package||'ins';
577: l_datetrack_mode varchar2(30) := hr_api.g_insert;
578: l_validation_start_date date;
579: l_validation_end_date date;
580: --
581: Begin