APPS.CSL_COUNTER_VALUES_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 206: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

202: */
203:
204: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
205: /*** exception occurred in API -> return errmsg ***/
206: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
207: (
208: p_api_error => TRUE
209: );
210: END IF;

Line 230: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

226: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
227: END IF;
228:
229: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
230: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
231: (
232: p_api_error => TRUE
233: );
234:

Line 379: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

375: */
376:
377: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
378: /*** exception occurred in API -> return errmsg ***/
379: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
380: (
381: p_api_error => TRUE
382: );
383: END IF;

Line 403: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

399: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
400: END IF;
401:
402: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
403: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
404: (
405: p_api_error => TRUE
406: );
407:

Line 476: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

472: , v_message => 'Delete is not supported for this entity'
473: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
474: END IF;
475:
476: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
477: (
478: p_message => 'CSL_DML_OPERATION'
479: , p_token_name1 => 'DML'
480: , p_token_value1 => p_record.dmltype$$

Line 494: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

490: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
491: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
492: END IF;
493:
494: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
495: (
496: p_message => 'CSL_DML_OPERATION'
497: , p_token_name1 => 'DML'
498: , p_token_value1 => p_record.dmltype$$

Line 522: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

518: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
519: END IF;
520:
521: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
522: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
523: (
524: p_api_error => TRUE
525: );
526:

Line 539: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CS_COUNTER_VALUES

535: x_return_status := FND_API.G_RET_STS_ERROR;
536: END APPLY_RECORD;
537:
538: /***
539: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CS_COUNTER_VALUES
540: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
541: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
542: public APIs.
543: ***/

Line 590: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

586: , v_message => 'Record successfully processed, deleting from inqueue'
587: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
588: END IF;
589:
590: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
591: (
592: p_user_name,
593: p_tranid,
594: r_CS_COUNTER_VALUES.seqno$$,

Line 626: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

622: , v_message => 'Record not processed successfully, deferring and rejecting record'
623: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
624: END IF;
625:
626: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
627: (
628: p_user_name
629: , p_tranid
630: , r_CS_COUNTER_VALUES.seqno$$