APPS.PA_CLIENT_EXTN_BUDGET dependencies on FND_MSG_PUB

Line 273: -- p_err_msg_count := FND_MSG_PUB.Count_Msg;

269: --
270: -- For error and warning messages, you must increment the p_err_msg_count
271: -- OUT-parameter before passing control to the calling procedure:
272: --
273: -- p_err_msg_count := FND_MSG_PUB.Count_Msg;
274: --
275: --
276: -- For a hard error, one that you want to force the calling procedure
277: -- to invoke a 'False' or 'Failure' transition:

Line 303: p_err_msg_count := FND_MSG_PUB.Count_Msg;

299: -- Make sure to update the OUT variable for the
300: -- message count
301: --
302:
303: p_err_msg_count := FND_MSG_PUB.Count_Msg;
304:
305:
306:
307: EXCEPTION

Line 390: -- x_msg_count := FND_MSG_PUB.count_msg;

386: -- ( p_app_short_name => 'PA'
387: -- ,p_msg_name => 'PA_INVALID_LAYOUT'
388: -- );
389: -- x_return_status := FND_API.G_RET_STS_ERROR;
390: -- x_msg_count := FND_MSG_PUB.count_msg;
391:
392: You can define your own message (PA_INVALID_LAYOUT is just an example)
393: and for the messages . Upto 5 tokens can be passed to the PA_UTILS.Add_Message procedure
394: */

Line 426: -- FND_MSG_PUB.add_exc_msg

422: --
423: -- x_return_status := FND_API.G_RET_STS_UNEXP_ERROR;
424: -- x_msg_count := 1;
425: -- x_msg_data := SQLERRM;
426: -- FND_MSG_PUB.add_exc_msg
427: -- ( p_pkg_name => 'PA_CLIENT_EXTN_BUDGET'
428: -- ,p_procedure_name => 'Get_Custom_Layout_Code'
429: -- ,p_error_text => sqlerrm);
430: -- IF l_pa_debug_mode = 'Y' THEN

Line 484: -- FND_MSG_PUB.add_exc_msg

480: --
481: -- x_return_status := FND_API.G_RET_STS_UNEXP_ERROR;
482: -- x_msg_count := 1;
483: -- x_msg_data := SQLERRM;
484: -- FND_MSG_PUB.add_exc_msg
485: -- ( p_pkg_name => 'PA_CLIENT_EXTN_BUDGET'
486: -- ,p_procedure_name => 'Get_Custom_Layout_Code'
487: -- ,p_error_text => sqlerrm);
488: -- RAISE;