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.PON_BIZ_EVENTS_PVT dependencies on STANDARD

Line 56: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

52: -- to this procedure call. It will have following
53: -- values -
54: -- 0 (for Success without warning)
55: -- 1 or more (for Error(s)/Warning(s)
56: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
57: -- used to return the first message of the stack
58: -- Version : Current version 1.0
59: -- Previous version 1.0
60: -- Initial version 1.0

Line 181: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

177: -- to this procedure call. It will have following
178: -- values -
179: -- 0 (for Success without warning)
180: -- 1 or more (for Error(s)/Warning(s)
181: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
182: -- used to return the first message of the stack
183: -- Version : Current version 1.0
184: -- Previous version 1.0
185: -- Initial version 1.0

Line 323: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

319: -- to this procedure call. It will have following
320: -- values -
321: -- 0 (for Success without warning)
322: -- 1 or more (for Error(s)/Warning(s)
323: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
324: -- used to return the first message of the stack
325: -- Versioni : Current version 1.0
326: -- Previous version 1.0
327: -- Initial version 1.0

Line 468: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

464: -- to this procedure call. It will have following
465: -- values -
466: -- 0 (for Success without warning)
467: -- 1 or more (for Error(s)/Warning(s)
468: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
469: -- used to return the first message of the stack
470: -- Version : Current version 1.0
471: -- Previous version 1.0
472: -- Initial version 1.0

Line 599: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

595: -- to this procedure call. It will have following
596: -- values -
597: -- 0 (for Success without warning)
598: -- 1 or more (for Error(s)/Warning(s)
599: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
600: -- used to return the first message of the stack
601: -- Version : Current version 1.0
602: -- Previous version 1.0
603: -- Initial version 1.0

Line 744: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter

740: -- to this procedure call. It will have following
741: -- values -
742: -- 0 (for Success without warning)
743: -- 1 or more (for Error(s)/Warning(s)
744: -- OUT : x_msg_data VARCHAR2, the standard message data output parameter
745: -- used to return the first message of the stack
746: -- Version : Current version 1.0
747: -- Previous version 1.0
748: -- Initial version 1.0

Line 918: -- Standard Start of API savepoint

914: BEGIN
915: -- Initialize API return status to success
916: x_return_status := FND_API.G_RET_STS_SUCCESS;
917:
918: -- Standard Start of API savepoint
919: SAVEPOINT pon_biz_event_raise_event;
920:
921: g_err_loc := '10.0 Going to start in RAISE_EVENT call';
922: LOG_MESSAGE('raise_event', g_err_loc);

Line 924: -- Standard call to check for call compatibility

920:
921: g_err_loc := '10.0 Going to start in RAISE_EVENT call';
922: LOG_MESSAGE('raise_event', g_err_loc);
923: --
924: -- Standard call to check for call compatibility
925: --
926: IF NOT FND_API.COMPATIBLE_API_CALL ( l_api_version,
927: p_api_version,
928: l_api_name,