Installing Fourth Shift Release 7.50 R2worthen.xdatasync.com/support/PrintDoc/InstallSQL.pdf · Fourth Shift Release 7.50 R2 Installing Fourth Shift 7 Module-Specific Directories

Installing Fourth ShiftRelease 7.50 R2

Fourth Shift Release Instructions2011, Release 7.50 R2© 2011 SoftBrands, Inc., an Infor affiliate All rights reserved

This documentation is copyrighted and all rights are reserved. This documentation may not, in whole or in part, be reproduced in any form.

SoftBrands, Inc. provides this publication “as is” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties or conditions of merchantability or fitness for a particular purpose. In no event shall SoftBrands, Inc. be liable for any loss of profits, loss of business, loss of use of data, interruption of business, or for direct, special, incidental, or consequential damages of any kind, even if SoftBrands, Inc. has been advised of the possibility of such damages arising from any defect or error in this publication.

Fourth Shift is a registered trademark of SoftBrands, Inc., an Infor affiliate.

Microsoft, SQL Server, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Installing Fourth Shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Initial Installation Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System Settings Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Application Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Multi-user Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Configuration Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SQL Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SQL Server Database Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Review Log Files and Complete Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Workstation Installation on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Interim Service Release Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Perform Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

System Post-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Workstation Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Workstation Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Environment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Workstation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Workstation Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Workstation Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Workstation Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Implementation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Implementation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Implementation Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Implementation Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Time-Saving Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Post-Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Implementation Checksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Phase 1: Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Phase 2: Global Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Phase 3: Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Phase 4: Initial Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Phase 5: Final Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Phase 6: SAAM Installation Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Implementing Net UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Implementing My Fourth Shift Workplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85SETUP Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Acceptable Log File Messages: SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91INSTALL.HIS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Fourth Shift Release 7.50 R2

Installing Fourth Shift

Before You InstallThe installation of your system can be completed easily by answering a series of questions presented by the installation wizard. The answers to these questions are critical to the success of your implementation because the settings are used in every aspect of your operations. The success of your installation depends on proper preparation and evaluation of the options available.

In addition, each network configuration has a unique set of preparation steps. This preparation is completed upfront to allow you to get started more quickly once you have completed the installation.

Review the information about the questions you will be asked during installation and complete the recommended configuration preparation for your system before you begin the actual installation.

About This ManualThis manual includes instructions on how to install your system along with startup considerations. The manual is divided into the sections based on installation tasks and the workstation operating systems you have selected. This graphic identifies the section number in boxes so that you can quickly determine which are needed to complete your installation.

It is recommended that you make a copy of this graphic and highlight the sections you will need to use. This allows you to use this graphic as a checksheet.

At the end of each section, you will find information about what to do next in the Next Step section to guide you through the process.

Before You Install1

3

2

4

5

6 Workstation Installation and Post-Installation section

7 Implementation Planning section

8 Implementation Checksheets section

Workstation Preparation section

Configuration Preparation section

System Installation sectionincluding database and module components

System Post-Installation section

Installing Fourth Shift 2


Additional information about updating an existing system or adding modules to your system is provided in the System Administration manual.

Installation OverviewThe installation process looks similar to the following.

Initial Installation PreparationThe installation program uses a wizard format to lead you through a series of questions about your system. The answers to these questions are then used to establish the overall selections for your system.

Since these overall selections are critical to your system operation and can be quite difficult to change later, this section is provided to help you determine the selections needed before beginning the installation.

Insert Module Access Key diskette

Run SETUP from the CD ROM.SETUP

Specify serial number and module access key

Select installation element: server

Select system settings for tax system, item costing method, systemmonetary precision and local bank currency code

Install database drivers based on your configuration

Choose destination drive

Verify module installation list and install module software

Review installation history file; complete post-installation tasks andpreparation for workstation installation

Complete workstation installation and post-installation tasksSETUP

Provide Module Access Key file



Installation MaterialsYour installation package includes several components. These components are used at different points in the installation process to provide the identification for your system and purchased components. These materials should be retained as a set for future reference. The installation materials require a CD-ROM drive.

These components include:

Installation TypesThe installation program supports several types of installations. This allows you to complete any type of installation from a single program. The installation types include:

Additional information about existing system installations is provided in the System Administration manual and the Release Instructions on the Fourth Shift CD.

Installation Component Description

Fourth Shift CD-ROMs Includes your Fourth Shift software and reference material available for your system

Fourth Shift Access Key CD Includes the unique access key, which identifies the modules you have purchased, and software to support your specific database configuration

Type Description

Initial installation Allows you to install the complete system into your environ-ment. This installation type ignores any existing installation in case you wish to install a test system for a new release.

Existing installation Allows you to update an existing system for a new release of the software, add modules to your system or change to a dif-ferent database platform when necessary.



Installation OptionsEach of the following options is required to complete your system installation.

The installation options include:

Installation Security RestrictionsWith its latest operating system releases, Microsoft has imposed security restrictions that will affect the way you install and run programs both on the server and the client workstations.

Where you previously double-clicked a setup file to run it, it may be necessary to install or run Fourth Shift programs by "running as administrator" for machines running Microsoft operating systems, including but not limited to:

• Windows Vista

• Windows 7

• Windows Server 2008

• Windows Server 2008 R2

To run an application as an administrator, right-click on the file and choose "Run as administrator."

This process is required even if the logged-in user has administrator rights to the computer.

In some cases, you may also see the message that asks if you want to allow the program to make changes to this computer.

Installation EnvironmentDomain RequirementsA domain and network resolution must be set up correctly for your network to run Fourth Shift. A workgroup environment is not supported.

Base DirectoryThe standard installation uses drive designator M:. During the server installation, a series of directories is created off of the drive designator that you will select during installation. Several files are also installed into this root directory. You may wish to create a permanent logical drive map to

Option Description

Server Installs the database, database server support, configuration files, print versions (PDF documents) of the online help, and supporting programs for overall system operation. This process also creates the standard directory structure used for the remainder of the installation. The server installation is completed from the CD-ROM.

Module Installs the application programs for each module. The module installation is com-pleted from the CD-ROM.

Workstation Installs programs, configuration files, online help, and icons on individual worksta-tions to allow access to the system. This process needs to be completed on each workstation which will access your system. The workstation installation is com-pleted from a directory created in the standard structure during server installation. At a minimum, this process needs to be completed to install the System Control module and the online help.



the FSHIFT directory as the root directory before you begin the installation. This allows the drive designator to appear as M: but actually use the FSHIFT directory for installing files.

See Assigning Logical Network Drive for more information on establishing a logical drive mapping.

Configuration and Settings FilesWhen you install your system, configuration and settings files are automatically created. The configuration file FS.CFG is created on the server, while the settings file FSMSS.INI is created on each workstation. These files identify the directories where your software and database components are located, server environment options, and operation selections.

The components included in these files vary based on the modules you install. The configuration and settings files include:

The default values in these files are set automatically for most options. When necessary, you may need to modify some values after you have completed the software installation. If you want to understand more about these files, see the "System Operation" section of the System Administration online manual.

Standard DirectoriesStandard directories are created automatically during the server installation. These directories include:

Filename Directory Description

FS.CFG MFGSYS Located on the server. Contains system-wide information such as the location of installed files and server options; this file is created during the server installation only

FSMSS.INI [WINDOWS] Located on each workstation. Contains workstation-specific settings such as the location where a program writes an audit trail file during pro-cessing; this file is created on each workstation during the workstation installation

Directory File Type

root utilities

CSTM files retained for historical purposes for pre-7.50C systems

FS_APPS programs, maintenance log file, and work files

FS_APPS\D supplemental database file

MFGSYS data files, reference files, work files, and batch logs

MFGSYS\CLIENT (includ-ing related subdirectories)

files needed for workstation installation processes

MFGSYS\CLIENT\ProgFile\Help

help files needed for workstation installation

MFGSYS\E supplemental programs and utilities

MFGSYS\FONTS font files used for generating bar coded reports

MFGSYS\FSReporting reporting services installation components

MFGSYS\FSSQLServer separate database server installation components



Module-Specific DirectoriesSome modules create additional directories during the server installation. These directories include:

User-Specific DirectoriesDuring normal operation, several programs create working files based on the features you are using. Each user needs a unique location for these files to be created and used. During installation, a default directory is created for this purpose.

The same location and directory is created on each workstation and the location is specified in the FS.CFG file.

If you install Net UI or My Fourth Shift Workplace, the user directory creation is slightly different.

MFGSYS\H\PrintDoc print versions of help files accessed on the server (PDF)

MFGSYS\H\Site optional custom site help files created by users accessed by the Custom Site Help button in the online help

MFGSYS\I data import files

MFGSYS\Reports report templates

MFGSYS\S screen and message files

MFGSYS\SQLMSS (including related subdirec-tories)

SQL Server installation tools and log files for the Fourth Shift database

MFGSYS\SYSTEM files used to execute an application such as *.DLL and *.EXE programs

XPORT extracted database files and indices

Directory Module Installed

EDIEXCEL (including related subdirecto-ries)

Electronic Data Interchange (EDIM)

EDIINTRN Electronic Data Interchange (EDIM)

MFGSYS\ENGM Engineering (ENGM)

MFGSYS\FSTM Fourth Shift Transactional Interface (FSTI)

MFGSYS\SAAM Sales Analysis (SAAM)

MFGSYS\SCREENS Screen Customizer (SCRM)

MFGSYS\WEB\NUIM Net UI (NUIM)

Directory FS.CFG Reference

C:\FSUSER UserDir=c:\fsuser

Directory File Type



• Net UI users have a user-specific directory created on the Net UI server. The Net UI User Id is used to create a subdirectory specific to each user. See the Net UI manual for more information.

• My Fourth Shift Workplace users have a user-specific directory created on the My Fourth Shift Workplace server. The Microsoft Internet Information Server session id is incorporated into the user directory name. See the My Fourth Shift Workplace manual for more information.

If you wish to understand more about user-specific directories, see the "System Operation" section of the System Administration manual.

Installation Information FilesSeveral files are available during the installation to provide additional information about your installation. These files include:

• Read Me (README.TXT). This file contains release information and important details associated with your system.

• Installation History File (INSTALL.HIS). This file, located in the MFGSYS directory, contains an audit trail of the installation steps completed and records any errors encountered. The INSTALL.HIS file for a workstation installation is located in the directory specified by the UserDir configuration variable.

Automatic Environment UpdatesSeveral automatic environment options are reviewed and updated when you install your system. The updates include:

Automatic Service File UpdateThe installation program automatically updates the service files which contain server communication port number assignments. These port numbers are used with the TCP/IP communication protocol.

The server installation program scans the services file for available port numbers and reserves two for Fourth Shift use. These port numbers are assigned to configuration variables in the server's FS.CFG file.

The services file on the workstation is also updated during the workstation installation process. The workstation installation reads the port number assignments from the FS.CFG file on the server and then updates the services file on the workstation with the same port number assignments.

Port Settings and Your FirewallIf a firewall is used to secure your Fourth Shift server, your system administrator should be managing the accessibility of the port numbers used for server-client connections if these ports are outside your company’s firewall. The following port numbers are set as defaults in Fourth Shift:

• Net UI server uses the default port 5432.

• NET UI web page uses port 80 for HTTP traffic.

Element Description

Path The M:\MFGSYS\SYSTEM directory is automatically added to your workstation path during the workstation installation.



• NET UI web page uses SSL port 443 for HTTPS traffic.

• Fourth Shift Remoting (on the Application Server) uses 7361.

• Fourth Shift Server uses port 2056 for Lock Server.

• Fourth Shift Server uses 2057 for MAINXX database service.

• Fourth Shift Server uses 2058 for the FINXX database service.

• Fourth Shift Server uses 445 for the mapped drive.

• SQL Server Database uses 1433 for SQL.

Your port numbers may be different if:

• There are multiple Fourth Shift installations on the server

• The default port numbers were already in use. Then the next sequential port number will be assigned.

System Settings QuestionsSystem settings questions are used to identify the overall settings used to operate your business. These answers to these questions can be selected at installation only and are used to configure your overall system for operation. It is difficult to change your selection after you have implemented your system so you should carefully consider your selection before beginning the installation.

System Identifier and System NameYour Fourth Shift system must be identified with a unique System Identifier. This two-character identifier is used in the names of several Fourth Shift important components, such as your database. The default system identifier is "MR." It is sometimes referred to as SystemIdentChar or System Identifier Character.

You must also specify a System Name for your Fourth Shift installation. The system name is added to the names of shortcuts and databases, and is also displayed in the application title bar. A system name can be up to eight characters in length.

Select a system identifier and system name for your Fourth Shift installation.

Tax SystemYour overall Fourth Shift system uses a single tax method. This tax system determines how tax information is reported for transactions and how it is tracked as you use the system.

The tax system options include:

Tax System Examples Description

Sales tax federal, state, county, municipal

Sales tax is tracked by customer ship-to location and is associ-ated with customer order and invoice transactions.

VAT VAT (1 level), VAT (2 level)

VAT (value added tax) is assigned based on the Item Product Code and Customer Code combination. The initial installation defines a VAT system as one level. During implementation, you can select two-level VAT, if necessary, using the TXCF screen.



Identify the tax system needed for your company. The tax system selection is made only at installation time.

System Monetary PrecisionThe monetary precision refers to the number of digits listed after the decimal symbol in values such as prices or costs in your local currency. The system monetary value indicates the currency used in your general ledger to report financial transactions. For example, the monetary precision of the United States is 2 decimal precision.

The monetary precision is not used to indicate quantities for items such as order quantities or item quantities used within a bill of material.

The system monetary precision options include:

Identify the system monetary precision needed for your company.

Option Example Value Displayed

0 decimals 150

1 decimal 150.9

2 decimals 150.99

3 decimals 150.999



Local Currency Code and DescriptionThe Fourth Shift system uses a single currency general ledger for tracking financial transactions and track item costs. The local currency code indicates the currency used in your general ledger to report financial transactions. The local currency code works with the local monetary precision to identify financial values in your system and is displayed on screens in the system when financial values are listed.

In a multi-currency environment, the local currency code is used as the basis for comparing other currencies to your own. The comparison of currency codes and the exchange rates associated with the currency codes are used in exchange rate fluctuation calculations. It is recommended that you enter the generally accepted international currency code for your currency. For example, use the code USD and description U.S. Dollars to identify the currency for United States dollars.

Identify the local currency code and description needed for your company.

Item Costing MethodItem costs can be assigned using one of the available methods. The costing method is used for all item transaction processing. The costing options include:

Identify the item costing system needed for your company.

Method Description

Standard cost Item costs are established and assigned at the beginning of the reporting period. Variances are recorded for transactions based on the item cost difference between the standard cost established and the actual cost of the transaction.

Average actual cost Item costs are initially established and are periodically revalued based on actual transactions. The item cost fluctuates and is tracked on an order-by-order basis through the system.



Application ModulesThe modules available for you to install are identified automatically using the Module Access Key diskette during installation. You can deselect modules if you wish to wait to install certain modules based on your implementation plan.

Some application modules require supplemental software in addition to the Fourth Shift software. All required additional software should be installed before you begin the installation of your Fourth Shift system. See the Additional Software Requirements section for more information on the specific software needed based on the modules you have purchased.

If you are installing My Fourth Shift Workplace, a separate CD-ROM and set of instructions are used. See the My Fourth Shift Workplace manual for more information and instructions.

If you are installing the Fourth Shift Business Intelligence module (BISM), a separate CD-ROM and set of instructions are used. See the Installing Fourth Shift Business Intelligence manual for more information and instructions.

Additional Software RequirementsThe SETUP program used to install your Fourth Shift system must be run from a Microsoft Windows environment. In addition, several modules require additional software to be installed in order to access the module features.

It is recommended that you install any additional software necessary for using the modules before beginning the Fourth Shift installation process, including the Verify Prerequisite Software Installation. The following table identifies the additional software requirements for each module.

Module Identifier Additional Software Required

Accounts Payable APSM none

Accounts Receivable ARSM none

Advanced Price Book APBM none

Approved Vendor Sourcing AVSM none

Bill of Material BILM none

Business Intelligence BISM SQL Server Analysis Services and Internet Explorer. See the Installing Fourth Shift Business Intelligence manual for more information.

Cash Management CSHM none

CIM Customizer CSTM none

Co-Products Manufacturing COPM none

Connectivity Toolkit CTKM Internet browser and Microsoft Internet Information Server

Custom Products Manufacturing CPMM none

EDI Services EDSM EDI mapping software

Electronic Data Interchange EDIM EDI mapping software

Engineering ENGM none

Fourth Shift Transactional Interface FSTM none



Next Step: Use Multi-user Preparation to prepare for your system installation.

FSExplorer Internet Explorer

G/L Restructuring RTSM none

General Ledger GLSM none

Inventory Control INVM none

Intrastat Reporting ISTM none

Lot Trace/Serialization LOTM none

Management Reports MGRM none

Manufacturing Analysis MMAM none

Manufacturing Order Management MOMM none

Material Requirements Planning MRPM none

Multi-Currency Management MCMM none

My Fourth Shift Workplace WEBUI Internet browser and Microsoft Internet Information Server; see "Installing My Fourth Shift Workplace" in the My Fourth Shift Workplace manual for more infor-mation.

Net UI NUIM Internet browser and Microsoft Internet Information Server (if Net UI clients installed from Internet)

Operations Performance OPFM none

Order Entry CUSM none

Payroll Connection PYCM none

Product Costing PRCM none

Purchasing PURM none

Repetitive Manufacturing RPTM none

Rules-Based Pricing RBPM Access

Sales Analysis SAAM none

Sales Order Processing SOPM none

Screen Customizer SCRM none

Shipping SHPM none

Shop Floor Tracking and Reporting SFRM none

System Control SYSM none

Module Identifier Additional Software Required


Fourth Shift Release 7.50 R2 Multi-user Preparation

Multi-user Preparation

Configuration OverviewA client/server system allows people throughout your company to share the most up-to-date manufacturing and accounting information. Implementing a client/server system allows many people to simultaneously use your system while, at the same time, protecting the integrity of your company's production database.

Microsoft Windows Server and SQL Server

The basic structure consists of the following components:

• The Microsoft SQL Server Database Server contains the Fourth Shift database.

• The Fourth Shift Server centralizes the security and access to all stored files for your Fourth Shift system. The Fourth Shift server can be on the same machine as the SQL Server Database Server or on a separate machine.

Note: The database server can be either a 32-bit or 64-bit (x64) Windows Server with SQL Server 2005 or SQL Server 2008 R2. The Fourth Shift server also can be a 32-bit or 64-bit (x64) Windows Server.

• The Fourth Shift Manufacturing and Financial Database Services and the LockServer service process workstation requests for accessing and updating information in the database.

• Workstations access the system through the network. Workstations request and update information from the server and database server processes.



Knowledge RequirementsThe instructions and explanations provided in this manual assume you have completed training and have a solid understanding in the areas applicable to your configuration.

You should have completed training and have a solid understanding in the following areas:

• Installing and configuring the Microsoft Windows operating system

• Microsoft Windows system administration utilities

• Microsoft Windows network related features

• TCP/IP network protocols including IP addressing, subnetting, IP routers, gateways, and name resolution or NetBIOS network protocol

AssumptionsThe installation instructions assume that you have installed the necessary operating systems and the server is up and running. If this is not the case, install the required operating systems. Microsoft Certified Systems Engineers are available from SoftBrands for on-site consulting if desired. Contact Customer Support for more information on this service.

Configuration PreparationYou need to prepare your server and client environments before installing your system. These instructions identify the directory where your Microsoft Windows operating system is installed as the [Windows] directory. Substitute the exact directory information based on your installation.

Backup Current SystemBefore starting the server installation, it is recommended that you perform a complete backup of your Windows server.

Configure Server EnvironmentSet up the Windows server in preparation for installing and operating Fourth Shift.

1. Go to the Windows server and log on as an administrator.

2. Create a directory on the new server that will contain the Fourth Shift system files.

For example C:\FSHIFT.

3. Right-click on the new directory then select Properties.

4. Give the directory "Full Control" permission to the “Everyone” group for both the Sharing and Security tabs.

5. Share the directory you just created, giving full control to all users.

6. Select the Advanced tab and verify the following check box settings:

- Indexing Service—selected

- Compression—cleared

Note: These instructions use M: as the example drive letter.

7. Select the System option in the Control Panel.

The System Properties screen is displayed.



8. Select the Advanced tab.

9. Click Settings in the Performance section.

The Performance Options screen is displayed.

10. Click the Advanced tab.

11. Click Change in the Virtual Memory section.

12. Set the Initial Size to 1.5 times the available RAM for the file server.

13. Set the Maximum Size to the same value as the Initial Size

14. Click Set.

15. Click OK to save your selection and close the Virtual Memory screen.

16. Click OK to close the Performance Options screen.

17. Click OK to close the Properties screen.

Note: Click No, if asked to restart the computer.

Notes on Name ResolutionFourth Shift requires the use of standardized name resolution in your TCP/IP setup. If name resolution is not configured at the server, workstations will have difficulty accessing the database.

The name of the database server can contain only the following characters:

• a-z or A-Z

• 0-9

If other characters are used in the server name, name resolution will not be successful. The preferred name resolution method is installation of a DNS server with either WINS or DHCP name resolution.

Configure Network EnvironmentComplete the following network environment configuration tasks to ensure all user workstations can access the Fourth Shift server.

Configuring Shared Drive1. Open Explorer to create a network SHARE and assign security permissions.

2. Select the directory to be shared, such as C:\FSHIFT.

3. Right-click, and select Properties.

4. Click the Sharing tab, or select Advanced Sharing...

5. Select the Share this folder option.

6. Enter FSHIFT in the Share name field

7. Enter a Comment, if necessary.

8. Enter a User limit, if applicable.

9. Click Permissions.

10. Select Add.

The Select Users, Computers, or Groups window is displayed.



11. Select Show Users.

12. Enter the Fourth Shift group and any others you wish to have permissions to this location.

13. Click OK.

14. Change the type of access to Full Control for the Fourth Shift group.

15. Click OK.

16. Click OK to close the Properties window.

Assigning Logical Network Drive1. If the server operating system is Windows 2003:

- Open Windows Explorer.

- Double-click the FSHIFT directory.

- From the Tools menu, select Map Network Drive.

2. If the server operating system is Windows 2008 or above:

- Open Computer.

- Select Map Network Drive.

3. Enter the following information:

- - Drive = M:

Note: For this example, M: is used as an example for the mapped drive letter. Any previously unmapped drive letter may be used.)

- - Path = \\computer_name\FSHIFT

4. Verify that Reconnect at login is selected. Click Finish.

5. Shut down and restart the Windows server.

Next Step: Use System Installation to complete the installation of your database components and modules.


Fourth Shift Release 7.50 R2 System Installation

System Installation

SQL Server InstallationSQL Server 2005 or SQL Server 2008 R2 can reside on the same server as your Fourth Shift server or on a separate server.

If SQL Server is not currently installed on the server, complete the following steps to install it.

Verify Prerequisite Software InstallationSee Application Modules in Before You Install for more information on additional software requirements.

1. Go to the server.

2. Verify that Operating System meets Fourth Shift prerequisites.

- One of the following is required:

- Windows Server 2003 Service Pack 2

- Windows Server 2003 R2 Service Pack 2



- Internet Explorer 7.0 or 8.0 is required.

- Adobe Reader 7.0, Version 7.0.5 or newer, or Adobe Acrobat 9 or newer is required.

3. Verify that all required additional software should be installed before you continue.

See Before You Install for more information on additional software requirements.

Install Microsoft SQL ServerInstall SQL Server 2005 (including Service Pack 3 for SQL Server 2005) or SQL Server 2008 R2 according to Microsoft’s instructions. Make sure that the following options are selected during the installation:

1. Verify that Use the same account for each service. Auto start SQL Server service is selected.

2. Select the Use the Local System Account option on the Services Accounts window under Service Settings.

3. Select Mixed Mode as the authentication mode.

4. Verify that the following settings are selected on the SQL Collations window:

- Dictionary order, case-insensitive, for use with 1252 character set (This is the default)

- Fourth Shift-specific settings are identified later in the installation when the empty database is created.

- Accept the default values for all other fields.



Reporting ServicesMicrosoft Reporting Services are a component of SQL Server. Make sure you select the option to install Reporting Services when installing SQL Server.

SQL Server Surface Area ConfigurationComplete the steps to configure the SQL Server Surface Area for the version of SQL Server you are running:

• SQL Server 2005 Surface Area Configuration

• SQL Server 2008 R2 Facet Configuration

SQL Server 2005 Surface Area ConfigurationAfter SQL Server 2005 is installed, it is important to ensure that SQL Server is configured to enable features used by Fourth Shift. This is done using the Microsoft SQL Server 2005 Surface Area Configuration utility:

1. From Start > All Programs, select Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration.

2. Select Surface Area Configuration for Services and Connections.

3. Under MSSQLSERVER > Database Engine, select Remote Connections.

4. Select Local and remote connections.

5. Select either Using TCP/IP only or Using both TCP/IP and named pipes.

Note: Failure to perform this step will prevent the ability to run Fourth Shift on a client machine separate from the server.

6. Click OK. If you get a message indicating that changes will not take effect until you restart the database engine service, click OK.

7. Select Surface Area Configuration for Features.

8. Select CLR Integration under Database Engine.

9. Select Enable CLR Integration.

10. Select Database Mail.

11. Select Enable Database Mail stored procedures.

12. Select xp_cmdshell.

13. Select Enable xp_cmdshell.

14. Click OK.

15. Close the SQL Server 2005 Surface Area Configuration window.

SQL Server 2008 R2 Facet Configuration1. From Start > All Programs, select Microsoft SQL Server 2008 R2 > SQL Server

Management Studio.

2. Select server type Database Engine and the current server name (or “.” for local) along with appropriate credentials and click Connect.

3. Right-click on the SQL Server and select Facets.



4. Select Server Configuration Facet.

a. Set AgentXPsEnabled to True.

b. Set ClrIntegrationEnabled to True.

c. Set RemoteAccessEnabled to True.

5. Select Server Installation Settings Facet.

a. Set TcpEnabled to True.

6. Select Surface Area Configuration Facet.

a. Set ClrIntegrationEnabled to True.

b. Set DatabaseMailEnabled to True.

c. Set XPCmdShellEnabled to True.

7. Click OK.

Update SQL Server Configuration OptionThe following SQL Server configuration option should be updated to match the Fourth Shift year range.

1. Open SQL Server Management Studio.

2. Connect to the database.

3. Right-click the name of the server.

4. Click Properties.

5. Select Advanced.

6. Change the ending year for Two Digit Year Cutoff to 2079 under the Miscellaneous group.

7. Click OK to save the year change.

Select Fourth Shift Server Installation Options1. Go to the Windows server machine designated for Fourth Shift to complete the Fourth Shift

installation.

Important: Do not attempt the Fourth Shift server installation while connected to the server remotely.

2. Restarting the server is recommended to clear memory fragmentation.

3. Sign on to your server.

You must have administrator rights to complete the installation.

4. Insert the Fourth Shift Release 7.50 R2 CD-ROM into the drive.

5. From the root of the CD-ROM, double-click the SETUP program or right-click the file and choose "Run as administrator" if the operating system requires it (i.e., Windows 7, Windows Vista, or later).

If you get a message asking if you want to allow the program to make changes to this computer, click Yes.

The Welcome screen is displayed.

6. Click Next.



7. Read the license agreement, then click Yes.

8. Select the installation type: Install initial Fourth Shift system.

9. Click Next.

10. Specify system identification characters for your system.

If you will have multiple Fourth Shift systems in your environment, this information must be unique for this Fourth Shift system.

- System Identifier—is the two-character designator for the system

- System Name—is an alpha-numeric eight-character maximum

11. Click Next.

The Serial Number and Module Access Key screen is displayed.

12. Enter the serial number for the Fourth Shift system printed on the Module Access Key CD-ROM.

13. Remove the Fourth Shift Release 7.50 CD from the CD-ROM Drive.

14. Insert the Module Access Key CD into the drive.

15. Click Browse to locate the Module Access Key on the CD.

16. Select the *.KEY file located on the CD.

17. Click Open.

The key is automatically displayed in the field.

18. Click Next.

19. Remove the Module Access Key CD from the drive.

20. Insert the Fourth Shift Release 7.50 CD in the drive.

Select System Settings and Destination Directory1. Choose the item costing method desired: Standard or Average Actual.

2. Choose tax system: Sales tax or VAT.

3. Choose the system monetary precision desired: 0, 1, 2, or 3 decimal precision.

4. Enter 1 to 5 characters for the Local Currency Code.

5. Enter the local currency code description.

6. Click Next.

7. Do one of the following to choose a destination directory

- Accept the system default—M:\

- Click Browse—to select another location

8. Click Next.



Verify Module ListThe list of modules available is displayed, and the modules you have purchased are checked automatically. You can deselect modules as desired if the module is not a prerequisite for another module. Modules that are prerequisites for other selected modules are shown in gray.

Additional modules cannot be installed until you receive a new module access key after purchasing the additional modules.

1. Verify modules listed are correct.

Any module shown in gray cannot be cleared or removed because it is a prerequisite for another selected module.

2. Click Next.

Establish SQL Server Connection Information1. Enter the password for the SQL Server Administrator “sa” user of the SQL Server 2005

instance that will contain your Fourth Shift database.

2. Select the SQL Server instance name for the SQL Server 2005 system that will contain your Fourth Shift database.

The SQL Server instance name defaults to an instance name on the same machine as your Fourth Shift server, if one exists. You can also select a SQL Server instance that is installed on a separate machine.

3. Click Next.

Establish Workstation Administrator LogonThe Workstation Administrator Logon allows you to record Windows administrator credentials for use during workstation upgrades. If you enter this information, even users who are not administrators on their computers can perform Fourth Shift workstation updates. This information is used after an Interim Service Release is installed on the server.

A user with administrator rights on the workstation must perform the first Fourth Shift workstation installation on each computer.

Note: The automated client installation feature is available for Windows XP clients with or without system administrator privileges. It is available for Windows Vista or Windows 7 clients only when the user has system administrator privileges.

1. Do one of the following for the No I do not wish to configure an administrative account to be used during automated client installations check box:

- Select the check box, If you do not want to enable automated workstation installations

- Clear the check box, if you do want to allow automated updates.

2. Enter a Windows user Id, password, and domain name for a user with Administrative rights to workstations.

3. Choose Next.



Determine Sales Analysis DatabaseThe Fourth Shift Sales Analysis data can either be stored in the Fourth Shift database (FSDBXX) or a separate Sales Analysis database (SADBXX). We recommend that your Sales Analysis data is stored in the Fourth Shift database so that the Sales Analysis data is always backed up consistently with the Fourth Shift data. If a separate Sales Analysis database is selected, it is created on the same SQL Server instance as the Fourth Shift database.

Note: If you are not installing the Sales Analysis (SAAM) module, skip to the next procedure: Enter Administrator Information for the IIS Server.

1. Select the database for Sales Analysis data storage.

2. Click Next.

Enter Administrator Information for the IIS Server1. Enter information for a user with administrative rights on the IIS server used for Fourth Shift

reporting.

This information is used to connect to the IIS server when a report is requested by a user in Fourth Shift.

2. Enter a user id, password, and domain name for the user.

3. Click Next.

Review Installation Summary1. Verify list of options and selections before beginning the actual installation process.

Note: Click Back, when available, to return to a selection which needs to be updated.

2. Click Next to begin the installation.

3. Accept the default selection to restart the machine when the installation is complete.

4. Click Finish.

The setup program will restart automatically.

Note: Verify that the server restarted when it was shut down. If you simply logged out and logged in again, restart the server.

5. If a message displays asking if you want to allow the following program to make changes to this computer, click Yes.

SQL Server Database InstallationTo install the Fourth Shift SQL Server database, complete the following steps:

1. Click Next when the Fourth Shift SQL Server database setup begins.

2. Close any other programs that are running and click Next at the Introduction screen.

3. Verify the two-letter system identifier.

4. Click Next.

5. Verify the correct SQL Server instance name where the databases will be created.

6. Verify sa as the system administrator login name.

7. Click Next.



8. Verify or modify the following manufacturing database parameters:

- Database name—this name is display only. The name is FSDBXX, where XX is the two letter system identifier.

- Database size—the default size for the initial database allocation is 150 MB.

- Database log size—the default size for the initial database allocation is 75 MB.

- Log file name—the default name is FSDBXXLOG.

- Path for database device creation—the default value is the SQL Server location stored in the registry of the SQL Server machine. You should not need to modify this location.

- Path for log device creation—the default value is the SQL Server location stored in the registry of the SQL Server machine. You should not need to modify this location.

- Collation—the default collation is Latin1_General_Bin. This is specific to the Fourth Shift database.

Note: If the SQL Server instance is on the same machine as the Fourth Shift server, the amount of free space is also displayed.

- Verify that enough free space exists to create the database and database log.

9. Click Next.

10. Verify that the Display Log Files at Completion check box is selected.

We recommend that you view these files.

11. Click Finish.

A dialog box displays messages regarding the status of the database creation, schema creation, and backup.

Review Log Files and Complete InstallationSeveral log files are created during the server installation. Each file has expected content as indicated in the following table:

Log File Description Expected Content

sqcrdb0.log database creation log “Changed database context to...” messages.

sqcrmsc0.log manufacturing data-base schema creation log

End of error list

sqcrfsc0.log financial database schema creation log

End of error list

sqbkp0.log database backup log Changed database context to “master”

sqapp.log stored procedures log Message for some procedures beginning with "Cannot add rows to sysdepends for the current stored proce-dure. . ." or “The module ‘xxx’ depends on the missing object.”

rolecrea.log role creation New role added or empty



When the log files are displayed, complete the following steps to review the log files and continue with the installation.

1. Review these files for unacceptable errors and warnings.

See the Appendix for a list of acceptable error messages.

2. Close the log files.

A message appears indicating that the *.SQL and *.BAT files contain database login information that may pose a security risk.

Note: We recommend that you click Yes to delete these files.

The Fourth Shift installation continues.

3. Select the files you want to review, when the module installation is complete.

4. Click Finish.

5. Review the README.TXT and INSTALL.HIS files displayed.

Important: If the SAAM module is installed, several tables are created in the appropriate database. There are post installation and implementation steps that must occur before the SAAM database is ready for use. In step 5, the following message may be displayed: THE SAAMINST PROGRAM SHOULD BE RUN SUCCESSFULLY BEFORE FCMTSAAM CAN CREATE THE INCREMENTAL LOAD DTS PACKAGE.

See Phase 6: SAAM Installation Completion in the Implementation Checksheets for more information.

6. Continue with the Workstation Installation on the Server steps.

Workstation Installation on the ServerWhen the workstation installation automatically begins on the server machine, do the following:

1. Click Next.

A message may appear indicating that the machine may need to be restarted during the client installation.

2. Click Yes to continue.

3. Browse to locate the FS.CFG configuration file—the default is M:\MFGSYS\FS.CFG.

4. Click Next.

5. Select the modules to install for this workstation.

The System Control Module is selected automatically. It may not be necessary to install all modules for all users.

6. Click Next.

The Summary screen is displayed.

Sqlsadb0.log Sales analysis schema log

List of files executed(may not appear if the Sales Analysis database is not separate from your production database)



7. Verify the selections before beginning the actual installation process.

Note: Click Back, if available, to return to a selection which needs to be updated.

8. Click Next.

Files are installed for the workstation.

9. Click Finish when the installation is complete.

10. Review the INSTALL.HIS file.

A series of Advisory messages is displayed. Use the Appendix section of this manual to determine actions necessary for any errors.

Interim Service Release InstallationAt this time, you should download the latest Interim Service Release (ISR) from the Fourth Shift Customer Center Web site. This ensures that you have the latest updates for Release 7.50.

1. Log on to the SoftBrands’ Customer Center Web site.

2. Follow the instructions for downloading the ISR and updating your Fourth Shift server.

Note: The earliest ISR compatible with this release 7.50 R2 is 7.50C.

Perform Backup1. Perform a full backup of your SQL Server database (FSDBXX) and all subdirectories created

for your mapped drive during your installation.

For example, if the mapped drive is M:, it includes the M:\MFGSYS, M:\FS_APPS, M:\XPORT and any module-specific directories.

2. Complete the actions listed in the Post-Installation Tasks and Workstation Preparation sections for your configuration.

Post-Installation TasksPost-installation tasks require you to make decisions and update installed components based on your environment. Complete the post-installation tasks necessary based on the modules you have installed.

SAAM Module: Additional Installation Steps RequiredSeveral steps in the Implementation Checklist must be completed prior to running specific SAAM install programs.

Next Step: Use section System Post-installation to complete the post-installation steps for the SQL Server configuration.


Fourth Shift Release 7.50 R2 System Post-installation

System Post-installation

Workstation Access

Share System DirectoryThe location on the Fourth Shift server specified by the SystemDir configuration variable is used for some application program processing. Therefore, all Fourth Shift users must have access to this location. The default SystemDir location is MFGSYS\SYSTEM.

Establish Access RightsUse the following table to assign access rights to Fourth Shift users on the Fourth Shift server.

• Create an access group, such as FSGROUP, and add to the group the users who will access the Fourth Shift system.

This group should be assigned Read access to all FSHIFT subdirectories except for those listed in the following table. You may not have all the directories listed based on the modules you have installed.

Directory Directory Access Assignments

\ (root) Read

EDIEXCEL (including related subdirectories)

Full Control

EDIINTRN Full Control

FS_APPS Full Control

FS_APPS\D Full Control

MFGSYS Read

MFGSYS\CLIENT Read

MFGSYS\E Read

MFGSYS\FONTS Read

MFGSYS\FSTM Full Control

MFGSYS\H Read

MFGSYS\I Full Control

MFGSYS\REPORTS Read

MFGSYS\S Read

MFGSYS\SCREENS Full Control

MFGSYS\SAAM Full Control

MFGSYS\SQLMSS Read

MFGSYS\SYSTEM Read

MFGSYS\WEB Full Control



Update the Fourth Shift Administrator PasswordThe Fourth Shift Administrator (fsadmin) user Id and password is created when you perform the first Fourth Shift server installation for a SQL Server instance.

Note:- Because the fsadmin password is specified for the SQL Server instance, the updated

password applies to all Fourth Shift systems on the SQL Server instance.

- Use the Fourth Shift SQL Administrator console to modify the password for the fsadmin user, if desired.

From the Start menu on the Fourth Shift server...

1. Go to the Fourth Shift Tools directory.

2. Select Fourth Shift SQL Administrator.

3. If you get a message asking if you want to allow the program to make changes to this computer, click Yes.

4. Expand Fourth Shift—Configurations from the console root.

5. Click the System Identification Characters (SystemIdentChar) specified during the server installation.

6. Right-click and select Properties.

7. Select the Data Source tab.

8. Enter a new password in the Password and Verify fields.

9. Click OK.

Creating the E-mail Addresses in fs.cfgYou need to identify an e-mail address for the system to use in the event that an error is encountered during modcom processing. That configuration variable has been added automatically to the fs.cfg file. In addition, if you have the Sales Analysis module, you need to identify e-mail addresses for the system to use in the event that errors are encountered during the incremental load process.

1. Go to the MFGSYS directory, on the Fourth Shift server, and open the fs.cfg file using Notepad. If Windows Server 2008 or higher, run Notepad as an administrator.

2. Locate the ModcomEmailRecipient= variable in fs.cfg and verify the appropriate e-mail address.

If SAAM is installed, the following three e-mail configuration variables were added to the fs.cfg file.

- SAAMAdminEmailRecipient=

- SAAMProductionEmailRecipient=

- SAAMFinancialEmailRecipient=

3. Review the fs.cfg file to locate the configuration variables for SAAM e-mail notification.

4. Add the appropriate e-mail addresses for these variables.

Note: You can add multiple e-mail addresses by separating each address with a semicolon. The maximum length of the total e-mail address is 4000 characters.



Activating the New E-mail Configuration VariablesFourth Shift will not recognize these added values until the system is restarted. Make sure that everyone is out of Fourth Shift and stop the Main and Fin services.

• Restart the Main and Fin services.

The new e-mail configuration variables are now operative and available for Fourth Shift processing implementation.

Next Step: Use Workstation Preparation for workstation preparation steps. You will need to repeat the preparation and workstation installation for each workstation and server which will access the Fourth Shift system.

If you are going to implement My Fourth Shift Workplace or NetUI, these installations are performed after the workstation installation has been completed on the server. See the online help for these modules for information on specific installation steps.


Fourth Shift Release 7.50 R2 Workstation Preparation

Workstation Preparation

Environment PreparationNote: For many of these tasks, the person performing these tasks must have administrative

rights to the workstation to complete them.

Verify Prerequisite Software Installation1. Go to the workstation.

2. Verify that Operating System meets Fourth Shift prerequisites.

One of the following is required.

- Windows 2003 Server Service Pack 2

- Windows XP Professional Service Pack 3

- Windows 7 Service Pack 1

- Windows Vista Service Pack 2



• Internet Explorer 7.0 or 8.0 is required.

• Adobe Reader 7.0, Version 7.0.5 or newer is required.

3. Verify that all required additional software should be installed before you continue.

See Before You Install for more information on additional software requirements.

Review System Date SettingsThe system date format set in your Microsoft Windows desktop environment should be the same as used for Fourth Shift. You will establish your Fourth Shift date format on the CNFG (System Installation Setup) screen during implementation.

1. From Control Panel, select “Regional Options” or “Region and Language.”

2. Review the short date format. Update the format if necessary. Click OK.

We recommend that you use a four-digit year, such as YYYY, in the short date format.

Update IE Security Settings for Users Within the DomainThis step allows users to generate reports from within Fourth Shift without requiring them to enter a network ID and password each time a report is requested. Completing this step on each workstation is strongly recommended.

If these settings are not modified, the user will be required to enter a network user ID and password each time a report is generated. In this case, the user would also need to have security rights to the report templates (RDL) files on the IIS server used for reporting.

1. Open an Internet Explorer window.

Run Internet Explorer as an administrator if the operating system requires it (i.e., Windows 7, Windows Vista, or later).

2. Select Internet Options from the Tools menu.


Fourth Shift Release 7.50 R2 Workstation Preparation

3. Select the Security tab.

4. Click on the Local intranet icon.

5. Click the Sites button.

6. If available, click the Advanced button on the Local intranet window.

7. Enter the Reporting Services IIS server and domain information (in IE address format) in the Add this Web site to the zone field.

For example, if the IIS server is SERV1 on the CorpCo domain, it would be entered as follows: http://serv1.corpco.com

8. Click Add.

9. Click Close to close the Local intranet window.

10. If the Local intranet settings window is displayed, click OK.

11. Verify that the Local intranet icon is highlighted on the Internet Options window.

12. Click the Custom Level… button in the Security level for this zone section.

13. Locate the User Authentication—Logon node.

14. Select the Automatic logon only in Intranet zone option.

15. Click OK to close the Security Settings window.

16. Click OK to close the Internet Options window.

17. Close the Internet Explorer window.

Next Step: Use section Workstation Installation and Post-Installation to complete the software installation and post-installation verification.


Fourth Shift Release 7.50 R2 Workstation Installation

Workstation Installation

Workstation Installation OverviewSeveral settings are updated automatically in your workstation environment when you complete the Workstation Installation. It is recommended that you install the online manuals access at a minimum to ensure that the automatic workstation environment updates are completed. See Before You Install for more information on these settings.

You have already completed the workstation installation process on your Fourth Shift server. Now you need to complete the workstation installation process on each workstation that will access your Fourth Shift system.

A module-specific workstation installation must be completed before any of the following modules (other than System Control) can be accessed from a workstation. Select the module-specific workstation installations appropriate for this workstation.

Workstation Installation Examples

Module Identifier Considerations

System Control SYSM All users must install this module

Engineering ENGM none

Manufacturing Analysis MMAM

Material Requirements Planning MRPM

Net UI NUIM Install for remote clients or to improve LAN client per-formance

Product Costing PRCM

Rules Based Pricing RBPM none

Sales Order Processing SOPM none

Screen Customizer SCRM Install only for users who should have the ability to customize screens; not needed for users who will access customized screens

Shop Floor Tracking and Reporting

SFRM



Installation MethodsThe workstation installation can be completed several ways. The installation steps vary based on the installation method selected.

Select one of the following installation methods.

Installation ProcessThe workstation installation consists of the following phases:

• workstation preparation for general configuration and network access

• installation of workstation files

• validation of workstation installation and access to the system

Additional Component InstallationAt the beginning of the workstation installation, the setup program may need to install several Microsoft Windows components if they are not already installed on the workstation. These components include:

• Microsoft Data Access Components Update

• Microsoft Common Control Update

• Microsoft Internet Explorer 7.0 or 8.0

The setup program will notify you if these components need to be installed. Each component requires that the workstation be restarted. After all components are installed, the setup program automatically resumes.

Method Description

Network files Files installed to the MFGSYS\CLIENT directory can be used directly to com-plete the installation. This method allows you to complete multiple installations at once and does not require use of the CD-ROM media.

CD-ROM Files are installed directly from the CD-ROM. This option requires the use of a CD-ROM drive on the workstation.

Internet "Thin client" components are installed from a Web page. This option allows remote users to install workstation components without access to the network or CD-ROM. This option is available only if the NUIM module is installed. See the Net UI manual for more information.



Workstation Installation ProcessWorkstation components include programs, drivers and icons which allow you to access the system. These instructions assume you are installing from the MFGSYS\CLIENT directory. It is possible to install directly from the CD-ROM but you must then select the workstation installation options.

It is also possible to install the components required for a Net UI ("thin client") workstation via the Internet. This requires a different set of instructions. See the Net UI online manual for more information.

We recommend that you install the online manuals at a minimum at each workstation.

This workstation installation must be repeated on each workstation which will access your Fourth Shift system.

Before You BeginYou must log in as administrator before beginning the workstation installation.

Start Installation1. Verify that you have completed the necessary workstation preparation.

2. Go to the workstation.

3. Map the M: drive to the database server.

4. Verify that the Reconnect at login check box is selected when you create this drive mapping.

M: is used as an example for the mapped drive letter. Be sure to select the same drive letter as mapped on the server in the step Assigning Logical Network Drive.

5. From the M:\MFGSYS\CLIENT directory, double-click SETUP program or right-click the file and choose "Run as administrator" if the operating system requires it (i.e., Windows 7, Windows Vista, or later).

If you get a message asking if you want to allow the program to make changes to this computer, click Yes.

6. On the Welcome screen, click Next.

A message may appear indicating that the machine may need to be restarted during the client installation.

7. Click Yes to continue.

8. Browse for the FS.CFG configuration file.

The default location is M:\MFGSYS\FS.CFG.

9. Click Next.

10. Select the modules to install for this workstation.

The System Control Module is selected automatically. It may not be necessary to install all modules for all users.

11. Click Next.

12. Verify the selections before beginning the actual installation process.

13. Click Back to return to a selection which needs to be updated.



14. Click Next.

Files are installed for the workstation.

15. Click Finish when the installation is complete.

16. Review the INSTALL.HIS file.

A series of Advisory messages is displayed. Use the Appendix section of this manual to determine actions necessary for any errors.

17. Reboot the computer to update your machine with the required changes.

Workstation Post-InstallationThe installation process creates folders and shortcuts in the Start menu and installs workstation files. Some additional setup is needed after installation including verifying the installation by signing onto the Fourth Shift system from the workstation.

Verify Printer SetupIf the workstation will be used to print or generate reports, make sure there is at least one printer set up on the workstation. A printer must be set up in each user profile.

1. Select Printers from the Control Panel.

2. Verify that at least one printer is set up and that the correct printer is chosen as the default printer.

3. Verify that at least one printer is set up for each user profile that will use Fourth Shift.

Verify Workstation InstallationAfter module installation is complete, you are ready to sign onto the system to verify the installation.

1. Sign onto the system from the workstation.

2. Click Start, then All Programs, then the folder that contains the Fourth Shift group.

3. Click Fourth Shift, if available.

The sign-on screen is displayed.

4. Type: AAA in the User Id and ADMIN (all upper case) in the Password fields.

5. Press Enter.

The Menu is displayed.

6. Sign onto the system at a second workstation after you successfully signed on at the first workstation.

7. From the File menu, select Exit from both workstations.

8. Verify that icons created to access module features are installed correctly.

9. Select each module (or module feature) to verify it can be accessed from the Fourth Shift—Fourth Shift Tools groups.

Next Step: Use Implementation Planning to begin the process of entering your production data.


Fourth Shift Release 7.50 R2 Implementation Planning

Implementation PlanningYour company has just purchased the most advanced manufacturing software on the market today. This system combines ease of use with features that, until now, have only been available on larger, more expensive systems. The education materials and support services available help assure success in your manufacturing operation.

Support ServicesSoftBrands is committed to customer service and support. We offer a full range of services designed to help you obtain the maximum benefits from your purchases of Fourth Shift products.

Reference MaterialsA comprehensive manual is provided for setting up each module. Much of this information is also available at your fingertips through context-sensitive online help built into the system.

Training MaterialsThe Mentor interactive training program, that you may purchase, provides basic system and application training. The Mentor program consists of sets of lessons on specific functional areas in the system. The set of lessons are designed to help you learn the areas of the system needed to perform your job.

Customer Support ProgramThe Customer Support Program (CSP), to which you may subscribe, provides several valuable services including:

• product updates

• telephone technical support

• electronic bulletin board

• Go Fourth monthly newsletter

Implementation ProgramThe Fourth Shift Implementation Program assists new users, on-site, with initial system startup and implementation. You can choose from these Implementation Programs based on your needs:

• manufacturing implementation

• financial implementation

• systems implementation

Contact Fourth Shift Consulting Services to schedule an implementation planning session to help you develop your plan.

Training CurriculumThe Fourth Shift Training Curriculum has been developed to meet the needs of today's manufacturing company. The classroom-based training includes recommended courses for both startup and ongoing training needs. Classes are generally held at our Headquarters in Minneapolis, but may be held at one of our regional offices or on-site. Contact the Training Department for more information.



On-Site ConsultingThe Fourth Shift Consulting staff is made up of experts in the application of the system. In addition, the staff has expertise in areas including manufacturing, financial, system administration and software development. Consulting is quoted on a time-and-materials basis. Contact Fourth Shift Consulting for more information.

Implementation ProcessImplementation involves several key steps including:

• Step 1: Organizing for Success and Creating a Plan

• Step 2: Defining Your System

• Step 3: Completing Implementation Preparation

• Step 4: Preparing For System Cutover

• Step 5: Implementing the Production System

• A sixth step, Auditing Ongoing System Operation, is covered under the Post-Implementation Considerations.

Step 1: Organizing for Success and Creating a PlanOrganization and planning are essential to good system implementation. The implementation plan consists of many activities and can include the following:

• forming an executive steering committee

• selecting a project manager

• establishing an implementation team

• establishing company objectives for the project

• obtaining and installing hardware and software

• developing an implementation timetable

• educating implementation team members

Other steps may be needed based on the complexity of your plan. Develop a plan that is best suited to your needs and goals.

Implementation TeamEstablish an implementation team and assign a team leader who reports to upper management. Initial system implementation involves, at a minimum, the following areas in your company:

• system administration• materials management• customer service• purchasing• sales• G/L, A/P, and A/R management• manufacturing management• cost accounting



Company ObjectivesThe contribution the system can make is directly tied to measurable objectives. Company objectives can include:

• inventory investment reduced by X% within Y time frame

• customer service improvement by X% within Y time frame

• manufacturing and part cost reduced by X%

• planning responsiveness to changing customer demand from X days to Y days within Z time frame

• overtime reduced by X% within Y time frame

• delivery and receipt lead times reduced by X days

Once you have established your objectives, the system results can communicate the same goals to everyone in your company.

Implementation TimetableAny good plan includes a list of activities and a schedule of when each task can be accomplished. Your implementation timetable should include all the steps and detailed tasks identified by the team. Resources needed to accomplish each task should be identified.

Education PlanThe implementation team, at a minimum, should go through the training materials you have purchased. Also, consider the Fourth Shift classroom-based training and Implementation Program.

Documentation ReviewYour system comes with a complete library of manuals for the entire system, regardless of the modules you have purchased. Here are some suggestions for gathering the information you need to begin implementation:

1. Read the entire Getting Started manual to understand the system at an overview level.

2. Familiarize yourself with the entire System Administration manual to understand daily operation requirements and ongoing system maintenance. Also review your database manager-specific administration manual, SQL Server Administration and Utilities.

3. Familiarize yourself with the Fourth Shift Basics manual to learn about basic operations of the main Fourth Shift program.

4. Print out the Setting Up the Module topics in the documentation corresponding to the modules you are implementing.

Note: For additional information on the Sales Analysis (SAAM) configuration, see Using the Sales Analysis Console in the Sales Analysis on SQL Server online Help.



Step 2: Defining Your SystemPlans must be established to incorporate your current business activities into processes of the new system. Several activities are essential to accomplishing this objective including:

• performing module walkthroughs

• conducting prototypes for all your modules

• analyzing current policies and procedures

• developing policies and procedures for the new system

• defining company business flow with new system

• identifying and specifying new job descriptions and organization changes

• defining performance measurements

• defining methods for incorporating existing data into the new system

• defining system interface needs

• developing a plan for user education

• review the standard format used for documents such as checks and invoices. Identify your custom forms requirements and order any forms necessary. For more information and examples, see "Documents that Use Preprinted Forms" in the Getting Started online manual.

Data GuidelinesBefore you implement the system, review current policies and procedures used for your data. For example, here are some considerations:

• Each item used to build your products should have a unique item number and the information about each item should be accurate.

• Physical and procedural controls should be established for stockroom and receiving transactions related to manufacturing orders and for collecting and entering these transactions into the computer.

• Guidelines and responsibility should be established for filing and retaining invoices and statements.

User EducationUser education is essential to achieving your company objectives. The following education methods should be included to help users learn the system and make the implementation a success:

• general industry concepts and technology training

• system hands-on training

• company-specific system training

• specific, task-oriented education



Step 3: Completing Implementation PreparationSeveral preparation activities should be completed before you begin the work of hands-on implementation. Some of these final activities include:

• completing policies and procedures for the new system

• completing job descriptions and organization changes

• completing plans for user education programs

• developing and testing a conversion plan

• preparing an area within the company to perform a pilot implementation

Step 4: Preparing For System CutoverIt is recommended that you run the system with a subset of data before using the system in a production setting. A sample database gives you the flexibility to adjust your assumptions.

Some other activities could include:

• performing a full pilot implementation

• beginning user training programs

• conducting system audit of pilot implementation

• approving pilot implementation results

• beginning production system implementation

Sample DatabaseChoose various end products that represent your normal business operations. The data you load should support manufacturing the product from start to finish. This sample database can test the areas of:

• product lines, including common components

• items

• bills of material

• purchase, manufacturing and customer orders

• invoicing

• G/L, A/P and A/R

• planning



Loading Data into the SystemLoading your data into the system can be segmented into five phases:

• Phase 1: Initial Configuration

• Phase 2: Global Data

• Phase 3: Master Data

• Phase 4: Initial Balances

• Phase 5: Final Setup

These five phases are shown in the Implementation Checksheets. Each phase involves using screens in a specific order to load data and then validate the data.

• Phase 6: SAAM Installation Completion

This phase requires a manually initiated process to populate the SAAM database and to prepare your system for processing daily activities.

Analyze ResultsOnce the sample database gives you expected results, analyze your data and decide whether to continue the pilot implementation or restore your installation database—the database you backed up after installation and begin to implement the production system.

It may be necessary to adjust user education, policies or procedures based on the pilot implementation results. Identify and complete these changes before beginning user education using these policies and procedures.

Step 5: Implementing the Production SystemAfter completing your pilot implementation, you are prepared to follow the implementation schedule steps again for your production system. Implementing your new system can include the following activities:

• assigning a person to a "command post" position to assist all departments while implementing your new system

• loading data into your production database using the same process as the sample database

• loading data using the conversion methods defined during your planning process to enter large amounts of similar data into your system (items, bills and so on)

• establishing cutover dates from your existing system

• beginning to use the system for daily operations



Implementation Assumptions

Installed ModulesThe Implementation Checksheets assume that all modules are being implemented. If you are not implementing a specific module, you can skip its related steps. Use a printout of the INSTALL.HIS file, created on the server during installation, as a reference for which modules are installed.

Implementation steps can vary depending on configuration choices and the customer order entry functionality you have installed. These variations are identified as options within a specific step. The variations include:

• Tax System. Steps vary based on whether you have chosen a sales tax system or VAT (value-added tax) system. This selection is identified on the CNFG (System Installation Setup) screen.

• SOPM (Sales Order Processing) Module. Steps vary if you have installed the SOPM Module. There are additional steps needed, such as security, as well as different steps, such as when loading customers, customer orders and custom products. This module creates a Sales Order Processing icon in the Fourth Shift folder when installed.

Master Account Number ValidationMaster account number validation is performed throughout the implementation process. If you do not intend to use the General Ledger Module, master account number validation does not need to be performed.

Initial BalancesCutover dates need to be established for data entry of balances so that the system is an accurate baseline from which to start. It is assumed that general ledger balances, as of the cutover date, already reflect your inventory balances, item costs, open orders, invoices, payments, and so on. Therefore, the functions that are normally used to synchronize transactions with the general ledger are disabled during the Initial Balances phase. These functions include transaction creation flags set for accounts receivable and accounts payable as well as module communication files.

Initial balance assumptions are:

Data Initial Data

general ledger one of four options:- current-year budgets/plans and current-year actuals

- prior-year budgets/plans and current-year actuals

- prior-year budgets/plans and prior-year actuals entered as prior-period adjustments

- prior-year budgets/plans and prior-year actuals entered as current-period activity

inventory balances quantities reflect issues made to partially completed ordersquantities reflect receipts made against partially completed orders

purchase order lines quantities not yet received

purchase order deliv-eries

quantities not yet received



subcontracted items quantities not yet receivedcomponent quantities not yet issued to vendor

customer orders quantities not yet shipped to the customer

custom product orders

quantities not yet shipped to the customercustom product component quantities not yet issued to manufacturing order

manufacturing orders component quantities not yet issued to manufacturing order

A/P invoices unpaid balances

A/P debit memos unapplied balances

A/P payments unapplied amounts, have been applied against partially paid invoices or are not yet reconciled;payment application against invoices so that the unapplied amounts reflect the cutover datedebit memo application against invoices so that the unapplied amounts reflect the cutover date

A/R invoices unpaid balances

A/R credit memos unapplied balances

Data Initial Data



Implementation Recommendations

Data ValidationA validation tool is identified for each screen or task listed on the Implementation Checksheets. Use the validation tool to double-check the accuracy of the data you have entered. Validation tools include:

• Screen reports. Create these reports by choosing Print from the File menu. For more information, see "Screen Reports" in the Fourth Shift Basics online manual.

• Batch reports and log files. Batch reports are produced using batch processes set up on the BSET (Batch Process Setup) screen and launched using the BEXE (Batch Process Execution) screen. The batch process produces a log file which records the results of the batch process. This log file is created with the filename LOG.XXX to correspond to the batch process id. For more information, see "Batch Reports" in the System Administration online manual.

• Print screens. When other report options are not available, you can capture an image of your screen and use it to validate your data entry. For more information, see "Using the Print Screen Key" in the Fourth Shift Basics online manual.

Two data validation alternatives are also available:

• Create data extracts to export detail for review.

• Use an ODBC-enabled query tool to perform queries against the database.



Shared Data CoordinationField ValuesA number of screens contain fields that support functionality in several modules. The values of these fields should be coordinated by members of the implementation team. These fields are:

Screen Field Supported Module

CNFG

Address Format APSMARSMCPMMCUSMPURMSHPM

Deferred Update Option CPMMCUSMMOMM

Order Lead Time CPMMCUSMMOMMPURM

Print Text on Ext Documents CPMMCUSM

Resource Component CPMMMOMMPRCMPURMRPTMSFRM

CNFA

Product Line / Desc CPMMINVMMOMMPRCMPURM

Average Actual Cost Purchase Price Var CPMMMOMMPURM

Cost of Goods Sold ARSMCPMMCUSMSHPM

Cust Prod Variance CPMMCUSMPURM



CNFA(continued)

Cust Prod WIP Inv CPMMCUSMPURM

Item Cost Change CPMMMOMMPURM

Sales ARSMCUSMSHPM

Resource Fixed Ovhd CPMMMOMMPURM

Resource Var Ovhd CPMMMOMMPURM

Labor Variance CPMMMOMMPURM

Manufacturing Exp CPMMMOMMPURM

Manufacturing Order Cost Change CPMMMOMMPURM

Material Usage Var CPMMMOMM

Misc Order Var CPMMMOMMPURM

Purchase Order Cost Change CPMMMOMMPURM

Overhead Variance CPMMMOMMPURM

Resource Direct Lab CPMMMOMMPURM

Standard Cost Var CPMMINVMMOMMPRCMPURM

Item Master Detail from ITMB

Item Class:position 7

MRPM for:daily capacity




Preprinted FormsSeveral types of documents are formatted for preprinted forms.

• If you choose to use preprinted forms, develop a plan for the ordering, printing and distribution of these forms. A dedicated printer, for example, might be an option. Information on ordering preprinted forms is included in your Customer Care Package.

• If you choose not to use preprinted forms, make arrangements to customize the report templates used to generate the documents.

The following documents are designed to be printed using preprinted forms or customized report templates:

Item Class:positions 7 or 8 selection

SFRM for:daily capacity

SHCF

Freight APSMARSMSHPM

POCF (or APCF if PURM is not installed)

Unvouchered A/P APSMPURM

ARCF

Commission Expense ARSMCUSMSHPM

Commission Liab ARSMCUSMSHPM

COCF

Duplicate Customer PO Notification CUSM or SOPM

Check Credit Co Line CUSM or SOPM

Obsolete Item Enforcement for CO Entry CUSM or SOPM

Consume Customer Credit by Customer Chain

SOPM

Document Printed By

Checks and Check Vouchers APCW

Invoices and Credit Memos IVPR and IVRR

Customer Statements ARST




Time-Saving RecommendationsSeveral features are available to assist you in your implementation. These features allow you to more rapidly complete data entry tasks and improve data accuracy.

Data ImportUsing the data import features of the System Control Module, you can automatically enter data into the system. See the System Control manual for more information on data conversion techniques.

Data Entry AlternativesData sets can be copied and updated to reduce data entry time and ensure accuracy. The following screens/tasks provide a copy function you can use to enter similar data:

Order Acknowledgment COMT (individual order)BOPR (multiple orders)

Purchase Order POMT (individual order)BOPR (multiple orders)

Bill of Lading SBOL

Shipping Summary SBOL

Shipping Invoice Summary SBOL

Data Module Screen/Task Alternate

bills of material BILM BILL CBIL

routings BILM BILL CBIL

G/L report definitions GLSM GLRD GLRC

G/L report instructions GLSM GLRD ALT+S on existing line activates copy mode for new line

budgets/plans GLSM GLBU GLBR

ABC classifications INVM Item Master Detail from ITMB

ABCR

customer orders SOPM customer order applica-tion

customer order templates



Data Entry AssistanceThere are a number of features available to you to help the data entry effort.

• Default records. You can change the default record to match different sets of entries as you perform the implementation steps. For example, you can set up the Default-Item for standard items and then change the Default-Item for entering workcenters. For more information, see "Default Entries" in the Fourth Shift Basics manual.

• Default product line. You can establish default accounts used when new product line accounts are created. For more information, see "Product Lines" and "Defining Product Lines" in the Product Costing manual.

• Input Masks. Use setup masks when entering repetitive line items for customer orders, purchase orders, components, and inventory information. For more information, see "Default Data Entry Masks" in the Fourth Shift Basics manual.

Post-Implementation ConsiderationsOnce your initial data is loaded and you are running a production system, you should:

• perform ongoing audits

• determine which advanced features to add to your system

Auditing Ongoing System OperationAuditing system results involves checking data accuracy as you run the system. These audits should be performed as part of the implementation as well as part of the ongoing analysis of company objectives. Monitoring ongoing operations can include the following areas:

• establishing performance monitoring procedures

• modifying server and client configurations to improve performance

• monitoring data accuracy

• continuing user education

• conducting post-implementation audits

Utilizing Advanced System FeaturesThere are several features which can be tuned after you are in production. These features are included in the modules you installed during implementation as well as additional modules you can add to the system.

Message FilteringUse the MSCF (Message Configuration) screen to select which messages should be generated by buyer, planner and CSR. For example, you may wish to generate all action messages except OFR (order follow-up required) messages. You may use a method for tracking scheduled completion other than based on the Order Lead Time.

Use the CCFG (Costing Configuration) screen to assign users to respond to manufacturing and purchase order cost exception action messages, which display on the CCAN (Cost Control Action) screen. This feature is available for an average actual costing system only.



G/L Transaction SummarizationThe GLSC (G/L Source Code Maintenance) screen maintains information for:

• internal (Fourth Shift) manufacturing transactions

• internal (Fourth Shift) accounts payable, accounts receivable and invoicing transactions

• external (non-Fourth Shift) transactions

The system is shipped with predefined, pre-combined internal transactions. External transactions must be identified on the GLSC screen before they can be processed.

The Detail/Summary field is used to determine if transactions should be combined further (summarized) or batched in detail. When Detail/Summary = S (summary), transactions with the same transaction date and master account number are combined. The transaction detail is in the module communication file, but the detail information is not included in the batch. This might be useful for CROV (Cost Roll Over) transactions, for example. When transactions are combined in this way, the Trans Description = SUMMARIZED and the Reference fields on the G/L Transaction Detail screen are blank.

Before deciding to summarize a general ledger transaction, be certain that processes and controls are in place to capture the detail. When Detail/Summary = S (summary), a backup of the MODCOMGL.FIL and external G/L <filename>.FIL files is the only audit trail.

AutoclosureAutoclosure of orders and invoices is an option you can enable once you determine the level of control needed for these transactions and the transaction volume you are managing. Autoclosure options are:

Automatic Order Number AssignmentOnce you have entered existing orders using the original order numbers for audit purposes, you can take advantage of the automatic Order Number Assignment feature. The Order Number Assignment feature provides a suggested order number during the order creation process; you select the desired format and the system automatically suggests the next sequential order number. Using the suggested order number ensures consistent and sequential identification of orders.

Order number formats can serve several purposes, such as:

• assigning a range of order numbers used by a planner or buyer

• assigning a range of customer order numbers by region, representative or type of customer order

• providing lot traceability

Order number assignment can be established for purchase, manufacturing and customer orders.

Data Screen Field

purchase orders POCF Autoclose Purchase Orders

manufacturing orders CNFG Autoclose Manufacturing Orders

customer orders SHCF Activate Autoclose Capability

invoices A/R Application Options from ARCF

Prompt Before ClosingTolerance AmtTolerance %



• For purchase or manufacturing orders, see the System Control manual for more information.

• For customer orders entered using the CUSM Module, see the System Control manual for more information.

• For customer orders entered using the SOPM Module, see the Sales Order Processing manual for more information.

Follow-on ModulesThere are several modules you can install to provide advanced management, advanced analysis support or alternative data entry methods. Consider adding these modules to enhance system usability:

Review the manuals for each of these modules to become familiar with their features and functionality. These modules are not included in the Implementation Checksheets. See the “Add-On Modules/Licenses” section in the System Administration manual when you are ready to begin the implementation.

Field-level SecurityThe SOPM (Sales Order Processing) Module allows you to restrict access of sensitive information, down to the field level. Security is assigned at the group level. A group contains one or more users with related security access requirements. Once you are in production, you can determine what field-level security, if any, is required.

Site ProceduresYou can use Fourth Shift's customizable site help feature to communicate details about how to use particular screens or tasks to the users in your company. Site help can also link to standard operating procedures, the Business Procedures module, or any available Internet or intranet site.

Consider taking advantage of the customizable site help feature after your operating procedures are in place and tested with the system for accuracy. See "Customizing Site Help" in the System Administration manual for details on developing site help for your company.

Next Step: Use Implementation Checksheets to enter your production data.

Module Id Module Name Function

APBM Advanced Price Book alternate data entry

BISM Business Intelligence advanced data analysis

CSHM Cash Management advanced bank management

CSTM CIM Customizer alternate data entry

EDIM Electronic Data Interchange alternate data entry

ENGM Engineering alternate data entry

MGRM Management Reports analysis

OPFM Operations Performance analysis

PYCM Payroll Connection alternate data entry

RBPM Rules Based Pricing alternate data entry

SAAM Sales Analysis analysis

SCRM Screen Customizer advanced system management


Fourth Shift Release 7.50 R2 Implementation Checksheets

Implementation ChecksheetsThe Implementation Checksheets provide the order for loading information into the system to achieve the best results. Once again, these checksheets assume the entire system is being implemented. Skip the steps that do not pertain to your own implementation. A checksheet is included for the following phases:

• Phase 1: Initial Configuration

• Phase 2: Global Data

• Phase 3: Master Data

• Phase 4: Initial Balances

• Phase 5: Final Setup

Each checksheet includes the following columns:

• Screen/Task is the screen, window or task used to perform the loading step. Detail screens and windows also identify the main screen from which they are accessed. Use the help for details on how to use each screen or task.

• Module identifies the business application which includes the screen, window, task, view, or dialog box. Use the Module column to determine if you need to perform the loading step based on what has been installed for your system.

• Description identifies the data being loaded. Use the "Before You Implement the Module" and "Preparing Your Data for Loading" topics in each manual for detail considerations. See the Time-Saving Recommendations topic for data entry assistance tips.

• Validation identifies the method you can use to verify your entries. See Data Validation in Implementation Recommendations for validation alternatives.

• By/Date is the area you can use to record step completion.

Screen/Task Module Description Validation By/Date



Phase 1: Initial Configuration

System Configuration

Users and Access Controls


CNFG SYSM company information;taxing method displayed

print screen

File Writing Config-urations from CNFG

SYSM Decide if using real-time function for data loading

print screen

APEX APSM Define A/P Queue Pro-cessing Status

print screen

AREX ARSM Define A/R Queue Pro-cessing Status

print screen

GLEX GLSM Define G/L Queue Pro-cessing Status

print screen


FCMT SYSM access codes for each screen and tasksecurity for inventory moves and adjustments:use the IHI1 Function Codesecurity for lot creation and lot splits:use the LO1T Function Code

screen report

PASS SYSM password and authorized access codes for each user

screen report

PASS SYSM review access of unlim-ited-access user (AAA);modify password or replace AAA with new unlimited-access userNote: Be sure to have at least one user with unlim-ited access for administra-tive purposes.

screen report



Users and Access Controls: SOPM Module

Phase 2: Global Data

Fiscal Calendar and Account Number Format

G/L Organizations

G/L Organization Groups (optional)


User Security application

SOPM user id and passwords print screen

Group Security application

SOPM security groups print screen

Group Security Detail application

SOPM group security rights print screen


GLCF SYSM account number format and accounting cycleUse GLSM manual as ref-erence

print screen


GLOS GLSM organizations and organi-zation groups

screen report


GLOT GLSM organization’s direct and indirect members

screen report

G/L Organization Group/No List win-dow from GLOT

GLSM organizations screen report



Chart of Accounts

Account Groups (optional)

Group Combinations (optional)

Valid Account/Organization Combinations (optional)


GLCA GLSM predefined Chart of Accounts modification

screen report

G/L Account Attributes window from GLCA

GLSM user-defined information for each accountcurrency code for each cash account and accounts used in foreign cash reference transac-tions

print screen


GLAG GLSM account groups screen report

GLAT GLSM account group’s direct and indirect members

screen report

G/L Account Group/No List win-dow from GLAT

GLSM G/L accounts and account groups

screen report


GLGQ GLSM organization/account com-binations for inquiring against current period activity

screen report


GLAV GLSM valid or invalid organiza-tions for use with specific G/L accounts

screen report



External G/L Transactions

Bank Master

TaxesSales Tax System


GLSC GLSM non-Fourth Shift transac-tions to be interfaced with the general ledger

screen report


BKMT GLSM bank master records screen report

Name, Address & Contacts window from BKMT

GLSM bank contactsbank account must match G/L account number on GLCA

print screen

Cash Receipts win-dow from BKMT

GLSM master account number defaultsmust match Cash G/L account number on GLCA

print screen

Disbursements window from BKMT

GLSM master account number defaults, check format and payment referencemust match Cash G/L account number on GLCA

print screen

BKMT GLSM active bank status: St = 4 screen report

Banking Configura-tion window from GLCF (ALT+F8)

GLSM banking configuration;security for banking trans-actions

print screen


TXTA SYSM default Tax Code = 99 or 999 for each tax authority; recommend using Tax Rate = 0 for default tax codestax codes for each taxing authority

screen report

Tax Base Calcula-tion Mask window from TXTA

SYSM default tax base calcula-tion mask specific tax base calcula-tion masks

print screen



VAT System

Currency

Costing Methods

Shop Calendar


TXCF SYSM taxing authorities and VAT Id

print screen

TXTA SYSM default Tax Code = 99 for each tax authority; recom-mend using Tax Rate = 0 for default tax codestax codes for each taxing authority

screen report

Tax Base Calcula-tion Mask window from TXTA

SYSM default tax base calcula-tion mask specific tax base calcula-tion masks

print screen

TXCF SYSM default tax codes and descriptions modifications

print screen

VATT SYSM product code/customer code relationships

screen report


CCMT SYSM local currency description, symbol and symbol loca-tionforeign currency codesEMU member status (if applicable)

screen report


CNFC SYSM costing types print screen

CCFG SYSM costing configuration;exception message reviewers for average actual costing

print screen


Shop Calendar SYSM calendar reflecting actual work schedule

print



Text Library

Commissions

Database Backup

Phase 3: Master Data

Module Configurations


TEXT SYSM standard text messages:Text Type = M or Fglobal extended text mes-sages;Text Type = G

screen report


CMTA ARSM or CUSM

commission codes screen report


Backup software n/a back up database and related files

media verifi-cation


MCCF MCMM euro currency code consolidation currency codecurrency conversion rounding gain/loss master account numbers (if appli-cable)currency exchange vari-ance master account num-bers

print screen

CCEX MCMM currency exchange rates for:- operating (local) currency- local banking currency- customer currencies- vendor currencies- bank currencies

screen report



APCF APSM A/P configurationSet the following field to stop general ledger trans-actions during initial data loading:Create G/L Transactions from A/P Invoice Entries = N

print screen

COCF CUSM or SOPM

Customer Order Entry Configuration

print screen

MOCF MOMM Manufacturing Order Man-agement Configuration

print screen

POCF PURM purchasing configuration print screen

ARCF ARSM A/R configurationSet the following two fields to stop general ledger transactions during initial data loading:Create G/L Transactions from IVIE CR Memo Entries = NCreate G/L Transactions from IVIE Invoice Entries = N

print screen

A/R Application Options window from ARCF

ARSM autoclosure and default entry optionsautoclosure variance account number

print screen

ARAD ARSM aging periods print screen

SHCF SHPM shipping configuration print screen

LTCF LOTM lot and serialization config-uration

print screen

SYSM default values for setup windows and screens

print screen

SYSM shop floor parameters print screen

FS.CFG file n/a CELSLotSizes configura-tion variable that defines default values for the Lot Size Estimate field.

print file

EmbeddedRevPrefix configuration variable that defines the revision prefix. Default is REV.

WorkCenterDelimiter configuration variable that defines default delimiter as brackets [ ].




Vendors

WorkCenterItemClass configuration variable that defines the location of the workcenter capacity in the Item Class field. Default value if not present is 7.


VEID APSM or PURM

default vendor values:Vendor Id = 000000

screen report

Vendor Master Detail from VEID

APSM or PURM

default vendor values:Vendor Id = 000000

print screen

VEID APSM or PURM

vendor identification screen report

Vendor Master Detail from VEID

APSM or PURM

vendor detail print screen

Vendor Configura-tion

PURM vendor performance crite-ria

print screen

Vendor G/L Accounts (optional)

APSM or PURM

Default vendor values:Vendor Id = 000000

print screen




CustomersWithout the SOPM Module

With the SOPM Module


CUID ARSM or CUSM

default customer values:Customer Id = 000000

screen report

Customer Name/Address Detail from CUID

ARSM or CUSM


print screen

Customer Financial Detail from CUID

ARSM or CUSM


print screen

CUID ARSM or CUSM

customer identification screen report

Customer Name/Address Detail from CUID

ARSM or CUSM

address informationdefault values for Ship Id = 000000 multiple sets of shipping information for each cus-tomerSelect Cust Class field position 1-6 for sales anal-ysis

print screen


ARSM financial information print screen


Trade Class appli-cation

SOPM values for DEFAULT-CLASS

FBV query of FS_Trade_Class

Trade Class appli-cation

SOPM trade classes FBV query of FS_Trade_Class

Customer applica-tion

SOPM default customer values:Customer Id = 000000

FBV query of FS_Customer

Customer applica-tion

SOPM customer information FBV query of FS_Customer



Locations

National Motor Freight Codes

Interface Accounts

Items


LMMT INVM stocking locationslocation for each parent item, component item or bill of material structure, based on backflushing method

screen report


NMTA SHPM NMFC item information screen report

Article Description window from NMTA

SHPM expanded NMFC item description and released/actual value data

print screen


Master Account Number Detail from CNFA

SYSM define product linesdefine accounts for use by product line

print screen


ITMB INVM default values for Default-Item

screen report


INVM default values for Default-Item

print screen

Item Master Plan-ning Detail from ITMB


print screen

Item Lot Trace And Serialization Detail from ITMB


print screen

ITMC INVM default inventory account for Default-Item

screen report



ITMB INVM items for each ECN class/ numberstandard item identifica-tion:Rev field change for each affected item to reflect the new revisionlot-traced and/or serialized item identificationproduction-plan items used for custom productsco-product items as nor-mal material (Item Type = N)

screen report


INVM reference detailItem Class field positions:- price book selection criteria- ABC class code- preferred part code- product line code- sales analysis sort

Alternative:Use the ABCR task, after the initial planning run, to update the ABC class code

print screen


INVM planning parameters print screen

Item Lot Trace And Serialization Detail from ITMB

INVM lot and serial parametersbackflush enabled using Backflush Policy field

print screen

ITMC INVM inventory master account number for each item each item:at-this-level costs each co-product:at-this-level costs using Cost Code = 0each item:product line

screen report

ITMC or ITCB INVM each co-product:total rolled costs

screen report




Workcenters

Alternate Item InformationWith the SOPM Module

Bills of Material


Workcenter Master SFRM default workcenter values for Default-Item

screen report

ITMC INVM default workcenter values for Default-Item

screen report


INVM daily capacity:Item Class field position 7

print screen

ITMC INVM labor and overhead rates associated with a work-center

screen report

Master Account Number Detail from CNFA

SYSM Labor and overhead mas-ter accounts based on the workcenter product line

screen report


Item application SOPM alternate item information print screen


BILL BILM bill of material information for each parent item

screen report

addition of revision history component for each affected parent

configuration bills

planning bills

Bill of Material Detail from BILL

BILM component text and detail information

print screen



Routings

Item Prices and Catalog Data

Customer ItemsWithout the SOPM Module



BILL BILM routings screen report

Bill of Material Detail from BILL

BILM operation description print screen


ITPB CUSM standard prices for items screen report

CCAT CUSM customer catalog item cross references

screen report


CIMT CUSM specific customer configu-rations for a family item

screen report


Customer Item application

SOPM customer item cross refer-ences

print screen



Default Documents/Orders

Default Customer OrdersWithout the SOPM Module



IVIE ARSM default values for invoices:Ref No = Default-InvoiceRef Seqn = 0000

screen report

Invoice Header Detail from IVIE

ARSM default values for invoices print screen

IVIE ARSM default values for credit memos:Ref No = Default-CR-MemoRef Seqn = 0000

screen report


ARSM default values for credit memos

print screen

IVIE ARSM default values for walk-in cash sales:Ref No = Default-Walk-InRef Seqn = 0000

screen report


ARSM default values for walk-in cash sales

print screen

MOMT MOMM default values for Default-Order

screen report

Purchase Order Header Detail win-dow from POMT

PURM default values for Default-Order

print screen


COMT CUSM only default values for Default-Order

screen report


Customer Order application and related tabs

SOPM default values for Default-Order

order acknowledg-ment


SOPM customer order templates order acknowledg-ment



Master Account Verification

Database Backup

Cost Roll-upFor average actual costing, cost roll-ups may be done initially, but then never again. The system is used to update costs as part of daily operations.


ACCT SYSM batch process:analyze current accounts

log fileACCT report



media verifi-cation


CNFC SYSM cost type for simulation or budget purposes

print screen

CROV and CROL PRCM batch process:CROV task: exchange product costs between Cost Type 0 and the simulation cost type.CROL task:calculate product costs for the simulation cost type.CROV task:copy calculated product costs from the simulation cost type to Cost Type 0

log file



Cost Roll-up Verification

Backflushing Task Setup

Database Backup


ITCB INVM total cost for each item screen report

ITMC INVM all costs defined for each item

screen report

CSLB PRCM costs for each parent item and related first-level com-ponents

screen report

CMLB PRCM costs for each parent item and all related compo-nents

screen report

INVR INVM batch process:inventory values sorted by master account number

log fileINVR reportThe values should recon-cile to the G/L Inventory account bal-ance.


BKFL or BKSV RPTM batch process:backflushing

screen report from BSET



media verifi-cation



Phase 4: Initial Balances

General LedgerSee “Loading Beginning Balances” in the General Ledger manual for a flowchart version applicable to your information requirements.

Option 1: No Historical Data

Option 2: Prior-Year Budgets/Plans


GLJE GLSM beginning balance JEsBatch Status = S

screen report

GLAU GLSM batch process:account update process

log fileGLAU reports

GLTG GLSM batch process:trial balance

log fileGLTG reports

GLDQ GLSM master account activity screen report

GLGQ GLSM group activity screen report

GLPC GLSM batch process:period close

log fileGLPC reports


GLPC GLSM batch process:period close of each period up to one period prior to current period



screen report











Option 3: Prior-Year Budgets/Plans and Prior-Year Actuals as Prior-Period Adjustments

Option 4: Prior-Year Budgets/Plans and Prior-Year Actuals as Current-Period Activity


GLPC GLSM batch process:period close of each period up to current period


GLJP GLSM beginning balance and net activity as prior-period JEsBatch Status = S

screen report









screen report











Option 5: Repeat for Each Prior Period

Database Backup

Master Account Limits (optional)

Budgets and Plans


GLJE GLSM net activity JEsBatch Status = S

screen report










backup software n/a back up database and related files

media verifi-cation


G/L Master Account Detail from GLMA

GLSM balance and transaction limits for each master account

print screen


GLBD GLSM budget/planning types screen report

GLBU GLSM budgets and plans GLBL



Financial Reports

Inventory

Forecast

Production Plan and Master Production Schedule


GLRD GLSM sample report modificationnew reports

GLRL

GLRP GLSM batch process:financial report print

log fileprinted reports

GLRD GLSM report definition modifica-tions

GLRP


INVA INVM inventory balances by stocking location and inventory codeinventory balances for backflush locationLots for existing inventory

SSII or SSIL


FCST MRPM independent demand fore-cast

screen report


MSMT MRPM production plan for each production-plan item

screen report

SDAL or SDAB MRPM master-scheduled item review

screen report from SDAL orSDAB report

MSMT MRPM master production sched-ule for each master-sched-uled item

screen report



Open PO Contracts

Released Purchase Orders


POCT PURM open contracts;use original identifiersdefault contract by vendor:use PRICE-QUOTE

screen report: singlePOCR: batch mode


Purchase Order Header Detail win-dow from POMT

PURM purchase orders;use original identifiersblanket purchase orders:use Blanket Order = Y

n/a

POMT PURM line itemsmultiple scheduled deliver-ies:ALT+M from line item

n/a

Purchase Order Line Item Detail window from POMT

PURM line item detail n/a

POMT PURM purchase order print screen report: singleBOPR: batch mode

PICK PURM order-dependent bill of material for subcontracted item (Ln# Typ = S)

screen report: singleBOPR: batch mode

Picklist Detail from PICK

PURM component detail print screen

PICK PURM picklist print screen report: singleBOPR: batch mode



Released Customer Orders: Standard ItemsWithout the SOPM Module



COMT CUSM header and lines;use original identifiers

n/a

CO Header Detail from COMT

CUSM header detail n/a

Standard Product Detail from COMT

CUSM line detail n/a

COMT CUSM order acknowledgment print




SOPM header and lines;use original identifiers




Released Customer Orders: Custom ProductsWithout the SOPM Module



COMT CUSM header;use original identifierslines for family item

n/a

OPSL or CPMT CPMM configure custom product: option selection or direct definition

screen report

Custom Product Detail from CPMT

CUSM header detail n/a

Custom Product Component Detail or PO Line Item Detail from CPMT

CUSM line detail n/a

CPMT CPMM custom product price n/a

COMT CUSM order acknowledgment print


JEST CPMM Optional:custom product estimate

screen report



SOPM header and lines;use original identifiers


Customer Item application

SOPM configure custom product print screen

Line Item Details + Custom Product tab from Customer Order Line Item grid

SOPM custom item detail print screen



Released Manufacturing Orders

MODCOM File DeletionDelete these files to have a clean start for production usage.

A/P Outstanding Documents


MOMT MOMM header and lines;use original identifiers

n/a

Manufacturing Order Line Item Detail

MOMM line detail n/a

PICK MOMM order-dependent bill of material.

n/a

Picklist Detail from PICK

MOMM component detail n/a

MOMT MOMM manufacturing order and picklist print



MFGSYS directory n/a MODCOMGL.FIL deletion directory review

MFGSYS directory n/a MODCOMAP.FIL deletion directory review

MFGSYS directory n/a MODCOMIV.FIL deletion directory review

MFGSYS directory n/a MODCOMSA.FIL deletion directory review

MFGSYS directory n/a MODCOMSL.FIL deletion directory review


APIE APSM invoices that have unpaid balances as of the cutover datedebit memos as of the cutover date

APRG



A/P Payments


APDS APSM payments that have unap-plied amounts,have been applied against partially paid invoices or are not yet reconciled as of the cutover date

screen report

G/L Distribution from APDS

APSM reversing entries so that the master account impact is zero, if necessary

screen reportVerify the sum of the debit and credit amounts, for each master account, equals zero

APCK APSM payment verification APCK report

APPA APSM payment application against invoices so that the unapplied amounts reflect the cutover date

screen report

G/L Distribution from APPA

APSM reversing entries so that the master account impact is zero

screen reportVerify the sum of the debit and credit amounts, for each master account, equals zero

APPA APSM debit memo application against invoices so that the unapplied amounts reflect the cutover date

APPH

APRC APSM payment clearing for those which have been recon-ciled as of the cutover date

screen report



A/R Outstanding Documents

APAG and APTB APSM batch process:- account aging- aged trial balance

log fileAPTB reportThe A/P Aged Trial Balance must recon-cile to the general led-ger balances.You can also use the Ven-dor Master Detail screen to review aging catego-ries by ven-dor.


IVIE ARSM outstanding invoices and credit memos as post-printed documents

n/a


ARSM outstanding invoice and credit memo detail

n/a

Invoice Line Item Detail from IVIE

ARSM outstanding invoice and credit memo lines

n/a

TEXT SYSM Optional:text message (Text Type = F) that can be included on each printed document

screen report

IVRR ARSM reprinting batch process:IVRR task: invoicesIVRR task: credit memos

log filedocuments marked as reprinted

ARIR and ARCJ ARSM batch process:- invoice register- credit memo journal

log fileARIR reportARCJ report

ARAG ARSM batch process:age accounts

log fileARAG reports

ARSC ARSM batch process:calculate service charges

log fileARSC report

ARSR ARSM service charge adjust-ments to match service charge balances as of the cutover date

ARSR report

ARTB ARSM batch process:aged trial balance

log fileARTB reports




Database Backup


ARSM aging categories by cus-tomer

print screenThe ARTB report and the A/R account aging bal-ances must reconcile to the A/R mas-ter account general led-ger balances.

GLSS GLSM ARSC and ARSR batches generated by creating and adjusting service charge invoices

screen report

GLJE GLSM reversing entries for the ARSC and ARSR batches so that the master account impact is zero

screen report

TEXT SYSM Optional:text message (Text Type = F) that can be included on each customer state-ment indicating that the statements represent the cutover balances

screen report

ARST ARSM batch process:A/R statement print

log fileARST docu-ments



media verifi-cation




Initial Planning Run

ABC Classifications


PLNG, PREV and SREV

MRPMCUSM or SOPM

batch process:- MRP planning using level-by-level method- period review- shipping review

log fileSDAL or SDAB report


INVM necessary item parameter adjustments

print screen


ABCR MGRM batch process:usage value calculations and ABC class update

log fileABCR report



Phase 5: Final Setup

Real-time Configuration Setup

G/L Communication Reset

Preprinted Form AlignmentSeveral types of documents are formatted for preprinted forms. The following documents have an alignment test which can be used to test the document layout against the preprinted form loaded in the printer before processing begins. This step is necessary only if you are printing these external documents on preprinted forms.

See "Printing External Documents" in the System Administration manual for more information on preprinted form alignment.


File Writing Config-urations from CNFG

SYSM Decide if using real-time functions

print screen

APEX APSM Define A/P Queue Pro-cessing Status

print screen

AREX ARSM Define A/R Queue Pro-cessing Status

print screen

GLEX GLSM Define G/L Queue Pro-cessing Status

print screen


APCF APSM Set the following field for normal operations:Create G/L Transactions from A/P Invoice Entries = Y

print screen

ARCF ARSM Set the following two fields for normal operations:Create G/L Transactions from IVIE CR Memo Entries = YCreate G/L Transactions from IVIE Invoice Entries = Y

print screen


APCW and APCR APSM checks and check vouch-ers

alignment test

IVPR and IVRR ARSM batch process:invoices and credit memos

log filealignment test



Printer Selection

Database Backup

ARST ARSM batch process:customer statements

log filealignment test

SBOL SHPM bill of lading alignment test

SBOL SHPM shipping summary alignment test

SBOL SHPM shipping invoice summary alignment test


Report Destination window (ALT+P) from CIM Custom-izer

SYSM report destination options for CIM Customizer

print screen



media verifi-cation




Phase 6: SAAM Installation CompletionIf the Sales Analysis module (SAAM) is installed and after all data has been loaded into Fourth Shift, you can now initiate the Initial Load of data into the Sales Analysis tables. Contact your consultant or CSP for more information and assistance.

• The first process involves the program SAAMINST. This executable loads items, customer, accounts, shipments, invoices, etc.

• The second process creates the SAIncrementalLoad DTS package.

SAAM Initial Load1. Locate and delete the modcomsl.fil file in the mfgsys directory.

Important: Failure to eliminate this file will create an error message that will stop the installation.

2. Open a Command prompt window, from the Fourth Shift server, and go to your mapped drive. (example M).

3. Go to the MFGSYS\SAAM directory.

4. Enter SAAMINST with the following parameters: -cm:\mfgsys\fs.cfg-uxx-pyyyyy

- cm:\mfgsys\fs.cfg—is the location of the fs.cfg file

- uxx—is the SQL Server system administrator user id (usually “sa”)

- pyyyyyy—is the SQL Server password

The Fourth Shift SAAM on SQL Installation window is displayed.

5. Click Next after closing all programs.

The parameters window is displayed.

6. Complete the fields as follows:

- Company Name and the GL Account Mask are display-only default values.

Click the drop-down arrows to select values for the following fields:

- Sales Analysis Cost Type (other than Cost Type = 0), and the appropriate

- Customer Class

- Item Class numbers

7. Click Next and verify the information displayed.

8. Click Finish to initiate the Initial Load.

- A progress window is displayed then the Successfully completed message.

9. Click OK to close the message.

The SAAMINST.log file is displayed.

10. Verify that there were no errors in processing, then click Done.



Create the SAIncrementalLoad DTS PackageTo create the SAIncrementalLoad DTS package, you will need to run the fcmtsaam.exe.

1. Open a DOS prompt window, from the Fourth Shift server, and go to your mapped drive.

For example: M.

2. Go to the MFGSYS\System directory.

3. Enter the following parameters: fcmtsaam-cm:\mfgsys\fs.cfg

-cm:\mfgsys\fs.cfg—is the location of the fs.cfg file

4. Verify the process was completed successfully.

5. Open Microsoft SQL Server Management Studio and connect to the Database Engine.

6. Go to Management\legacy\Data Transformation Services to verify that the XX_SAIncrementalLoad DTS package exists, where XX is the system identifier characters (SystemIdentChar).

Set Up the SAAM Parameters for the Incremental Load Process1. Go to Fourth Shift Tools\Sales Analysis on the Fourth Shift Server and select the

SAConsole.

2. Complete the processing parameters for fiscal periods, GL Accounts, Customer Class, Item Class, and Region.

Note: For additional information on the Sales Analysis (SAAM) configuration, see Using the Sales Analysis Console in the Sales Analysis on SQL Server online Help.

E-mail NotificationVerify that the E-mail Notification has been set up for error reporting.

See the E-Mail Notification topic in the Sales Analysis on SQL Server online Help.

Confirm that the Incremental Load DTS Package is Implemented1. Go to Fourth Shift Tools\Sales Analysis on the Fourth Shift Server and select the

SAConsole.

2. Select the Data Load tab and click the Load button.

The Execute the Incremental Load window is displayed and the process steps.

Note: When the Status for each step is updated to Completed, the Begin and End time for each step is added.

3. Click OK to close the Process completed successfully message.

4. Click Cancel to close the Incremental Load window.

5. Click Cancel to exit from SAConsole.


Fourth Shift Release 7.50 R2 Appendix

Appendix

Implementing Net UIFourth Shift can be installed and used through a Web page. The Fourth Shift Web page can be used to complete a remote workstation installation and to access Fourth Shift after completing the required server modifications.

See the Net UI manual for more information about implementing the Net UI Module.

Implementing My Fourth Shift WorkplaceMy Fourth Shift Workplace is an optional module that allows you to run Fourth Shift in conjunction with a web server. Users interact with the Fourth Shift WebUI and customizable portals through a web browser such as Microsoft Internet Explorer.

See "Installing My Fourth Shift Workplace" in the My Fourth Shift Workplace manual for more information about implementing WebUI and My Fourth Shift Workplace.

SETUP Error Messages

Severe MessagesSevere messages indicate that a problem was detected in your installation environment. These errors require action before you can continue with the installation.

Failed to connect to SQL Server on <computer name>. Cannot determine if database already exists.A connection with the server can not be established. The most common causes of this error are:

- incorrectly typing the server name

- trying to connect to a server that does not have SQL Server installed

- entering an invalid user name and password combination for the SQL Server login (sa)

Verify that all information was entered correctly and that the server has SQL Server installed. Try to continue with the installation.

FINXX Service not stopped.The FINXX service is running and the database update can not continue. Stop the FINXX service on the server and restart Setup.

Lockserver Service not stopped.The Lockserver service is running and the database update can not continue. Stop the Lockserver service on the server and restart Setup.

MAINXX Service not stopped.The MAINXX service is running and the database update can not continue. Stop the MAINXX service server and restart Setup.



A selected module has as a prerequisite a module for which you do not have a license. Please contact Fourth Shift Customer Support for further details.You have selected a module for which you do not have a license for its prerequisite. An adjustment must be made in your license information. Contact Fourth Shift Customer support for additional instructions.

Server installation must be completed before completing this workstation installation.The version of Fourth Shift on the server is older than the version of the workstation installation being attempted. The server installation must be completed before the workstation installation. Update the server installation and then try the workstation installation again.

Setup has determined that Fourth Shift SQL services are running. Shut down all running Fourth Shift services and restart SETUP.At least one of the Fourth Shift SQL Server database services is running. Verify that both the MAINXX and FINXX database services are stopped and restart SETUP. If you have multiple sets of Fourth Shift database services running with different system identifiers, such as MAINMR and MAINML, all services must be stopped before restarting setup.

Setup is unable to open the database. Make sure the database is running and restart Setup.The database could not be opened. Verify that the databases are running and restart the setup program.

TCP/IP is not installed on this machine. Setup cannot continue.The installation program cannot find the SERVICES file. This file is present in the system root directory on machines with TCP/IP installed. Verify that TCP/IP is properly installed.

The Fourth Shift database required the use of 1252 ISO binary sort order, but the SQL Server installation uses a different sort order. The installation cannot proceed using this SQL Server installation.The current SQL Server installation does not use 1252 ISO binary sort order. This sort order is required by the Fourth Shift databases. Discontinue the Fourth Shift setup program on the current SQL Server installation and use an installation with the required sort order.

If you are using an existing SQL Server installation, it must be uninstalled and reinstalled with the correct sort order, or another SQL Server installation must be used.

The login parameters specified for the system administrator do not register as a SQL Server system administrator login. The login specified must be a member of the sysadmin security role.The SQL Server system administrator login name you specified is not a member of the sysadmin security role. Click the Back button to get the appropriate screen and specify another login name that is a member of the sysadmin security role.

The module access key is invalid.You have entered a module access key which does not contain the required information. Insert the Module Access Key diskette and reread the file to obtain the correct module access key.



The serial number is invalid.You have manually entered a system serial number which does not contain the required information. Insert the Module Access Key diskette and reread the file to obtain the correct serial number or retype the information.

This module access key is not valid for this serial number.You have entered a system serial number and module access key combination which does not contain the required information. Insert the Module Access Key diskette and reread the file to obtain the correct information.

Unable to access license information. The currently installed version is incompatible with this installation. Review your update instructions.You have tried to start an installation for a release which is incompatible with your current installation. For example, you have tried to install updates to modules before completing the necessary database updates. Use the Release Instructions document for this release to update the license information stored in your database before trying this installation again.

Unable to copy files. Check free space, access rights and file locking.The SETUP program is trying to install files to a specific location and the files cannot be copied. Verify that free space is available in the location listed. Also verify that you have network rights to write files to this location, and that the file is not locked (in use). In some cases, this message is displayed when the file already exists and it was expected to be read-only and it is not. If the file already exists, delete or move the file before continuing.

Unable to load required dll file.The SETUP program was trying to complete a process when required access to a specific network DLL. In most cases, this error is caused by the FSSETUP.DLL file being unavailable. If the network components were installed incorrectly in your Windows environment, this DLL may not be available. Reinstall the network components for your Windows environment before trying the SETUP program again.

Unable to open module access key file: xxxxxxxx.KEYThe module access key file located on the Module Access Key diskette is either damaged or formatted incorrectly. Verify that you are using the diskette shipped with your system. Contact Customer Support for assistance in obtaining a new module access key file if necessary.

Unable to open the Fourth Shift configuration file: xxxxxxThe FS.CFG configuration file you specified cannot be accessed. This may occur if another user has opened the file while you were completing the installation. Verify that no users are accessing the FS.CFG file and retry.

Unable to write to xxxx. Check free space, access rights and file locking.The SETUP program is trying to install files to a specific location and the files cannot be copied. Verify that free space is available in the location listed. Also verify that you have network rights to write files to this location, and that the file is not locked (in use). In some cases, this message is displayed when the file already exists and it was expected to be read-only and it is not. If the file already exists, delete or move the file before continuing.



Workstation installation files (xx.xx.xxx) are older than currently installed server files (xx). Install from the current CD-ROM or ClientDir directory.The workstation installation being attempted is an older version than the corresponding server installation version. Verify that you are using the current CD-ROM or are running setup from the latest ClientDir location and try again.

You must be signed on with System Administrator access for this workstation before you can complete this installation. Log on as System Administrator and try again.You are currently not using a user name with system administrator rights. Use a different user name that has system administrator rights on this workstation and restart Setup.

You must restart your computer before proceeding with this installation.One or more of the installed Fourth Shift components requires that the computer be restarted. SETUP cannot continue until this is done. Restart the computer. The SETUP program resumes automatically.

Warning MessagesWarning messages usually indicate that a value was entered into a field which does not meet the Fourth Shift-specific system rules. For example, a required field was left blank on a SETUP dialog box.

Error 432 Setup has detected that unInstall Shield is in use. Please close unInstall Shield and restart Setup.This message may appear if Setup has inadvertently been started more than once. You do not need to restart Setup and can ignore this message.

Invalid <locksrvr or tdenet> port entry in xxxxxx. SETUP cannot continue.An invalid Lockserver or tdenet port number was detected in the \WINDOWS\SYSTEM32\DRIVERS\ETC file. Verify that the port number in this file

Only A through Z, 0 through 9, or '-' are valid characters in this field.The currency code you entered contains an invalid character. Enter another currency code that contains only A through Z, 0 through 9 or "-".

The currency code must be from 1 to 5 characters.A currency code is required to complete the installation. The currency code is assigned as your local currency for your Fourth Shift system. See Before You Install for more information if you need additional assistance before entering your selection.

The file, xxxxxx, is not a valid KEY file.You have selected a module access key file which does not contain the required information. Insert the Module Access Key diskette and reread the file to obtain the correct module access key.



The specified database already exists. Continuing will destroy all data stored by Fourth Shift. Continue anyway?The SQL Server database name you have specified already exists. If you continue with the installation the data stored in the existing database will be lost. If you do not wish to overwrite existing data, change the System Identifier for this installation. If you wish to overwrite the existing data, click Continue.

The xxxxxx configuration file cannot be opened.A configuration file is required for the file installation process. The file you have entered cannot be opened. You must have sufficient network rights and no other user can be accessing this file. Try to resume the installation after verifying that you can access the file.

The xxxxxx configuration file does not exist.A configuration file is required for the file installation process. The file you have entered does not exist in the location specified. Check for entry errors or click Browse to locate the file yourself.

This program requires VGA or better resolution.The computer being used does not have 640 x 480 or better video resolution. This is the minimum resolution required for this program. Upgrade the computer as needed and restart SETUP.

This version of Fourth Shift (xx.xx.xxx) is older than your currently installed version (xx). Setup cannot continue.You have tried to start an installation for a release which is prior to the release you already have installed. Prior releases cannot be installed over an existing system. If you need to reinstall a prior release, install to a new location.

Setup was unable to set the xxxxxx environment variable.An error occurred when setting the specified environment variable. Go to Control Panel, Settings, System and the Environment tab. Review the current list and add the variable manually.

Unable to open log file.The INSTALL.HIS file cannot be accessed. This may occur if another user has opened the file while you were completing the installation. Verify that no users are accessing the services file and retry.

Unable to open services file. Setup can not continue.The \WINDOWS\SYSTEM32\DRIVERS\ETC file cannot be accessed. This may occur if another user has opened the file while you were completing the installation. Verify that no users are accessing the services file and retry.

Unable to write to log file.The SETUP program is unable to write to the INSTALL.HIS file. Verify that you have network rights to write files to this location, and that the file is not locked (in use). In some cases, this message is displayed when the file already exists and it was expected to be read-only and it is not. If the file already exists, delete or move the file before continuing.



Unable to write to services file. Setup can not continue.The SETUP program is unable to write to the \WINDOWS\SYSTEM32\DRIVERS\ETC file. Verify that you have network rights to write files to this location, and that the file is not locked (in use). In some cases, this message is displayed when the file already exists and it was expected to be read-only and it is not. If the file already exists, delete or move the file before continuing.

UnInstaller setup failed to initialize. You may not be able to uninstall this product.The unInstaller component of Setup was not initialized properly. Setup can continue normally and complete the installation. However, you may not be able to uninstall Fourth Shift.

If you want to insure that Fourth Shift can be uninstalled, stop Setup and delete the UNINFSWK.ISU from the UserDir location. Restart Setup and try again.

You cannot use '00000' as your local bank currency code.A currency code is required to complete the installation. The Currency Code = 00000 is reserved for system use and cannot be assigned for your local bank currency code. See Before You Install for more information if you need additional assistance before entering your selection.

You have chosen not to restart your computer at this time. Please be sure to restart your computer before using your Fourth Shift system.The Fourth Shift installation requires that the system be restarted. You have elected not to restart your system at this time. You must restart the system before attempting to use Fourth Shift.

You must select at least one module to install.You have no module selected from the list. The SETUP program requires a minimum of one module before continuing with the installation. If you are unsure which modules to select initially, you can select the System Control Module and meet the minimum requirement to continue with the installation.

Your currency code description must be from 1 to 15 characters.A currency code description is required to complete the installation. The currency code description is assigned to the local banking currency code for your Fourth Shift system. See Before You Install for more information if you need additional assistance before entering your selection.

InformationStarting SQL Server Setup.The SQL Server setup program is about to launch. This setup program runs separately from the Fourth Shift setup program.

There may already be a Fourth Shift installation in <location>. Continue installation in this location?There may be an existing Fourth Shift installation in the specified locations. Specify whether or not to continue installing to that location.



Acceptable Log File Messages: SQL ServerThe SQL Server database installation creates several log files. These files should be reviewed at the end of the server installation. This section lists the acceptable messages that may be found in these log files. Messages not included in the following list are not acceptable and should be resolved before proceeding with the Fourth Shift implementation.

Alias user added.

All fragments for database 'tempdb' on device 'ddddd' are now dedicated for log usage only.

All XX matched objects now have their 'insert row lock'' setting as 'true'. Updates were required for XX objects.

Cannot add rows to sysdepends for the current object …

Configuration option changed. Run the RECONFIGURE command to install.

Could not find enough space on disks to extend database tempdb.

Database 'XXXXDBXX' is not in single user mode - may find spurious allocation problems due to transaction in progress.

DBCC execution completed. If DBCC printed error messages, see your System Administrator.

End of error list.

Extending database by nnnn pages on disk xxxx.

Login 'fsadmin' is aliased or mapped to a user in one or more database(s). Drop user or alias before dropping login.

New login created.

Non-cluster index (index id=X) is being rebuilt.

The login 'fsadmin' already exists.

The number of data pages in Sysindexes for this table was X. It has been corrected to X.

The specified user name is already aliased.

There is no such user fsadmin.

Changed database context to XXX.



INSTALL.HIS MessagesThe INSTALL.HIS file is created in separate locations based on the type of installation completed.

The following messages may be included in the INSTALL.HIS file. Some messages are information only, some require review and additional action.

Advisory MessagesAdvisory messages indicate the action the SETUP program was completing and the result of the action. This list of messages provides a record of all the processing completed to use for troubleshooting in the event that an error is encountered.

Advisory: Failed to install font.The font installation process was not necessary because the font was previously installed. No additional action is needed.

Advisory: Font already installed.The font installation process was not necessary because the font was previously installed. No additional action is needed.

Advisory: Font file already in system.The font installation process was not necessary because the font was previously installed. No additional action is needed.

Advisory: No font files found.The font installation process was unable to complete because the font files were not available. If you are not using the Flexible Report Manager, the font files are not necessary. The font files should be available in the location indicated by the FontsDir configuration variable if you wish to install these files to the workstation.

Advisory: Not a valid font file.The font installation process was unable to complete because the font file was invalid. If you are not using the Flexible Report Manager, the font files are not necessary. The font files should be available in the location indicated by the FontsDir configuration variable if you wish to install these files to the workstation.

Advisory: Source file is ...A set of these messages are used to indicate that the requested action to install a file was skipped because a newer file was found in the destination location. This can happen when you have installed an update to the operating system or other program. No additional action is needed.

Install Type Location of INSTALL.HIS Messages

Database/modules MFGSYS directory

Workstation FSUSER directory



Advisory: Unable to delete file. File does not exist.The SETUP program attempted to delete a file which was no longer needed. Your installation did not include this file. No deletion was necessary. No additional action is needed.

Advisory: Unable to rename file. File does not exist.The SETUP program attempted to rename a file. Your installation did not include this file. No rename was necessary. No additional action is needed.
