I am using a self hosted copy of ERPnext and have some issues since Version 11 with manufacturing operations. To check whether this is limited to my own instance, I checked and found the same issues on the current cloud version at erpnext.com (ERPnext: v11.1.17 (master) Frappe Framework: v11.1.17 (master)):
(A) Material Consumption for Manufacture
This feature was introduced recently to “consume materials for manufacturing of a production order without booking a finished quantity” ( https://github.com/frappe/erpnext/issues/13368)
The button “Material Consumption” (see example at https://erpnext.com/docs/assets/img/manufacturing/material-consumption-button.png) does not show up.
When trying to “consume materials for manufacturing” with zero in the “For Quantity” field, an error shows up saying that “For Quantity” is mandatory. This sort of defies the purpose of this type of stock entry, which was created exactly for consumption of material without producing any finished goods.
(B) Manufacturing Settings: "Backflush Raw Materials Based On Material Transferred for Manufacture"
The manual explains: “When creating Manufacture Entry, raw-material items are back-flush based on BOM of production item. If you want raw-material items to be back-flushed based on Material Transfer entry made against that Work Order instead, then you should set Back-flush Raw Materials Based On Material Transferred for Manufacture”
This setting does not work anymore since Version 11. Both stock entry types “Manufacture” and “Material Consumption for Manufacture” now always suggest the BOM quantities, and never “transferred quantities”, irrespective of above manufacturing settings.
I have pointed out the latter problem a while ago in December (Version 11 - Backflushing Raw Materials based on Material Transfer - Bug?), and was hoping it would get fixed in one of the regular updates. It really upsets our processes, as we literally have to copy the transferred quantities by pen and paper, and then manual add them to the “Manufacture” stock entry. We would also happily to pay for fixing this issue.