-
-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to allocate stock #7137
Comments
To add to this: when i select a part and go for Build ORder Allocations, that page keeps loading data and never finishes. |
@mabroens if I am understanding what you are saying: Selecting "Remove Allocated Stock" when cancelling a build order will actually remove that quantity of stock and it will be consumed by the build order. Thus, it will not be available any longer. So, I think that this is simply what has happened here - the quantity of stock has been consumed by the build order during cancellation. |
Can you reproduce this on the demo server? |
@SchrodingersGat ai. yes that is what i did but not how i thought it would work. |
You can go to the build order and for each "consumed stock item" you will need to open the admin view and set the "consumed_by" field to null. That should be enough to bring those stock items back into the system |
Can you open up the developer console in your browser, and in the "console" tab you will probably see an error message there? |
@SchrodingersGat was this the right location or should i wait for a fix?? |
This issue seems stale. Please react to show this is still important. |
Please verify that this bug has NOT been raised before.
Describe the bug*
After Cancelling a build order
im not able to allocate stock a new build order:
but if i understand correct: than i still have 1377 pcs availeble and require 1125 more. but for some reason i can not allocate them.
coudl you please advice what t check .
and its for many parts not this single item.
Steps to Reproduce
Expected behaviour
i would expect the 2799 pcs to be availeble:
Deployment Method
Version Information
Version Information:
InvenTree-Version: 0.14.5
Django Version: 4.2.11
Commit Hash: b32f081
Commit Date: None
Commit Branch: stable
Database: sqlite3
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-6.5.0-28-generic-x86_64-with-glibc2.35
Installer: PKG
Target: ubuntu:20.04
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.0.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}]
Please verify if you can reproduce this bug on the demo site.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: