Hi,
my company is currently using oracle E- Business suite 11i on solaris 9(UNIX).
the company is upgrading to oracle E- Business suite R12 on a solaris 9(UNIX).
There is a custom form that compiled perfectly on the existing 11i environment,
but when the form is compiled in the R12 environment it produces an error:
Compiling procedure DISPLAY_ALERT...
Compilation error on procedure DISPLAY_ALERT:
PL/SQL ERROR 201 at line 4, column 4
identifier 'CALL' must be declared
PL/SQL ERROR 0 at line 4, column 4
Statement ignored
the error is caused by CALL in display_alert.The display_alert procedure is:
procedure display_alert(MESSAGE_TEXT in VARCHAR2, ALERT_RESPONSE out VARCHAR2) is
begin
:GLOBAL.MESSAGE_TEXT := MESSAGE_TEXT;
call('ALERT',NO_HIDE,DO_REPLACE);
default_value('N','GLOBAL.ALERT_RESPONSE');
ALERT_RESPONSE := :GLOBAL.ALERT_RESPONSE;
erase('GLOBAL.ALERT_RESPONSE');
end;
The procedure CALL was found in a package called 'PACKAGE app_form'. The package is apart of the library APPCORE.pll.
this APPCORE.pll is in the AU_TOP/resource directory on the server.
i modified the code in the display_alert and qualified the 'call' to 'app_form.call' and recompiled it in the R12 environment:
procedure display_alert(MESSAGE_TEXT in VARCHAR2, ALERT_RESPONSE out VARCHAR2) is
begin
:GLOBAL.MESSAGE_TEXT := MESSAGE_TEXT;
app_form.call('ALERT',NO_HIDE,DO_REPLACE);
default_value('N','GLOBAL.ALERT_RESPONSE');
ALERT_RESPONSE := :GLOBAL.ALERT_RESPONSE;
erase('GLOBAL.ALERT_RESPONSE');
end;
the form was compiled without any errors!!
my question is...is there any way that i can get the form to see the procedure 'CALL' directly instead of referencing it with 'app_form.call' ?
] 
Blog
Search
Help
Members
Register
Login
Home
