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
Cannot create shipment: Source item not found by source code: default and sku: [my-sku custom option] #2043
Comments
Hi @adarshkhatri! Thank you for your report. I could not reproduce this issue, In my case I was able to create invoice and shipment without problems. May you please provide more information about your issue. Did you make new install of Magento 2.3.0 with MSI or you did upgrade from previous version of Magento? What version of MSI you have installed? Was it installation via composer or from git repository? May please give all details of custom option you created for your product as well. |
Hi @smoskaluk Thanks for reply. I had installed clean M2 2.3.0. Product has to be configurable with custom option. Product detail: https://imgur.com/a/rCOasA9 Hope this helps. Thanks. |
This looks like a duplicate of issue #1912 Btw we have a pull request fixing this issue, which was not validated for other product types - #2012 @adarshkhatri could you please check that fix in #2012 works for you? Btw @smoskaluk is it really not reproducible for you? As the initial ticket created back to November 2018 |
And after applying above #2012, it now gives similar exception:
|
Hi @adarshkhatri ! I've tried fix in PR #2012 , and it was working well.
|
They are zero because I am not managing stocks. |
@smoskaluk @maghamed |
@adarshkhatri what the reason to use multiple sources if managing stock is disabled? |
Exactly, I am not managing stock but MSI is enabled by default. Also, I might want to manage stock for specific item in future. In this case I would still want to have MSI enabled. PS, I haven't created any source, there is just 1 available ie. "default". Thanks. |
It looks like there is check in place:
I think solution would be to find the list by For example: Because of this, system will never find the product.
I think, finding the source item by |
Also on my further investigation, I found this:
I also confirm, in my different instance, I have not created any STOCK SOURCE yet. |
Fixed in 2.3 develop |
I have the same issue on 2.3.1 with simple product without any custom options. The issue is when the products are imported but 'Salable Quantity' is 0. If you Edit/Save the product the issue will be fixed. |
I can confirm I just encountered the same issue as @teodorpav above with Magento Open Source 2.3.1 and imported products. Saving the product in the backend solves the issue |
We had this happen when a sku was put in , ordered, then changed before shipping. The shipment then tries to find an skus that is no longer being indexed (and nor should it be). The index would be far better off running on product entity_ids so this kind of this doesn't happen. |
This has happened on our 2.3.6-p1 version with the latest msi installed. The best solution we've found is to block out the sku field on edit, so it's treated like an id that can't be edited. This also doesn't work well if skus have spaces in them |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
PS I had reported this in magento/magento2#21219, but they advised to report here.
The text was updated successfully, but these errors were encountered: