Upgrade Changes Vendor.VendorNum

Does anyone know how to keep the same vendor numbers through an upgrade? We’re going from E9 to E10.
It seems that the business objects want to assign a new vendor number even if we provide one using the DMT.

Does any Epicor employee familiar with the vendor business object know why we can’t keep our same vendor numbers? We have many outside systems and reports that rely on specific vendor numbers and changing them in the upgrade is going to be a pain point.

AFAIK in SQL you can specify a primary key even if the field is an identity. Seems that there isn’t really a good reason.

Some hopefully helpful, random thoughts.

Can you modify the vendor number in a post process after it’s been created?

What about adding a cross-ref field to link your vendor number to E10 vendor number in a worst case scenario?

Hopefully you have no gaps in numbers…
Sort the dmt list in (old) Vendor number order ??

I’m not sure you can modify the vendor number after it’s been created. Or if you can I’m not sure how.

Our DMT spreadsheet has the old vendor numbers we want to keep.
We’ve tested it and it doesn’t set the vendor number we provide, it assigns it a new one. It starts at 1 and increments for each record. And inside the database table, it looks like the Vendor.VendorNum is not an IDENTITY column.

Epicor designed the VendID (CustID for that matter) so they can be changed without losing all of the associated data. I believe that they use these in the External System stuff (like Intercompany Trading). In a pinch, you could pass the VendID to your integrations and assign it the previous E9 vendnum.

Mark W.

I would try to set the entire range and DMT them in sequence. Then run a second DMT to remove the unwanted vendor numbers.

There’s VendorID and VendorNum. Like the previous poster had mention, VendID can be changed. You will probably need to change the report to use VendorID. When we originally started Epicor, we were aware of company field however we never added the company links to our SQL JOINS. Few years later, we are multi-company and we had to change all our SQL stored procedures/queries with the company joins. it was painful but it was the correct method.

You can match your old VendorID to the new VendorNum too.

Do what Greg says. Create a simple DMT template containing the VendorID and Name only. Sort the data in this DMT template to be in VendorNum sequence. Any gaps that you have because records were previously deleted would need to be accounted for in terms of a dummy/placeholder record. Then, again like Greg says once you’ve got the vendors created with the VendorNum that you want you can run another DMT in Delete mode to remove the dummy vendors you just created.

2nd stage would be to DMT in the proper data, but this time use VendorID and not VendorNum.