eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PQP_VAL_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 303: When hr_api.check_integrity_violated Then

299: --
300: hr_utility.set_location(' Leaving:'||l_proc, 15);
301: --
302: Exception
303: When hr_api.check_integrity_violated Then
304: -- A check constraint has been violated
305: --
306: pqp_val_shd.constraint_error
307: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

303: When hr_api.check_integrity_violated Then
304: -- A check constraint has been violated
305: --
306: pqp_val_shd.constraint_error
307: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
308: When hr_api.unique_integrity_violated Then
309: -- Unique integrity has been violated
310: --
311: pqp_val_shd.constraint_error

Line 308: When hr_api.unique_integrity_violated Then

304: -- A check constraint has been violated
305: --
306: pqp_val_shd.constraint_error
307: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
308: When hr_api.unique_integrity_violated Then
309: -- Unique integrity has been violated
310: --
311: pqp_val_shd.constraint_error
312: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

308: When hr_api.unique_integrity_violated Then
309: -- Unique integrity has been violated
310: --
311: pqp_val_shd.constraint_error
312: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
313: When Others Then
314: --
315: Raise;
316: End dt_insert_dml;

Line 629: when hr_api.cannot_find_prog_unit then

625: );
626: --
627: exception
628: --
629: when hr_api.cannot_find_prog_unit then
630: --
631: hr_api.cannot_find_prog_unit_error
632: (p_module_name => 'PQP_VEHICLE_ALLOCATIONS_F'
633: ,p_hook_type => 'AI');

Line 631: hr_api.cannot_find_prog_unit_error

627: exception
628: --
629: when hr_api.cannot_find_prog_unit then
630: --
631: hr_api.cannot_find_prog_unit_error
632: (p_module_name => 'PQP_VEHICLE_ALLOCATIONS_F'
633: ,p_hook_type => 'AI');
634: --
635: end;

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

660: --
661: -- Post Failure:
662: -- The Lck process can fail for:
663: -- 1) When attempting to lock the row the row could already be locked by
664: -- another user. This will raise the HR_Api.Object_Locked exception.
665: -- 2) When attempting to the lock the parent which doesn't exist.
666: -- For the entity to be locked the parent must exist!
667: --
668: -- Developer Implementation Notes:

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

725: ,p_rec in out nocopy pqp_val_shd.g_rec_type
726: ) is
727: --
728: l_proc varchar2(72) := g_package||'ins';
729: l_datetrack_mode varchar2(30) := hr_api.g_insert;
730: l_validation_start_date date;
731: l_validation_end_date date;
732: --
733: Begin