We have not used our Transaction Codes so I cannot say much about them. The main reason we chose not to use them is because they are limited and we need more options. So we use Transaction Attributes. And you can connect between modules if you set them up through a table. (I personally did not do the set up it was done before I started using the program, but I have maintained/updated the table to make it connect between the GL and A/P).
We are new to FE so I am not sure by I think our T-codes are set up as our appeals and events.
We use transaction codes for items that we would like to be able to report on from the General Ledger. For example to keep track of uniform expenses for employees within a department. We also use transaction codes for all of our buildings and equipment. As far as I know you can not run general ledger reports and filter out attributes from invoices. We do use account and project attributes, which we have helped in our VCO reporting set up. We have also started to use vendor attributes to help identify vendors who are instructors, employees, museum store vendors... Hope this helps in your decision. Michelle
We are able to run reports from the General Ledger and Financial Statement from Transaction Attributes. I think you are thinking that we are using invoice attributes and not Transaction Attributes in the A/P module. With Transaction Attributes you enter it with the distributution of the invoice as you enter total invoice allowing you as many Transaction Attributes as you like and at different amounts. With Invoice Attributes you can assign as many attributes to an invoice as you like but you are assigning the whole invoice amount to those attributes.
Invoice Attributes cannot be viewed in the GL, Transaction Attributes can.