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

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

125: --
126: -- If the datetrack_mode is not INSERT then we must populate the WHO
127: -- columns with the 'old' creation values and 'new' updated values.
128: --
129: If (p_datetrack_mode <> hr_api.g_insert) then
130: hr_utility.set_location(l_proc, 10);
131: --
132: -- Get the object version number for the insert
133: --

Line 228: When hr_api.check_integrity_violated Then

224: --
225: hr_utility.set_location(' Leaving:'||l_proc, 15);
226: --
227: Exception
228: When hr_api.check_integrity_violated Then
229: -- A check constraint has been violated
230: --
231: ame_acf_shd.constraint_error
232: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

228: When hr_api.check_integrity_violated Then
229: -- A check constraint has been violated
230: --
231: ame_acf_shd.constraint_error
232: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
233: When hr_api.unique_integrity_violated Then
234: -- Unique integrity has been violated
235: --
236: ame_acf_shd.constraint_error

Line 233: When hr_api.unique_integrity_violated Then

229: -- A check constraint has been violated
230: --
231: ame_acf_shd.constraint_error
232: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
233: When hr_api.unique_integrity_violated Then
234: -- Unique integrity has been violated
235: --
236: ame_acf_shd.constraint_error
237: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

233: When hr_api.unique_integrity_violated Then
234: -- Unique integrity has been violated
235: --
236: ame_acf_shd.constraint_error
237: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
238: When Others Then
239: --
240: Raise;
241: End dt_insert_dml;

Line 345: hr_api.mandatory_arg_error

341: p_effective_date between ame_action_type_usages.start_date and
342: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, p_effective_date);
343: end if;
344: else
345: hr_api.mandatory_arg_error
346: (p_api_name => l_proc
347: ,p_argument => 'order_number'
348: ,p_argument_value => p_order_number
349: );

Line 557: when hr_api.cannot_find_prog_unit then

553: );
554: --
555: exception
556: --
557: when hr_api.cannot_find_prog_unit then
558: --
559: hr_api.cannot_find_prog_unit_error
560: (p_module_name => 'AME_ACTION_TYPE_CONFIG'
561: ,p_hook_type => 'AI');

Line 559: hr_api.cannot_find_prog_unit_error

555: exception
556: --
557: when hr_api.cannot_find_prog_unit then
558: --
559: hr_api.cannot_find_prog_unit_error
560: (p_module_name => 'AME_ACTION_TYPE_CONFIG'
561: ,p_hook_type => 'AI');
562: --
563: end;

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

588: --
589: -- Post Failure:
590: -- The Lck process can fail for:
591: -- 1) When attempting to lock the row the row could already be locked by
592: -- another user. This will raise the HR_Api.Object_Locked exception.
593: -- 2) When attempting to the lock the parent which doesn't exist.
594: -- For the entity to be locked the parent must exist!
595: --
596: -- Developer Implementation Notes:

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

640: ,p_rec in out nocopy ame_acf_shd.g_rec_type
641: ) is
642: --
643: l_proc varchar2(72) := g_package||'ins';
644: l_datetrack_mode varchar2(30) := hr_api.g_insert;
645: l_validation_start_date date;
646: l_validation_end_date date;
647: --
648: Begin