APPS.PAY_PPR_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 201: When hr_api.check_integrity_violated Then

197: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
198: hr_utility.set_location(' Leaving:'||l_proc, 15);
199: --
200: Exception
201: When hr_api.check_integrity_violated Then
202: -- A check constraint has been violated
203: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
204: pay_ppr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

201: When hr_api.check_integrity_violated Then
202: -- A check constraint has been violated
203: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
204: pay_ppr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
209: pay_ppr_shd.constraint_error

Line 206: When hr_api.unique_integrity_violated Then

202: -- A check constraint has been violated
203: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
204: pay_ppr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
209: pay_ppr_shd.constraint_error
210: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
209: pay_ppr_shd.constraint_error
210: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
211: When Others Then
212: pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
213: Raise;
214: End dt_insert_dml;

Line 476: when hr_api.cannot_find_prog_unit then

472: );
473: --
474: exception
475: --
476: when hr_api.cannot_find_prog_unit then
477: --
478: hr_api.cannot_find_prog_unit_error
479: (p_module_name => 'PAY_STATUS_PROCESSING_RULES_F'
480: ,p_hook_type => 'AI');

Line 478: hr_api.cannot_find_prog_unit_error

474: exception
475: --
476: when hr_api.cannot_find_prog_unit then
477: --
478: hr_api.cannot_find_prog_unit_error
479: (p_module_name => 'PAY_STATUS_PROCESSING_RULES_F'
480: ,p_hook_type => 'AI');
481: --
482: end;

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

507: --
508: -- Post Failure:
509: -- The Lck process can fail for:
510: -- 1) When attempting to lock the row the row could already be locked by
511: -- another user. This will raise the HR_Api.Object_Locked exception.
512: -- 2) When attempting to the lock the parent which doesn't exist.
513: -- For the entity to be locked the parent must exist!
514: --
515: -- Developer Implementation Notes:

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

567: ,p_formula_mismatch_warning out nocopy boolean
568: ) is
569: --
570: l_proc varchar2(72) := g_package||'ins';
571: l_datetrack_mode varchar2(30) := hr_api.g_insert;
572: l_validation_start_date date;
573: l_validation_end_date date;
574: l_processing_rule varchar2(1);
575: l_formula_mismatch_warning boolean;