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.OE_SERVICE_UTIL dependencies on DBMS_DESCRIBE

Line 386: l_overload dbms_describe.number_table;

382:
383: )
384: is
385:
386: l_overload dbms_describe.number_table;
387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;

Line 387: l_position dbms_describe.number_table;

383: )
384: is
385:
386: l_overload dbms_describe.number_table;
387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;

Line 388: l_level dbms_describe.number_table;

384: is
385:
386: l_overload dbms_describe.number_table;
387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;

Line 389: l_argumentname dbms_describe.varchar2_table;

385:
386: l_overload dbms_describe.number_table;
387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;

Line 390: l_datatype dbms_describe.number_table;

386: l_overload dbms_describe.number_table;
387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;

Line 391: l_defaultvalue dbms_describe.number_table;

387: l_position dbms_describe.number_table;
388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;

Line 392: l_inout dbms_describe.number_table;

388: l_level dbms_describe.number_table;
389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;

Line 393: l_length dbms_describe.number_table;

389: l_argumentname dbms_describe.varchar2_table;
390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;
397: l_spare dbms_describe.number_table;

Line 394: l_precision dbms_describe.number_table;

390: l_datatype dbms_describe.number_table;
391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;
397: l_spare dbms_describe.number_table;
398:

Line 395: l_scale dbms_describe.number_table;

391: l_defaultvalue dbms_describe.number_table;
392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;
397: l_spare dbms_describe.number_table;
398:
399: --

Line 396: l_radix dbms_describe.number_table;

392: l_inout dbms_describe.number_table;
393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;
397: l_spare dbms_describe.number_table;
398:
399: --
400: l_debug_level CONSTANT NUMBER := oe_debug_pub.g_debug_level;

Line 397: l_spare dbms_describe.number_table;

393: l_length dbms_describe.number_table;
394: l_precision dbms_describe.number_table;
395: l_scale dbms_describe.number_table;
396: l_radix dbms_describe.number_table;
397: l_spare dbms_describe.number_table;
398:
399: --
400: l_debug_level CONSTANT NUMBER := oe_debug_pub.g_debug_level;
401: --

Line 408: dbms_describe.describe_procedure

404: IF l_debug_level > 0 THEN
405: oe_debug_pub.add( 'ENTERING CHECK_PROC API' ) ;
406: END IF;
407: BEGIN
408: dbms_describe.describe_procedure
409: (
410: p_procedure_name,
411: null,
412: null,