APPS.CSL_NOTIFICATION_ATTR_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 81: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

77: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
78: END IF;
79:
80: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
81: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
82: (
83: p_api_error => TRUE
84: );
85:

Line 120: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

116: x_return_status := FND_API.G_RET_STS_SUCCESS;
117:
118: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
119: /*** exception occurred in API -> return errmsg ***/
120: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
121: (
122: p_api_error => TRUE
123: );
124: END IF;

Line 144: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

140: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
141: END IF;
142:
143: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
144: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
145: (
146: p_api_error => TRUE
147: );
148:

Line 217: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

213: , v_message => 'Delete is not supported for this entity'
214: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
215: END IF;
216:
217: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
218: (
219: p_message => 'CSL_DML_OPERATION'
220: , p_token_name1 => 'DML'
221: , p_token_value1 => p_record.dmltype$$

Line 235: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

231: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
232: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
233: END IF;
234:
235: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
236: (
237: p_message => 'CSL_DML_OPERATION'
238: , p_token_name1 => 'DML'
239: , p_token_value1 => p_record.dmltype$$

Line 263: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

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

Line 280: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item WF_NOTIFICATION_ATTR

276: x_return_status := FND_API.G_RET_STS_ERROR;
277: END APPLY_RECORD;
278:
279: /***
280: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item WF_NOTIFICATION_ATTR
281: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
282: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
283: public APIs.
284: ***/

Line 331: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

327: , v_message => 'Record successfully processed, deleting from inqueue'
328: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
329: END IF;
330:
331: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
332: (
333: p_user_name,
334: p_tranid,
335: r_not_attr.seqno$$,

Line 367: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

363: , v_message => 'Record not processed successfully, deferring and rejecting record'
364: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
365: END IF;
366:
367: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
368: (
369: p_user_name
370: , p_tranid
371: , r_not_attr.seqno$$