AR Transaction Type Extension

Hi,

Our customer has entity (OU) wise unique list of around 70 transaction types, for each OU, in AR defined, and in use already in live instance. Now, we are implementing project billing and amoung 70 defined in AR, in each OU, we may use only around 10 unique same transaction types for each OU for project related invoices in PA.

Hence, to fulfill this, we understood that, to customize the AR transaction type extension.

So the question is, if we customize this extension keeping in view that, only above 10 transaction types that are going to be used in PA, say later if customer wish to include more transaction types to use for PA Invoices, do we again have to revisit the extension code? or we can setup the customization now, in such a way that, it can used even for future added transaction types?