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.PQH_ASA_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 335: When hr_api.check_integrity_violated Then

331: --
332: hr_utility.set_location(' Leaving:'||l_proc, 15);
333: --
334: Exception
335: When hr_api.check_integrity_violated Then
336: -- A check constraint has been violated
337: --
338: pqh_asa_shd.constraint_error
339: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

335: When hr_api.check_integrity_violated Then
336: -- A check constraint has been violated
337: --
338: pqh_asa_shd.constraint_error
339: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
340: When hr_api.unique_integrity_violated Then
341: -- Unique integrity has been violated
342: --
343: pqh_asa_shd.constraint_error

Line 340: When hr_api.unique_integrity_violated Then

336: -- A check constraint has been violated
337: --
338: pqh_asa_shd.constraint_error
339: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
340: When hr_api.unique_integrity_violated Then
341: -- Unique integrity has been violated
342: --
343: pqh_asa_shd.constraint_error
344: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

340: When hr_api.unique_integrity_violated Then
341: -- Unique integrity has been violated
342: --
343: pqh_asa_shd.constraint_error
344: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
345: When Others Then
346: --
347: Raise;
348: End dt_insert_dml;

Line 693: when hr_api.cannot_find_prog_unit then

689: );
690: --
691: exception
692: --
693: when hr_api.cannot_find_prog_unit then
694: --
695: hr_api.cannot_find_prog_unit_error
696: (p_module_name => 'PQH_ASSIGN_ACCOMMODATIONS_F'
697: ,p_hook_type => 'AI');

Line 695: hr_api.cannot_find_prog_unit_error

691: exception
692: --
693: when hr_api.cannot_find_prog_unit then
694: --
695: hr_api.cannot_find_prog_unit_error
696: (p_module_name => 'PQH_ASSIGN_ACCOMMODATIONS_F'
697: ,p_hook_type => 'AI');
698: --
699: end;

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

724: --
725: -- Post Failure:
726: -- The Lck process can fail for:
727: -- 1) When attempting to lock the row the row could already be locked by
728: -- another user. This will raise the HR_Api.Object_Locked exception.
729: -- 2) When attempting to the lock the parent which doesn't exist.
730: -- For the entity to be locked the parent must exist!
731: --
732: -- Developer Implementation Notes:

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

786: ,p_rec in out nocopy pqh_asa_shd.g_rec_type
787: ) is
788: --
789: l_proc varchar2(72) := g_package||'ins';
790: l_datetrack_mode varchar2(30) := hr_api.g_insert;
791: l_validation_start_date date;
792: l_validation_end_date date;
793: --
794: Begin