Sage 100

Wondering about warehouse transfers that require BOL's and time in transit. How do you suggest your users track/process these? They've tried several things but none resolves the issue of printing a BOL - which they currently do by entering a sales order, printing a modified SO form, then deleting the order. Once they have confirmation it has been received, they then re-enter the items in inventory as a transfer. During this time in transit, the originating whse is short these items and they often get adjusted out since no one knows they are in transit. Plus the time it takes to rekey the items. These aren't small transfers either. They are truckloads. We have suggested three options: - Transfer to an In-transit warehouse - no BOL and re-keying; - Invoice the order then create a PO - costs may change; - Invoice the order, create an RMA for the entire invoice then receive the RMA into the second whse - they think this confuses what RMA is meant to do (i.e. the inventory guy does NOT want to do this). TL;DR Does anyone know of an enhanced warehouse transfer solution???

Any real answer needs an in transit warehouse. Add a UDF to the transfer screen for ""final destination warehouse"" Add a script to print a Crystal BOL and create another transfer batch from the transit warehouse to the final warehouse, and leave that batch open until the items get there. Of course I am assuming there are not bugs or ""oops, we forgot to let you access that from BOI"" to get in the way of this.

I think ACS's Multibin can include this sort of paperwork.

ACS has a nice transfer program with good features including in transit warehouses, auto generate PO (for the receiving whse) and reports so that you can see what needs to transfer, what's in transit, etc.

Timely. I just had a user ask about this.

Thanks. Will have to contact them since their website is not the easiest to navigate.

ACSG is definitely the solution.

This gets murkier when the user has existing third party enhancements.

It must be a fragment of a memory but I recall that Master Developer mods, when the new framework was released, were to get along more seamlessly. Yet it seems that if you have mods from more than one developer you can run into more issues than less now.

I understand from ACSG that there is a ""rule"" that their custom code resides outside the standard Sage code. ACSG follows this, but apparently there are others where this is not true. So it ends up being like the Pirate Code - ""more what you call guidelines, than actual rules . . .