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 146: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

142:
143: exception
144: when others then
145: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
146: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
147: (
148: p_api_error => TRUE
149: );
150: CSM_UTIL_PKG.log( 'Exception in ' || g_object_name || '.APPLY_UPDATE:'

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

146: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
147: (
148: p_api_error => TRUE
149: );
150: CSM_UTIL_PKG.log( 'Exception in ' || g_object_name || '.APPLY_UPDATE:'
151: || ' for PK ' || p_record.NOTIFICATION_ID,'CSM_MAIL_RECIPIENTS_PKG.APPLY_UPDATE',FND_LOG.LEVEL_EXCEPTION );
152:
153: x_return_status := FND_API.G_RET_STS_ERROR;
154: END APPLY_UPDATE;

Line 188: CSM_UTIL_PKG.LOG

184: x_return_status
185: );
186: ELSE
187: -- Process delete; not supported for this entity
188: CSM_UTIL_PKG.LOG
189: ( 'Delete is not supported for this entity'
190: || ' for PK ' || p_record.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_ERROR );
191:
192: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

Line 192: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

188: CSM_UTIL_PKG.LOG
189: ( 'Delete is not supported for this entity'
190: || ' for PK ' || p_record.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_ERROR );
191:
192: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
193: (
194: p_message => 'CSM_DML_OPERATION'
195: , p_token_name1 => 'DML'
196: , p_token_value1 => p_record.dmltype$$

Line 204: CSM_UTIL_PKG.LOG

200: END IF;
201:
202: EXCEPTION WHEN OTHERS THEN
203: /*** defer record when any process exception occurs ***/
204: CSM_UTIL_PKG.LOG
205: ( 'Exception occurred in CSM_mail_recipients_PKG.APPLY_RECORD:' || ' ' || sqlerrm
206: || ' for PK ' || p_record.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_EXCEPTION);
207:
208: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);

Line 209: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT

205: ( 'Exception occurred in CSM_mail_recipients_PKG.APPLY_RECORD:' || ' ' || sqlerrm
206: || ' for PK ' || p_record.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_RECORD',FND_LOG.LEVEL_EXCEPTION);
207:
208: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
209: p_error_msg := CSM_UTIL_PKG.GET_ERROR_MESSAGE_TEXT
210: (
211: p_api_error => TRUE
212: );
213:

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

214: x_return_status := FND_API.G_RET_STS_ERROR;
215: END APPLY_RECORD;
216:
217: /***
218: This procedure is called by CSM_UTIL_PKG when publication item
219: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
220: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
221: public APIs.
222: ***/

Line 255: CSM_UTIL_PKG.DELETE_RECORD

251: /*** was record processed successfully? ***/
252: IF l_process_status = FND_API.G_RET_STS_SUCCESS THEN
253: /*** Yes -> delete record from inqueue ***/
254:
255: CSM_UTIL_PKG.DELETE_RECORD
256: (
257: p_user_name,
258: p_tranid,
259: r_mail_recipients.seqno$$,

Line 270: CSM_UTIL_PKG.LOG

266:
267: /*** was delete successful? ***/
268: IF l_process_status <> FND_API.G_RET_STS_SUCCESS THEN
269: /*** no -> rollback ***/
270: CSM_UTIL_PKG.LOG
271: ( 'Deleting from inqueue failed, rolling back to savepoint'
272: || ' for PK ' || r_mail_recipients.notification_id ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR); -- put PK column here
273: ROLLBACK TO save_rec;
274: x_return_status := FND_API.G_RET_STS_ERROR;

Line 280: CSM_UTIL_PKG.LOG

276: END IF;
277:
278: IF l_process_Status <> FND_API.G_RET_STS_SUCCESS THEN
279: /*** Record was not processed successfully or delete failed -> defer and reject record ***/
280: CSM_UTIL_PKG.LOG
281: ( 'Record not processed successfully, deferring and rejecting record'
282: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
283:
284: CSM_UTIL_PKG.DEFER_RECORD

Line 284: CSM_UTIL_PKG.DEFER_RECORD

280: CSM_UTIL_PKG.LOG
281: ( 'Record not processed successfully, deferring and rejecting record'
282: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
283:
284: CSM_UTIL_PKG.DEFER_RECORD
285: (
286: p_user_name
287: , p_tranid
288: , r_mail_recipients.seqno$$

Line 300: CSM_UTIL_PKG.LOG

296:
297: /*** Was defer successful? ***/
298: IF l_process_status <> FND_API.G_RET_STS_SUCCESS THEN
299: /*** no -> rollback ***/
300: CSM_UTIL_PKG.LOG
301: ( 'Defer record failed, rolling back to savepoint'
302: || ' for PK ' || r_mail_recipients.notification_id,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_ERROR ); -- put PK column here
303: ROLLBACK TO save_rec;
304: x_return_status := FND_API.G_RET_STS_ERROR;

Line 312: CSM_UTIL_PKG.LOG

308: END LOOP;
309:
310: EXCEPTION WHEN OTHERS THEN
311: /*** catch and log exceptions ***/
312: CSM_UTIL_PKG.LOG
313: ( 'Exception occurred in APPLY_CLIENT_CHANGES:' || ' ' || sqlerrm
314: ,'CSM_MAIL_RECIPIENTS_PKG.APPLY_CLIENT_CHANGES',FND_LOG.LEVEL_EXCEPTION);
315: x_return_status := FND_API.G_RET_STS_ERROR;
316: END APPLY_CLIENT_CHANGES;