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_RMR_INS dependencies on HR_API

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

112: --
113: -- If the datetrack_mode is not INSERT then we must populate the WHO
114: -- columns with the 'old' creation values and 'new' updated values.
115: --
116: If (p_datetrack_mode <> hr_api.g_insert) then
117: hr_utility.set_location(l_proc, 10);
118: --
119: -- Get the object version number for the insert
120: --

Line 201: When hr_api.check_integrity_violated Then

197: --
198: hr_utility.set_location(' Leaving:'||l_proc, 15);
199: --
200: Exception
201: When hr_api.check_integrity_violated Then
202: -- A check constraint has been violated
203: --
204: pqh_rmr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

201: When hr_api.check_integrity_violated Then
202: -- A check constraint has been violated
203: --
204: pqh_rmr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: --
209: pqh_rmr_shd.constraint_error

Line 206: When hr_api.unique_integrity_violated Then

202: -- A check constraint has been violated
203: --
204: pqh_rmr_shd.constraint_error
205: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: --
209: pqh_rmr_shd.constraint_error
210: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

206: When hr_api.unique_integrity_violated Then
207: -- Unique integrity has been violated
208: --
209: pqh_rmr_shd.constraint_error
210: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
211: When Others Then
212: --
213: Raise;
214: End dt_insert_dml;

Line 477: when hr_api.cannot_find_prog_unit then

473: );
474: --
475: exception
476: --
477: when hr_api.cannot_find_prog_unit then
478: --
479: hr_api.cannot_find_prog_unit_error
480: (p_module_name => 'PQH_RATE_MATRIX_RATES_F'
481: ,p_hook_type => 'AI');

Line 479: hr_api.cannot_find_prog_unit_error

475: exception
476: --
477: when hr_api.cannot_find_prog_unit then
478: --
479: hr_api.cannot_find_prog_unit_error
480: (p_module_name => 'PQH_RATE_MATRIX_RATES_F'
481: ,p_hook_type => 'AI');
482: --
483: end;

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

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

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

567: ,p_rec in out nocopy pqh_rmr_shd.g_rec_type
568: ) is
569: --
570: l_proc varchar2(72) := g_package||'ins';
571: l_datetrack_mode varchar2(30) := hr_api.g_insert;
572: l_validation_start_date date;
573: l_validation_end_date date;
574: --
575: Begin