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.OKC_UTIL dependencies on STANDARD

Line 23: -- standard trace constants

19: l_complete_trace_file_name VARCHAR2(255);
20: l_complete_trace_file_name2 VARCHAR2(255) DEFAULT ' ';
21:
22: -------------------------
23: -- standard trace constants
24: -------------------------
25: g_trc_trace_file_prefix CONSTANT VARCHAR2(30) := 'okc_';
26: g_trc_trace_file_suffix CONSTANT VARCHAR2(30) := '.trc';
27:

Line 284: -- copies standard article text to non-standard article's varied text

280: ------------------------------------------------------------------------------
281: FUNCTION Copy_Articles_Text(p_id NUMBER,lang varchar2,p_text VARCHAR2 DEFAULT NULL) RETURN VARCHAR2;
282:
283: -----------------------------------------------------------------------------
284: -- copies standard article text to non-standard article's varied text
285: ------------------------------------------------------------------------------
286: FUNCTION Copy_Articles_Varied_Text(
287: p_article_id NUMBER,
288: p_sae_id NUMBER,

Line 425: -- Purpose: print the standard header for trace files

421: p_module IN VARCHAR2 DEFAULT 'OKC');
422:
423: -------------------------------------------------------------------------------------------
424: -- Procedure: print_trace_header
425: -- Purpose: print the standard header for trace files
426: --
427: -- In Parameters:
428: -- Out Parameters:
429: --

Line 434: -- Purpose: print the standard footer for trace files

430: PROCEDURE print_trace_header;
431:
432: -------------------------------------------------------------------------------------------
433: -- Procedure: print_trace_footer
434: -- Purpose: print the standard footer for trace files
435: --
436: -- In Parameters:
437: -- Out Parameters:
438: --

Line 527: --p_api_version: standard input parameter for the API version

523: ----------------------------------------------------------------------------
524: --Function to decide to a descriptive flexfield should be displayed
525: --It will return 'Y' if at least one of the DFF segment is both enabled and displayed
526: --It will return 'N' otherwise
527: --p_api_version: standard input parameter for the API version
528: --p_init_msg_list: standard input parameter for initialize message or not, defaulted to False
529: --p_application_short_name: the three letter application short name, e.g. 'OKC'
530: --p_dff_name: the name of the descriptive flexfield, e.g., 'DELIVERABLES_FLEX'
531: ----------------------------------------------------------------------------

Line 528: --p_init_msg_list: standard input parameter for initialize message or not, defaulted to False

524: --Function to decide to a descriptive flexfield should be displayed
525: --It will return 'Y' if at least one of the DFF segment is both enabled and displayed
526: --It will return 'N' otherwise
527: --p_api_version: standard input parameter for the API version
528: --p_init_msg_list: standard input parameter for initialize message or not, defaulted to False
529: --p_application_short_name: the three letter application short name, e.g. 'OKC'
530: --p_dff_name: the name of the descriptive flexfield, e.g., 'DELIVERABLES_FLEX'
531: ----------------------------------------------------------------------------
532: FUNCTION Dff_Displayed ( p_api_version IN NUMBER,