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

Line 64: FND_MSG_PUB.initialize;

60: x_return_status := FND_API.G_RET_STS_SUCCESS;
61:
62: --Clear the global PL/SQL message table
63: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
64: FND_MSG_PUB.initialize;
65: END IF;
66:
67: IF p_page_type = FND_API.g_miss_char THEN
68: l_page_type := 'PPR';

Line 122: x_msg_count := FND_MSG_PUB.Count_Msg;

118: -- IF the number of messaages is 1 then fetch the message code from the stack
119: -- and return its text
120: --
121:
122: x_msg_count := FND_MSG_PUB.Count_Msg;
123: IF x_msg_count = 1 THEN
124: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
125: ,p_msg_index => 1
126: ,p_data => x_msg_data

Line 143: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Create_Page_Layout'

139: WHEN OTHERS THEN
140: rollback;
141:
142: -- Set the excetption Message and the stack
143: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Create_Page_Layout'
144: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
145: --
146: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
147: RAISE; -- This is optional depending on the needs

Line 192: FND_MSG_PUB.initialize;

188: x_return_status := FND_API.G_RET_STS_SUCCESS;
189:
190: --Clear the global PL/SQL message table
191: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
192: FND_MSG_PUB.initialize;
193: END IF;
194:
195:
196: pa_page_layout_pvt.Update_Page_Layout

Line 224: x_msg_count := FND_MSG_PUB.Count_Msg;

220: --
221: -- IF the number of messaages is 1 then fetch the message code from the
222: -- stack and return its text
223: --
224: x_msg_count := FND_MSG_PUB.Count_Msg;
225: IF x_msg_count = 1 THEN
226: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
227: ,p_msg_index => 1
228: ,p_data => x_msg_data

Line 243: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Update_Page_Layout'

239: EXCEPTION
240: WHEN OTHERS THEN
241:
242: -- Set the exception Message and the stack
243: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Update_Page_Layout'
244: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
245: --
246: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
247: RAISE; -- This is optional depending on the needs

Line 281: FND_MSG_PUB.initialize;

277: x_return_status := FND_API.G_RET_STS_SUCCESS;
278:
279: --Clear the global PL/SQL message table
280: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
281: FND_MSG_PUB.initialize;
282: END IF;
283:
284:
285: -- Call the private API

Line 304: x_msg_count := FND_MSG_PUB.Count_Msg;

300: --
301: -- IF the number of messaages is 1 then fetch the message code from the
302: -- stack and return its text
303: --
304: x_msg_count := FND_MSG_PUB.Count_Msg;
305: IF x_msg_count = 1 THEN
306: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
307: ,p_msg_index => 1
308: ,p_data => x_msg_data

Line 324: FND_MSG_PUB.add_exc_msg( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_Page_Layout'

320:
321: rollback;
322:
323: -- Set the excetption Message and the stack
324: FND_MSG_PUB.add_exc_msg( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_Page_Layout'
325: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
326: --
327: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
328: RAISE; -- This is optional depending on the needs

Line 379: FND_MSG_PUB.initialize;

375: x_return_status := FND_API.G_RET_STS_SUCCESS;
376:
377: --Clear the global PL/SQL message table
378: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
379: FND_MSG_PUB.initialize;
380: END IF;
381:
382: --debug_msg_s1('***p_view_region_code ' || p_view_region_code);
383: --debug_msg_s1('***p_view_region_code ' || p_region_source_type);

Line 422: x_msg_count := FND_MSG_PUB.Count_Msg;

418: -- IF the number of messaages is 1 then fetch the message code from the stack
419: -- and return its text
420: --
421:
422: x_msg_count := FND_MSG_PUB.Count_Msg;
423: IF x_msg_count = 1 THEN
424: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
425: ,p_msg_index => 1
426: ,p_data => x_msg_data

Line 442: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.ADD_Page_Region'

438: WHEN OTHERS THEN
439: rollback;
440:
441: -- Set the excetption Message and the stack
442: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.ADD_Page_Region'
443: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
444: --
445: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
446: RAISE; -- This is optional depending on the needs

Line 478: FND_MSG_PUB.initialize;

474: x_return_status := FND_API.G_RET_STS_SUCCESS;
475:
476: --Clear the global PL/SQL message table
477: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
478: FND_MSG_PUB.initialize;
479: END IF;
480:
481: pa_page_layout_pvt.Delete_Page_Region
482: (

Line 503: x_msg_count := FND_MSG_PUB.Count_Msg;

499: --
500: -- IF the number of messaages is 1 then fetch the message code from the
501: -- stack and return its text
502: --
503: x_msg_count := FND_MSG_PUB.Count_Msg;
504: IF x_msg_count = 1 THEN
505: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
506: ,p_msg_index => 1
507: ,p_data => x_msg_data

Line 522: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_Page_Region'

518: EXCEPTION
519: WHEN OTHERS THEN
520:
521: -- Set the exception Message and the stack
522: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_Page_Region'
523: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
524: --
525: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
526: RAISE; -- This is optional depending on the needs

Line 558: FND_MSG_PUB.initialize;

554: x_return_status := FND_API.G_RET_STS_SUCCESS;
555:
556: --Clear the global PL/SQL message table
557: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
558: FND_MSG_PUB.initialize;
559: END IF;
560:
561: pa_page_layout_pvt.Delete_All_Page_Region
562: (

Line 583: x_msg_count := FND_MSG_PUB.Count_Msg;

579: --
580: -- IF the number of messaages is 1 then fetch the message code from the
581: -- stack and return its text
582: --
583: x_msg_count := FND_MSG_PUB.Count_Msg;
584: IF x_msg_count = 1 THEN
585: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
586: ,p_msg_index => 1
587: ,p_data => x_msg_data

Line 602: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_All_Page_Region'

598: EXCEPTION
599: WHEN OTHERS THEN
600:
601: -- Set the exception Message and the stack
602: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_All_Page_Region'
603: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
604: --
605: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
606: RAISE; -- This is optional depending on the needs

Line 638: FND_MSG_PUB.initialize;

634: x_return_status := FND_API.G_RET_STS_SUCCESS;
635:
636: --Clear the global PL/SQL message table
637: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
638: FND_MSG_PUB.initialize;
639: END IF;
640:
641: pa_page_layout_pvt.Delete_All_link_Page_Region
642: (

Line 663: x_msg_count := FND_MSG_PUB.Count_Msg;

659: --
660: -- IF the number of messaages is 1 then fetch the message code from the
661: -- stack and return its text
662: --
663: x_msg_count := FND_MSG_PUB.Count_Msg;
664: IF x_msg_count = 1 THEN
665: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
666: ,p_msg_index => 1
667: ,p_data => x_msg_data

Line 682: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_All_link_Page_Region'

678: EXCEPTION
679: WHEN OTHERS THEN
680:
681: -- Set the exception Message and the stack
682: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_LAYOUT_PUB.Delete_All_link_Page_Region'
683: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
684: --
685: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
686: RAISE; -- This is optional depending on the needs