APPS.CSL_LOBS_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 209: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

205: END IF;
206:
207: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
208:
209: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
210: (
211: p_api_error => TRUE
212: );
213:

Line 287: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

283: , v_object_name => g_object_name
284: , v_message => l_error_msg
285: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_FULL);
286:
287: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
288: (
289: p_message => 'CSL_DML_OPERATION'
290: , p_token_name1 => 'DML'
291: , p_token_value1 => p_record.dmltype$$

Line 307: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

303: , v_object_name => g_object_name
304: , v_message => l_error_msg
305: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_FULL);
306:
307: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
308: (
309: p_message => 'CSL_DML_OPERATION'
310: , p_token_name1 => 'DML'
311: , p_token_value1 => p_record.dmltype$$

Line 326: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

322: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
323: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
324: END IF;
325:
326: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
327: (
328: p_message => 'CSL_DML_OPERATION'
329: , p_token_name1 => 'DML'
330: , p_token_value1 => p_record.dmltype$$

Line 357: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

353: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
354: END IF;
355:
356: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
357: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
358: (
359: p_api_error => TRUE
360: );
361:

Line 375: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication

371: END APPLY_RECORD;
372:
373:
374: /***
375: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication
376: item CSL_LOBS is dirty. This happens when a mobile field service device
377: executed DML on an updatable table and did a fast sync. This procedure
378: will insert the data that came from mobile into the backend tables using
379: public APIs.

Line 428: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

424: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
425: END IF;
426:
427:
428: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
429: (
430: p_user_name,
431: p_tranid,
432: r_FND_LOBS.seqno$$,

Line 467: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

463: , v_message => 'Deleting from inqueue failed, rolling back to savepoint'
464: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
465: END IF;
466:
467: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
468: (
469: p_user_name
470: , p_tranid
471: , r_FND_LOBS.seqno$$