Counting differences can not be transfered to a MISSING location.
Currently, it is possible to auto acccept a counting difference, or wait until the pending cycle count difference is accepted (or rejected).
What is preferred in practice:
If there is any missing quantity detected upon counting, the missing quantity should be transfered to a MISSING location (instead of an adjustment out).
Then the inventory on the counted location is correct again, and the normal warehouse processes can continue. The MISSING location can be investigated e.g. once a day.
If there is a surplus found in the location, and the difference can be covered from the MISSING location, this should be an option too.
Based on the Yammer topic raised by Steve Mulaik
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/1869742631116800
Comments
A long overdue piece of functionality that is practical and useful. Thanks for posting this common sense update ask.
Category: Warehouse Management
Agree, I have seen this in other WMS systems too. It is common practice and would massively improve cycle counting and reduce errors. Otherwise we have no effective visibility of what was counted as missing.
Category: Warehouse Management
Placing missing inventory as they are discovered by warehouse users (via directed pick) with a reason code into a temporary holding area is desirable. If after a certain time the inventory is not found, the system should generate a cycle count request for the temp location (virtual). This is standard in other advanced warehouse solutions.
Category: Warehouse Management
Is there a MISSING location in D365 for cycle count adjustments?
In other WMS products, there is a means to configure cycle counts in such a way that when a location is cycle counted and a variance discovered, the variance is automatically accepted, but instead of the inventory going "poof" and disappearing from the on hand records for the warehouse, the inventory is moved from the location being counted to a special location called MISSING or LOST, etc. (Also, if inventory is found unexpectedly during a cycle count it will be moved from the MISSING or LOST location into the location being counted. )
In both scenarios, adjustments are spooled for review for the respective quantities. However, these are for the qtys that have been moved in and out of the MISSING or LOST location -not the normal locations. These are reviewed and researched by an inventory control manager weekly and then accepted much like variances are accepted today in the standard CC functionality within D365. Only at this point of acceptance does the inventory truly disappear (get created) from the on hand inventory records for that warehouse.
This approach:
- Lets you continue using a location for picking, etc. but gives you time to do the research before the inventory goes "poof"
- Provides a single location to reference when doing research to see when and where a product has moved in and out of the LOST location. This makes research faster.
It strikes me that there is no way to configure this sort of pending adjustment in D365. Does anyone disagree?
Category: Warehouse Management
Administrator
Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Per Lynnerup
PM, Microsoft