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_PTY_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 363: When hr_api.check_integrity_violated Then

359: --
360: hr_utility.set_location(' Leaving:'||l_proc, 15);
361: --
362: Exception
363: When hr_api.check_integrity_violated Then
364: -- A check constraint has been violated
365: --
366: pqp_pty_shd.constraint_error
367: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

363: When hr_api.check_integrity_violated Then
364: -- A check constraint has been violated
365: --
366: pqp_pty_shd.constraint_error
367: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
368: When hr_api.unique_integrity_violated Then
369: -- Unique integrity has been violated
370: --
371: pqp_pty_shd.constraint_error

Line 368: When hr_api.unique_integrity_violated Then

364: -- A check constraint has been violated
365: --
366: pqp_pty_shd.constraint_error
367: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
368: When hr_api.unique_integrity_violated Then
369: -- Unique integrity has been violated
370: --
371: pqp_pty_shd.constraint_error
372: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

368: When hr_api.unique_integrity_violated Then
369: -- Unique integrity has been violated
370: --
371: pqp_pty_shd.constraint_error
372: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
373: When Others Then
374: --
375: Raise;
376: End dt_insert_dml;

Line 803: when hr_api.cannot_find_prog_unit then

799: );
800: --
801: exception
802: --
803: when hr_api.cannot_find_prog_unit then
804: --
805: hr_api.cannot_find_prog_unit_error
806: (p_module_name => 'PQP_PENSION_TYPES_F'
807: ,p_hook_type => 'AI');

Line 805: hr_api.cannot_find_prog_unit_error

801: exception
802: --
803: when hr_api.cannot_find_prog_unit then
804: --
805: hr_api.cannot_find_prog_unit_error
806: (p_module_name => 'PQP_PENSION_TYPES_F'
807: ,p_hook_type => 'AI');
808: --
809: end;

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

834: --
835: -- Post Failure:
836: -- The Lck process can fail for:
837: -- 1) When attempting to lock the row the row could already be locked by
838: -- another user. This will raise the HR_Api.Object_Locked exception.
839: -- 2) When attempting to the lock the parent which doesn't exist.
840: -- For the entity to be locked the parent must exist!
841: --
842: -- Developer Implementation Notes:

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

893: ,p_rec in out nocopy pqp_pty_shd.g_rec_type
894: ) is
895: --
896: l_proc varchar2(72) := g_package||'ins';
897: l_datetrack_mode varchar2(30) := hr_api.g_insert;
898: l_validation_start_date date;
899: l_validation_end_date date;
900: --
901: Begin