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 194: -- Don't need to add the x_errormsg again to stack by calling fnd_msg_pub.add_exc_msg

190: exception
191: when others then
192: x_returnStatus := fnd_api.g_ret_sts_unexp_error;
193: -- Fixed for bug 5255226
194: -- Don't need to add the x_errormsg again to stack by calling fnd_msg_pub.add_exc_msg
195: -- Removed this API call. Instead adding this error message to debug log using
196: if (l_logLevel <= wip_constants.trace_logging) then
197: wip_logger.log(x_errorMsg,l_retstatus);
198: End if;

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

573: end if;
574: exception
575: when others then
576: x_returnStatus := fnd_api.g_ret_sts_unexp_error;
577: fnd_msg_pub.add_exc_msg(p_pkg_name => g_pkgName,
578: p_procedure_name => l_procName,
579: p_error_text => x_errorMsg);
580: if(l_logLevel <= wip_constants.trace_logging) then
581: wip_logger.exitPoint(p_procName => g_pkgName || '.' || l_procName,