Moving from one ERP to Epicor - ID/EmpID/Resource, etc

Coming from our old ERP, built in house, each employee has an Employee ID, how can I get this ID to come over into Epicor to be the same across Contact and Employee Person ID Code?

I have copied the structure into Excel from both Employees and Contact, placed all of our employees in both excel documents, and inserted them, I get duplicates bringing them in (even though I have deleted all contacts and employees) and some fields that just won’t insert properly.

  1. Is there any way to correctly clear/delete all contacts and employees
    1a. Why is it that when you clear/delete them, they are not really gone?
  2. Is there a way to import them and have them use the Id/EmpID/Resource, etc I chose
  3. I want that number to match both in Contacts and Employees, can it be done?

I hate PerCon just for the record… :slight_smile:

2 Likes

haha, I guess you had the same issue?

We enabled Global PerCon there was a setting in Multi-Company to enable it. But I remember the whole linking was quite an effort. I have my templates somewhere.

ok, so I am not stupid,… (I mean not totally at least), I figured I was doing something 100% wrong

oh and, should I enable Global PerCon, because I don’t have that enabled?

Yes If I remember we Enabled that and then when we DMTd users we had a GlbPerConDMT.xlsx

hmmmm, ok cool, thank you

Also make sure you configure Global Table to pass/receive PerCon

yes, thank you

oh… “This company not licensed to be the parent of a Global PerCon.”

You need to have the Multi-Site Module. If you do, make sure its enabled in Admin Console.

The specific one that throws that error is called Multi Site Publish

I am just going one by 1 adding everyone, pissing me off, but I am doing it, Epicor is such a PITA sometimes.

In an upcoming transfer from E9 to E10 (with a brand-new fresh PerCon table), we’re looking at something like:

Create a list of Percon records starting with an ID of 1 and making the name "Unused " + the ID num. Numbers run to at least the highest PerCon ID in E9.

Then when we copy the E9 PerCon records, we DMT update the records onto the newly existing E10 PerCon records.

Then we query out anything with “Unused” in the name and DMT delete it.

That way the IDs stay the same from E9 to E10 and there’s no reason to have to map anything from old number to new number.

Caveat 1: You can’t start at 1 if you have previously had any records in PerCon – it just sets up the next highest number.

Caveat 2: We haven’t actually tried it yet.

We’ll see.

Joe

1 Like

Not sure if it is what you’re seeing with DMT, but some DMT “uploads” used to ignore key fields you supplied and create their own.

First example, When adding customers, You only supply the CustID. E10 will automatically make assign the customer number. So if your data from your old system looks like:

CustNum  CustName
1        Acme Industries
2        Rocket Enterprises
4        Jet Skates Inc.
5        Meep-Meep Ltd.

Notice that you had a Cutomer with CustNum = 3, but had deleted them (or decided not to bring them over).

So you decide to use the CustNum from your old company as the CustID in E10. So your DMT looks like:

CustNum  CustID  CustName
1        1        Acme Industries
2        2        Rocket Enterprises
4        4        Jet Skates Inc.
5        5        Meep-Meep Ltd.

What you end up with in E10 is:

CustNum  CustID  CustName
1        1        Acme Industries
2        2        Rocket Enterprises
3        4        Jet Skates Inc.
4        5        Meep-Meep Ltd.

See how the last two CustNum’s were changed…

To get it to match your current data, your DMT file would need to look like:

CustNum  CustID  CustName
1        1        Acme Industries
2        2        Rocket Enterprises
3        3        DELETE ME LATER!!!
4        4        Jet Skates Inc.
5        5        Meep-Meep Ltd.

Then afterwards, you’d go back and delete Customer “3”.

Adding OrderDtls would do the same. If my DMT data skipped a line, all the subsequent lines would be created with a OrderLine that does match my data. Then when you go to upload Release info, they’re totally mismatched.

sadly cancelling the request, since I have imported a few times already, the person/contact ID #'s stay behind, even if they have been deleted, so they continue to increase so I have to do everything 1 by 1, so annoying

sadly cancelling the request, since I have imported a few times already, the person/contact ID #'s stay behind, even if they have been deleted, so they continue to increase so I have to do everything 1 by 1, so annoying. Also, there are a few skips in the ID’s from our database, so I can’t do anything in increments, so horrible.

I’ve also stored the old PerCon ID in an unused field like “IM” in the export. Then after importing into the new environment I’ll dump PerCon with a BAQ and copy to a spreadsheet, where I’ll create a map of “old” to “new” PerCon IDs. Then use that make for a vlookup in excel to replace PerCon IDs in customers, employers, etc.

It’s a bit of work since PerCon touches so many places, but doable.

Joe