APPS.PQH_DOC_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 203: When hr_api.check_integrity_violated Then

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

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

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

Line 208: When hr_api.unique_integrity_violated Then

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

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

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

Line 430: when hr_api.cannot_find_prog_unit then

426: );
427: --
428: exception
429: --
430: when hr_api.cannot_find_prog_unit then
431: --
432: hr_api.cannot_find_prog_unit_error
433: (p_module_name => 'PQH_DOCUMENTS_F'
434: ,p_hook_type => 'AI');

Line 432: hr_api.cannot_find_prog_unit_error

428: exception
429: --
430: when hr_api.cannot_find_prog_unit then
431: --
432: hr_api.cannot_find_prog_unit_error
433: (p_module_name => 'PQH_DOCUMENTS_F'
434: ,p_hook_type => 'AI');
435: --
436: end;

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

461: --
462: -- Post Failure:
463: -- The Lck process can fail for:
464: -- 1) When attempting to lock the row the row could already be locked by
465: -- another user. This will raise the HR_Api.Object_Locked exception.
466: -- 2) When attempting to the lock the parent which doesn't exist.
467: -- For the entity to be locked the parent must exist!
468: --
469: -- Developer Implementation Notes:

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

520: ,p_rec in out NOCOPY pqh_doc_shd.g_rec_type
521: ) is
522: --
523: l_proc varchar2(72) := g_package||'ins';
524: l_datetrack_mode varchar2(30) := hr_api.g_insert;
525: l_validation_start_date date;
526: l_validation_end_date date;
527: --
528: Begin