APPS.PAY_IVL_INS dependencies on HR_API

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

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

Line 217: When hr_api.check_integrity_violated Then

213: pay_ivl_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_ivl_shd.g_api_dml := false; -- Unset the api dml status
220: pay_ivl_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_ivl_shd.g_api_dml := false; -- Unset the api dml status
220: pay_ivl_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_ivl_shd.g_api_dml := false; -- Unset the api dml status
225: pay_ivl_shd.constraint_error

Line 222: When hr_api.unique_integrity_violated Then

218: -- A check constraint has been violated
219: pay_ivl_shd.g_api_dml := false; -- Unset the api dml status
220: pay_ivl_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_ivl_shd.g_api_dml := false; -- Unset the api dml status
225: pay_ivl_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_ivl_shd.g_api_dml := false; -- Unset the api dml status
225: pay_ivl_shd.constraint_error
226: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
227: When Others Then
228: pay_ivl_shd.g_api_dml := false; -- Unset the api dml status
229: Raise;
230: End dt_insert_dml;

Line 511: when hr_api.cannot_find_prog_unit then

507: );
508: --
509: exception
510: --
511: when hr_api.cannot_find_prog_unit then
512: --
513: hr_api.cannot_find_prog_unit_error
514: (p_module_name => 'PAY_INPUT_VALUES_F'
515: ,p_hook_type => 'AI');

Line 513: hr_api.cannot_find_prog_unit_error

509: exception
510: --
511: when hr_api.cannot_find_prog_unit then
512: --
513: hr_api.cannot_find_prog_unit_error
514: (p_module_name => 'PAY_INPUT_VALUES_F'
515: ,p_hook_type => 'AI');
516: --
517: end;

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

542: --
543: -- Post Failure:
544: -- The Lck process can fail for:
545: -- 1) When attempting to lock the row the row could already be locked by
546: -- another user. This will raise the HR_Api.Object_Locked exception.
547: -- 2) When attempting to the lock the parent which doesn't exist.
548: -- For the entity to be locked the parent must exist!
549: --
550: -- Developer Implementation Notes:

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

610: ,p_formula_message out nocopy varchar2
611: ) is
612: --
613: l_proc varchar2(72) := g_package||'ins';
614: l_datetrack_mode varchar2(30) := hr_api.g_insert;
615: l_validation_start_date date;
616: l_validation_end_date date;
617:
618: cursor csr_display_sequence is