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_PBC_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 255: When hr_api.check_integrity_violated Then

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

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

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

Line 260: When hr_api.unique_integrity_violated Then

256: -- A check constraint has been violated
257: --
258: pay_pbc_shd.constraint_error
259: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
260: When hr_api.unique_integrity_violated Then
261: -- Unique integrity has been violated
262: --
263: pay_pbc_shd.constraint_error
264: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

260: When hr_api.unique_integrity_violated Then
261: -- Unique integrity has been violated
262: --
263: pay_pbc_shd.constraint_error
264: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
265: When Others Then
266: --
267: Raise;
268: End dt_insert_dml;

Line 587: when hr_api.cannot_find_prog_unit then

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

Line 589: hr_api.cannot_find_prog_unit_error

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

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

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

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

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