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.HR_DATA_PUMP dependencies on FND_MESSAGE

Line 355: fnd_message.set_name('PER','HR_DP_EXCEPTION');

351: if(p_arg08 is not null) then
352: g_fail_info.arg_values := g_fail_info.arg_values || ':' || p_arg08;
353: end if;
354:
355: fnd_message.set_name('PER','HR_DP_EXCEPTION');
356: fnd_message.set_token('ROUTINE',p_function_name);
357: fnd_message.set_token('SQL_ERROR',p_error_message);
358: fnd_message.set_token('PARAM',g_fail_info.arg_values);
359: fnd_message.raise_error;

Line 356: fnd_message.set_token('ROUTINE',p_function_name);

352: g_fail_info.arg_values := g_fail_info.arg_values || ':' || p_arg08;
353: end if;
354:
355: fnd_message.set_name('PER','HR_DP_EXCEPTION');
356: fnd_message.set_token('ROUTINE',p_function_name);
357: fnd_message.set_token('SQL_ERROR',p_error_message);
358: fnd_message.set_token('PARAM',g_fail_info.arg_values);
359: fnd_message.raise_error;
360:

Line 357: fnd_message.set_token('SQL_ERROR',p_error_message);

353: end if;
354:
355: fnd_message.set_name('PER','HR_DP_EXCEPTION');
356: fnd_message.set_token('ROUTINE',p_function_name);
357: fnd_message.set_token('SQL_ERROR',p_error_message);
358: fnd_message.set_token('PARAM',g_fail_info.arg_values);
359: fnd_message.raise_error;
360:
361: end fail;

Line 358: fnd_message.set_token('PARAM',g_fail_info.arg_values);

354:
355: fnd_message.set_name('PER','HR_DP_EXCEPTION');
356: fnd_message.set_token('ROUTINE',p_function_name);
357: fnd_message.set_token('SQL_ERROR',p_error_message);
358: fnd_message.set_token('PARAM',g_fail_info.arg_values);
359: fnd_message.raise_error;
360:
361: end fail;
362:

Line 359: fnd_message.raise_error;

355: fnd_message.set_name('PER','HR_DP_EXCEPTION');
356: fnd_message.set_token('ROUTINE',p_function_name);
357: fnd_message.set_token('SQL_ERROR',p_error_message);
358: fnd_message.set_token('PARAM',g_fail_info.arg_values);
359: fnd_message.raise_error;
360:
361: end fail;
362:
363: /* logs failure from get id functions */

Line 751: l_encoded := fnd_message.get_encoded;

747: -- Use the override message, if available.
748: l_exception_text := p_overmsg;
749: elsif (sqlcode = hr_utility.HR_ERROR_NUMBER) then
750: -- This is an application error.
751: l_encoded := fnd_message.get_encoded;
752: fnd_message.set_encoded(l_encoded);
753: l_exception_text := fnd_message.get;
754: if l_exception_text is null then
755: l_exception_text := sqlerrm;

Line 752: fnd_message.set_encoded(l_encoded);

748: l_exception_text := p_overmsg;
749: elsif (sqlcode = hr_utility.HR_ERROR_NUMBER) then
750: -- This is an application error.
751: l_encoded := fnd_message.get_encoded;
752: fnd_message.set_encoded(l_encoded);
753: l_exception_text := fnd_message.get;
754: if l_exception_text is null then
755: l_exception_text := sqlerrm;
756: end if;

Line 753: l_exception_text := fnd_message.get;

749: elsif (sqlcode = hr_utility.HR_ERROR_NUMBER) then
750: -- This is an application error.
751: l_encoded := fnd_message.get_encoded;
752: fnd_message.set_encoded(l_encoded);
753: l_exception_text := fnd_message.get;
754: if l_exception_text is null then
755: l_exception_text := sqlerrm;
756: end if;
757: else

Line 1452: -- FND_MESSAGE.RAISE_ERROR case.

1448: -- and non-apps messages cleanly.
1449: --
1450: -- Adding to the message list is appropriate as it preserves
1451: -- order and avoids problems with expanding message text for
1452: -- FND_MESSAGE.RAISE_ERROR case.
1453: --
1454: if not p_multi_msg_error then
1455: -- Use the API name as the error source.
1456: l_procedure := p_module_package || '.' || p_module_name;