# Order Entry error - OurRequestedQty is required **URL:** \ **Category:** Epicor ERP 10\ **Tags:** e10\ **Created:** [October 2, 2020, 7:44pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495 "2020-10-02T19:44:55Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Jamie\_B](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Jamie\_B](https://www.epiusers.help/u/Jamie_B)\ **Post date:** [October 2, 2020, 7:44pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/1 "2020-10-02T19:44:55Z")
Hello all, some of our order entry team have been having this error pop up when entering lines. Entering part, then quantity, they have this error pop up. ![our req qty error](https://www.epiusers.help/uploads/default/original/3X/7/5/7532ea47bf22fb37e11945312a8253135545b2db.jpeg) They say that pressing OK causes the lines to duplicate when they come back to the order. ![dupe lines](https://www.epiusers.help/uploads/default/original/3X/1/4/14da0618ab06013ef93117c780849b8e58419a2f.jpeg) They say that they have not noticed any particular pattern for what causes this error, and in my own attempts to track it down I have not noticed a pattern either. I haven’t been able to find any other discussion of this error on this forum. Does anyone have any experience with it and/or know what is causing it or how to prevent it? ---
**Author:** ![TomAlexander](https://www.epiusers.help/user_avatar/www.epiusers.help/tomalexander/32/98890_2.png) [@TomAlexander](https://www.epiusers.help/u/TomAlexander)\ **Post date:** [October 2, 2020, 7:58pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/2 "2020-10-02T19:58:40Z")
Do you have any BPMs running on the SalesOrder business object? Sounds like a BPM gone wrong… ---
**Author:** ![Jamie\_B](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Jamie\_B](https://www.epiusers.help/u/Jamie_B)\ **Post date:** [October 2, 2020, 8:12pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/3 "2020-10-02T20:12:30Z")
There is one that changes the need by date, but it goes on every order and the error only pops up intermittently. And while I wouldn’t swear to it, I think it was occurring before we enabled that BPM. ---
**Author:** ![Jonathan](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/aeb1de/32.png) [@Jonathan](https://www.epiusers.help/u/Jonathan)\ **Post date:** [October 2, 2020, 10:40pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/4 "2020-10-02T22:40:52Z")
What epicor version are you running? Can you paste the entire exception detail text? ---
**Author:** ![Jason\_Woods](https://www.epiusers.help/user_avatar/www.epiusers.help/jason_woods/32/80101_2.png) [@Jason\_Woods](https://www.epiusers.help/u/Jason_Woods)\ **Post date:** [October 4, 2020, 12:35am UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/5 "2020-10-04T00:35:04Z")
The Details for the error will be more helpful, but It is likely set as a Required Field in Extended Properties if it isn’t a BPM. You will want to check for both OrderDtl and OrderRel. ---
**Author:** ![Jamie\_B](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Jamie\_B](https://www.epiusers.help/u/Jamie_B)\ **Post date:** [October 8, 2020, 2:00pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/6 "2020-10-08T14:00:26Z")
Here’s that detail text. Sorry it took a couple days, like I said the error comes up very sporadically. * * * Business Layer Exception Our Requested Qty is required. Exception caught in: Epicor.ServiceModel # Error Detail Correlation ID: 6d9ae600-cc7f-4f79-bd13-450fcee5b11a Description: Our Requested Qty is required. Program: Epicor.Ice.dll Method: ValidateColumn Line Number: 254 Column Number: 17 Table: OrderRel Field: OurReqQty # Client Stack Trace at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets) 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() ---
**Author:** ![Randy](https://www.epiusers.help/user_avatar/www.epiusers.help/randy/32/51539_2.png) [@Randy](https://www.epiusers.help/u/Randy)\ **Post date:** [October 8, 2020, 2:24pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/7 "2020-10-08T14:24:12Z")
So it’s the OrderRel table. What is the difference between orders that do and do not get this error? Is it quotes pulled into an order? Is this user or part number specific? etc ---
**Author:** ![Jamie\_B](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Jamie\_B](https://www.epiusers.help/u/Jamie_B)\ **Post date:** [October 8, 2020, 2:31pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/8 "2020-10-08T14:31:27Z")
Unfortunately we haven’t able to find any discernible pattern yet. I’ve asked our order entry team to try and identify a pattern for when they see it coming up, but as far as they can tell it seems random. ---
**Author:** ![Jason\_Woods](https://www.epiusers.help/user_avatar/www.epiusers.help/jason_woods/32/80101_2.png) [@Jason\_Woods](https://www.epiusers.help/u/Jason_Woods)\ **Post date:** [October 8, 2020, 3:14pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/9 "2020-10-08T15:14:58Z")
The error shows “ValidateColumn”. This is either the Extended Properties or base Epicor logic. ---
**Author:** ![Jamie\_B](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Jamie\_B](https://www.epiusers.help/u/Jamie_B)\ **Post date:** [October 8, 2020, 4:17pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/10 "2020-10-08T16:17:20Z")
I checked the extended properties and the OurReqQty is not marked as required in the OrderRel table. If it’s base epicor logic is there anything that can be done about it? ---
**Author:** ![Jason\_Woods](https://www.epiusers.help/user_avatar/www.epiusers.help/jason_woods/32/80101_2.png) [@Jason\_Woods](https://www.epiusers.help/u/Jason_Woods)\ **Post date:** [October 8, 2020, 4:18pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/11 "2020-10-08T16:18:54Z")
You will unfortunately have to find what is causing the error and correct it. Have you verified that the OrderRel table does not have a Data Directive and the SalesOrder.Update and SalesOrder.MasterUpdate do not have a Method Directive that is causing this? ---
**Author:** ![Jonathan](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/aeb1de/32.png) [@Jonathan](https://www.epiusers.help/u/Jonathan)\ **Post date:** [October 8, 2020, 7:41pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/12 "2020-10-08T19:41:13Z")
Can you enable server logging and get more details for the exception? ---
**Author:** ![Sdewaard](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/bbce88/32.png) [@Sdewaard](https://www.epiusers.help/u/Sdewaard)\ **Post date:** [March 30, 2021, 6:40am UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/13 "2021-03-30T06:40:46Z")
@Jamie_B Hello Jamie, I don’t see this topic solved yet. Have you gained any further insights? Our sales team is getting the same error. We are now on 10.2.600, but also got the error on 10.2.400. I also find it difficult to find the pattern. I tested with make to stock, make to order, purchased parts, in different sites and in different companies. I tested several ways of adding a new release, for example 1) add line with quantity, save, add a new release, 2) add line with quantity, no save, add new release, 3) add line without quantity, add new release. And also in these different methods sometimes I got the error and sometimes I didn’t. Then I realized I only get the errors on a new order on the first line. I was wondering whether this is also the case at your company? No solution yet, but perhaps it might get us a bit closer to finding one. Kind Regards, Saskia ---
**Author:** ![Jonathan](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/aeb1de/32.png) [@Jonathan](https://www.epiusers.help/u/Jonathan)\ **Post date:** [March 30, 2021, 5:41pm UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/14 "2021-03-30T17:41:38Z")
Can you enable server logging and sharing the error details? So even if you do two orders the same way only one gets the error? Same customer/part/date/etc? ---
**Author:** ![Sdewaard](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/bbce88/32.png) [@Sdewaard](https://www.epiusers.help/u/Sdewaard)\ **Post date:** [March 31, 2021, 5:18am UTC](https://www.epiusers.help/t/order-entry-error-ourrequestedqty-is-required/71495/15 "2021-03-31T05:18:43Z")
Hello Jonathan, I tested with the same customer, part, date etc. At first it seemed like only one gets the error, but then I realized it’s dependent on the linenumber. So when I do two orders exactly the same way I also get the same error, when it concerns the first line. WHen I add new releases on line 2, 3 andsoforth then I don’t get the error on neither order. The error itself is a logical/standard E10 message. When you add a new release and try to save it without a quantity it will come up with this message. That’s regular behavior. Only in our system the message already comes up the moment we add the new release and without a chance of saving or entering a quantity. Yesterday after my post I looked at it with our ERP-consultant.He enabled trace logging and saw that somehow the save-function was already triggered the moment we add the new release on the first line. I don’t have the error details myself. I asked him to test in his own clean environment (because of the method and data directives we have in our system), and he couldn’t replicate. So it must be a flaw in one of our method or data directives. So I will disable them one by one to identify which one is causing this error and have our developer look into it.