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_ACT_BUS dependencies on HR_API

Line 97: hr_api.g_number) <>

93: IF(approvalGroup) THEN
94: /* Action is based on an approval group so it's not updateable. */
95: IF
96: nvl(p_rec.parameter,
97: hr_api.g_number) <>
98: nvl(ame_act_shd.g_old_rec.parameter,
99: hr_api.g_number) THEN
100: l_argument := 'parameter';
101: RAISE l_error;

Line 99: hr_api.g_number) THEN

95: IF
96: nvl(p_rec.parameter,
97: hr_api.g_number) <>
98: nvl(ame_act_shd.g_old_rec.parameter,
99: hr_api.g_number) THEN
100: l_argument := 'parameter';
101: RAISE l_error;
102: END IF;
103: /* Descriptions for seeded actions cannot be updated. */

Line 108: hr_api.g_number) <>

104: ELSIF(createdBy = ame_util.seededDataCreatedById
105: and ame_utility_pkg.check_seeddb = 'N') THEN
106: IF
107: nvl(p_rec.description,
108: hr_api.g_number) <>
109: nvl(ame_act_shd.g_old_rec.description,
110: hr_api.g_number) then
111: l_argument := 'description';
112: RAISE l_error;

Line 110: hr_api.g_number) then

106: IF
107: nvl(p_rec.description,
108: hr_api.g_number) <>
109: nvl(ame_act_shd.g_old_rec.description,
110: hr_api.g_number) then
111: l_argument := 'description';
112: RAISE l_error;
113: end if;
114: IF nvl(p_rec.parameter,hr_api.g_number) <> nvl(ame_act_shd.g_old_rec.parameter,hr_api.g_number) THEN

Line 114: IF nvl(p_rec.parameter,hr_api.g_number) <> nvl(ame_act_shd.g_old_rec.parameter,hr_api.g_number) THEN

110: hr_api.g_number) then
111: l_argument := 'description';
112: RAISE l_error;
113: end if;
114: IF nvl(p_rec.parameter,hr_api.g_number) <> nvl(ame_act_shd.g_old_rec.parameter,hr_api.g_number) THEN
115: l_argument := 'parameter';
116: RAISE l_error;
117: END IF;
118:

Line 123: hr_api.argument_changed_error

119: END IF;
120: --
121: EXCEPTION
122: WHEN l_error THEN
123: hr_api.argument_changed_error
124: (p_api_name => l_proc
125: ,p_argument => l_argument);
126: WHEN OTHERS THEN
127: RAISE;

Line 273: hr_api.mandatory_arg_error

269: l_action_type_name ame_action_types.name%TYPE;
270: l_temp number;
271: begin
272: --The following call is a fix for bug 4380512
273: hr_api.mandatory_arg_error
274: (p_api_name => l_proc
275: ,p_argument => 'parameter'
276: ,p_argument_value => p_parameter
277: );

Line 564: (p_action_type_id in number default hr_api.g_number

560: --
561: -- {End Of Comments}
562: -- ----------------------------------------------------------------------------
563: Procedure dt_update_validate
564: (p_action_type_id in number default hr_api.g_number
565: ,p_datetrack_mode in varchar2
566: ,p_validation_start_date in date
567: ,p_validation_end_date in date
568: ) Is

Line 576: hr_api.mandatory_arg_error

572: Begin
573: --
574: -- Ensure that the p_datetrack_mode argument is not null
575: --
576: hr_api.mandatory_arg_error
577: (p_api_name => l_proc
578: ,p_argument => 'datetrack_mode'
579: ,p_argument_value => p_datetrack_mode
580: );

Line 586: hr_api.mandatory_arg_error

582: -- Mode will be valid, as this is checked at the start of the upd.
583: --
584: -- Ensure the arguments are not null
585: --
586: hr_api.mandatory_arg_error
587: (p_api_name => l_proc
588: ,p_argument => 'validation_start_date'
589: ,p_argument_value => p_validation_start_date
590: );

Line 592: /*hr_api.mandatory_arg_error

588: ,p_argument => 'validation_start_date'
589: ,p_argument_value => p_validation_start_date
590: );
591: --
592: /*hr_api.mandatory_arg_error
593: (p_api_name => l_proc
594: ,p_argument => 'validation_end_date'
595: ,p_argument_value => p_validation_end_date
596: );*/

Line 659: hr_api.mandatory_arg_error

655: Begin
656: --
657: -- Ensure that the p_datetrack_mode argument is not null
658: --
659: hr_api.mandatory_arg_error
660: (p_api_name => l_proc
661: ,p_argument => 'datetrack_mode'
662: ,p_argument_value => p_datetrack_mode
663: );

Line 668: If (p_datetrack_mode = hr_api.g_delete or

664: --
665: -- Only perform the validation if the datetrack mode is either
666: -- DELETE or ZAP
667: --
668: If (p_datetrack_mode = hr_api.g_delete or
669: p_datetrack_mode = hr_api.g_zap) then
670: --
671: --
672: -- Ensure the arguments are not null

Line 669: p_datetrack_mode = hr_api.g_zap) then

665: -- Only perform the validation if the datetrack mode is either
666: -- DELETE or ZAP
667: --
668: If (p_datetrack_mode = hr_api.g_delete or
669: p_datetrack_mode = hr_api.g_zap) then
670: --
671: --
672: -- Ensure the arguments are not null
673: --

Line 674: hr_api.mandatory_arg_error

670: --
671: --
672: -- Ensure the arguments are not null
673: --
674: hr_api.mandatory_arg_error
675: (p_api_name => l_proc
676: ,p_argument => 'validation_start_date'
677: ,p_argument_value => p_validation_start_date
678: );

Line 680: /*hr_api.mandatory_arg_error

676: ,p_argument => 'validation_start_date'
677: ,p_argument_value => p_validation_start_date
678: );
679: --
680: /*hr_api.mandatory_arg_error
681: (p_api_name => l_proc
682: ,p_argument => 'validation_end_date'
683: ,p_argument_value => p_validation_end_date
684: );*/

Line 686: hr_api.mandatory_arg_error

682: ,p_argument => 'validation_end_date'
683: ,p_argument_value => p_validation_end_date
684: );*/
685: --
686: hr_api.mandatory_arg_error
687: (p_api_name => l_proc
688: ,p_argument => 'action_id'
689: ,p_argument_value => p_action_id
690: );