ORA-04091: is mutating, trigger / function / ORA-06519: active autonomous transaction detected and rolled back in IFS

--Avoid performing SELECT or DML operations on the same table or view.

The Event Action "Execute Online SQL" on "X_GPL_NEXT_PURCH_ORD_AUTH" has failed. 

Please contact your System Administrator to manage the Event Actions. 

ORA-04091: table IFSAPP.PURCHASE_ORDER_APPROVAL_TAB is mutating, trigger/function 

may not see it in IFS cust event

The Event Action "Execute Online SQL" on "X_GPL_NEXT_PURCH_ORD_AUTH" has failed. Please contact your 

System Administrator to manage the Event Actions. ORA-06519: active autonomous transaction detected 

and rolled back in IFS

You can trigger events without hitting irreverent mutations by using a AUTONOMOUS_TRANSACTION block. Here you have to manually handle commits and rollbacks as the block will not be impacted by the triggering transaction. 

Sample would be something like below.

DECLARE 
  PRAGMA AUTONOMOUS_TRANSACTION;

BEGIN
    
 -- Some logic
 
  COMMIT; -- or rollback.. this would need to be handled manually within the autonomous block
END;