Best approach to Disabling Encumbrance Budget Check for Travel Auths

We have been asked to disable Budget Checking (or moreso stop encumbering) Travel Auths, while continuing to allow Travel Auths to be used in the Expenses Module.

From a general approach standpoint:

- We've unaware of any configuration in Expenses that would allow us to disable Commitment Control only on Travel Auths.  [would love other input if it's possible]

- We can not use the Excluded Account Types on the Budget Definition, as the accounts leverage the same accounts on the Expense Types for Expense Reports

- Oracle Support suggested we change the Selection Criteria, but I'm not sure that does anything for us.....other than either budget checking everything or nothing