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_CONTENTS_PUB dependencies on FND_MSG_PUB

Line 5: --added in publish flow might already be there in fnd_msg_pub. In this case, this API

1: PACKAGE BODY PA_PAGE_CONTENTS_PUB AS
2: --$Header: PAPGCTPB.pls 120.1 2006/02/24 02:33:46 appldev noship $
3:
4: --Bug 5020365.When this API is called from paxstcvb.Generate_Error_Page, some messages
5: --added in publish flow might already be there in fnd_msg_pub. In this case, this API
6: --should not raise error and let the calling API take care of it. Made changes to not
7: --raise error if the error message is not added to the msg pub by this API
8:
9: procedure CREATE_PAGE_CONTENTS (

Line 57: FND_MSG_PUB.initialize;

53: x_return_status := FND_API.G_RET_STS_SUCCESS;
54:
55: --Clear the global PL/SQL message table
56: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
57: FND_MSG_PUB.initialize;
58: END IF;
59:
60: --Bug 5020365. Keep track of the messages that are there in the stack at the begining.
61: l_init_msg_count:=0;

Line 62: l_init_msg_count := fnd_msg_pub.count_msg;

58: END IF;
59:
60: --Bug 5020365. Keep track of the messages that are there in the stack at the begining.
61: l_init_msg_count:=0;
62: l_init_msg_count := fnd_msg_pub.count_msg;
63:
64: OPEN existing_record;
65: FETCH existing_record INTO l_content_id;
66:

Line 109: x_msg_count := FND_MSG_PUB.Count_Msg;

105:
106: -- IF the number of messages is 1 then fetch the message code from the stack
107: -- and return its text
108: -- Bug 5020365. Get the message only if the message is added to stack in this procedure.
109: x_msg_count := FND_MSG_PUB.Count_Msg;
110: IF (l_init_msg_count <>1 AND x_msg_count = 1) THEN
111: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
112: ,p_msg_index => 1
113: ,p_data => x_msg_data

Line 124: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_CONTENTS_PUB.SAVE_PAGE_CONTENTS'

120:
121: EXCEPTION
122: WHEN OTHERS THEN
123: -- Set the excetption Message and the stack
124: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_CONTENTS_PUB.SAVE_PAGE_CONTENTS'
125: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
126:
127: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
128: RAISE;

Line 176: FND_MSG_PUB.initialize;

172: x_return_status := FND_API.G_RET_STS_SUCCESS;
173:
174: --Clear the global PL/SQL message table
175: IF FND_API.TO_BOOLEAN( p_init_msg_list ) THEN
176: FND_MSG_PUB.initialize;
177: END IF;
178:
179: l_content_id := P_PAGE_CONTENT_ID;
180:

Line 210: x_msg_count := FND_MSG_PUB.Count_Msg;

206: ,x_msg_data);
207:
208: -- IF the number of messages is 1 then fetch the message code from the stack
209: -- and return its text
210: x_msg_count := FND_MSG_PUB.Count_Msg;
211: IF x_msg_count = 1 THEN
212: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_TRUE
213: ,p_msg_index => 1
214: ,p_data => x_msg_data

Line 228: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_CONTENTS_PUB.DELETE_PAGE_CONTENTS'

224: EXCEPTION
225: WHEN OTHERS THEN
226: rollback;
227: -- Set the excetption Message and the stack
228: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_CONTENTS_PUB.DELETE_PAGE_CONTENTS'
229: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
230:
231: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
232: RAISE;