A table DML trigger only works inside the scope of the table it belongs to. Therefore, you'll need two triggers for the A and B tables respectively. I assume that tables A and B are related in some way, so it should be easy to get the full picture of a particular workflow even with two separate auditing tables.

Or, create some custom auditing code on the workflow procedure itself.