APPS.PAY_PUR_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 195: When hr_api.check_integrity_violated Then

191: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
192: hr_utility.set_location(' Leaving:'||l_proc, 15);
193: --
194: Exception
195: When hr_api.check_integrity_violated Then
196: -- A check constraint has been violated
197: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
198: pay_pur_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

195: When hr_api.check_integrity_violated Then
196: -- A check constraint has been violated
197: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
198: pay_pur_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
203: pay_pur_shd.constraint_error

Line 200: When hr_api.unique_integrity_violated Then

196: -- A check constraint has been violated
197: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
198: pay_pur_shd.constraint_error
199: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
203: pay_pur_shd.constraint_error
204: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

200: When hr_api.unique_integrity_violated Then
201: -- Unique integrity has been violated
202: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
203: pay_pur_shd.constraint_error
204: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
205: When Others Then
206: pay_pur_shd.g_api_dml := false; -- Unset the api dml status
207: Raise;
208: End dt_insert_dml;

Line 473: when hr_api.cannot_find_prog_unit then

469: );
470: --
471: exception
472: --
473: when hr_api.cannot_find_prog_unit then
474: --
475: hr_api.cannot_find_prog_unit_error
476: (p_module_name => 'PAY_USER_ROWS_F'
477: ,p_hook_type => 'AI');

Line 475: hr_api.cannot_find_prog_unit_error

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

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

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

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

565: ,p_disable_range_overlap_check in boolean default false
566: ) is
567: --
568: l_proc varchar2(72) := g_package||'ins';
569: l_datetrack_mode varchar2(30) := hr_api.g_insert;
570: l_validation_start_date date;
571: l_validation_end_date date;
572: --
573: Begin