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_ECU_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 200: When hr_api.check_integrity_violated Then

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

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

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

Line 205: When hr_api.unique_integrity_violated Then

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

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

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

Line 468: when hr_api.cannot_find_prog_unit then

464: );
465: --
466: exception
467: --
468: when hr_api.cannot_find_prog_unit then
469: --
470: hr_api.cannot_find_prog_unit_error
471: (p_module_name => 'PAY_ELEMENT_CLASS_USAGES_F'
472: ,p_hook_type => 'AI');

Line 470: hr_api.cannot_find_prog_unit_error

466: exception
467: --
468: when hr_api.cannot_find_prog_unit then
469: --
470: hr_api.cannot_find_prog_unit_error
471: (p_module_name => 'PAY_ELEMENT_CLASS_USAGES_F'
472: ,p_hook_type => 'AI');
473: --
474: end;

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

499: --
500: -- Post Failure:
501: -- The Lck process can fail for:
502: -- 1) When attempting to lock the row the row could already be locked by
503: -- another user. This will raise the HR_Api.Object_Locked exception.
504: -- 2) When attempting to the lock the parent which doesn't exist.
505: -- For the entity to be locked the parent must exist!
506: --
507: -- Developer Implementation Notes:

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

558: ,p_rec in out nocopy pay_ecu_shd.g_rec_type
559: ) is
560: --
561: l_proc varchar2(72) := g_package||'ins';
562: l_datetrack_mode varchar2(30) := hr_api.g_insert;
563: l_validation_start_date date;
564: l_validation_end_date date;
565: --
566: Begin