Error on New Line Order Entry: Order Quantity UOM is required

Our users have been getting this error on adding new lines to orders in Kinetic 2022.1.1 (PILOT).
We’re not sure what’s causing this. Has anyone else had this issue?

Note that the error does not happen for users that are security managers.

Business Layer Exception

Order Quantity UOM is required

Exception caught in: Epicor.ServiceModel

Error Detail 
============
Correlation ID:  31a29b1c-e27d-427e-abd7-2fc897b33472
Description:  Order Quantity UOM is required
Program:  Erp.Services.BO.SalesOrder.dll
Method:  OrderDtlBeforeUpdate
Line Number:  22643
Column Number:  33
Table:  OrderDtl
Field:  SalesUM

Client Stack Trace 
==================
   at Ice.Cloud.ProxyBase`1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
   at Ice.Cloud.ProxyBase`1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Erp.Proxy.BO.SalesOrderImpl.MasterUpdate(Boolean lCheckForOrderChangedMsg, Boolean lcheckForResponse, String cTableName, Int32 iCustNum, Int32 iOrderNum, Boolean lweLicensed, Boolean& lContinue, String& cResponseMsg, String& cCreditShipAction, String& cDisplayMsg, String& cCompliantMsg, String& cResponseMsgOrdRel, String& cAgingMessage, SalesOrderDataSet ds)
   at Erp.Adapters.SalesOrderAdapter.MasterUpdate(Boolean lCheckForOrderChangedMsg, Boolean lcheckForResponse, String cTableName, Int32 iCustNum, Int32 iOrderNum, Boolean lweLicensed, Boolean& lContinue, String& cResponseMsg, String& cCreditShipAction, String& cDisplayMsg, String& cCompliantMsg, String& cResponseMsgOrdRel, String& cAgingMessage)
   at Erp.UI.App.SalesOrderEntry.Transaction.Update()

We are getting the same issue as well. I have a ticket in with Epicor, I will update if we get this resolved.

Hi Vicki. I found the solution to this problem. You have to go into field security maintenance and select the sales order table. Then make sure that the SalesUM record is not showing ‘Read’ access.

We also had this same problem on APInvoiceDtl_PartDescription and PODetail_PartDescription.
Thanks

Hi Steven. Thank you for the info, but this one did not work on my end. I am not showing “Read” but “Full”. Looks like there may be mutliple fixes for this one. Still puzzles me its just this one user and not across the board.

Vicky,
Look at the user groups too. If they’re listed as ‘Read’ then they’ll continue to have the same issue. You can select ‘Full’ or ‘Default’ and it should work for you.
Note that this wasn’t a problem for us if the user was listed as the security administrator.

All users are showing default. I tried to change this particular user to full to see it if helped. It did not.

Did you ever find a solution to this problem? We are having the same issue and we really do not want to keep making everyone a Security Manager to solve this.
Thank you.

@dschneider Welcome. This is an issue with field security I am assuming from this old thread. How many fields are you trying to make read only? I would suggest to move them to bpms to prevent changes rather than field security.

Thank you. I will look into this aspect. I appreciate your time to answer.
Please excuse me if I do not respond soon as we are at quarter end and it gets a little hectic around here.