So either we enabled some tax feature we don’t understand and don’t want or 2025.2.x broke my Supplier entry. WTH(eck) is USA?
Why am i getting this error all of a sudden upon save new or edit existing Supplier?
Seems related to values wanting in some new USA panel I’ve never seen before(?)
HELP!
This would be the USA Country Specific Functionality (CSF) “module” that gets you 1099 reporting functionality among other things.
I think you should be able to uncheck the enabled checkbox on your license file if you definitely don’t want it.
Thanks. The thing is we may want it but it’s not been recently enabled (by us) to my knowledge yet all my vendors are broken. Guess I need to figure out what’s required and run some DMTs but wish I knew why it happened. I’m suspicious of 2025.2.5
Hmm if you are SaaS I guess you need them to manage the licensed / enabled module status, but from Company Config screen you should still have a read-only version where you can see what is enabled.
Although I just checked and in 2022.2 classic, Supplier Entry does not complain about TIN unless the 1099 Supplier checkbox is checked, so you may have a bug in play regardless.
Yeah They check Licensed and we are able to check and uncheck Enabled. But we’d didn’t do so AFAIK and it’s enabled on both our pilot and live. So only diff is 2025.2.5 upgrade the other day.
@jbooker I’m seeing the same thing, I’m thinking as a patch you (maybe us too) could put a pre-processing on the method that’s being called, VendorSvc.ValicateTINSubType, to just bail.
Thanks. Consultants are saying it’s a bug from update. Time to make a epicare on a Friday. Wish me luck.
Good to know, hopefully it’s fixed in .6
At least if it’s not fixed before they push it to live it’s a relatively easy thing to deal with.
whens dot 6? id rather go trick or treating than file a case 
I think dot releases are supposed to be released every 2 weeks and the updated us to .5 on Tuesday this week. I don’t think they push every dot release to the cloud but with the CMP you can get it yourself once it’s available.
Thanks. Have a nice weekend.
Remind me to ask @klincecum how to put a 
in the subject line.
:dumpster_fire:
Now don’t going encouraging him!
Support update:
I’ll be assisting you with this case. This error is already reported under PRB0307320/ERPS-300153 which is under Development’s review, as a workaround, please follow the next:
Please let me know if you have any questions
You going to have to DMT that then?
yeah or wait
My reply to case:
Thanks for the workaround, but we’d prefer a data fix or update ASAP. We don’t have time to build and run DMTs to fix problems introduced due to Epicor’s lack of QA testing.
I mean how does this even happen? They roll-out to EU-Asia weeks ago. Is that why they don’t catch USA-CSF issues cuz N/A to foreign user unpaid testers?
