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_TYPE_REGION_PUB dependencies on PA_DEBUG

Line 56: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Create_Page_Type_Region');

52:
53: BEGIN
54:
55: -- Initialize the Error Stack
56: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Create_Page_Type_Region');
57:
58: -- Initialize the return status to success
59: x_return_status := FND_API.G_RET_STS_SUCCESS;
60:

Line 192: PA_DEBUG.Reset_Err_Stack;

188: );
189: END IF;
190:
191: -- Reset the error stack when returning to the calling program
192: PA_DEBUG.Reset_Err_Stack;
193:
194: --commit;
195:
196: -- Put any message text from message stack into the Message ARRAY

Line 203: ,p_procedure_name => PA_DEBUG.G_Err_Stack );

199: rollback;
200:
201: -- Set the excetption Message and the stack
202: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_TYPE_REGION_PUB.Create_Page_Type_Region'
203: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
204: --
205: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
206: RAISE; -- This is optional depending on the needs
207:

Line 253: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Update_Page_Type_Region');

249: l_edit_region_code VARCHAR2(250);
250: BEGIN
251:
252: -- Initialize the Error Stack
253: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Update_Page_Type_Region');
254:
255: -- Initialize the return status to success
256: x_return_status := FND_API.G_RET_STS_SUCCESS;
257:

Line 358: PA_DEBUG.Reset_Err_Stack;

354: END IF;
355:
356:
357: -- Reset the error stack when returning to the calling program
358: PA_DEBUG.Reset_Err_Stack;
359:
360:
361: -- Put any message text from message stack into the Message ARRAY
362: EXCEPTION

Line 367: ,p_procedure_name => PA_DEBUG.G_Err_Stack );

363: WHEN OTHERS THEN
364:
365: -- Set the exception Message and the stack
366: FND_MSG_PUB.add_exc_msg ( p_pkg_name => 'PA_PAGE_TYPE_REGION_PUB.Update_Page_Type_Region'
367: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
368: --
369: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
370: RAISE; -- This is optional depending on the needs
371: --

Line 400: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Delete_Page_Type_Region');

396:
397: BEGIN
398:
399: -- Initialize the Error Stack
400: PA_DEBUG.init_err_stack('PA_PAGE_TYPE_REGION_PUB.Delete_Page_Type_Region');
401:
402: x_return_status := FND_API.G_RET_STS_SUCCESS;
403:
404: --Clear the global PL/SQL message table

Line 443: PA_DEBUG.Reset_Err_Stack;

439: END IF;
440:
441:
442: -- Reset the error stack when returning to the calling program
443: PA_DEBUG.Reset_Err_Stack;
444:
445:
446: EXCEPTION
447: WHEN OTHERS THEN

Line 453: ,p_procedure_name => PA_DEBUG.G_Err_Stack );

449: rollback;
450:
451: -- Set the excetption Message and the stack
452: FND_MSG_PUB.add_exc_msg( p_pkg_name => 'PA_PAGE_TYPE_REGION_PUB.Delete_Page_Type_Region'
453: ,p_procedure_name => PA_DEBUG.G_Err_Stack );
454: --
455: x_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
456: RAISE; -- This is optional depending on the needs
457: