Problem calling function inside a procedure

Question

I have a procedure that simply calls a function, but I'm not sure how to declare it.
When I run my script oracle returns an error:
CREATE OR REPLACE PROCEDURE pr_entrada_close(
     var_id_entrada int)
AS
BEGIN
     fn_criaJobAnalise(var_id_entrada);
END;
ERROR at line 5: PL/SQL: Statement ignored3. AS
4. BEGIN
5.      fn_criaJobAnalise(var_id_entrada);
6. END;

Answer 1

As far as I know, that structure worked in at least 8.0 and possibly earlier. I actually saw something similar in production code on that version of Oracle. The actual function took several parameters, and using those paramters did a series of statements along the lines of:
BEGIN
   SELECT 1 INTO l_var
   FROM table1
   WHERE <predicates>
EXCEPTION
   WHEN NO_DATA_FOUND THEN
      RAISE APPLICATION_ERROR (-20001, 'Error');
   WHEN TOO_MANY_ROWS THEN
      RAISE APPLICATION_ERROR (-20002, 'Error');
END;
BEGIN
   SELECT 1 INTO l_var
   FROM table2
   WHERE <predicates>
EXCEPTION
   WHEN NO_DATA_FOUND THEN
      RAISE APPLICATION_ERROR (-20003, 'Error');
   WHEN TOO_MANY_ROWS THEN
      RAISE APPLICATION_ERROR (-20004, 'Error');
END;
-- About 4 or 5 more tables checked
RETURN 1;and the caller looked kind of like:
DECLARE
   NO_ROWS_TABLE1 EXCEPTION;
   DUP_ROWS_TABLE1 EXCEPTION;
   NO_ROWS_TABLE2 EXCEPTION;
   DUP_ROWS_TABLE2 EXCEPTION;
   PRAGMA EXCEPTION_INIT (NO_ROWS_TABLE1, -20001);
   PRAGMA EXCEPTION_INIT (DUP_ROWS_TABLE1, -20002);
   PRAGMA EXCEPTION_INIT (NO_ROWS_TABLE2, -20003);
   PRAGMA EXCEPTION_INIT (DUP_ROWS_TABLE2, -20004);
   l_v NUMBER;
BEGIN
   BEGIN
      l_v := test_tables(<parameters>);
   EXCEPTION
      WHEN NO_ROWS_TABLE1 THEN
         <do something about it>
      WHEN DUP_ROWS_TABLE1 THEN
         <do something about it>
      WHEN NO_ROWS_TABLE2 THEN
         <do something about it>
      WHEN DUP_ROWS_TABLE2 THEN
         <do something about it>
   END;
   <Continue normal processing>
END;and, yes, <Continue normal processing> occasionally failed for mysterious reasons when more than one of the checks would have failed had the function got to them, and l_v was never ever used.
This was one of the clevererbits of code in that app.
John