APPS.CSL_NOTES_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 66: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

62: );
63:
64: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
65: /*** exception occurred in API -> return errmsg ***/
66: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
67: (
68: p_api_error => TRUE
69: );
70: END IF;

Line 90: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

86: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
87: END IF;
88:
89: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
90: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
91: (
92: p_api_error => TRUE
93: );
94:

Line 147: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

143: );
144:
145: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
146: /*** exception occurred in API -> return errmsg ***/
147: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
148: (
149: p_api_error => TRUE
150: );
151: END IF;

Line 171: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

167: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
168: END IF;
169:
170: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
171: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
172: (
173: p_api_error => TRUE
174: );
175:

Line 244: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

240: , v_message => 'Delete is not supported for this entity'
241: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
242: END IF;
243:
244: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
245: (
246: p_message => 'CSL_DML_OPERATION'
247: , p_token_name1 => 'DML'
248: , p_token_value1 => p_record.dmltype$$

Line 262: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

258: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
259: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
260: END IF;
261:
262: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
263: (
264: p_message => 'CSL_DML_OPERATION'
265: , p_token_name1 => 'DML'
266: , p_token_value1 => p_record.dmltype$$

Line 290: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

286: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
287: END IF;
288:
289: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
290: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
291: (
292: p_api_error => TRUE
293: );
294:

Line 307: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item JTF_NOTES_VL

303: x_return_status := FND_API.G_RET_STS_ERROR;
304: END APPLY_RECORD;
305:
306: /***
307: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item JTF_NOTES_VL
308: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
309: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
310: public APIs.
311: ***/

Line 358: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

354: , v_message => 'Record successfully processed, deleting from inqueue'
355: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
356: END IF;
357:
358: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
359: (
360: p_user_name,
361: p_tranid,
362: r_note.seqno$$,

Line 394: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

390: , v_message => 'Record not processed successfully, deferring and rejecting record'
391: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
392: END IF;
393:
394: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
395: (
396: p_user_name
397: , p_tranid
398: , r_note.seqno$$