Compound trigger returns too many lines

Question

Hi all.
I have created a compound trigger which executes a procedure. Although the trigger now runs (I was getting a mutating table error before), it returns multiple lines where I am expecting only one line. When I run the procedure by itself, without the trigger, it runs as expected. Truth is, I created the trigger based on an example I found online, and I am not sure how to modify it to my needs. I don't need the data I am generating in the AFTER EACH ROW section. It exists because the trigger doesn't seem to run otherwise. Any help would be highly appreciated.
create or replace trigger test.requisitions_trigger
  FOR INSERT OR UPDATE ON test.supply_items
COMPOUND TRIGGER
TYPE t_change_tab IS TABLE OF test.tab1_audit%ROWTYPE; g_change_tab t_change_tab := t_change_tab();
AFTER EACH ROW IS
BEGIN
  g_change_tab.extend;
  IF INSERTING THEN
    g_change_tab(g_change_tab.last).action := 'INSERT';
  ELSE
    g_change_tab(g_change_tab.last).action := 'UPDATE';
  END IF;
  g_change_tab(g_change_tab.last).created_time := SYSTIMESTAMP;
END AFTER EACH ROW;
AFTER STATEMENT IS
BEGIN
  test.Requisitions;
END AFTER STATEMENT;
END requisitions_trigger;

Answer 1

In your Re: Mutating Table error - Compound Trigger, the REQUISITIONS procedure was taking an argument that was taken from the row being inserted or updated. In this version, there is no argument. If the REQUISITIONS procedure takes no arguments (and just to harp on it, I'll reiterate that having a table and a procedure with the same name is more than a bit confusing), then you just need a statement level trigger. A statement level trigger is free to query the table being modified all it likes without raising any mutating table concerns (because the current statements changes are either guaranteed to have not been applied or to have been completely applied, there is no risk of seeing data in an inconsistent state).
Justin