Darn, starting to really scratch my head
Have you tried enabling tracing in the DMT?
The other thing that would be nice to do is what happens when you enter in the order manually with that customer, apologies if you’ve already tried that.
Is the Customer on Credit hold? I think the DMT does actually tell you that, but sometimes the errors can be misleading.
My only other thought is if you have some problem with your Xasyst table, which is where the starting order number is stored. I know in 10.1.600 I had to change the format in extended properties to allow me to change to increase the number of digits 9 instead of 6 which is standard for the XaSyst.StartOrderNum. Funnily the default format in OrderHed.OrderNum is 9. So someone was having a bad day somewhere. Not sure if this has been changed in later versions.
I did notice today that there is also a TmpStartOrderNum with some a description of “Used to establish the beginning Sales Order #. When the system generates a new order it will assign the greater of (StartOrderNum) or (the last orders # on file + 1) as the order number.”
There is an old post here about it:
E10 Starting Sales Order Number - Yahoo Archive - Epicor User Help Forum, which I think @ckrusen posted a looooong time ago.
As I said changing the format on StartOrderNum fixed that limitation for me.
This could be a red herring so sorry if it is. I might even be worth just altering your starting ordernum saving and setting it back to the original.
As Calvin mentioned about how the next order number is obtained
So perhaps you have something not correct in your OrderHed table.
I can’t remember if you mentioned it works in one environment and not another. Did you try replicating in a different environment (Pilot or Test)? As @TobyLai and I mentioned our templates work so I’m pretty sure the problem is environment based .