Given that you guys limited the “Allow on Submit” feature to only work on custom fields back in Sep 2014 (see links below) I’m stuck with some scenarios which are not nice at all.
Previously, I had “Allow on Submit” enabled on the
rate field in Sales Order Items. We have regular rush orders, which we place on behalf of customers. The price is not known at the beginning, and the customer accepts that. We issue a SO, and in due course, a MREQ, PO and sometimes even a PR. Previously, when the price is known, the ERP user would go back to the SO and correct the
rate before shipping and invoicing goods to the client.
The alternative is to cancel the SO, Amend, and re-submit. But the system forces the user to deal with all descendants first. When trying to cancel the SO, the user gets the error
Cannot delete or cancel because Sales Order SO22093 is linked with MREQ-01074 Material Request. This makes sense to me. But now the erp user needs to cancel and re-issue many more records, MREQ, possibly multiple POs, and sometimes also Purchase Receipts. That’s a lot of work, and the supplier PO name will also change, so if we are to be rigorous, we should rightly resend the PO to our supplier even though there was no material change on that PO, just that the PO suffix now has a
Now “Allow on Submit” is no longer an option for our scenario (as per issue erpnext/956). I accept that our configuration was not the best anyway (editable price fields are bad!), but comparing it to the the alternative of Cancelling/Amending/Submitting all downstream records, it was a reasonable trade-off.
My question is, given this scenario, what could the correct way to deal with this scenario? Is there a way to Cancel/Amend/Re-Submit a SO without having to do the same for all downstream Docs related to that SO instance?
Thank you guys,
Links to previous discussion, and issue in github.