eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.CSL_REQUIREMENTS_PKG dependencies on CSL_SERVICEL_WRAPPER_PKG

Line 153: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

149: );
150:
151: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
152: /*** exception occurred in API -> return errmsg ***/
153: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
154: (
155: p_api_error => TRUE
156: );
157: END IF;

Line 177: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

173: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
174: END IF;
175:
176: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_INSERT', sqlerrm);
177: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
178: (
179: p_api_error => TRUE
180: );
181:

Line 216: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

212: x_return_status := FND_API.G_RET_STS_SUCCESS;
213:
214: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
215: /*** exception occurred in API -> return errmsg ***/
216: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
217: (
218: p_api_error => TRUE
219: );
220: END IF;

Line 240: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

236: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
237: END IF;
238:
239: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_UPDATE', sqlerrm);
240: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
241: (
242: p_api_error => TRUE
243: );
244:

Line 318: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

314: , v_message => 'Delete is not supported for this entity'
315: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
316: END IF;
317:
318: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
319: (
320: p_message => 'CSL_DML_OPERATION'
321: , p_token_name1 => 'DML'
322: , p_token_value1 => p_record.dmltype$$

Line 336: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

332: , v_message => 'Invalid DML type: ' || p_record.dmltype$$
333: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
334: END IF;
335:
336: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
337: (
338: p_message => 'CSL_DML_OPERATION'
339: , p_token_name1 => 'DML'
340: , p_token_value1 => p_record.dmltype$$

Line 364: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT

360: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_ERROR);
361: END IF;
362:
363: fnd_msg_pub.Add_Exc_Msg( g_object_name, 'APPLY_RECORD', sqlerrm);
364: p_error_msg := CSL_SERVICEL_WRAPPER_PKG.GET_ERROR_MESSAGE_TEXT
365: (
366: p_api_error => TRUE
367: );
368:

Line 417: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

413: -- Loop through this cursor to delete all requirement headers from the requirement header inqueue
414: FOR r_get_req_headers_from_inq IN c_get_req_headers_from_inq ( p_user_name, p_tranid) LOOP
415:
416: -- Delete the requirement header from the requirement header inqueue.
417: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
418: (
419: p_user_name,
420: p_tranid,
421: r_get_req_headers_from_inq.seqno$$,

Line 452: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

448: , v_message => 'Record not processed successfully, deferring and rejecting record'
449: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
450: END IF;
451:
452: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
453: (
454: p_user_name
455: , p_tranid
456: , r_get_req_headers_from_inq.seqno$$

Line 551: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

547: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
548: END IF;
549:
550: -- Delete the requirement line from the requirement line inqueue.
551: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
552: (
553: p_user_name,
554: p_tranid,
555: r_requirements.seqno$$,

Line 587: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

583: , v_message => 'Record not processed successfully, deferring and rejecting record'
584: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
585: END IF;
586:
587: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
588: (
589: p_user_name
590: , p_tranid
591: , r_requirements.seqno$$

Line 688: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD

684: , v_message => 'Record successfully processed, deleting from inqueue'
685: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
686: END IF;
687:
688: CSL_SERVICEL_WRAPPER_PKG.DELETE_RECORD
689: (
690: p_user_name,
691: p_tranid,
692: r_requirements.seqno$$,

Line 724: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD

720: , v_message => 'Record not processed successfully, deferring and rejecting record'
721: , v_level_id => JTM_HOOK_UTIL_PKG.G_DEBUG_LEVEL_MEDIUM);
722: END IF;
723:
724: CSL_SERVICEL_WRAPPER_PKG.DEFER_RECORD
725: (
726: p_user_name
727: , p_tranid
728: , r_requirements.seqno$$

Line 774: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CSP_REQUIREMENT_LINES

770:
771: END PROCESS_REQS_NO_HEADERS;
772:
773: /***
774: This procedure is called by CSL_SERVICEL_WRAPPER_PKG when publication item CSP_REQUIREMENT_LINES
775: is dirty. This happens when a mobile field service device executed DML on an updatable table and did
776: a fast sync. This procedure will insert the data that came from mobile into the backend tables using
777: public APIs.
778: ***/