DBA Data[Home] [Help]

APPS.CSL_NOTIFICATIONS_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 86: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

82: -- Check if receiver is valid for the current date
83: IF TRUNC(r_fnd_user.start_date) > TRUNC(SYSDATE) THEN
84: -- The receiver is not yet valid
85: x_return_status := FND_API.G_RET_STS_ERROR;
86: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
87: ( p_message => 'CSL_MAIL_RECEIVER_NOT_YET'
88: , p_token_name1 => 'MAIL_RECEIVER'
89: , p_token_value1 => p_record.recipient_role
90: , p_token_name2 => 'START_DATE'

Line 97: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

93: ELSIF TRUNC(r_fnd_user.end_date) < TRUNC(SYSDATE)
94: THEN
95: -- The receiver is no longer valid
96: x_return_status := FND_API.G_RET_STS_ERROR;
97: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
98: ( p_message => 'CSL_MAIL_RECEIVER_OUTDATED'
99: , p_token_name1 => 'MAIL_RECEIVER'
100: , p_token_value1 => p_record.recipient_role
101: , p_token_name2 => 'END_DATE'

Line 111: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

107: END IF;
108: ELSE
109: -- The receiver is unknown
110: x_return_status := FND_API.G_RET_STS_ERROR;
111: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
112: ( p_message => 'CSL_MAIL_RECEIVER_UNKNOWN'
113: , p_token_name1 => 'MAIL_RECEIVER'
114: , p_token_value1 => p_record.recipient_role
115: );

Line 198: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

194: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
195: END IF;
196:
197: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
198: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
199: (
200: p_api_error => TRUE
201: );
202:

Line 237: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

233: x_return_status := FND_API.G_RET_STS_SUCCESS;
234:
235: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
236: /*** exception occurred in API -> return errmsg ***/
237: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
238: (
239: p_api_error => TRUE
240: );
241: END IF;

Line 261: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

257: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
258: END IF;
259:
260: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
261: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
262: (
263: p_api_error => TRUE
264: );
265:

Line 336: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

332: , v_message => 'Delete is not supported for this entity'
333: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
334: END IF;
335:
336: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
337: (
338: p_message => 'CSL_DML_OPERATION'
339: , p_token_name1 => 'DML'
340: , p_token_value1 => p_record.dmltype$$

Line 354: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

350: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
351: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
352: END IF;
353:
354: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
355: (
356: p_message => 'CSL_DML_OPERATION'
357: , p_token_name1 => 'DML'
358: , p_token_value1 => p_record.dmltype$$

Line 382: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

378: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
379: END IF;
380:
381: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
382: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
383: (
384: p_api_error => TRUE
385: );
386:

Line 399: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item WF_NOTIFICATIONS

395: x_return_status := FND_API.G_RET_STS_ERROR;
396: END APPLY_RECORD;
397:
398: /***
399: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item WF_NOTIFICATIONS
400: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
401: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
402: public APIs.
403: ***/

Line 451: CSL_SERVICEL_WRAPPER_PKG.REJECT_RECORD

447: , v_message => 'Record successfully processed, rejecting record'
448: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
449: END IF;
450:
451: CSL_SERVICEL_WRAPPER_PKG.REJECT_RECORD
452: (
453: p_user_name,
454: p_tranid,
455: r_notification.seqno$$,

Line 476: CSL_SERVICEL_WRAPPER_PKG.REJECT_RECORD

472:
473: FOR r_notification_attr IN c_notification_attr( p_user_name
474: , p_tranid
475: , r_notification.notification_id ) LOOP
476: CSL_SERVICEL_WRAPPER_PKG.REJECT_RECORD
477: ( p_user_name,
478: p_tranid,
479: r_notification_attr.seqno$$,
480: r_notification_attr.notification_id,

Line 497: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

493: , v_message => 'Record successfully processed, deleting from inqueue'
494: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
495: END IF;
496:
497: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
498: (
499: p_user_name,
500: p_tranid,
501: r_notification.seqno$$,

Line 533: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

529: FOR r_notification_attr IN c_notification_attr( p_user_name
530: , p_tranid
531: , r_notification.notification_id ) LOOP
532:
533: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
534: (
535: p_user_name,
536: p_tranid,
537: r_notification_attr.seqno$$,

Line 558: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

554: , v_message => 'Record not processed successfully, deferring and rejecting record'
555: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
556: END IF;
557:
558: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
559: (
560: p_user_name
561: , p_tranid
562: , r_notification.seqno$$

Line 595: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

591: FOR r_notification_attr IN c_notification_attr( p_user_name
592: , p_tranid
593: , r_notification.notification_id ) LOOP
594:
595: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
596: (
597: p_user_name,
598: p_tranid,
599: r_notification_attr.seqno$$,