We are single company multi-site. I’ve noticed that several of our sites do not have a PlantCostID specified. We only have the single cost ID anyway. I can’t see any issue that it’s causing. However, I read its good practice to join to PartCost using the CostID based on the Plant.PlantCostID in the event that we ever do split our costs between sites that it will all work smoothly. So do I add the CostID? Or just leave well enough alone and continue to join to PartCost and just filter to CostID = 1.
1 Like
Costing-wise, Epicor will work just fine with a blank Cost ID on some plants. However, I do think Epicor will allow you to select different costing methods for the same part in plants where the Cost ID is different. So if site MfgSys has a blank Cost ID and Site 2 has a Cost ID of “1” then you could in theory have one part set to standard in one site and average in the other. If both sites had the same cost ID filled in, Epicor would not allow different costing methods for each site for that part.
Our original company’s MfgSys site never had the cost ID filled in and we do use different costing IDs for different sites in that company, so all of our BAQs have extra conditions on joins to PartCost to default in the “1” value if it’s blank. We’ve tried in Pilot to assign the ID but we’ve run into the mismatching cost methods before and just haven’t dedicated time to work through it all and get everything set correctly since it’s an easy enough fix on reporting and everything in the system seems to work correctly.
2 Likes
Thanks for sharing your experience. We are going to start using multiple cost site IDs and many reports were made without the consideration that we’d ever do this so now trying to go back through and prepare for this condition where we only want the one cost site ID.
1 Like
That’s basically my fear. Nothing is “broken” today and I worry that if I open Pandora’s box I end up breaking something haha.
1 Like
We did it here and it clobbered some FIFO layers, but beyond that no issues at all.
2 Likes
What does that mean?
The PartFIFOCost table uses CostID, and I think some were blank before we had to assign the CostID to the current site and set up the new site. As a result, some of the FIFO layers were set to “InActive” and we had to get a fix to re-activate them. Testing FTW!