Dynamics 365 F&O/AX Dynamics 365 CE / CRM Dynamics GP Business Central / NAV UG Dynamics SL Power Platform Fabric UG MS Copilot UG

[Mike Cunningham]

We are using “Basic Warehousing” (NOT “Directed Pick and Put-Away”) in NAV 2016.  According to the HELP Text, if the Bin Contents = 0 (zero), the program should delete the record as long as it is not checked as a “Fixed” Bin, but we constantly have many, many zero quantity Bin Content records for Bins that are NOT “Fixed.”

We do have “Require Pick” and “Require Ship” checked, and have a From-Production Bin called “Finished” where all Production Output automatically gets posted.  We “Move” (Item Reclass Journal) from the Finished Bin to a regular Warehouse Bin, and then create the Pick.  The Pick gets registered to the Shipping Bin and the Shipment posted from there using Lanham E-Ship.  The transactions all flow properly, but more often than not, it is the “Shipping” Bin and the “Finished” Bin where the zero Bin Content records persist.

Are we missing something? 

——————————
Mike Cunningham
PSSI
South Bend IN
——————————

[Alex Wiley]

You’re not missing anything, that sounds like a bug. Possibly with E-ship if it’s the shipping bin. I’m curious though why do you do a Reclass instead of a movement?

——————————
Alex Wiley
Haschen
Denver CO
——————————
——————————————-

[Mike Cunningham]

Small Warehouse, small crew, same people do all tasks…   Only using “Basic” NAV Warehousing and Item Reclass is a simple Bin to Bin move…   No need to create a another layer of Warehouse activity or a worksheet…    Also, matches workflow on prior WMS replaced by NAV….

——————————
Mike Cunningham
PSSI
South Bend IN
——————————
——————————————-

[Alex Wiley]

That makes sense, it’s most likely not what is causing the issues but I wanted to make sure it wasn’t related to a modification that could have caused the issue. You don’t have any items set to use extended decimals do you, or use different units of measure when moving product in the warehouse than the base? Rounding issues and having ‘0.00001’ quantity remaining is the only other thing I can think of that would cause the bin content to show 0 and not be deleted, and you can check the warehouse ledger entries to make sure that isn’t happening.

——————————
Alex Wiley
Haschen
Denver CO
——————————
——————————————-

[Mike Cunningham]

No, we don’t have any bizarre decimals or units of measure…    All whole numbers and EA or FT….   We are also fighting with NAV’s behavior of initially setting a new Bin Contents Record to both “Fixed” and “Default”…   We’d prefer a setting that only set “Default” and never “Fixed”…    We routinely go in and clear the “Fixed” flags manually, and are researching if we can modify NAV to not set anything to “Fixed”…

Thanks for the suggestions, though…

——————————
Mike Cunningham
PSSI
South Bend IN
——————————
——————————————-

[Shawn Landers]

We had a similar issue in NAV when we went live last year. We had our partner develop a simple processing report that deletes 0 Qty Bin Content records nightly. This is setup to run the off the job queue. Our business analyst created the processing report so it did not need to go to a developer. It should be pretty easy for your partner to do. 

——————————
Shawn Landers
IT Manager
FoodState
Manchester NH
——————————
——————————————-