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.WIP_BOMROUTING_PVT dependencies on FND_MSG_PUB

Line 221: -- Don't need to add the x_errormsg again to stack by calling fnd_msg_pub.add_exc_msg

217: exception
218: when others then
219: x_returnStatus := fnd_api.g_ret_sts_unexp_error;
220: -- Fixed for bug 5255226
221: -- Don't need to add the x_errormsg again to stack by calling fnd_msg_pub.add_exc_msg
222: -- Removed this API call. Instead adding this error message to debug log using
223: if (l_logLevel <= wip_constants.trace_logging) then
224: wip_logger.log(x_errorMsg,l_retstatus);
225: End if;

Line 705: fnd_msg_pub.add_exc_msg(p_pkg_name => g_pkgName,

701: end if;
702: exception
703: when others then
704: x_returnStatus := fnd_api.g_ret_sts_unexp_error;
705: fnd_msg_pub.add_exc_msg(p_pkg_name => g_pkgName,
706: p_procedure_name => l_procName,
707: p_error_text => SUBSTRB(x_errorMsg, 1,240));--bug 13608871
708: if(l_logLevel <= wip_constants.trace_logging) then
709: wip_logger.exitPoint(p_procName => g_pkgName || '.' || l_procName,