We are preparing our warehouse and processes to support locations. Currently we have only one (default) location, which is default for all receipt and issue locations in all warehouses, BOM, etc etc. We also use multiple warehouses, but because they’re all used for inventory, I want to combine them to one, beacuse I don’t see any advantages for having four.
In this one warehouse we want to use locations to specify where the worker has to put or pick the item.
Because a location can change over time (because there’s not sufficient space, or it’s easier to place an item near you) I am struggling with the default issue locations.
Nowadays, with the one location we use, the process is as follows:
- Creation of SO (SO screen)
- Confirm the SO (SO screen)
- Batch create the picking list for all open orders (Accounts receivable > Periodic > Sales update > Picking list)
- Pick the order
- Register each picking list line/whole picking list (Inventory management > Periodic > Picking list registration)
- Post the packing slip (SO screen)
This works well because there’s only one possible location. In the future, the item can be stocked at any location. So we need to have the picking location dynamically determined.
I have seen two options: Release Sales Order picking and Shipments.
The Release Orders screen determines the location dynamically, in alphabetical order, but only if the default issue location is removed. This could be a problem: I have to change the settings for all items and I don’t know what happens with items that are used in a BOM.
The second option is by using output orders, shipment templates and shipments. By using templates I can specify in which order the locations have to appear: instead of alphabetically I can use sort orders, which is very nice.
I have some questions about this:
-
It seems to me that ‘shipments’ is the only way to keep the default issue location on the item AND dynamically assign locations at pick time, right?
-
It seems to me that shipments are mainly used for pallet transports. That would be overkill: 98% of our pick actions are item level picks off the rack or even from the inbound dock (straight out of production) to the packing location. At the packing location each order gets its own pallet with address label on it (we deliver to the end customer). So I use the shipment function only for the dynamic location, not to prepare pallets for end customers.
-
If we need to use shipments for the location assignments, the new process would be:
- Create SO
- Confirm SO
- Batch create picking list OR use the release orders screen to generate picking list/output order
- Use shipments screen activate picking
- Pick and register in picking list registration screen
- Post packing slip
Is this correct?
I hope to see some opinions about my thinking process