Ques on "CALL" in a Database Trigger

Question

Sir ,
I am invoking one package procedure in one row level trigger on Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bi , PL/SQL Release 10.1.0.4.0 – Production, CORE 10.1.0.4.0 Production,TNS for Solaris: Version 10.1.0.4.0 – Production, NLSRTL Version 10.1.0.4.0 – Production.
The part of the code is attached below. This code gives compilation error but if I delete the word “CALL” from invoking the package procedure, trigger is created. My question when do I use “CALL” to call a procedure in a trigger.
Regards,
Student
CREATE OR REPLACE TRIGGER AIR_REQST
AFTER INSERT ON INFO_REQS
FOR EACH ROW
DECLARE
v_r_id requests.l_id%TYPE;
v_lang_code language_lkups.Lang_Code%TYPE;
BEGIN
SELECT Lang_Code
INTO v_lang_code
FROM language_lkups
WHERE lang_id = :NEW.language_id ;
CALL cg$_appl_pkg.process_reqst
('M5001' ,
v_lang_code ,
'INFO_REQS ' ,
:NEW.infr_id ,
v_lmreq_id -- This is OUT parameter in the procedure
END;

Answer 1

Well, you please let me quote from "Oracle 9i Application Developer’s Guide - Fundamentals Release2(9.2) March 2002 Part No. A96590-01"
Page No. 15-13
The trigger body is a CALL procedure or a PL/SQL block that can include SQL and PL/SQL statements. The CALL procedure can be either a PL/SQL or a Java procedure that is encapsulated in a PL/SQL wrapper. These statements are run if the triggering statement is entered and if the trigger restriction (if included) evaluates to TRUE.
Page No. 15-15
CREATE OR REPLACE PROCEDURE foo (c VARCHAR2) AS
BEGIN
INSERT INTO Audit_table (user_at) VALUES(c);
END;
CREATE OR REPLACE TRIGGER logontrig AFTER LOGON ON DATABASE
-- Just call an existing procedure. The ORA_LOGIN_USER is a function
-- that returns information about the event that fired the trigger.
CALL foo (ora_login_user)
Page No. 15-51
CALL Syntax
CREATE OR REPLACE TRIGGER Secdemo.Setexpseetx
AFTER LOGON ON DATABASE
CALL Secdemo.Exprep_etx.Set_otx
So from Page No. 15-13 , we can easily come to a conclusion that CALL procedure or a PL/SQL block that can include SQL and PL/SQL statements. Right ?