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.AD_MV dependencies on DBMS_SQL

Line 9: ga_stmt dbms_sql.varchar2s;

5:
6: gn_timeout_c CONSTANT INTEGER := dbms_lock.maxwait;
7: gs_lockhandle_name_c CONSTANT VARCHAR2(12) := 'AD_MV_CREATE';
8:
9: ga_stmt dbms_sql.varchar2s;
10:
11: check_tspace_exist varchar2(100);
12:
13: mv_exists EXCEPTION;

Line 29: -- and dbms_sql.parse() is expected to be used, i.e.

25:
26: --
27: -- This procedure should not be called directly from an
28: -- external program when the statement is really long
29: -- and dbms_sql.parse() is expected to be used, i.e.
30: -- ab_long_stmt_i=TRUE. In these cases, the call should
31: -- be made to do_mv_ddl().
32: --
33: PROCEDURE create_mv (

Line 114: ln_cursor := dbms_sql.open_cursor;

110: -- to init section of the package body
111:
112: IF (ab_long_stmt_i)
113: THEN
114: ln_cursor := dbms_sql.open_cursor;
115: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
116: , lb => 1, ub => ga_stmt.COUNT
117: , lfflg => FALSE, language_flag => dbms_sql.native
118: );

Line 115: dbms_sql.parse(c => ln_cursor, statement => ga_stmt

111:
112: IF (ab_long_stmt_i)
113: THEN
114: ln_cursor := dbms_sql.open_cursor;
115: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
116: , lb => 1, ub => ga_stmt.COUNT
117: , lfflg => FALSE, language_flag => dbms_sql.native
118: );
119: ln_dummy := dbms_sql.execute(ln_cursor);

Line 117: , lfflg => FALSE, language_flag => dbms_sql.native

113: THEN
114: ln_cursor := dbms_sql.open_cursor;
115: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
116: , lb => 1, ub => ga_stmt.COUNT
117: , lfflg => FALSE, language_flag => dbms_sql.native
118: );
119: ln_dummy := dbms_sql.execute(ln_cursor);
120: dbms_sql.close_cursor(ln_cursor);
121: ga_stmt.DELETE;

Line 119: ln_dummy := dbms_sql.execute(ln_cursor);

115: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
116: , lb => 1, ub => ga_stmt.COUNT
117: , lfflg => FALSE, language_flag => dbms_sql.native
118: );
119: ln_dummy := dbms_sql.execute(ln_cursor);
120: dbms_sql.close_cursor(ln_cursor);
121: ga_stmt.DELETE;
122: ELSE
123: EXECUTE IMMEDIATE as_stmt_i;

Line 120: dbms_sql.close_cursor(ln_cursor);

116: , lb => 1, ub => ga_stmt.COUNT
117: , lfflg => FALSE, language_flag => dbms_sql.native
118: );
119: ln_dummy := dbms_sql.execute(ln_cursor);
120: dbms_sql.close_cursor(ln_cursor);
121: ga_stmt.DELETE;
122: ELSE
123: EXECUTE IMMEDIATE as_stmt_i;
124: END IF;

Line 147: -- and dbms_sql.parse() is expected to be used, i.e.

143: -- passing boolean parameters in PL/SQL Stored Procedures.
144: --
145: -- This procedure should not be called directly from an
146: -- external program when the statement is really long
147: -- and dbms_sql.parse() is expected to be used, i.e.
148: -- ab_long_stmt_i=1. In these cases, the call should
149: -- be made to do_mv_ddl2().
150: --
151: PROCEDURE create_mv2 (

Line 168: -- and dbms_sql.parse() is expected to be used, i.e.

164:
165: --
166: -- This procedure should not be called directly from an
167: -- external program when the statement is really long
168: -- and dbms_sql.parse() is expected to be used, i.e.
169: -- ab_long_stmt_i=TRUE. In these cases, the call should
170: -- be made to do_mv_ddl().
171: --
172: PROCEDURE mv_ddl (

Line 205: ln_cursor := dbms_sql.open_cursor;

201:
202: BEGIN
203: IF (ab_long_stmt_i)
204: THEN
205: ln_cursor := dbms_sql.open_cursor;
206: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
207: , lb => 1, ub => ga_stmt.COUNT
208: , lfflg => FALSE, language_flag => dbms_sql.native
209: );

Line 206: dbms_sql.parse(c => ln_cursor, statement => ga_stmt

202: BEGIN
203: IF (ab_long_stmt_i)
204: THEN
205: ln_cursor := dbms_sql.open_cursor;
206: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
207: , lb => 1, ub => ga_stmt.COUNT
208: , lfflg => FALSE, language_flag => dbms_sql.native
209: );
210: ln_dummy := dbms_sql.execute(ln_cursor);

Line 208: , lfflg => FALSE, language_flag => dbms_sql.native

204: THEN
205: ln_cursor := dbms_sql.open_cursor;
206: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
207: , lb => 1, ub => ga_stmt.COUNT
208: , lfflg => FALSE, language_flag => dbms_sql.native
209: );
210: ln_dummy := dbms_sql.execute(ln_cursor);
211: dbms_sql.close_cursor(ln_cursor);
212: ga_stmt.DELETE;

Line 210: ln_dummy := dbms_sql.execute(ln_cursor);

206: dbms_sql.parse(c => ln_cursor, statement => ga_stmt
207: , lb => 1, ub => ga_stmt.COUNT
208: , lfflg => FALSE, language_flag => dbms_sql.native
209: );
210: ln_dummy := dbms_sql.execute(ln_cursor);
211: dbms_sql.close_cursor(ln_cursor);
212: ga_stmt.DELETE;
213: ELSE
214: EXECUTE IMMEDIATE as_stmt_i;

Line 211: dbms_sql.close_cursor(ln_cursor);

207: , lb => 1, ub => ga_stmt.COUNT
208: , lfflg => FALSE, language_flag => dbms_sql.native
209: );
210: ln_dummy := dbms_sql.execute(ln_cursor);
211: dbms_sql.close_cursor(ln_cursor);
212: ga_stmt.DELETE;
213: ELSE
214: EXECUTE IMMEDIATE as_stmt_i;
215: END IF;

Line 251: -- executed by preparing ga_stmt before dbms_sql.parse()

247: END drop_mv;
248:
249: --
250: -- This procedure allows really long statements to be
251: -- executed by preparing ga_stmt before dbms_sql.parse()
252: -- is called in other procedures.
253: --
254: -- If the calling program needs to call this procedure
255: -- several times to pass a single statement, make sure