You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have a "Consumption Schedule" where we assume that a depot will consume the lots in order of expiration date from soonest expiration date to the longest. It would be nice to display this to the user in a graphical format - something like a Gantt chart. This would allow the user to see which lot (on the Y axis) will be used during which time (on the X axis). We could include cutoffs for their expiration dates so the user can see why they are unable to use all the quantity they think they have in stock, even if they have a large quantity in stock.
This would be linked from the Articles in Stock registry.
The diagram looks kind of like a scheduling diagram of when you would consume different stock lots. That's what I meant by the "consumption schedule". Arguably, we could pick a better term.
The diagram looks kind of like a scheduling diagram of when you would consume different stock lots. That's what I meant by the "consumption schedule". Arguably, we could pick a better term.
I thought you meant that there is something that computed the dates for the lots but was not graphical. So I wanted to see that to use it as a starting point.
This feature depends on #5226.
We currently have a "Consumption Schedule" where we assume that a depot will consume the lots in order of expiration date from soonest expiration date to the longest. It would be nice to display this to the user in a graphical format - something like a Gantt chart. This would allow the user to see which lot (on the Y axis) will be used during which time (on the X axis). We could include cutoffs for their expiration dates so the user can see why they are unable to use all the quantity they think they have in stock, even if they have a large quantity in stock.
This would be linked from the Articles in Stock registry.
Here is a good example of how it should look:
https://cdpn.io/tutsplus/fullembedgrid/ZEzerNB?animations=run&type=embed
The text was updated successfully, but these errors were encountered: