Robson,
The suggestion can be a bit complex, but maybe you can develop a queries with the help of the user_tab_columns and the syntax of the triggers creation DDL command.
Search a little more on the subject in these Asktom links, which is the site of an Oracle Technical Director named Tom Kyte:
http://asktom.oracle.com/pls/asktom/f?p ... 9412348055 http://asktom.oracle.com/pls/apex/f?p=1 ... 4825535375 ]
maybe the solution that the tone presents in these links (the first of it already presents the complete solution) is as close as possible than you want.
Another suggestion, much more "laborious", would be you use Erwin and the macros language of the same to create these triggers. Only in this case you would need a little time to study how the macro language works on Erwin. It seems at first a little complicated but when "you get the way", you can develop the DDL codes quickly and reliably, from a small amount of macro command lines. And it is best that these macros guarantee you that you will not have future problems by changing the structure of the table. The macro reads this structure and dynamically rides the trigger code in real time. You do not spend any time trying to maintain / update the triggers code. And since you have managed to develop a trigger macro for a table, you can reuse this macro to generate the trigger DDLs of the other system tables (and here no matter how many columns the table has).
I understand that it is a paid product, but you can download the Erwin Community Edition from the CA website (an evaluation version that allows you to work with up to 20 tables) and to make reverse engineering One of your bank's tables. Study the macros and then try to develop a trigger. Obtaining a macro, you can import table the table from your Erwin and reuse the macro to generate the table trigger DDL.
Hugs and good luck,
Sergio Coutinho