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.CSM_MAIL_RECIPIENTS_PKG dependencies on CSM_UTIL_PKG

Line 61: CSM_UTIL_PKG.LOG ( 'Entering Update for '|| p_record.notification_id

57: l_dummy NUMBER;
58:
59: BEGIN
60:
61: CSM_UTIL_PKG.LOG ( 'Entering Update for '|| p_record.notification_id
62: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_PROCEDURE);
63:
64: if p_record.delete_flag IS NOT NULL AND substr(p_record.delete_flag,1,1) = 'Y' then
65:

Line 66: CSM_UTIL_PKG.LOG ( 'Delete flag set for notification '|| p_record.notification_id

62: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_PROCEDURE);
63:
64: if p_record.delete_flag IS NOT NULL AND substr(p_record.delete_flag,1,1) = 'Y' then
65:
66: CSM_UTIL_PKG.LOG ( 'Delete flag set for notification '|| p_record.notification_id
67: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_PROCEDURE);
68:
69: begin
70: wf_notification.respond(nid=>p_record.NOTIFICATION_ID,responder=>p_record.clid$$cs);

Line 84: CSM_UTIL_PKG.LOG ( 'Read flag is being set for notification '|| p_record.notification_id

80: ,P_PK1_NUM_VALUE => p_record.notification_id
81: ,P_USER_ID => asg_base.get_user_id(p_record.clid$$cs)
82: );
83: else -- any other update - means this msg is read
84: CSM_UTIL_PKG.LOG ( 'Read flag is being set for notification '|| p_record.notification_id
85: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_PROCEDURE);
86: begin
87: select 1 into l_dummy
88: from wf_notification_attributes wna

Line 101: CSM_UTIL_PKG.LOG ( 'Leaving Update for '|| p_record.notification_id

97:
98:
99: x_return_status := FND_API.G_RET_STS_SUCCESS;
100:
101: CSM_UTIL_PKG.LOG ( 'Leaving Update for '|| p_record.notification_id
102: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_PROCEDURE);
103:
104: exception
105: when others then

Line 107: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

103:
104: exception
105: when others then
106: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
107: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
108: (
109: p_api_error => TRUE
110: );
111: CSM_UTIL_PKG.log( 'Exception in ' || g_object_name || '.APPLY_UPDATE:'

Line 111: CSM_UTIL_PKG.log( 'Exception in ' || g_object_name || '.APPLY_UPDATE:'

107: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
108: (
109: p_api_error => TRUE
110: );
111: CSM_UTIL_PKG.log( 'Exception in ' || g_object_name || '.APPLY_UPDATE:'
112: || ' for PK ' || p_record.NOTIFICATION_ID,'CSM_MAIL_RECIPIENTS_PKG.APPLY_UPDATE',FND_LOG.LEVEL_EXCEPTION );
113:
114: x_return_status := FND_API.G_RET_STS_ERROR;
115: END APPLY_UPDATE;

Line 149: CSM_UTIL_PKG.LOG

145: x_return_status
146: );
147: ELSE
148: -- Process delete; not supported for this entity
149: CSM_UTIL_PKG.LOG
150: ( 'Delete is not supported for this entity'
151: || ' for PK ' || p_record.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_ERROR );
152:
153: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

Line 153: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

149: CSM_UTIL_PKG.LOG
150: ( 'Delete is not supported for this entity'
151: || ' for PK ' || p_record.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_ERROR );
152:
153: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
154: (
155: p_message => 'CSM_DML_OPERATION'
156: , p_token_name1 => 'DML'
157: , p_token_value1 => p_record.dmltype$$

Line 165: CSM_UTIL_PKG.LOG

161: END IF;
162:
163: EXCEPTION WHEN OTHERS THEN
164: /*** defer record when any process exception occurs ***/
165: CSM_UTIL_PKG.LOG
166: ( 'Exception occurred in CSM_mail_recipients_PKG.APPLY_RECORD:' || ' ' || sqlerrm
167: || ' for PK ' || p_record.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_EXCEPTION);
168:
169: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);

Line 170: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

166: ( 'Exception occurred in CSM_mail_recipients_PKG.APPLY_RECORD:' || ' ' || sqlerrm
167: || ' for PK ' || p_record.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_EXCEPTION);
168:
169: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
170: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
171: (
172: p_api_error => TRUE
173: );
174:

Line 179: This procedure is called by CSM_UTIL_PKG when publication item

175: x_return_status := FND_API.G_RET_STS_ERROR;
176: END APPLY_RECORD;
177:
178: /***
179: This procedure is called by CSM_UTIL_PKG when publication item
180: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
181: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
182: public APIs.
183: ***/

Line 216: CSM_UTIL_PKG.DELETE_RECORD

212: /*** was record processed successfully? ***/
213: IF l_process_status = FND_API.G_RET_STS_SUCCESS THEN
214: /*** Yes -> delete record from inqueue ***/
215:
216: CSM_UTIL_PKG.DELETE_RECORD
217: (
218: p_user_name,
219: p_tranid,
220: r_mail_recipients.seqno$$,

Line 231: CSM_UTIL_PKG.LOG

227:
228: /*** was delete successful? ***/
229: IF l_process_status <> FND_API.G_RET_STS_SUCCESS THEN
230: /*** no -> rollback ***/
231: CSM_UTIL_PKG.LOG
232: ( 'Deleting from inqueue failed, rolling back to savepoint'
233: || ' for PK ' || r_mail_recipients.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR); -- put PK column here
234: ROLLBACK TO save_rec;
235: x_return_status := FND_API.G_RET_STS_ERROR;

Line 240: CSM_UTIL_PKG.LOG

236: END IF;
237:
238: ELSE --l_process_Status <> FND_API.G_RET_STS_SUCCESS
239: /*** Record was not processed successfully or delete failed -> defer and reject record ***/
240: CSM_UTIL_PKG.LOG
241: ( 'Record not processed successfully, deferring and rejecting record'
242: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
243:
244: CSM_UTIL_PKG.DEFER_RECORD

Line 244: CSM_UTIL_PKG.DEFER_RECORD

240: CSM_UTIL_PKG.LOG
241: ( 'Record not processed successfully, deferring and rejecting record'
242: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
243:
244: CSM_UTIL_PKG.DEFER_RECORD
245: (
246: p_user_name
247: , p_tranid
248: , r_mail_recipients.seqno$$

Line 260: CSM_UTIL_PKG.LOG

256:
257: /*** Was defer successful? ***/
258: IF l_process_status <> FND_API.G_RET_STS_SUCCESS THEN
259: /*** no -> rollback ***/
260: CSM_UTIL_PKG.LOG
261: ( 'Defer record failed, rolling back to savepoint'
262: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
263: ROLLBACK TO save_rec;
264: x_return_status := FND_API.G_RET_STS_ERROR;

Line 272: CSM_UTIL_PKG.LOG

268: END LOOP;
269:
270: EXCEPTION WHEN OTHERS THEN
271: /*** catch and log exceptions ***/
272: CSM_UTIL_PKG.LOG
273: ( 'Exception occurred in APPLY_CLIENT_CHANGES:' || ' ' || sqlerrm
274: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_EXCEPTION);
275: x_return_status := FND_API.G_RET_STS_ERROR;
276: END APPLY_CLIENT_CHANGES;