VI Contracting for Sage ERP 1000 v3 & v4 Getting Started

Transcription

1 VI Contracting for Sage ERP 1000 v3 & v4 Getting Started Contracting for Sage ERP 1000 Getting Started Page : 1

2 Contents PREFACE... 3 PRE-INSTALLATION... 4 INSTALL VIA COMMAND LINE Set Sage Environment a Installing from CD b Installing from zip file Install Forms... 5 POST-INSTALLATION Add Menu Option Create Contracting Tables Licensing Menu Options Payroll Timesheets Posting from other modules... 7 DATA MIGRATION... 7 Contracting for Sage ERP 1000 Getting Started Page : 2

3 Preface This manual describes the process for installing version of the VI Contracting suite of modules for Sage ERP 1000 versions 3 and 4. The same process is used for both new installations and upgrades on existing systems. The software is installed via the Windows Command Line and Windows Explorer. The following components are installed for the selected modules: binaries messages options menus system key information system keys data dictionaries forms The following documents may also be accessed from the media: this guide Contracting user manuals Contracting project documentation These documents are held in PDF format and require Acrobat reader to view them. Contracting for Sage ERP 1000 Getting Started Page : 3

4 Pre-Installation On some platforms problems have been encountered when upgrading an existing installation of the software due to the permissions of existing folders and files. You should check that the c?load folders and their contents and the binaries in the bin/production folder on the Sage server are not Read Only. PLEASE NOTE: when migrating to a new version of Sage or to a new server, when unloading the data from the source system you should use the unloadall n command so that the column names are not written to the top of the load files. This is because some of the tables include column names that are reserved words in SQL. Running unloadall without the n option results in the data in these columns not being populated when loadall is used on the target system. Install via command line 3.1 Set Sage Environment From the Windows Command Line set the Sage environment by moving to the Sage home directory and typing the name of the bat file that sets the environment, e.g: csmaster 3.2a Installing from CD Change directory to the CD drive. For each module that you wish to install type: installxx where xx is the module prefix. Note that where multiple modules are being installed via this method, Contract Costing should be installed last. 3.2b Installing from zip file Extract the contents of the zip file into a temporary folder. Note that the temporary folder name should not include any spaces since this causes problems with the Sage load programs which are used in the installation process (a common problem is to install the software into a folder called VI Software ). Change directory to the temporary folder created above. For each module that you wish to install type: installxx where xx is the module prefix. Contracting for Sage ERP 1000 Getting Started Page : 4

5 Note that where multiple modules are being installed via this method, Contract Costing should be installed last. 4.3 Install Forms Via Windows Explorer copy the forms from the sage1000forms folder below each module folder to your forms directory within Sage. Having done this you must change the Read Only status of the forms folder and all its subfolders so that they are not Read Only. Post-Installation 5. Add Menu Option The menu contracting and all its options are automatically added into the Sage database by the installation routine. To allow you to access the Contracting module you must add this menu option to the required Sage menu via the Menus program in the System Manager, Configure User Interface menu. 6. Create Contracting Tables The database dictionaries are automatically installed as part of the Application installation routine. However this does not create the database tables in the relevant companies and you must therefore create these tables via the Create Module Tables option in each Create/Amend Master files menu before you can use the Contracting modules. You should do this in each company in which you wish to use the Contracting module for each of the required modules. Note that these menu options do not require the Contracting modules to be licensed for use. This program will create new tables. System key information and system key default values will also be loaded. The program will prompt for the directory in which the load files are held. This should be the same directory into which the Load Files were loaded via the installation process. A default value will be displayed and it will only be necessary to change this value if the load files have been moved. Press ESC if you wish to abort the process otherwise press CR. After CR has been pressed the program will list each table being created. If the table already exists, for example if you are installing a new version of Contracting over an existing version, then the program will inform you of this. Any data in these tables will remain intact. A pop-up message will inform you when the process is complete. Contracting for Sage ERP 1000 Getting Started Page : 5

6 7. Licensing You will be issued with a separate password for each company which will license the Contracting modules for use. To activate the license you must make entries in system keys as follows: VIPASSMODS VIPASSWORD the modules to be licensed entered in a string of lower case characters, e.g.: cfcicscocqv3 the password issued which will be in the format XXX-XXX-XXX-XXX and must be entered in upper case characters. Note that the version of Contracting for Sage ERP 1000 v3 requires an additional module of v3 to be licensed and included in the list of modules in system key VIPASSMODS. Error messages will be displayed when you access any of the Contracting options (apart from the Create Contracting Tables option) if the system keys do not exist or do not contain valid entries or if the license has expired or is for a different company name or number of users than that held on the Sage license. A warning message will be displayed when the license for the Contracting module is within 7 days of expiring. 8. Menu Options 8.1 Payroll Timesheets Within Sage 1000 the order that forms are displayed in the applications is now controlled by the menu option name. In previous versions of our Contracting modules it was necessary to create separate menu options which were specific to the payrolls in use at the user s site. This applied to the Timesheet Entry and Posting options and the modified Payroll G/L Distribution Report and required menu options to be set up (where the payroll number was entered after the program commands). To avoid implementers having to configure the options for each payroll we have added new options to the standard menus for five payrolls. The menu options are linked to the relevant payrolls via a new series of system keys COTSPAYnn, where nn is the number 01 to 05 entered against the menu option. The value of these system keys should be the payroll number to be linked to the menu option. e.g. on a system where the user has payrolls MM, WW and HH, system keys may be set up as follows: COTSPAY01 COTSPAY02 COTSPAY03 MM WW HH Contracting for Sage ERP 1000 Getting Started Page : 6

7 8.2 Posting from other modules We have added a menu to the Contract Costing Housekeeping menu called Sage Integration with Contracts. This menu contains all the Sage programs which have been modified to integrate with contracts, split between sub-menus for each module. Data Migration If migrating data from Sage Line 500 or earlier versions of Sage 1000 using the unload or unloadall commands you should use the n option so that column names are not written to the load files. This prevents data loading issues on the target server which would arise without the n option due to a number of tables containing SQL reserved words. Contracting for Sage ERP 1000 Getting Started Page : 7