SQL Triggers and Multiple Member Database Files

We are using SQL Triggers on an 830 running v5r2 in connection with an
application that is writing transactions to an audit file for later
updates to a data warehouse.  We are finding that one source of a lot of
transactions is a program that creates and then deletes a temporary
member in one of our major database files. These transactions are
useless to us, and are causing some issues because the key values are
the same as the primary member, and the audit records show up as another
insert of the same keys.  I am looking for a way to reference the member
name in the SQL trigger to exclude updates to the secondary member from
being written to our transaction audit files.  Any ideas about how to do
this?  
 
Thanks,
 
Jim Reinardy
Badger Meter, Inc.