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_VRE_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 339: WHEN hr_api.check_integrity_violated THEN

335: --
336: hr_utility.set_location(' Leaving:'||l_proc, 15);
337: --
338: EXCEPTION
339: WHEN hr_api.check_integrity_violated THEN
340: -- A check constraint has been violated
341: --
342: pqp_vre_shd.constraint_error
343: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

339: WHEN hr_api.check_integrity_violated THEN
340: -- A check constraint has been violated
341: --
342: pqp_vre_shd.constraint_error
343: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
344: WHEN hr_api.unique_integrity_violated THEN
345: -- Unique integrity has been violated
346: --
347: pqp_vre_shd.constraint_error

Line 344: WHEN hr_api.unique_integrity_violated THEN

340: -- A check constraint has been violated
341: --
342: pqp_vre_shd.constraint_error
343: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
344: WHEN hr_api.unique_integrity_violated THEN
345: -- Unique integrity has been violated
346: --
347: pqp_vre_shd.constraint_error
348: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

344: WHEN hr_api.unique_integrity_violated THEN
345: -- Unique integrity has been violated
346: --
347: pqp_vre_shd.constraint_error
348: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
349: WHEN OTHERS THEN
350: --
351: RAISE;
352: END dt_insert_dml;

Line 616: WHEN hr_api.cannot_find_prog_unit THEN

612: );
613: --
614: EXCEPTION
615: --
616: WHEN hr_api.cannot_find_prog_unit THEN
617: --
618: hr_api.cannot_find_prog_unit_error
619: (p_module_name => 'PQP_VEHICLE_REPOSITORY_F'
620: ,p_hook_type => 'AI');

Line 618: hr_api.cannot_find_prog_unit_error

614: EXCEPTION
615: --
616: WHEN hr_api.cannot_find_prog_unit THEN
617: --
618: hr_api.cannot_find_prog_unit_error
619: (p_module_name => 'PQP_VEHICLE_REPOSITORY_F'
620: ,p_hook_type => 'AI');
621: --
622: END;

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

647: --
648: -- Post Failure:
649: -- The Lck process can fail for:
650: -- 1) When attempting to lock the row the row could already be locked by
651: -- another user. This will raise the HR_Api.Object_Locked exception.
652: -- 2) When attempting to the lock the parent which doesn't exist.
653: -- For the entity to be locked the parent must exist!
654: --
655: -- Developer Implementation Notes:

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

706: ,p_rec IN OUT NOCOPY pqp_vre_shd.g_rec_type
707: ) IS
708: --
709: l_proc varchar2(72) := g_package||'ins';
710: l_datetrack_mode varchar2(30) := hr_api.g_insert;
711: l_validation_start_date date;
712: l_validation_end_date date;
713: --
714: BEGIN