RSSP Preferences Project defaults - Validation error triggering too early

Summary:

We have created Purchasing Category to expenditure type object mappings. An error is triggered too early when the Purchasing category chosen in Non-Catalog Requisition creation does not correlate to the default expense type that is selected in Preferences - Project Defaults. See attached. This problem does not occur in the old Self Service because the error is triggered upon submission of the requisition--allowing the user to be able to edit the expense type. The other option is to NOT have the expense type default, which is what happens in the old self service. The error in RSSP occurs upon adding