You can transfer major master tables from DBA Classic to DBA Manufacturing. This data transfer is accomplished by exporting master tables into Excel spreadsheets, then editing the spreadsheets as needed, then importing the data into DBA Manufacturing.
In this chapter we show you how to use the DBATRAN data export utility to create a set of Excel spreadsheets that you will use for various tasks during the “setup” phase of implementation.
Why spreadsheets transfer instead of direct import?
Master tables are exported into spreadsheets instead of being imported directly into Next-Gen. This is because most of the tables require some editing before they can be imported to make them compatible with the requirements of the corresponding tables in DBA Manufacturing. Spreadsheets are optimized for editing large sets of data and are the ideal medium for data transfer purposes.
Classic System Requirements
In order to run DBATRAN, your DBA Classic system must meet these requirements.
•You must be on DBA Clas0sic version 2001.1 or higher.
•Your database engine must be Pervasive 2000i or later. Version 2000i must be SP4 with the Pervasive 2000i “Hot Fix” applied.
You can determine which version of Pervasive you have by launching DBA and noting the version listed on the Pervasive banner screen that is briefly displayed when the database engine starts up.
On the following website page you will find download links to to the Pervasive 2000i SP4 update and the Pervasive 2000i “Hot Fix”.
NOTE: Pervasive.SQL 2000i SP4 updates your Pervasive.SQL 2000i SP3 database engine. If you do not have SP3 installed, running this program has no effect on your installation.
Incompatible Versions
DBATRAN is not compatible with versions earlier than 2000i or Pervasive 9.5 and higher.
If you cannot get DBATRAN to run
If you cannot get DBATRAN to run, you can create your data transfer manually. See the next chapter, Exporting from DBA Classic, for details.
Installing DBATRAN
1. Download DBA2NG.EXE from our website
The first strep is to download an installation file named DBA2NG.EXE. A link to this file is provided on the DBA Classic FAQs page on our website. Links to this web page can be found on the Pricing page and Contact page.
Download DBA2NG.EXE into a temporary folder on the same machine where your DBA Classic data resides.
2. Run DBA2NG.EXE
Double click on DBA2NG.EXE, which extracts DBATRANEXE as well as several accompanying DLL files. Leave all these files in the temporary folder.
3. Prepare DBA Classic for conversion
Do the following before you run DBATRAN.
•Have all other users exit DBA Classic.
•Run DBA Classic and change to the company from which you will be exporting data.
•Go to UT-A and run ODBDDF. This program creates a full set of DDF files that are needed for data export.
4. Run DBATRAN
Browse to your temporary folder and double click on DBATRAN.EXE, which launches the Pervasive database engine and then the main screen, which contains these settings:
1. Select DBA Classic Location
Browse to the location of your main DBAMFG folder.
2. Select DBA Classic Company
Use the lookup to select the DBA Classic company from which you wish to export data.
3. Set Output File Location
Browse to the folder where you want your export spreadsheets to be created.
4. Connect to DBA Classic Data
Click the Connect button to connect to the DBA Classic database.
5. Begin the Export
Click the Export button to begin the export.
If you are on Pervasive 2000i and cannot get DBATRAN to run:
If you are on Pervasive 2000i and you cannot get DBATRAN to run, you must apply two service pack updates, as follows:
•First, you must update to Pervasive 2000i SP4 (service pack 4). You can download SP4 from the DBA Classic FAQs page on our website.
•After you install SP4, you must install the Pervasive.”Hot Fix” (HF_SRDE.exe). This file is also found on the DBA Classic FAQs page on our website.
Spreadsheet Listing
DBATRAN creates the following 12 Excel spreadsheets in the CSV file format.
ClassicCustomer.csv
ClassicCustomerContacts.csv
ClassicSupplier.csv
ClassicSupplierContacts.csv
ClassicInventory.csv
ClassicInventoryExclusions.csv
ClassicBasePrices.csv
ClassicItemSources.csv
ClassicBOMs.csv
ClassicBOMExclusions.csv
ClassicRoutings.csv
ClassicRoutingExclusions.csv
Data Import Considerations
Here are some points to consider when importing the following tables:
Item Sources
File: ClassicItemSources.csv
In DBA Classic there was no association between Suppliers and Manufacturers, whereas in DBA Manufacturing, Manufacturers and Mfgr Part Nos are assigned to Suppliers.
This spreadsheet has separate lines for Suppliers and Manufacturers. You must blend this information into single lines by adding the Manufacturer and Mfgr Part No into each Supplier line and then deleting the Manufacturer line.
Descriptors
File: ClassicInventoryExclusions.csv
In DBA Manufacturing, non-stock items were referred to as “Descriptors” and are stored in a separate table from Stock Items. Descriptors cannot be imported and must be entered manually.
Your non-stock items were excluded from the ClassicInventory.csv spreadsheet used for Stock Items import. All your non-stock items are listed on this spreadsheet (ClassicInventoryExclusions.csv), which you can use as guide for manual data entry.
BOM Routings
File: ClassicRoutingExclusions.csv
In DBA Classic you could assign a routing to a non-stock parent item, which is not possible in DBA Manufacturing. Any such routings were excluded from the ClassicRoutings.csv spreadsheet used for BOM Routings import. This spreadsheet (ClasicRoutingExclusions.csv) lists these excluded routings for your reference.
Manual entry recommended
Routings drive shop control and subcontracting, so it is vitally important that they are set up properly and conform to subassembly product structures. Instead of importing your routings, consider setting up work centers, subcontractors, routing processes, and tasks from scratch to achieve proper setup and take full advantage of the settings and capabilities available in DBA Manufacturing routings. Click this link for an overview:
BOM Components
File: ClassicBOMExclusions.csv
In DBAClassic, BOM labor could be defined with non-stock labor items instead of using Routings. In DBA Manufacturing we are standardizing on the use of Routings for labor definition. All non-stock items were excluded from the ClassicBOMs.csv used for BOM Components import. This spreadsheet (ClassicBOMExclusions.csv) lists these non-stock components and can be used as a guide for manually entering Routings.
Additionally, in DBA Classic you could assign BOM Components to a non-stock parent item, which is not possible in DBA Manufacturing. All components for such BOMs are listed on this spreadsheet for your reference.
