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.PAY_PRT_INS dependencies on HR_API

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

119: --
120: -- If the datetrack_mode is not INSERT then we must populate the WHO
121: -- columns with the 'old' creation values and 'new' updated values.
122: --
123: If (p_datetrack_mode <> hr_api.g_insert) then
124: hr_utility.set_location(l_proc, 10);
125: --
126: -- Select the 'old' created values
127: --

Line 252: When hr_api.check_integrity_violated Then

248: --
249: hr_utility.set_location(' Leaving:'||l_proc, 15);
250: --
251: Exception
252: When hr_api.check_integrity_violated Then
253: -- A check constraint has been violated
254: --
255: pay_prt_shd.constraint_error
256: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

252: When hr_api.check_integrity_violated Then
253: -- A check constraint has been violated
254: --
255: pay_prt_shd.constraint_error
256: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
257: When hr_api.unique_integrity_violated Then
258: -- Unique integrity has been violated
259: --
260: pay_prt_shd.constraint_error

Line 257: When hr_api.unique_integrity_violated Then

253: -- A check constraint has been violated
254: --
255: pay_prt_shd.constraint_error
256: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
257: When hr_api.unique_integrity_violated Then
258: -- Unique integrity has been violated
259: --
260: pay_prt_shd.constraint_error
261: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

257: When hr_api.unique_integrity_violated Then
258: -- Unique integrity has been violated
259: --
260: pay_prt_shd.constraint_error
261: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
262: When Others Then
263: --
264: Raise;
265: End dt_insert_dml;

Line 589: when hr_api.cannot_find_prog_unit then

585: );
586: --
587: exception
588: --
589: when hr_api.cannot_find_prog_unit then
590: --
591: hr_api.cannot_find_prog_unit_error
592: (p_module_name => 'PAY_RUN_TYPES_F'
593: ,p_hook_type => 'AI');

Line 591: hr_api.cannot_find_prog_unit_error

587: exception
588: --
589: when hr_api.cannot_find_prog_unit then
590: --
591: hr_api.cannot_find_prog_unit_error
592: (p_module_name => 'PAY_RUN_TYPES_F'
593: ,p_hook_type => 'AI');
594: --
595: end;

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

620: --
621: -- Post Failure:
622: -- The Lck process can fail for:
623: -- 1) When attempting to lock the row the row could already be locked by
624: -- another user. This will raise the HR_Api.Object_Locked exception.
625: -- 2) When attempting to the lock the parent which doesn't exist.
626: -- For the entity to be locked the parent must exist!
627: --
628: -- Developer Implementation Notes:

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

679: ,p_rec in out nocopy pay_prt_shd.g_rec_type
680: ) is
681: --
682: l_proc varchar2(72) := g_package||'ins';
683: l_datetrack_mode varchar2(30) := hr_api.g_insert;
684: l_validation_start_date date;
685: l_validation_end_date date;
686: --
687: Begin