IMPORTING VENDOR/CUSTOMER FILES -- Bring everyone over?

system · October 28, 2013, 2:21pm

If you have to bring in ALL the Vendor/Customer Files, have the Sales Reps and Customer service clean up the spreadsheet of names, addresses, phones, contacts, etc. BEFORE they get imported. We broke ours out by territory onto separate files and distributed. Had everything back in a few days, more accurate than when it left.

To go along with the check, you should have a layout of Capitalization, punctuation, and format for all columns so everyone’s data looks the same after loading.

Regards,

Chris Wineinger

ERP Specialist

Interior Systems, Inc.

241 N Broadway Ste 600

Milwaukee, WI 53202

Office # 414.224.0957 X2051

Direct# 414.847.0701

Cell # 414.840.6594

IT related problem? Contact helpdesk@...

system · October 17, 2013, 3:08pm

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber

Vamco International, Inc.

555 Epsilon Drive

Pittsburgh, PA 15238

(412) 963-7100 x 203

(412) 963-9511

www.vamcointernational.com

*****

This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 17, 2013, 3:20pm

I agree with you….

I had an employer who insisted as well, until I told him that some of our vendors went out of business and that it made no sense to bring everyone over.

He agreed eventually…

Manasa

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Dina Hieber
Sent: Thursday, October 17, 2013 2:09 PM
To: vantage@yahoogroups.com
Subject: [Vantage] IMPORTING VENDOR/CUSTOMER FILES -- Bring everyone over??

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber

Vamco International, Inc.

555 Epsilon Drive

Pittsburgh, PA 15238

(412) 963-7100 x 203

(412) 963-9511

www.vamcointernational.com

*****

This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 17, 2013, 3:36pm

In both implementations that I have been involved with, we have brought over
only the "current" vendors (ones we have purchased from in the last year or
two). This is pretty typical for most companies. At both companies, at
least one person cleansed the list of suppliers that were imported to Epicor
making sure that standards were followed (upper/lower case, phone numbers
with dashes, etc).

Bethany Rye
Epicor Business Analyst

<http://www.teampti.com/>

[Non-text portions of this message have been removed]

system · October 17, 2013, 3:45pm

I also agree with you. We decided against bringing all of our vendors/customers/parts over because they did not contribute anything to the quality of the database. One of the major opportunities presented during an upgrade like yours is to clean out the garbage. we have probably had fewer than 10 instances over the last 6 years where we needed to go back. I wouldn't do it.

---In vantage@yahoogroups.com, <vantage@yahoogroups.com> wrote:

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber
Vamco International, Inc.
555 Epsilon Drive
Pittsburgh, PA 15238

(412) 963-7100 x 203
(412) 963-9511

www.vamcointernational.com

*****
This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 17, 2013, 5:02pm

I agree, we only imported any vendors we did business with over the last three years and customers that we did business with over the last two years. For vendors, there were not that many that had to be keyed in manually, and for customers there were about 100, but we used it as a training exercise. It only amounted to a couple of records per user, but we were able to not bring in thousands of garbage records that had accumulated over the last 25 years spanning two different systems previous systems were they kept bringing over all possible records. You are just better off starting with clean and necessary records than bringing over a lot of unnecessary junk to make your database files larger.

Regards,

Sigfredo.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of chuck.degreeff@...
Sent: Thursday, October 17, 2013 3:45 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: IMPORTING VENDOR/CUSTOMER FILES -- Bring everyone over??

I also agree with you. We decided against bringing all of our vendors/customers/parts over because they did not contribute anything to the quality of the database. One of the major opportunities presented during an upgrade like yours is to clean out the garbage. we have probably had fewer than 10 instances over the last 6 years where we needed to go back. I wouldn't do it.

---In vantage@yahoogroups.com, <vantage@yahoogroups.com> wrote:

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber

Vamco International, Inc.

555 Epsilon Drive

Pittsburgh, PA 15238

(412) 963-7100 x 203

(412) 963-9511

www.vamcointernational.com

*****

This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 18, 2013, 9:39am

Explain to the owner that there are not just storage space costs to dead weight data but that it can multiply the time reports take to run (depending on indexes and linking) as transaction data accumulates. Smart decisions now about having a trim and clean database will pay off years down the road.

-Todd C.

(Hanging on by the fingertips and actively seeking employment elsewhere. Vantage/Epicor preferred.)

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Dina Hieber
Sent: Thursday, October 17, 2013 2:09 PM
To: vantage@yahoogroups.com
Subject: [Vantage] IMPORTING VENDOR/CUSTOMER FILES -- Bring everyone over??

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber

Vamco International, Inc.

555 Epsilon Drive

Pittsburgh, PA 15238

(412) 963-7100 x 203

(412) 963-9511

www.vamcointernational.com

*****

This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 18, 2013, 9:59am

system · October 25, 2013, 5:30pm

Has anyone successfully programmatically restored a SQL backup into Pilot or Test database? We backup our SQL database every two hours and would like to restore the last backup, which is at 6:00PM, into Pilot or Test database every night. To do this every night manually is almost impossible.

Mike Tonoyan / Natel EMS

mtonoyan@...

_________________________________________________________________________________ Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements. _________________________________________________________________________________

system · October 25, 2013, 8:22pm

Mike, I used this in 8.03.4xx

It’s not doing completely what you ask, but it’s 90%. Should get you a good start. This restored my dumped live database to TEST. All the “MOVE” stuff in the beginning is for full text indexing/catalogs if you have that enabled.

It updates the restored database to use the correct ports in sysagent. It also kills all system tasks that you would normally have running in LIVE. (you don’t want TEST doubly running any scheduled tasks (at least I didn’t).

You would need to update the paths and the dumped/backed-up database name, too. If you need help tweaking, email me directly.

Good luck. HTH

--

-- PROCEDURE TO UPDATE TEST DB

--

-- *** MAKE SURE TO CHANGE "FROM DISK" LOCATION EACH MONTH ***

RESTORE DATABASE [MfgTEST803]

FROM DISK = N'D:\SQLBackup\LIVE\mfgsys803_2011Jul17_.bak' -- **** CHANGE **** --

WITH FILE = 1,

MOVE N'mfgsys803' TO N'D:\SQLData\mfgtest803.mdf',

MOVE N'mfgsys803_log' TO N'D:\SQLLogs\Mfgtest803_log.LDF',

MOVE N'sysft_custxprt' TO N'd:\fulltextcatalogs\test\custxprt\custxprt',

MOVE N'sysft_fscalldt' TO N'd:\fulltextcatalogs\test\fscalldt\fscalldt',

MOVE N'sysft_fscontdt' TO N'd:\fulltextcatalogs\test\fscontdt\fscontdt',

MOVE N'sysft_glacct' TO N'd:\fulltextcatalogs\test\glacct\glacct',

MOVE N'sysft_glchart' TO N'd:\fulltextcatalogs\test\glchart\glchart',

MOVE N'sysft_invchead' TO N'd:\fulltextcatalogs\test\invchead\invchead',

MOVE N'sysft_jobasmbl' TO N'd:\fulltextcatalogs\test\jobasmbl\jobasmbl',

MOVE N'sysft_jobhead' TO N'd:\fulltextcatalogs\test\jobhead\jobhead',

MOVE N'sysft_langorg' TO N'd:\fulltextcatalogs\test\langorg\langorg',

MOVE N'sysft_langtran' TO N'd:\fulltextcatalogs\test\langtran\langtran',

MOVE N'sysft_orderdtl' TO N'd:\fulltextcatalogs\test\orderdtl\orderdtl',

MOVE N'sysft_orderhed' TO N'd:\fulltextcatalogs\test\orderhed\orderhed',

MOVE N'sysft_part' TO N'd:\fulltextcatalogs\test\part\part',

MOVE N'sysft_podetail' TO N'd:\fulltextcatalogs\test\podetail\podetail',

MOVE N'sysft_quotedtl' TO N'd:\fulltextcatalogs\test\quotedtl\quotedtl',

MOVE N'sysft_reqdetail' TO N'd:\fulltextcatalogs\test\reqdetail\reqdetail',

MOVE N'sysft_rfqitem' TO N'd:\fulltextcatalogs\test\rfqitem\rfqitem',

MOVE N'sysft_rcvdtl' TO N'd:\fulltextcatalogs\test\rcvdtl\rcvdtl',

MOVE N'sysft_shipdtl' TO N'd:\fulltextcatalogs\test\shipdtl\shipdtl',

MOVE N'sysft_ECORev' TO N'd:\fulltextcatalogs\test\ECORev\ECORev',

MOVE N'sysft_FAsset' TO N'd:\fulltextcatalogs\test\FAsset\FAsset',

MOVE N'sysft_CostPart' TO N'd:\fulltextcatalogs\test\CostPart\CostPart',

MOVE N'sysft_HDCase' TO N'd:\fulltextcatalogs\test\HDCase\HDCase',

MOVE N'sysft_ResourceCollection' TO N'd:\fulltextcatalogs\test\ResourceCollection\ResourceCollection',

MOVE N'sysft_WCGroup' TO N'd:\fulltextcatalogs\test\WCGroup\WCGroup',

MOVE N'sysft_xfileref' TO N'd:\fulltextcatalogs\test\xfileref\xfileref',

NOUNLOAD, REPLACE, STATS = 10

GO

USE MFGtest803;

UPDATE COMPANY SET NAME = '#-> TEST DATABASE ONLY <-#' WHERE COMPANY = 'MYCOMPANY' ; --UPDATE NAME HERE!!

UPDATE SYSAGENT

SET APPSERVERURL = 'AppServerDC://localhost:8323',

MFGSYSAPPSERVERURL = 'AppServerDC://localhost:8321'

WHERE AGENTID = 'SystemTaskAgent';

TRUNCATE TABLE sysagentsched;

TRUNCATE TABLE sysagenttask;

TRUNCATE TABLE sysagenttaskparam;

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Mike Tonoyan
Sent: Friday, October 25, 2013 5:31 PM
To: vantage@yahoogroups.com
Subject: [Vantage] SQL database restore to Pilot or Test

Has anyone successfully programmatically restored a SQL backup into Pilot or Test database? We backup our SQL database every two hours and would like to restore the last backup, which is at 6:00PM, into Pilot or Test database every night. To do this every night manually is almost impossible.

Mike Tonoyan / Natel EMS

mtonoyan@...

_________________________________________________________________________________ Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements. _________________________________________________________________________________

system · October 26, 2013, 3:40pm

>>Any older vendor, do not import to the new system.

>> If we see there was a vendor we did not import, we can easily add them at that time.

Sounds about right to me.

Will be cleaner and I think it is easy to manually add Vendor records if needed.

>>The owner of the company thinks we should import all vendors.

I know people hate to lose anything but... how many useful records could you really be leaving out?

I

---In vantage@yahoogroups.com, <dhieber@...> wrote:

We are getting ready to import Vendors in to 9.xx. I currently have the vendors in an excel spreadsheet. My recommendation was only import vendors which we have purchased from since 2011. Any older vendor, do not import to the new system. If we see there was a vendor we did not import, we can easily add them at that time. But I thought that would give us a good foundation.

We are not bringing over history, we plan on having 5.2 where I can still see the information and access it.

The owner of the company thinks we should import all vendors.

Any thoughts? What did others do?

Best Regards,

Dina M. Hieber
Vamco International, Inc.
555 Epsilon Drive
Pittsburgh, PA 15238

(412) 963-7100 x 203
(412) 963-9511

www.vamcointernational.com

*****
This e-mail message and any files transmitted with it are confidential and are intended for the sole use of the intended receipient(s). Any unauthorized use or disclosure is prohibited. Any opinions express in the email are those of the individual and not necessarily the company. If you are not the intended recipient, please contact the send by reply email and destroy all copies of the original message.

system · October 28, 2013, 11:15am

Vic,

Thank you for sharing the script! This will be a place to start from. I’ll contact you if I hit a snag.

No we don’t want to run MRP in Production and Test environment simultaneously, it will drain the server recourses.

Mike Tonoyan / Natel EMS

mtonoyan@...

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Vic Drecchio
Sent: Friday, October 25, 2013 5:22 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL database restore to Pilot or Test