when stock is zero in starting and we have set auto reorder level of 5 and re-order quantity of 5, then it generate material request for purchase tomorrow with 5 quantity, then after that it also create one more material request of 5 quantity day after tomorrow.
reorder level : 5
re-order quantity : 5
tomorrow material request is generated with 5 quantity.
then day after tomorrow it again generated material request of 5 quantity
Seems correct.
What did you expect instead?
@Peer ,
Seems that it is expected that since a re-order request has been generated, then a grace period should be implemented before re-order again if stock is not updated.
Well, I read this as:
Background job looks and sees level is at 0, which is below reorder level 5, so we order 5.
Next day the job looks again, sees 0 + 5 to be expected, which is exactly the reorder level of 5, and thus reorders again 5.
Only the next day the job should not reorder (if level doesn’t move for other reasons).
Or check with number 1-off, like set order quantity to 6 but leave reorder level at 5 and again start with 0, and then see it won’t reorder the (second) next day because reorder level of 5 is still exceeded.
item quantity is zero
item re-order level is 5 and re-order quantity 5
what I am expecting to happen : tomorrow generate material request of 5 quantity then again generate Material request whenever it goes below 5
what is happening: tomorrow generating material request of 5 quantity now quantity after this material request is 5, I have not used single quantity, now again day after tomorrow one more material requset of 5 quantity generates
You can build it like:
I don’t know if any of these is universally correct, but I think you can make it work to your requirements in most of use cases.
please try this with putting re-order level in an item with zero stock
please try this with putting reorder level in an item with zero stock
This is the doc about this feature:
https://docs.frappe.io/erpnext/user/manual/en/auto-creation-of-material-request
If you want to understand it more precisely and maybe undig a real bug, you need to look at the code.
Or you “try out the things”, e.g. experiment as you do and suggest, while looking at the system and it’s output generated by your input in a block box approach.
This might take more time than reading the code, at least once you learned where to look. The code is more or less neatly organized in apps, modules and doctypes, near the latter you find most of the controller logic’s code (but some of it is in libraries for reuse and DRY purposes).
Are You From ERP Team, Please State truth??
I have tried with practically in system like docs of erpnext said. Auto Creation of Material Request
but what is happening: tomorrow generating material request of 5 quantity now quantity after this material request is 5, I have not used single quantity, now again day after tomorrow one more material request of 5 quantity generates
I think its upon ERP NEXT CODE ONLY??
I’m trying to figure things out and, sometimes flabberghastedly sometimes awefully amazedly, advance just like you and most of the forum members, and also trying to be helpful to others.
That said, I’m not sure every Frappe employee fully understands the whole system. Like everywhere else, people learn, come and go (and come back, as read on frappe’s blog), change what they work on, etc. They seem to have a lower communication hurdles though.
Nobody knows everything, and in this fast changing world, the terms “official”, “certified”, “expert” and also imagined delimitations of “team” while simultaneously conjuring a diffusely and variably-sized “ecosystem” where so many self-made people live etc. mean very different things to different people.
I agree
But Please provide solution and check code for me please
please see if you can