Are intra-plant Transfer Orders possible?

All,

We have warehouses affiliated with the same plant that are located such that the physical transfer of inventory between warehouses exceeds a day. This renders Inventory Transfer insufficient for these transactions as there is no status logging of the inventory in transit between the two warehouses. Is there a provision in Epicor to configure Transfer Order Entry to allow intra-plant transfers between warehouses? Thx.

1 Like

Seems like it’d be a different plant at that point.

No. For costing and functionality reasons, we have only one plant in each company and multiple warehouses in each. Is it possible?

As @utaylor said Epicor would expect you to have different sites set up for these locations. If that isn’t an option, I think the best you could do out of the box would be to utilize the Warehouse Replenishment settings on your parts and use the Replenishment Workbench and the Material Request Queue to facilitate movement between buildings.

image

Okay, thanks. Again, the current tools don’t work because they don’t recognize materials in transit between warehouses within a plant.

1 Like

If you are using your own trucks to transport stuff just make them BINs. :man_shrugging:

I was thinking along those lines as well… it would require two transfers… but I was thinking, create a Warehouse Bin called “TRANSFER” (or something of that ilk)… make it non-nettable, so anything in that bin is removed from on-hand status, ignored by MRP, etc. (while in-transit).

Then when they get to their destination, someone would then do a second transfer out of the TRANSFER bin and into whatever final bin destination you want.

The only thing here is that you don’t get a Transfer “Order” within the system. You’d have to find another way of communicating the demand between the two facilities.

1 Like

my typical advice for customers when I was a consultant was:
YOU NEED Multiple plants if any of the below is true:

  1. it takes time to move material from one place to another
  2. the two places have different costs (NOTE: multiple SITES does not force multiple costs. they can share a common cost table).
  3. purchasing/inventory is managed by different people based on site.

Note that it only takes ONE of the above to suggest you should have a second site.

In your case, you want to have the same cost, but two different sites, then you can create a second site, apply the same cost table, and all is good.

BUT WARNING… making things multiple sites does also cause another challenge. If you have JOBS that move mid-manufacturing cycle from one site to another, this is difficult. I have had some customers where this became the deciding factor, and they still went with one site/two warehouses, even though the two sites were a distance away. At that point, they “handled” the challenge of moving inventory differently.

2 Likes

Might need an idea created to handle the in-between @BBussey !

Great comments Tim!

Actually, this portion can be handled by the “Move Inventory Request” menu.

Create a move request by entering your part, select the From warehouse & bin and then the TO warehouse & bin.

That request then appears in the Material Request Queue.

You could use your TRANSFER bin here, so when the request is processed, they move to the TRANSFER bin (again, while in transit) and then when they hit their destination they’re transferred again into their final bin.

1 Like