1 PACKAGE XLA_UTIL AUTHID CURRENT_USER AS
2 /* $Header: xlautil.pkh 120.0 2003/11/22 02:29:33 weshen noship $ */
3
4 PROCEDURE enable_debug;
5 PROCEDURE enable_debug(buffer_size NUMBER);
6 PROCEDURE enable_debug(path_name in varchar2,
7 file_name in varchar2 default 'DEFAULT');
8 PROCEDURE disable_debug;
9 PROCEDURE debug(text IN VARCHAR2);
10
11 /*===========================================================================+
12 | PROCEDURE |
13 | set_query_context |
14 | |
15 | DESCRIPTION |
16 | Sets the query context in a package variable. The query context can be |
17 | retreived using the function get_query_context. The get_query_context |
18 | function is a SQL function that can be used in SQL as well. |
19 | |
20 | This procedure is typically used with get_query_context. XLA uses this |
21 | function to set and get contexts within the View Accounting Lines and |
22 | Drilldown product views. XLA uses these functions to access the view |
23 | based on product transaction class(group). This approach is used to |
24 | improve performance when accessing union views. |
25 | |
26 | EXTERNAL PROCEDURES/FUNCTIONS ACCESSED |
27 | none |
28 | |
29 | ARGUMENTS |
30 | IN p_context -- Varchar2(100); E.g AR_TRANSACTION |
31 | |
32 | USAGE NOTES: |
33 | Begin |
34 | XLA_UTIL.set_query_context('AR_TRANSACTION'); |
35 | End; |
36 | |
37 | MODIFICATION HISTORY |
38 | 14-Apr-99 Mahesh Sabapathy Created |
39 | |
40 +===========================================================================*/
41 PROCEDURE set_query_context (
42 p_context IN VARCHAR2);
43
44 /*===========================================================================+
45 | PROCEDURE |
46 | get_query_context |
47 | |
48 | DESCRIPTION |
49 | Gets the query context set using set_query_context. |
50 | get_query_context function is designed to be used as a SQL function. |
51 | |
52 | This procedure should be used with set_query_context. XLA uses this |
53 | function to get contexts within the View Accounting Lines and |
54 | Drilldown product views. XLA uses these functions to access the view |
55 | based on product transaction class(group). This approach is used to |
56 | improve performance when accessing union views. |
57 | |
58 | EXTERNAL PROCEDURES/FUNCTIONS ACCESSED |
59 | none |
60 | |
61 | ARGUMENTS |
62 | none |
63 | |
64 | USAGE NOTES: |
65 | Begin |
66 | x := XLA_UTIL.get_query_context; |
67 | End; |
68 | |
69 | MODIFICATION HISTORY |
70 | 14-Apr-99 Mahesh Sabapathy Created |
71 | |
72 +===========================================================================*/
73 FUNCTION get_query_context RETURN VARCHAR2;
74 PRAGMA RESTRICT_REFERENCES( get_query_context, WNDS, WNPS );
75
76
77
78
79 /*===========================================================================+
80 | PROCEDURE |
81 | get_function_id |
82 | |
83 | DESCRIPTION |
84 | Gets the function_id of function p_function_name from the data base. |
85 | Its a wrapper over FND_FUNCTION.GET_FUNCTION_ID.It is used |
86 | to check the existence of any function at the data base. |
87 | |
88 | EXTERNAL PROCEDURES/FUNCTIONS ACCESSED |
89 | FND_FUNCTION.GET_FUNCTION_ID |
90 | |
91 | ARGUMENTS |
92 | IN p_function_name VARCHAR2 |
93 | |
94 | USAGE NOTES: |
95 | Begin |
96 | x := XLA_UTIL.get_function_id(l_function_name) |
97 | End; |
98 | |
99 | MODIFICATION HISTORY |
100 | 14-Jun-03 Lokesh Gandhi Created Bug 2969915 |
101 +===========================================================================*/
102
103 FUNCTION get_function_id(p_function_name in varchar2
104 ) RETURN NUMBER;
105
106
107
108 END XLA_UTIL;
[Home] [Help]