This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hello,
We would like to create a new set of expense types, which allow a secondary level of validation. For example: Expense type = staff entertainment, within which there are two options: "Christmas" or "other". This is to allow automation of the tax allocations without the user having to know anything about tax. However, I understand that there is a limit (12) on the number of custom fields (presumably per installation, not expense type?). If we don't use custom fields, how else can we achieve this?
Thank you
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@KB108 there are more than 12 custom fields that can be used, however in looking at your site, you appear to have used almost all of them. So, I think you are going to be hard pressed to achieve what you need using custom fields.
Why wouldn't you simply create two expense types instead of doing a second level of validation? Couldn't you create an expense type named: Staff Entertainment - Christmas and then another named: Staff Entertainment - Other?
I think this would be less involved and I don't see why the tax calculation wouldn't still be done. The tax calculation comes from the configured tax groups which have certain expense types assigned to them.
Let's see what other say.