We are 2 months from Go-Live and setting up in a multi-site environment. Our 2 sites are only 30 minutes apart from each other.
We will be manufacturing certain models in Site 1, but that site does not have a testing facility. Only Site 2 has a test lab. So once models are fully assembled in Site 1, we will need to ship them to Site 2 for testing.
Ideally, we would like to handle it with one job, that could move between sites. But I haven’t been able to figure out a way to handle that. Or do we have to close out the job in Site 1 and then open a new job in Site 2 to finish the order. Either way, it would need to stay linked to the original sales order.
Does anyone have suggestions for how they may have handled something similar?
We have a similar process where we manufacture parts in site A for a Sales Order that is shipping from site B.
This does require 2 jobs. It’s called Job to Job by Epicor.
Job A in site A has a demand link to the Job B in site B.
The Job B has a demand link to the Order Line.
We are on E10, having developed workflow for jobs / multiple sites back in E9. I’m saying this in case there is a better way to handle this than we’ve done to date, originating in E9. It is my understanding that across-site jobs cannot be done, at least not in E9 ever. If anyone has better plan then below, Please share (I’ve wondered about the make to job functionality, not sure if better than below).
We sometimes have similar situation to you, with job done in site A, part sent to site B for testing then shipment. Site A does the Mfg and Site B is the sales order release plant with make direct job to do the testing.
We use a part number with originating site tacked onto the end, eg. EngineeredPart12345-TX and then sell/ship EngineeredPart12345 from secondary testing site to fulfill order. We use transfer order to move the EngineeredPart12345-TX to second site, with the part setup as manufacture in SiteA (TX) and transfer in SiteB. Job in SiteA for the Mfr makes to inventory and then Job in SiteB for the testing, makes the EngineeredPart12345 to order with the EngineeredPart12345-TX called for in its BOM.
If serial numbers are required, as they usually are for us, then that’s another bit of complexity to add.
We only manufacture in one site (A), but often have to ship manufactured parts to another site (B, C, or D), that it will join up with parts at the second site, for final delivery. There’s nothing done to the original mfg’d part at the second site - it just needs to ship from there. The Mfg’d parts is almost always custom and made to order.
The way E10 works, we can’t transfer the completed part from site A’s WIP to site B’s WIP, for a final MFG-CUS type shipment. We are forced receive the mfg’d part into A’s inventory, do a Transfer Order to B’s inventory. Then ship from B’s inventory.
You may have to do something similar. Make a sub assy (that you’ll stock) for the part, without the testing. Receive it into stock, do a TO, then make a job in the second plant that uses the stocked sub-assy, as the material, and just add the testing.
Does the tested item need to go back to the original site? If so, maybe treating the testing as a sub-contract would work.