Setup New plant In Epicor

Epicor ERP 10
1

I need to create a new plant and its been a while since I did so can you someone send me a check list on how to do it again so everything flows right? I search the archives and only saw four steps but I feel like there is more then that?

2
  1. create a new Site (plant), and configure it Define site-to-site rules
  2. create new warehouses for the site
  3. define a costID (if you want it to have a separate cost id)
  4. in user security, assign users to the site.
  5. go into Part Class & Product Group to define any Site specific parameters
  6. create new partplant records for the new site.
2 Likes
3

We are working through this now also.

Iā€™d add to this,

  1. If you need to share revisions across sites, youā€™ll need to make an Alt Method for every M part and all of its M components. And designate that alt as the ā€œPrimary Alternate Methodā€ in the Part>Sites>Planning tab of Part Entry.
  2. You may want to flex the ā€œDivisionā€ of your GL accounts via the GL Control tab in Site Maintenance (NOT the GL Control tabs in Site Config), and possibly in Warehouse Maintenance also.
  3. If you want MRP to make demand in the new site, for example, you may want to assign this new site as the ā€œSales Siteā€ in the Product Groups that sell from there. It saves people from manually assigning the site on the release.
1 Like
4

Consider if you really want a Plantā€¦ or if you want a New Company which can be considered just a Plant. That is my first checklist item. How flexible do I need to be. We make all our plants companies because how we handle finance and books.

2 Likes
5

great point re Site (plant) vs companyā€¦
Some organizations treat their individual sites as completely separate orgs, with separate AP Payments, AR Collections etc, even though they are the same company. If this is the case, then it might deserve a company.
If you do limited transactions between sites, and you share very little data, then a company can keep things cleanerā€¦
BUT if you share informationā€¦ same parts, same customers, same suppliers, etc, and if you are part of the same tax id, then one company with multiple sites is the answer.

1 Like
6

In all cases I would still add an additional site so I can delete the original site called MfgSys. I really wish the new company creation dialog in the admin console would give the option to define the ID of the first site.

2 Likes
7

:notes: If I could turn back timeā€¦ :notes:

1 Like
8

hahaā€¦ ā€œthat goes without sayingā€ā€¦ but you did say itā€¦ My opinion is that MfgSys should NEVER be used. I personally wish that when you create a new company that the system would ASK you what you want to site name to be, but it currently doesnā€™t do that (heyā€¦ this could be an Epicor Idea!).

For every project that I consulted on, one of my first steps was to create a new, properly named site, and delete MfgSys. (note, there is an urban legend that MfgSys is ā€œrequiredā€ā€¦ this is TOTALLY not trueā€¦ proven over and over again!).

1 Like
9

If this is a brand new implementation and you donā€™t have the multi-site module, how could you do this?

10

Is this a preference? Or is there a tangible benefit to doing this?

12

For a single company single site itā€™s not a problem. When you start adding sites like we did after the fact you end up with a MfgSys and an ET for the second site. This means on reports you have to drag the plant table in or create a calculated field to display the site code so that it makes sense to the user. Forever and ever amen.

Case when partplant.plant = ā€˜MfgSysā€™ then ā€˜WWā€™ else partplant.plant end
Every dang time

1 Like
13

So we are going through this right now and my two cents on the topic in addition to what the smart people already said

2A. (Under create new warehouses for the site) Create new bins for the warehouse, update the plant settings with the new warehouse/bins for receiving, RMA, Inspection, etc.

  1. Update the Resource Groups if Required
  2. Set up a new manifest warehouse (If you use Manifest/QuickShip)
  3. If you use configurators be aware they are tied to a revision which is tied to a plant a new revision or updating of the plant may require some maintenance
  4. We had a few BPMā€™s that did things based on the site, those needed to be updated.

I feel like there were/are more gotchaā€™s but I canā€™t think of anything right now. If I do Iā€™ll come back and edit the post.

-Max

14

If you get a chance test out the transfer warehouse function, in Site Configuration - Modules - Inventory - transfer resources. This can move an entire existing warehouse to the new site/plant, including costs and quantities.

15

Wellā€¦ yes, it is a preference for sureā€¦ and it really only matters when you have more than one site. Imagine you have 4 sites with their site ID and Name:

  • LAX = Los Angeles
  • SFX = San Fransisco
  • MKE = Milwaukee
  • MFGSYS = Dallas

The Site ID is what shows on a bunch of reportsā€¦ it is what you use when moving parts, it shows everywhere.
So when moving inventory from Los Angeles to Dallas, you would see a transaction that goes from LAX to MFGSYSā€¦ just confusing.

1 Like
16

@timshuwy Can you provide me with the steps to properly delete that MfgSys site after creating the proper one. What EpiCare provided me isnā€™t working.

Iā€™m creating the company in the admin console.
Log in using the admin user and creating the new plant.

Now I cannot delete the plant from Site Maintenance if I remove it from the admin user first, as it doesnā€™t display to select, nor can I delete it if itā€™s accessible my the admin user

So, I have to open up the Site Maintenance screen, then bring up the User Account Maintenance and remove the MfgSys plant from access, then switch back and delete the MfgSys plant, which seems to work on the surface. But when I log out and log back in, the MfgSys plant is still available, and if I move it over to being accessible, it reappears in Site Maintenance.

So how do I actually get rid of this thing???

Weā€™re currently on Version 2023.1.13

17

My instructions that I created and tested many years ago include the following stepsā€¦ NOTE that I have not done this for a while, so hopefully nothing has changed.

  1. Create new company
  2. log into new company
  3. using Product Calendar Maintenance, create your new calendar
  4. using Site Maintenance, create your new site. Assign the new calendar to the new site.
  5. change your current site to the new site. This puts you into the new site, and you are no longer logged into MFGSYS.
  6. In Company Configuration, change the default site to the new site instead of MFGSYS
  7. NOW, go into Site Maintenance, and delete Mfgsys

Note that ALL this must be done before anything else is doneā€¦ if you do add a part, then the site is ā€œusedā€ and you will no longer be able to delete it.

1 Like
18

Thanks @timshuwy The saving the company config was fun working through the errorsā€¦ but finally got it and it worked.

1 Like