How to identify what transaction lead to inventory...
# ask-stanley-ai
a
How to identify what transaction lead to inventory added in a location but not in a specific bin?
c
AI generated answer (using internal Slack threads):
Based on the conversations, to identify what transaction led to inventory being added in a location but not in a specific bin, you can perform a transaction search by joining the
inventory details fields..
at the bottom. The lines that come back in the search without those would be your culprit. This usually happens when an item receipt is made but not put into a bin. If you find such an item receipt and the period is not closed, you can modify it and put it in a bin. If you cannot find the item receipt or the period is closed then you need to follow these steps: 1. Turn off bins for that item 2. Adjust out the quantity not in a bin 3. Turn bins on for that item 4. Adjust quantity back into the bin it's physically in (or do not do this step if you don't actually have this inventory) Remember, any transaction that brings stuff into inventory could cause this situation. The most common way to get inventory is item receipts, so that's why it's recommended to start there. If you have over 200 bins with inaccurate amounts, you can import inventory adjustment with bin detail. This does not require resetting the bins to zero first. Please note that using workarounds to ship orders when an item is not physically in a bin but should be, according to the system, could potentially cause issues where a bin has a committed item in it for an order that has potentially already shipped using the new item from Order Receiving. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.857214689
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.839095831
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.835644424
Please provide your feedback on this answer.