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.PJI_UTILS dependencies on UTL_FILE

Line 359: when UTL_FILE.INVALID_PATH then

355: end if;
356:
357: exception
358:
359: when UTL_FILE.INVALID_PATH then
360: raise_application_error(-20010,
361: 'INVALID PATH exception from UTL_FILE');
362:
363: when UTL_FILE.INVALID_MODE then

Line 361: 'INVALID PATH exception from UTL_FILE');

357: exception
358:
359: when UTL_FILE.INVALID_PATH then
360: raise_application_error(-20010,
361: 'INVALID PATH exception from UTL_FILE');
362:
363: when UTL_FILE.INVALID_MODE then
364: raise_application_error(-20010,
365: 'INVALID MODE exception from UTL_FILE');

Line 363: when UTL_FILE.INVALID_MODE then

359: when UTL_FILE.INVALID_PATH then
360: raise_application_error(-20010,
361: 'INVALID PATH exception from UTL_FILE');
362:
363: when UTL_FILE.INVALID_MODE then
364: raise_application_error(-20010,
365: 'INVALID MODE exception from UTL_FILE');
366:
367: when UTL_FILE.INVALID_FILEHANDLE then

Line 365: 'INVALID MODE exception from UTL_FILE');

361: 'INVALID PATH exception from UTL_FILE');
362:
363: when UTL_FILE.INVALID_MODE then
364: raise_application_error(-20010,
365: 'INVALID MODE exception from UTL_FILE');
366:
367: when UTL_FILE.INVALID_FILEHANDLE then
368: raise_application_error(-20010,
369: 'INVALID FILEHANDLE exception from UTL_FILE');

Line 367: when UTL_FILE.INVALID_FILEHANDLE then

363: when UTL_FILE.INVALID_MODE then
364: raise_application_error(-20010,
365: 'INVALID MODE exception from UTL_FILE');
366:
367: when UTL_FILE.INVALID_FILEHANDLE then
368: raise_application_error(-20010,
369: 'INVALID FILEHANDLE exception from UTL_FILE');
370:
371: when UTL_FILE.INVALID_OPERATION then

Line 369: 'INVALID FILEHANDLE exception from UTL_FILE');

365: 'INVALID MODE exception from UTL_FILE');
366:
367: when UTL_FILE.INVALID_FILEHANDLE then
368: raise_application_error(-20010,
369: 'INVALID FILEHANDLE exception from UTL_FILE');
370:
371: when UTL_FILE.INVALID_OPERATION then
372: raise_application_error(-20010,
373: 'INVALID OPERATION exception from UTL_FILE');

Line 371: when UTL_FILE.INVALID_OPERATION then

367: when UTL_FILE.INVALID_FILEHANDLE then
368: raise_application_error(-20010,
369: 'INVALID FILEHANDLE exception from UTL_FILE');
370:
371: when UTL_FILE.INVALID_OPERATION then
372: raise_application_error(-20010,
373: 'INVALID OPERATION exception from UTL_FILE');
374:
375: when UTL_FILE.READ_ERROR then

Line 373: 'INVALID OPERATION exception from UTL_FILE');

369: 'INVALID FILEHANDLE exception from UTL_FILE');
370:
371: when UTL_FILE.INVALID_OPERATION then
372: raise_application_error(-20010,
373: 'INVALID OPERATION exception from UTL_FILE');
374:
375: when UTL_FILE.READ_ERROR then
376: raise_application_error(-20010,
377: 'READ ERROR exception from UTL_FILE');

Line 375: when UTL_FILE.READ_ERROR then

371: when UTL_FILE.INVALID_OPERATION then
372: raise_application_error(-20010,
373: 'INVALID OPERATION exception from UTL_FILE');
374:
375: when UTL_FILE.READ_ERROR then
376: raise_application_error(-20010,
377: 'READ ERROR exception from UTL_FILE');
378:
379: when UTL_FILE.WRITE_ERROR then

Line 377: 'READ ERROR exception from UTL_FILE');

373: 'INVALID OPERATION exception from UTL_FILE');
374:
375: when UTL_FILE.READ_ERROR then
376: raise_application_error(-20010,
377: 'READ ERROR exception from UTL_FILE');
378:
379: when UTL_FILE.WRITE_ERROR then
380: raise_application_error(-20010,
381: 'WRITE ERROR exception from UTL_FILE');

Line 379: when UTL_FILE.WRITE_ERROR then

375: when UTL_FILE.READ_ERROR then
376: raise_application_error(-20010,
377: 'READ ERROR exception from UTL_FILE');
378:
379: when UTL_FILE.WRITE_ERROR then
380: raise_application_error(-20010,
381: 'WRITE ERROR exception from UTL_FILE');
382:
383: when UTL_FILE.INTERNAL_ERROR then

Line 381: 'WRITE ERROR exception from UTL_FILE');

377: 'READ ERROR exception from UTL_FILE');
378:
379: when UTL_FILE.WRITE_ERROR then
380: raise_application_error(-20010,
381: 'WRITE ERROR exception from UTL_FILE');
382:
383: when UTL_FILE.INTERNAL_ERROR then
384: raise_application_error(-20010,
385: 'INTERNAL ERROR exception from UTL_FILE');

Line 383: when UTL_FILE.INTERNAL_ERROR then

379: when UTL_FILE.WRITE_ERROR then
380: raise_application_error(-20010,
381: 'WRITE ERROR exception from UTL_FILE');
382:
383: when UTL_FILE.INTERNAL_ERROR then
384: raise_application_error(-20010,
385: 'INTERNAL ERROR exception from UTL_FILE');
386:
387: when others then raise;

Line 385: 'INTERNAL ERROR exception from UTL_FILE');

381: 'WRITE ERROR exception from UTL_FILE');
382:
383: when UTL_FILE.INTERNAL_ERROR then
384: raise_application_error(-20010,
385: 'INTERNAL ERROR exception from UTL_FILE');
386:
387: when others then raise;
388:
389: end WRITE2OUT;