APPS.CSL_TASK_ASSIGNMENTS_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 76: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

72: );
73:
74: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
75: /*** exception occurred in API -> return errmsg ***/
76: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
77: (
78: p_api_error => TRUE
79: );
80: END IF;

Line 127: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

123: );
124:
125: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
126: /*** exception occurred in API -> return errmsg ***/
127: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
128: (
129: p_api_error => TRUE
130: );
131: IF g_debug_level = JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_FULL THEN

Line 159: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

155: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
156: END IF;
157:
158: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
159: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
160: (
161: p_api_error => TRUE
162: );
163:

Line 342: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

338: );
339:
340: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
341: /*** exception occurred in API -> return errmsg ***/
342: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
343: (
344: p_api_error => TRUE
345: );
346: IF g_debug_level = JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_FULL THEN

Line 386: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

382: , x_task_status_id => l_task_status_id
383: );
384: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
385: /*** exception occurred in API -> return errmsg ***/
386: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
387: (
388: p_api_error => TRUE
389: );
390: IF g_debug_level = JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_FULL THEN

Line 419: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

415: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
416: END IF;
417:
418: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
419: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
420: (
421: p_api_error => TRUE
422: );
423:

Line 494: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

490: , v_message => 'Delete is not supported for this entity'
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 512: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

508: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
509: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
510: END IF;
511:
512: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
513: (
514: p_message => 'CSL_DML_OPERATION'
515: , p_token_name1 => 'DML'
516: , p_token_value1 => p_record.dmltype$$

Line 530: l_rc := CSL_SERVICEL_WRAPPER_PKG.AUTONOMOUS_MARK_DIRTY(

526: p_resource_id => JTM_HOOK_UTIL_PKG.get_resource_id( p_record.clid$$cs ),
527: p_pk1_name => 'TASK_ASSIGNMENT_ID',
528: p_pk1_num_value => p_record.TASK_ASSIGNMENT_ID
529: );
530: l_rc := CSL_SERVICEL_WRAPPER_PKG.AUTONOMOUS_MARK_DIRTY(
531: P_PUB_ITEM => g_pub_name,
532: P_ACCESSID => l_access_id,
533: P_RESOURCEID => JTM_HOOK_UTIL_PKG.get_resource_id( p_record.clid$$cs ),
534: P_DML => 'U',

Line 557: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

553: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
554: END IF;
555:
556: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
557: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
558: (
559: p_api_error => TRUE
560: );
561:

Line 574: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CSL_JTF_TASK_ASSIGNMENTS

570: x_return_status := FND_API.G_RET_STS_ERROR;
571: END APPLY_RECORD;
572:
573: /***
574: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CSL_JTF_TASK_ASSIGNMENTS
575: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
576: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
577: public APIs.
578: ***/

Line 692: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

688: , v_message => 'Record successfully processed, deleting from inqueue'
689: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
690: END IF;
691:
692: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
693: (
694: p_user_name,
695: p_tranid,
696: r_task_ass.seqno$$,

Line 728: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

724: , v_message => 'Record not processed successfully, deferring and rejecting record'
725: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
726: END IF;
727:
728: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
729: (
730: p_user_name
731: , p_tranid
732: , r_task_ass.seqno$$