System Administration ADMMworthen.xdatasync.com/support/PrintDoc/ADMM.pdfFourth Shift Release 7.50 System Administration 6 Standard Directories and Files The standard environment contains

System AdministrationFourth Shift Release 7.50

Fourth Shift HelpRelease 7.50E

Important Notices

Copyright © 2014 Infor. All rights reserved.

The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor.

By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and all supplemental related materials ("Purpose").

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.

Without limitation, U.S. export control laws and other applicable export and import laws govern your use of this material and you will neither export or re-export, directly or indirectly, this material nor any related materials or supplemental information in violation of such laws, or use such materials for any purpose prohibited by such laws.

Trademark Acknowledgements

The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

Fourth Shift Release 7.50

ContentsSystem Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Standard Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11FS.CFG File Details and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Using Multiple Fourth Shift Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Module Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22E-Mail Notification Setup and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Audit Trail Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Fourth Shift Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Purging Outdated Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Upgrade Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Additional Workstation Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Computer Operation Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Printing and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Reprint Feature for SQL Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Customizing Site Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Fourth Shift Transactional Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Fourth Shift Remoting Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Fourth Shift Services and License Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51A – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51B – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53C – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54D – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56E – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57F – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57G – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57H – Custom Site Help File Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59I – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59J K – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61L – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61M – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62N – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63O – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63P – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Q R – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64S – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65T – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66U – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66V – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66W X Y Z – Custom Site Help File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Batch Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Parameter Entry and Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68File Location Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Parameter Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

System Administration 3


Task On-Line Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Batch Setup Suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Nesting Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Batch Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Batch Process Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Batch Prerequisites and Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Database Locking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Module-Specific Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Fiscal Year-End Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Other Year-End Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Add-On Modules/Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Installing Add-On Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Cash Management Module Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

System Administration Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115File Manipulation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Configuration Variable and File Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Configuration Variable Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Fourth Shift Print Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Active Users List Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Active Users List Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143



System Administration

System OperationThis section provides an overview of how your system is configured.

Administration OverviewIt is strongly recommended that you assign the responsibility for administration of your system to one person in your company. This person is referred to in this guide as the system administrator. An alternate system administrator should also be assigned. The system administrator's responsibilities include the following duties:

• be the technical expert in and around the computer system for hardware, operating system and network operation

• train at least one backup system administrator and publish a daily activity schedule

• perform installation and setup tasks for each module

• keep system information up-to-date and orderly

• define, develop and document standard operating procedures and schedules for your site

• maintain security and access control

• periodically clean up the directory structure and eliminate unused and outdated files

• keep users informed of system changes

• ensure users are trained at the appropriate levels on system topics

• monitor system usage to identify ongoing and potential hardware and software requirements

• monitor disk capacity to ensure adequate free space and system performance

• maintain the system installation exactly as directed in applicable Fourth Shift documentation

• perform daily and periodic administrative tasks, including the backup procedure

• perform network administration tasks, including user maintenance and network rights assignments

• perform history and archive management

• monitor system operation to obtain maximum efficiency, including the scheduling of data entry and cutoff times for processing

• schedule and execute batch runs

• become the primary contact for hardware and software vendors

• diagnose and solve system problems

• prepare and manage a disaster preparedness plan

• perform recovery procedures when needed



Standard Directories and FilesThe standard environment contains standard directories consisting of a set of standard directories, supplemental directories and files in the MFGSYS directories and subdirectories.

Standard DirectoriesThe standard system directories are created automatically during the installation process. See the Installing and Implementing Fourth Shift online manual for more information.

Note: Verify that the drive on which the standard Fourth Shift directories are located is not using compression. Some data files may not be recognized by Fourth Shift if compression is used.

Directory Files Stored Config Variables Using

root utilities FSScripts

MFGSYS data files;reference files;temporary files

AuxDataFiles;AuxRefDataFiles;WorkDir

MFGSYS\CLIENT workstation installation com-ponents

ClientDir

MFGSYS\E programs ProgramFiles

MFGSYS\FONTS font sets FontsDir

MFGSYS\FSREPORTING reporting services installa-tion components

MFGSYS|FSSQLSERVER separate database server installation components

MFGSYS\HMFGSYS\H\ImagesMFGSYS\H\NetUIMFGSYS\H\PrintDocMFGSYS\H\Site

Online Help .PDF filesLogos, style sheets, and HTML files

MFGSYS\I data import files ImportFiles

MFGSYS\REPORTS report templates ReportsDir

MFGSYS\S screen files; message files ScreenFiles

MFGSYS\SQLMSS Fourth Shift SQL Server database, log files, installa-tion components, adminis-tration tools

SQLMSS

MFGSYS\SYSTEM programs SystemDir

FS_APPS programs WinProgFiles

FS_APPS\D internal database file WinDataFiles

XPORT extracted database files and indices

WinXportFiles



Supplemental DirectoriesThe following directories are created when a specific module is installed:

A USER directory is required for each user to store user-requested files. The system automatically creates a TEMP directory in the USER directory for command line task working files. See the Installing and Implementing Fourth Shift online manual for more information.

You can modify the standard configuration, if necessary, using the configuration file. See Configuration Overview in this section for more information on the configuration file.

Root FilesThe files in the root directory include supplemental programs and utilities. These files include:

MFGSYS FilesThe files stored in the MFGSYS directory can be divided into the following categories:

• Data Files

• Reference Files

• Temporary Work Files

• Batch Log Files

Data FilesData files contain information used or updated during normal operation. These files include:

Directory Created Module Installed

EDIEXCEL Electronic Data Interchange (EDIM)

EDIINTRN Electronic Data Interchange (EDIM)

MFGSYS\FSTM Fourth Shift Transactional Interface sample code

MFGSYS\SAAM Sales Analysis (SAAM)

MFGSYS\SCREENS Screen Customizer (SCRM)

MFGSYS\WEB\NUIM Net UI (NUIM)

Filename Description

ARCREORG.EXE reorganizes the ARCHIVE.FIL file

CFG2DOS.EXE converts configuration variables in batch commands

FSLICENS.EXE reviews and updates the number of workstation licenses

FSLOCKST.EXE configures the Fourth Shift Lockserver service


ARCHIVE.FIL audit trail file of all transactions that update the database; used as a tool during recovery



Reference FilesReference files contain supplemental information, outside of the database, used by your system. These files include:

Temporary Work FilesTemporary work files are created during normal system operation and are used for internal processing. These files include:

Batch Log Files

BATCHUPD.FIL file of labor/resource transactions entered on the LRRP (Labor/Resource Reporting) screen and not yet processed by the TRUD (Transaction Update) task

BATCHUPD.OLD BATCHUPD.FIL files that have already been processed

INSTALL.HIS installation history file; is used as reference when verifying your installation

MODCOM*.FIL financial communication files used to store transactions between modules. The two letters after MODCOM designate the module destination. For example, the MODCOMGL.FIL file contains transactions transferred to the GLSM (General Ledger) Module. MODCOM*.FIL files may be processed by module communi-cation tasks such as GLMQ (G/L Module Communication), APMQ (A/P Module Communication), and ARMQ (Invoice Module Communication) when the Write to Queue option on the File Writing Configuration (CNFG—Alt+F8) screen is set to N.

MODCOM*.MC financial communication files processed unsuccessfully

MODCOM*.OLD financial communication files processed successfully


DBDEF.DAT database information paths for the data export features in the SYSM Module; information paths are displayed on the DVUD (Data View Definition) screen

FS.CFG configuration file identifying drive/directory locations of Fourth Shift files and specifying any optional features

FUNCFILE displays field titles on the History Detail screen; accessed from the AUDT (Item History Audit) screen; this is a read-only file

HISDEF.DAT history information paths for the data export features in the SYSM Module; information paths are displayed on the DVUD (Data View Definition) screen

PATH.FIL represents the screens and tasks currently installed and assigned security; updated by the FCMT (Function Code Maintenance) screen

PEGSDESC index to MRP pegging messages displayed on the SDAL (Supply/Demand Analysis) screen; this is a read-only file


*.CMD temporary database server information files

*.WRK temporary files used for sorting purposes during some operations



Batch log files are created while a batch process is running to record processing and error messages. These files include:

MFGSYS\E Files

MFGSYS\FONTS Files

MFGSYS\H Files

MFGSYS\H\IMAGES Files

MFGSYS\H\NETUI Files

MFGSYS\H\SITE Files


XXX.LOG batch process log file created during batch execution using the BEXE (Batch Process Execution) screen. The first part of the file is the batch Process Id.

IMPORT.ERR data import process log file used to record processing errors

RCVR.ERR system recovery log file used to record processing errors


*.COM programs

*.EXE programs and utilities.


*.TTF font files used within Microsoft Windows for reports


MFGSYS\H Online Help .PDF filesLogos, style sheets, and HTML files


*.GIF Fourth Shift and SoftBrands logo images


*.HTML Copyright, PrintDoc, Print Library Link, and Site Help files




MFGSYS\H\PRINTDOC Files

MFGSYS\I Files

MFGSYS\REPORTS Files

MFGSYS\S Files

MFGSYS\SYSTEM Files

*.HTML*.CSS.*.GIF

customized site help files linked from the Custom Site Help button from a help topiccascading style sheetscustomer logo image


*.PDF PDF (Adobe Acrobat) printable versions of help topics


*.MAC predefined macros used by the IMPT (Data Import) task

*.TBL conversion tables defined using the Data Conversion Table window, opened from the TMPT (Template Maintenance) screen

*.TPL templates defined using the TMPT (Template Maintenance) screen

RCVR.IDX system recovery index file; used by the RCVR (System Recovery) task when using the ARCHIVE.FIL file as the incoming data file during the recovery pro-cess


*.RDL report template files used by Reporting Services stored in folders by model name

FSDB.DSV Data Source View for Fourth Shift Report Model

FSModel.smdl Fourth Shift Report Model


FMX Fourth Shift screens; each *.FMX file corresponds to a module

STRINGS.MDB file containing messages


*.DLL program files



FS_APPS Files

Configuration OverviewThe standard system configuration uses a number of methods for setting system variables. These methods work together to prepare your system as you sign onto the system.

• The FS.CFG file is the standard system-level configuration file. This file contains configuration variables which describe file locations as well as modify options for your system such as requesting to use the screen timeout feature.

• The [system name]FSMSS.INI file contains a set of workstation-specific settings used with Fourth Shift modules. These settings allow preferences to be established for a workstation rather than the entire system.

• The LOCALFS.CFG file is an optional user-specific configuration file. There is no LOCALFS.CFG configuration file created during installation. Since this file does not exist, the INCLUDE directive listed in the default FS.CFG file is ignored.

For detail about each configuration variable, see "Configuration Variables" in the Administration Reference section of the System Administration online manual.

System Configuration File (FS.CFG)The standard configuration file, FS.CFG, contains configuration variables which describe how your system is set up. Some configuration variables identify locations and filenames used by the system. Other configuration variables modify the behavior of your system such as requesting to use the screen timeout feature.

In the standard configuration, one configuration file exists at the file server and no supplemental configuration file (LOCALFS.CFG) exists. This configuration is recommended when all workstations can be configured exactly the same way.

It is recommended that you use the standard configuration until you have had some experience with the system. The standard system configuration has several advantages:

• All configuration information is read from the same configuration file. Each workstation has the same configuration.

• This is the easiest configuration to maintain.

• You can modify the FS.CFG file from one workstation. This prevents you from having to change configuration files on each workstation.

The standard multi-user configuration uses the M:\MFGSYS\FS.CFG as the configuration file for all workstations. This configuration assumes that a C:\FSUSER directory exists on each workstation to be used as a USER directory. If the directory does not exist, the USER directory is created automatically when any operation that requires the USER directory is processed.

Configuration Variable Types

*.EXE program files


*.EXE programs that run a certain group of operations within the specific application



There are two types of configuration variables: required and optional.

• Required configuration variables are added to the FS.CFG file automatically when you install your system. Required variables must be in the FS.CFG file. Default values indicate standard installation locations.

Several modules add required configuration variables automatically during module installation.

• Optional configuration variables are added manually using an ASCII text editor such as Notepad. You should add optional variables after the required variables section. Optional variables have a default value that is used by the system unless a new value is specified in the FS.CFG file. Some optional variables are added during installation to ensure proper system operation.

For detail about each configuration variable, see "Configuration Variables" in the Administration Reference section of the System Administration online manual.

CommentsComments can be added throughout the FS.CFG file to document changes. Comments begin with the # symbol.

INCLUDE DirectivesINCLUDE directives can be added to the FS.CFG file to combine the standard configuration file with a workstation-specific configuration file. This allows you to specify workstation-specific configuration variables. See "The INCLUDE Directive Feature" for more information.

Fourth Shift Settings File ([system name]FSMSS.INI)The settings file, [system name]FSMSS.INI, is created when you install the System Control Module on a client. This file contains workstation-specific settings. For example, client application window sizes and placement are recorded to allow you to open applications without resizing the application window each time.

Workstation-Specific SettingsThe [system name]FSMSS.INI file is divided into sections. The sections available vary based on the modules installed on the client. The following sections and settings are created as appropriate:

Section Variable Description

FSMSS Frequently accessed standard settings file informa-tion listed here to improve performance

FSCfgFile Location and filename for the server configuration file (FS.CFG); used only by systems with the SOPM Module installed

ShipImportFile Location and filename for the import-ready file cre-ated for customer orders to be shipped from the SOPM Module

ShipSerialFile Location and filename for the list of customer orders to be shipped that also require manual entry of serial number information

ConvertCharType Controls whether OEM characters are converted to ANSI characters when displayed in a DOS window; used by workstations executing DOS-based appli-cations from Fourth Shift

Fourth Shift GUI Edit3dBorders Controls whether graphical borders are displayed around entry fields



Net UI Server VariablesWhen the Net UI Module is installed, the NETUI.INI file is created on the server. The following settings are included in this file. These settings are included in the [Net UI 9999] section of the NETUI.INI file, where 9999 is replaced by the port number used.

ScreensDir Identifies the location of the screen customization files; by default this is the Mfgsys\Screens directory

Installable ISAMs Available drivers for ODBC access

ListBoxScrollStyle xxxxCollectionView Default scroll style for each application in the SOPM Module; available values are ListBox and Buttons

MSSWinConfig Default values for the overall operation of the SOPM Module

WindowTimeOutSec-onds

Number of seconds an SOPM Module application can be idle before the IDLE routine is called

OnIdleTrigger Number of times the IDLE routine is called before memory cleanup begins

CustOrderAssign (used by the SOPM Module only)

Prefix Default prefix used for new orders; based on last prefix selected

AutoCalculateATP Calculation of ATP quantities is performed as each line is added rather than on request only

DefaultOrderLineUnit-PriceZero

Indicates if zero value lines are permitted on cus-tomer orders

Reports xxxxReport Report template for specific report used by the SOPM Module

RBPM UserDir Location of the user-specific directory; this location must match the UserDir location specified in FS.CFG. If one location is changed, the other must be updated as well.

Database Location of the RBPM database (FS_RBPM.MDB); this location must match the PricingFiles location specified in FS.CFG. If one location is changed, the other must be updated as well.

ImportBrowseEnabled Enables the Online Browse feature

ImportFindButton Enables the Find button; must be enabled to use the Online Browse feature to locate orders to be imported

RebuildUserDB Refreshes user temporary files (RBP_USER.MDB and RBP_USER.LDB) upon sign in

Variable Default Description



User-Specific Configuration File (LOCALFS.CFG)The default installation consists of a standard configuration file (FS.CFG) and no supplemental user-specific configuration files. This configuration is recommended when all workstations can be configured exactly the same way.

A user-specific configuration file is listed in the FS.CFG file in the event you wish to use it. The default file, LOCALFS.CFG, is recommended but another filename can be substituted if needed. The LOCALFS.CFG file is an ASCII text file which uses the same format as the standard FS.CFG file.

It is recommended that you use the standard configuration until you have had some experience with the system. The standard system configuration has several advantages:

• All configuration information is read from the same configuration file. Each workstation has the same configuration.

• This is the easiest configuration to maintain.

• You can modify the FS.CFG file from one workstation. This prevents you from having to change configuration files on each workstation.

The standard configuration assigns values to the configuration variables using the following process:

AddtoPath m:\mfgsys\system supplemental directory location which should be included in the PATH when running the Net UI server; used for the session started on the Win-dows NT server when the client accessed Fourth Shift

ServerExe M:\MFGSYS\SYSTEM\ FSGUISVR.EXE where M:\ is the application program installation location

name and location of the server process that is started for each client connection

ServerMssDir M:\ location of application programs; working directory from which the application programs run

UserDir C:\FSUSER\[System-Name]\@NETUIID@

location of the user-specific directory; this location must match the UserDir location specified in FS.CFG. If one location is changed, the other must be updated as well.



If you need to use a configuration other than the standard configuration on a workstation, see the following FS.CFG File Details and Options topic for additional information.

FS.CFG File Details and OptionsThe FS.CFG file is as ASCII file with specific format and syntax. There are a number of optional features which are controlled by variables in the configuration file.

See "Configuration Variable Quick Reference" in the Appendix for a summarized list of the configuration variables.

Configuration Variable Format and DefinitionsConfiguration variables are defined using the format Keyword=Value. Spaces are allowed between the keyword and value.

See "Configuration Variables" in the Administration Reference section of the System Administration online manual for more information about a specific configuration variable.

KeywordsThe keyword represents the name of the configuration option. For example, ProgramFiles identifies Fourth Shift program files.

ValuesThe value associated with the keyword is one of the following types:

• Location indicates a specific drive/directory. For example, AuxDataFiles=m:\mfgsys, is a Location value.

Specify the fully-qualified drive/directory identifier for each location.

FSCFG=M:\MFGSYS\FS.CFG

#Required Configuration Variables...##Workstation-specific Config File#.INCLUDE $UserDir$\localfs.cfg##Default Workstation Variables#...#Optional Configuration Variables

File Server

M:\MFGSYS\FS.CFG

Resulting Configuration

#Required Configuration Variables...#Optional Configuration Variables

Workstation

none existsC:\FSUSER\LOCALFS.CFG

1

2

3

Workstation



• Location List indicates one or more drive/directory location(s). The locations are searched in order. Locations must be separated by a semicolon. For example, ProgramFiles=d:\;m:\mfgsys\e is a location list.

Specify the fully-qualified drive/directory identifier for each location.

Note: The installation process uses the last directory of a location list for installing and updating files. For example, with the location list value ProgramFiles=d:\;m:\mfgsys\e, new modules and system updates would install program files only in the M:\MFGSYS\E directory.

• Location+Filename indicates the drive/directory and filename. For example, WinMaintLogFile=m:\fs_apps\am_log.fil is a Location+Filename value.

Specify the fully-qualified drive/directory identifier with the filename.

• Yes/No indicates one of the options must be selected. For example, RecordLogin=Yes identifies YES as the Yes/No value.

• Number indicates a numeric value is needed. Numeric values can be whole numbers or hexadecimal numbers. For example, MaxUsers=3 identifies 3 as the Number value.

• String indicates entry of several characters is needed. For example, DatabaseType=TTCPNT identifies TTCPNT as the String value.

Case SensitivityConfiguration variable keywords and values are not case-sensitive. For example, the following configuration variables and values are equivalent:

• AuxDataFiles=m:\mfgsys

• AUXDATAFILES=M:\MFGSYS

• auxdatafiles=m:\mfgsys

Format ConditionsThe following conditions also apply to configuration variables:

• Embedded spaces may be used in string values if the value is enclosed in quotes. For example, "Company Name" could be used as a string value with an embedded space. Embedded spaces are not recommended in any standard configuration variables.

• Keywords can consist of any character A-Z and a-z, numbers Ø-9, the underscore (_) symbol and the dash (-) symbol. Keywords can be up to 32 characters. Blanks are not allowed in keywords.

• The combination of characters used for the keyword and value have a maximum length of 128 characters. Lines longer than 128 characters cause unreliable system behavior.

• Locations, other than user-specific directories, are ignored if the location specified does not exist.

• Keywords must be entered exactly as documented. Values associated with unrecognized variables are ignored.

Substitution VariablesSubstitution variables can be used to specify locations in the FS.CFG file. For example, the default INCLUDE directive for the LOCALFS.CFG file in FS.CFG is as follows:

.INCLUDE $UserDir$\LOCALFS.CFG

$UserDir$ is the location specified by the UserDir configuration variable.



Several types of variables can be listed in the FS.CFG file including the following:

All substitution variables must be defined before they are used. For example, when using the above INCLUDE directive, the UserDir variable must be defined by either:

• using the default UserDir value (C:\FSUSER)

• explicitly stating the UserDir location in FS.CFG before the INCLUDE directive

In this case, UserDir can not be defined in LOCALFS.CFG because the LOCALFS.CFG file is located using the substituted value. Without a value for UserDir the file cannot be opened.

Workstation-Specific Configurations (LOCALFS.CFG)Configuration variables can define two basic types of information:

• Required configuration variables are used by all users and the value must be the same for each user. For example, the location of the module communication or archive files must be the same to ensure all users are updating the same information.

• Workstation-specific configuration variables allow you to set specific options or redirect file searches to other locations when needed. For example, you may wish to have a unique location for the UserDir variable for some users.

Workstation-specific variables are defined in the LOCALFS.CFG file. A default INCLUDE directive is included in the FS.CFG file. This directive can be moved in the file as needed. If a LOCALFS.CFG file does not exist, the INCLUDE directive is ignored and the workstation assigns only the variables from the standard configuration file.

See "The INCLUDE Directive Feature" for more information.

The INCLUDE Directive FeatureThe INCLUDE directive allows you to identify additional configuration files, if necessary, to supplement the standard configuration file.

The INCLUDE directive uses the format:

.INCLUDE filename

where filename is the drive/directory and filename for the workstation-specific configuration file.

The system searches the configuration file in the order lines are listed in the file. INCLUDE directives are treated as though the included file contents were listed where the directive is positioned. You should therefore list only workstation-specific configuration variables in the included file.

The way the standard system configuration would incorporate the INCLUDE directive looks similar to the following. In this example, the LOCALFS.CFG is located successfully because UserDir is defined as C:\FSUSER before the INCLUDE directive is used.

Symbol Variable Type Example

$ Configuration variable $UserDir$

@ Environment variable @NetUIId@

# Remembered_Field #Item#



The following rules are also associated with INCLUDE directives:

• INCLUDE directives can be nested up to two levels deep to create a custom configuration file. For example, the standard configuration file, FS.CFG, can have an INCLUDE directive to FILE1.CFG and FILE1.CFG can have an INCLUDE directive to FILE2.CFG. INCLUDE directives that nest beyond two levels are ignored.

• INCLUDE directives can not contain undefined substitution variables. Configuration variables and environment variables can be used in INCLUDE directives if they are defined before the INCLUDE directive is invoked. See "Substitution Variables" for more information.

• The INCLUDE directive is ignored if the file specified does not exist.

• Once defined, configuration variables can not be reassigned by a subsequent line in either the LOCALFS.CFG or FS.CFG file. For example, if the UserDir variable is assigned in the LOCALFS.CFG file the value is not reassigned by the UserDir variable in the standard FS.CFG file.

Configuration Variable ModificationsConfiguration variables can be modified for a number of reasons. It is recommended that you use your system in the standard configuration for a period of time before changing any values. This allows you the opportunity to observe system performance and disk space requirements based on daily activities.

You need to provide information about the new locations and filenames to users of your system, as appropriate, if you choose to change your configuration. Instructions and examples in all user guides, online manuals and the on-line help use the standard system configuration.

See "Configuration Variables" for more information on specific defaults or options for a configuration variable.

Changing the FS.CFG FileOptional configuration variables are used to modify the default behavior of the system. Required configuration variables are automatically created in the FS.CFG file when you install the system.

#Required Configuration Variables.UserDir=C:\FSUSER.##Workstation-specific Config File#.INCLUDE $UserDir$\localfs.cfg#

##Default Workstation Variables#...#Optional Configuration Variables

Workstation

M:\MFGSYS\FS.CFG

# Workstation-specific VariablesC:\FSUSER\LOCALFS.CFG



Configuration variable keywords must be entered exactly as documented. Values associated with unrecognized variables are ignored. Verify that all keywords are entered correctly if you modify the FS.CFG file.

Using Multiple Fourth Shift SystemsMultiple Fourth Shift systems can be installed in your network environment. There are several business reasons you may want to implement multiple systems, including:

• conducting training on one system while using another for production

• using a different system for each region or segment of your company

• testing new business procedures on a system separate from your production system

In an environment such as this, Fourth Shift clients must access multiple Fourth Shift systems from the same workstation. The following graphic illustrates an example of multiple system use.

Action Completed

Create a complete system backup, including the FS.CFG file, before adding optional configuration variables. Some variables change system behavior and data could be altered.

Verify that no users are signed in.

Stop the database server processes. Some configuration variables are activated only when you restart the database server processes.

Use an ASCII text editor, like Notepad, to open the FS.CFG file in the MFGSYS directory.Add comment lines to document your changes for future reference.

Restart the database server processes.

Test your configuration changes.



A multiple system configuration is set up and configured properly based on information entered during the installation process.

How Multiple Systems WorkMultiple system support is based on the Fourth Shift applications locating the specific configuration information needed for each installed system rather than assuming there is only a single system installed in the environment. In order to do this, the applications use profile services to obtain the necessary information.

System Identifier and System NameEach system must be given a unique system identifier when installed. The system identifier is used in the names of databases, registry entries, data sources and other system components, and provides database integrity by "directing" data to the correct system's database.

In addition, each system is also given a system name when installed. The system name is used as a prefix for the displayed names of shortcuts and data sources, and is also used in creating registry entries. For example, if the "TEST" system name is used, the Fourth Shift title bar would read as follows:

TEST – Fourth Shift

The combination of the system identifier and system name is used to uniquely identify each system in a multiple system environment.

Configuration File (FS.CFG)Fourth Shift applications use the –C command line parameter to locate the configuration file (FS.CFG) to be used when starting applications. Each system uses a different configuration file that includes important information and locations for the system, and ensures that each system uses the correct locations and data.

Requirements for Multiple SystemsIf you want to install multiple Fourth Shift systems, the following requirements and considerations exist.

• Release level. All systems installed in an environment must be running the same release level of Fourth Shift, including Interim Service Releases (ISR). You cannot, for example, use a production system that is one release level, and then install a test system on the same server at the next release level.

In addition, all clients used to access multiple Fourth Shift systems must be at the same release level. To access Fourth Shift systems at different release levels, thin client access is required (Net UI or WebUI).

• System Name. Once a System Name has been assigned to a Fourth Shift system, it can not easily be changed, and Fourth Shift does not provide support for such a modification.

• Client licenses. Each client consumes a user license for every unique Fourth Shift system simultaneously being accessed. If a client is concurrently accessing two Fourth Shift systems simultaneously, two user licenses are consumed (one for each system).

Using Thin ClientsBoth Net UI and My Fourth Shift Workplace clients can be used in environments with multiple systems installed.

• Net UI clients locate the correct Fourth Shift system through the port number used to listen for Fourth Shift transactions. (This port number is an argument on the Fourth Shift command line, and is 5432 by default.) Each port number has a corresponding section in the NETUI.INI file



on the server. Each section lists the appropriate configuration file for a system, allowing the client to access the correct system information for that port number.

• My Fourth Shift Workplace clients locate the correct Fourth Shift system using the configuration file (FS.CFG) path entered in the Locations dialog. The configuration file path must be entered manually for each portal location before the My Fourth Shift Workplace client will work correctly in a multiple system environment.

Unlike traditional clients, the system name does not automatically appear in the title bar when using thin clients. However, My Fourth Shift Workplace users can add the system name to the Location Name if desired. See "Using Multiple Fourth Shift Systems" in the My Fourth Shift Workplace online manual for more information.

Component Installation ConsiderationsSeveral components are installed with your system to enhance the performance of certain batch tasks. These components are installed in the MFGYSY\SYSTEM directory, and are registered during the server setup process.

When multiple systems are installed on a server, certain components are registered in the location of the most recent installation. For example, if you install one system in a directory mapped to the M: drive, then install a second system in a directory mapped to the T: drive, the components installed in the T:\MFGSYS\SYSTEM directory will be used by both systems.

For this reason, it is essential that all Fourth Shift systems installed on a server be running the same release level, including Interim Service Releases (ISR) from Fourth Shift Customer Support.

If an outdated system exists on a server, or if you attempt to remove a system from a server, you may inadvertently disable the components for all of the systems installed on the server. In this case, you must manually register the components.

Additionally, if you need to use or test an updated version of one of these components, you must first register the components manually.

To register components manually, use the following command line:

M:\MFGSYS\SYSTEM\<filename> /regserver

Substitute the drive letter for the location of the files you want to use.

The component files affected by these considerations include:

Task Component File Name

ARAG (A/R Account Aging) ArAgingSvr.exe

BKFL (Backflushing) BackflushSvr.exe

CROL (Cost Roll-Up) CostRollSvr.exe

GLAU (G/L Account Update) GLAccountUpdateSvr.exe

ITHU (Inventory History Update) InventoryUpdateHistorySvr.exe

PLNG (MRP Planning) PlanningSvr.exe

SREV (Shipping Order Review) ShippingOrderReviewSvr.exe



Module Communication

OverviewFinancial module communication transactions are automatically created as a result of operational activities. You have two options for processing these module communication transactions throughout the production day: real-time and batch.

• The Real-time Processing option takes advantage of SQL Server’s Service Broker Messaging Queues, which when active, immediately manage the communication needed between manufacturing and financial transactions.

• If the Batch Processing option is chosen, it is typically run as part of the nightly batch (using a batch task) to populate the financial tables in the Fourth Shift database with information written to either files or queues by Fourth Shift manufacturing transactions.

Note: In Release 7.50, the recommended method for processing the manufacturing financial transactions is: Real-time processing.

Processing method settings on the CNFG—File Writing Configuration screen used to control whether module communication transactions are written to files or queues include:

- Write to Queue = Y—module communication information is written to the queues, which are not activated until nightly batch is run with the A option of APMQ, ARMQ, or GLMQ.

- Write to Queue = N—module communication information is written to modcom files, which are not added to the queues until the nightly batch is run with the F option APMQ, ARMQ, or GLMQ.

Both real-time and batch processing methods are designed to send e-mail notification messages in the form of poison message notifications, in the unexpected event that there are any problems with module communication transactions that would cause any of the Service Broker queues to be disabled. These notifications require configuring the FSMail account in the SQL Server Management Studio Database Engine and are used to inform a designated system administrator of interruptions in transaction processing due to errored out transactions, disabled queue activity, or other queue failures. For more information on notification e-mails, see E-Mail Notification Setup and Maintenance later in this document.



Real-time ProcessingThe real-time processing option takes advantage of SQL Server’s Service Broker Messaging Queues, which when active, immediately manage the communication needed between manufacturing and financial transactions. Real-time processing places module communication transactions in processing queues and releases them to provide immediate updates to the General Ledger, Accounts Payable, or Accounts Receivable financial tables.

A service broker queue stores service broker messages, allowing for asynchronous communication between services; activation stored procedures automatically process messages.

The service broker queue is activated when its activation stored procedure is setup to automatically process messages as they are committed to the queue. The system default setting for queues are activated on new installs; inactivated on converted databases. There are two ways to activate/inactivate real-time modcom queues in Fourth Shift:

- By screen: APEX, AREX, GLEX

- By batch task: APMQ, ARMQ, GLMQ

Feature Highlights

• Financial transaction validations to the manufacturing transactions. Manufacturing transactions must now satisfy both the manufacturing and financial validations.

• Modcom processing is allowed while any financial transactions are running, regardless of whether modcom processing is performed in real time or batch.

• Write To File and Write To Queue

Additional processing options have been added to the System Installation Setup—File Writing Configuration window (CNFG—Alt+F8) that enable you to choose to:

- Write To File = Y—the MAINXX application service will write to the files soon after the manufacturing transaction is committed.

- Write To Queue = Y—the manufacturing transactions are written to the Modcom queue automatically, making real-time Modcom processing possible.

Note: For more information on the File Writing Configuration options, see the System Control manual in the System online Help.

• APEX, AREX, GLEX – Queue Processing Status field

The Queue Processing Status field is available on the GLEX, APEX, and AREX screens to manually activate or inactivate the processing queue for real-time processing. The following options are available to temporarily pause (I—Inactive) or to restart (A—Active) the real-time modcom processing.

Note: After a new installation or conversion, the Queue Processing Status field can be used to manually change the system default setting for the queue status.



The module communication for real-time processing looks similar to the following when the Write To Queue option is set to Y.



Batch Processing If you do not wish to take advantage of real-time processing, Manufacturing and Financial module communication using batch processing can be done two different ways.

• One batch method is to set the processing queues to inactive and later activate the queues, either manually or by a batch task. This method allows for delay of financial updates so the financial transactions can be verified or for any other business reason. This is the default option when upgrading to R7.50.

• A second batch method is to write the financial transactions (modcoms) to a flat file and then later add them to the queues by a batch task. The queues may be active or inactive. This option is needed when transactions must be modified by external alternate custom processes. This option, although not the recommended approach, is available for custom solutions.

Note: Module Communication batch tasks are: G/L Module Communication (GLMQ), AP Module Communication (APMQ), and Invoice Module Communication (ARMQ).

Module Communication Batch Task ParametersThe parameters for batch tasks APMQ, ARMQ, and GLMQ, include:

- A or I—is used to indicate whether to activate or inactivate the financial transaction processing queue. The system default is A.

- S—is used to indicate how many seconds after the last queue activity was detected the system should wait before inactivating the queue. This option acts like a safety buffer for the processing queue. The system default is S5 (five seconds).

- F—this option is available for customers who perform additional steps to their financial information flat files before moving them into the transaction processing queue for batch processing. It is used to specify the file containing modcom transactions that will be added to the queue.

- O—(for GLMQ only) this option is used to guarantee in-order processing of the file specified by the F option in the same order as they were added to the queue.

Note: For more information on the individual batch tasks, see the Accounts Payable (for APMQ), Accounts Receivable (for ARMQ), and General Ledger (GLMQ) manuals in the Financial online Help.



Module Communication Batch Processing Using FilesFinancial transactions are automatically created as a result of operational activities. These transactions can be communicated using batch processes. The module communication for batch processing looks similar to the following when the Write To Queue option is set to N and Write To File is set to Y on the File Writing Configuration screen.



The module communication files are in ASCII, comma delimited format (CDF). A valid module communication file must contain all the identified fields in the file layout.

See Module Communication File Layouts or Financial Transaction Detail topics in the Administration Reference manual of the System online Help for more information on specific financial transactions and module communication file layouts.

The module communication process is completed using three batch process tasks, when the Write to Queue is set to N on the File Writing Configuration screen (CNFG—Alt+F8).

Note: For the F option of APMQ, ARMQ, and GLMQ, we are using <filename> to indicate that you can use any name for your external files as long as they have the .FIL extension. They will be renamed to <filename>.OLD if they are successfully processed by APMQ/ARMQ/GLMQ; or to <filename>.MC, if the transactions process failed.

Module Communication TasksThe APMQ, GLMQ, and ARMQ tasks rename the filename*.FIL file to <filename>*.MC as part of a transaction validation step. Once validated, the <filename>*.MC file is the file that is processed. The existing <filename>*.MC file is renamed to filename*.OLD to allow you to create an audit trail of module communication files.

An existing <filename>*.MC file always takes precedence over a new <filename>*.FIL file. This forces rejected transactions to be resolved before the next set of transactions is processed. This also prevents users from generating new transactions for a file while it is being processed.

The module communication tasks process one file per run. When a <filename>*.MC file is found, only the <filename>*.MC file is processed. The module communication tasks must be rerun to process the <filename>*.FIL file.

Processing Status Field ValuesEach transaction in a modcom file contains a special field which is updated during processing. The Processing Status field (field 5) indicates what type of processing has been completed for the transaction. It is incremented during the module communication process to prevent transactions from being posted more than once.

The Processing Status field contains one of the following values:

Task File Used

APMQ (A/P Module Communication) <filename>.FIL

GLMQ (G/L Module Communication) <filename>.FIL

ARMQ (Invoice Module Communication) <filename>.FIL

Status Description

0 new transaction; no processing completed

1 transaction has passed the edit phase; ready to process

2 transaction processing completed successfully

3 transaction format or content errors exist; corrections are required before the transac-tion can process successfully



Maintaining an Audit TrailIf you want to save the current <filename>*.OLD file transactions before running a module communication task, consider creating a batch process or DOS batch file that renames any <filename>*.OLD files to a name such as <filename>*.SAV. This allows you to maintain a backup copy of processed module communication files for archive purposes.

Program OperationThe validation and update processing looks similar to the following:



Module Communication ExceptionsModule communication processing exceptions are listed on the exception report automatically generated when you run the APMQ, ARMQ, or GLMQ tasks.

If you are using a SQL Server configuration, some module communication exceptions are displayed on the APEX (A/P Receipt Exceptions) or GLEX (G/L Journal Entry Exceptions) screen. These exceptions do not prevent the successful processing of the MODCOMAP.* or MODCOMGL.* files, but the transactions listed can not be used for further processing until modifications are made and the exceptions are reprocessed. Additional Processing Status values are used to indicate the type of exceptions listed.

See APEX in the Accounts Payable online manual or GLEX in the General Ledger online manual for more information.

Poison Message NotificationPoison messages are created when transactions error out and cannot be processed. Service Broker provides automatic poison message detection, which sets the queue status to Off, if a transaction that receives messages from the queue rolls back after five consecutive attempts. This feature provides a safeguard against catastrophic failures that the application cannot detect programmatically. Because the work of Service Broker is performed in background, you may not be aware of the queue shutting down at the time it happens, so notification is sent in the form of a poison message e-mail to notify the IT administrator as soon as any one of the three modcom target queues has shut down.

E-Mail Notification Setup and MaintenanceAn E-mail notification feature provides the system administrator with the ability to set up e-mail addresses in the event that Fourth Shift detects various error conditions. Notifications can reflect problems in these areas:

• Modular communication errors between the Manufacturing and Financial databases

• Errors detected during SAAM Incremental load processing

The e-mail notification setup starts with configuring the FSMail account in the SQL Server Management Studio Database Engine. After the FSMail profile has been configured, the individual e-mail addresses need to be entered in the FS.CFG file.

Once this setup has taken place, shutting down the FIN and MAIN services and restarting them activate the e-mail addresses for use.

Note: Remember to copy the FS.CFG file to any machine that may be used for sandbox testing activity.

This setup takes place as part of the Post-Upgrade or New Install activity. Once this process is complete, you only need to make changes if:

- the sending e-mail address changes

- the e-mail address recipients need to be altered

- you change the SQL Server



E-mail Notification MessagesImportant: E-mail functionality for Module Communication is now included as part of the Fourth Shift configuration setup in the fs.cfg file. For more information, see also the Configuration Variables topic in the Administration Reference manual in the System online Help.

The following FS.CFG configuration variable is used to define the e-mail recipient(s) who should receive notification for errors detected during the Module Communication transaction process.

Note: You may specify one e-mail address or multiple addresses separated by semicolons.

• ModcomEmailRecipient=The modcom e-mail recipient will receive e-mails directly if the real-time module communication transactions cannot be processed and the queue is shut down.

The following FS.CFG configuration variables are used to define the e-mail recipients who should receive notification for errors detected during SAAM Incremental Load processing.

• SAAMAdminEmailRecipient=The administrative e-mail recipient will receive e-mails directly if the Incremental Load process can not be processed. In all other error conditions, the administrator will receive Cc (electronic carbon) copies of problems detected for either financial or production related problems.

• SAAMFinancialEmailRecipient=The financial e-mail recipient will receive e-mails for errors processing the following areas:

- Fiscal Period definition

- GL Accounts

- AR Invoice Header and AR Invoice Lines

• SAAMProductionEmailRecipient=The production e-mail recipient will receive e-mails for errors processing the following areas:

- Customer Orders

- Customers and Ship To/Delivery Locations

- Custom Product and Custom Product Component data generated by OVAR

- Inventory Adjustments

- Items and Product Lines

- Shipments

- Deletion of data

Note: These e-mail configuration variables are set up as part of the post-installation tasks and can be changed as necessary to reflect current business procedures.

Changing the Sending E-mail Address1. Open SQL Server Management Studio and connect to the Database Engine.

2. Select Management, then right click on the DataBaseEmail option.

3. Select Configure Database Mail.

4. Change the Sending address for the FSMail account using the Database Mail Configuration Wizard.



Changing the E-mail Recipient addresses1. Open the FS.CFG file using Notepad.

2. Locate the e-mail recipient address configuration variable that needs to be changed.

ModcomEmailRecipient=

SAAMAdminEmailRecipient=

SAAMFinancialEmailRecipient=

SAAMProductionEmailRecipient=

3. Make any applicable changes or corrections.

4. Shut down then restart the FINXX and MAINXX (where XX is the SystemIdentChar) services to apply your changes.

Note: E-mails may continue to be sent to the former addresses until these services have been restarted.

Changing SQL ServerIn the event that there is a SQL Server change, complete these steps to configure the FSMail account.

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

2. Select Management then right-click the DataBaseMail option to select Configure Database Mail.

The Database Mail Configuration Wizard is displayed.

3. Click Next.

4. Select Manage Database Mail accounts and profiles then click Next.

Note: If this feature has not been utilized before, a setup message is displayed—click OK to proceed.

5. Select one of the following for an existing account: View, Change, or Delete.

6. Click Next.

Note: Account Name FSMailAccount and Profile name FSMail have been installed by the upgrade.

7. Select the account: FSMailAccount.

8. Enter an E-mail address, your e-mail server name, and verify the Port number.

SMTP Authentication is automatically set as Anonymous authentication. You can select the appropriate authentication and enter any necessary parameters, as needed.

9. Click Next.

The Complete the Wizard screen is displayed.

10. Review your changes then click Finish.

A window is displayed with the results.

11. Click Close.

12. Verify that the e-mail account and profile has been configured correctly by sending a test e-mail.



13. Right-click the DatabaseMail option and select Send Test E-mail from <server name>.

14. Enter the To: e-mail address and change the body of the message, if desired.

15. Click Send Test E-Mail.

The Database Mail Test E-mail window is displayed.

Note: If the e-mail isn’t delivered as expected, right click the DatabaseMail option and select View Database Mail Log to review any error messages generated.

- Correct the e-mail account, if necessary.

Module Communication E-Mail MessagesOnce a poison message has been detected and the Service Broker queue is shut down, it must be restarted. The E-mail Notification message contains the following information you need to complete this process:

- The e-mail Subject informs you which queue is down

- The e-mail body text informs you where, when, and how to restart the queue

Example Messages

• Accounts Payable

From: Mail Notification for Fourth Shift [mailto:<user ID>@softbrands.com]

Sent: Friday, May 16, 2008 1:15 PM

To: <ModcomEmailReceipient>

Subject: The queue q_ModcomAPTarget is disabled. Please check Fourth Shift database

The queue q_ModcomAPTarget is disabled by error transactions. Modcom A/P records will not be processed until the queue is enabled.

Queue Name: q_ModcomAPTarget

Database Name: <database name>

Server Name: <server name>

Queue Shut Down Date Time: 2008-05-16T13:15:24.040

Please run the following query of the table FS_ModcomException in the Fourth Shift database in order to determine the problem modcom records and errors:

SELECT *

FROM FS_ModcomException

WHERE ModcomCode = 'AP'

AND ErrorType = 'P'

ORDER BY ModcomExceptionKey DESC

After determining the reason of the error and making the necessary fix, please run the following Transact-SQL script at the Fourth Shift database to bring the queue back:



ALTER QUEUE q_ModcomAPTarget WITH STATUS = ON

• Accounts Receivable




Subject: The queue q_ModcomIVTarget is disabled. Please check Fourth Shift database

The queue q_ModcomIVTarget is disabled by error transactions. Modcom IV records will not be processed until the queue is enabled.

Queue Name: q_ModcomIVTarget





SELECT *


WHERE ModcomCode = 'IV'

AND ErrorType = 'P'



ALTER QUEUE q_ModcomIVTarget WITH STATUS = ON

• General Ledger




Subject: The queue q_ModcomGLTarget is disabled. Please check Fourth Shift database

The queue q_ModcomGLTarget is disabled by error transactions. Modcom GL records will not be processed until the queue is enabled.

Queue Name: q_ModcomGLTarget







SELECT *


WHERE ModcomCode = 'GL'

AND ErrorType = 'P'



ALTER QUEUE q_ModcomGLTarget WITH STATUS = ON

Financial Transaction TypesFinancial transactions originating from manufacturing, invoicing, accounts receivable and accounts payable are identified by a Trans Code and Batch Source Code. These predefined identifiers are supplied with each corresponding module.

Financial transactions are categorized into Batch Types, by source, as follows:

General Ledger Transaction BatchingWhen the General Ledger (GLSM) module is installed, the GLSC (G/L Source Code Maintenance) screen displays the list of internal transactions. It can be used to maintain the internal transactions as well as define external transactions for communication with the GLSM module.

Transactions with the same batch source code, status, type and accounting period are combined into a single batch, with a maximum of 9950 transactions per batch. A sequential Batch No is assigned to each new batch, starting with the Last Batch No initialized on the GLCF (G/L Configuration) screen.

Transaction Type Batch Type Description

Manufacturing C placed in a module communication transaction

Accounts payable, accounts receivable and invoicing

A automatically batched

General ledger N, M or S manually created using the GLJE, GLJP and GLJR screens

General ledger consolidated activity C, M or S placed in a module communication transaction and batched by the GLCO (G/L Consolidation Process) screen

External to Fourth Shift C placed in a module communication file for batching by the GLMQ task



• The Batch Source Code and Batch Status used to combine transactions are maintained on the GLSC (G/L Source Code Maintenance) screen and are initially preassigned.

• The Batch Type is based on the transaction source.

• The accounting period is based on the transaction date. Transactions with different dates within the same accounting period are batched together. When the transaction date corresponds to a prior period, the current accounting period is used.

Audit Trail InformationAudit trail information can be accessed to examine transaction history and diagnose sources of error. The two major sources of audit trail information are:

• the AUDT (Item History Audit) screen, which provides on-line transaction history for item-related transactions

• the ARCHIVE.FIL file, which provides a transaction history for all transactions entered in the database

Supplemental audit trail files are created by other operations such as batch processing, purging and history offloading.

The Archive FileThe ARCHIVE.FIL file is an audit trail of the transactions entered into the Fourth Shift system. The ARCHIVE.FIL file is in ASCII comma delimited format (CDF). Numeric fields are not surrounded by quotes. Alphanumeric and date fields are surrounded by quotes.

Each transaction in the ARCHIVE.FIL file starts with identification information in the first six fields. Field values are as follows:

The Transaction Id consists of a Main screen Function Code followed by two digits. The two digits correspond to unique transactions performed on the screen.

The sixth field, the Action Code, identifies the transaction as add, change, delete and so on.

The seventh field is often a transaction type indicator, such as T (Top or header) or B (Bottom or line item). The remainder of the information corresponds to the fields entered during the transaction, generally in the order in which the information was entered.

Note: Not all transactions have a transaction type indicator.

Some system transactions produce multiple, interdependent archive records for one transaction. The G/L Distribution screen used after entering cash receipts on the ARCD (A/R Cash Deposits)

Field# Value

1 Transaction Id

2 User Id

3 Date

4 Time

5 Internal Flag

6 Action Code



screen is one example. In a multi-user configuration, the transactions are not necessarily recorded contiguously in the ARCHIVE.FIL file.

Interdependent archive records include a flag in the last field identifying where a transaction belongs in a sequence. The flags are:

Recovery ToolThe ARCHIVE.FIL file can be used as a tool during recovery. Two utilities are used in preparing the ARCHIVE.FIL file for recovery purposes: ARCREORG and ARCBEXE.

• The ARCREORG utility is used to reorganize the ARCHIVE.FIL file so that interdependent archive records are contiguous. These records include a flag identifying where the transaction belongs in a sequence. The ARCREORG utility uses this flag to reorganize the ARCHIVE.FIL file.

• Contact Fourth Shift Customer Support Services for further information on the ARCBEXE instructions.

SYST TransactionsThe ARCHIVE.FIL file can include SYST transactions which record system activity including signing on, signing off and network statistics. SYST transactions are skipped during the recovery process.

SYST transactions can be included by adding configuration variables to the FS.CFG file. The default setting for writing these transactions is off. See "Configuration Variables" in the Administration Reference section of the System Administration online manual for more information on the RecordLogin and RecordLoginNetStats configuration variables.

The archive records created for the SYST transactions are as follows.

SYST01: User Login"SYST01","User Id","Date","Time","","","Multi-User (y/n)","SystemIdentChar variable value","Unique login identifier","Machine Name","DatabaseType","Database Version"

SYST02: User Logout"SYST02","User Id","Date","Time","","","Number of Seconds signed onto system","Unique login identifier","Machine Name"

SYST03: Abnormal Exit from System"SYST03","User Id","Date","Time","","","Function Code","Status identifier associated with abort","Inquiry Mode (y/n)","Inquiry Status","ABNORMAL EXIT","Error Message","STATUS=(Status Identifier associated with abort)","Database Type","Database Version","Company Name","Serial Number"

BEXE TransactionsThere are two categories of BEXE (Batch Process Execution) transactions included in the ARCHIVE file that record:

• database updates (BEXE00)

Flag Transaction Order

F first

M middle

L last

B both first and last



• activity other than database updates (BEXE01 upwards)

Database update transactions (BEXE00) are considered non-recovered transactions and must be reentered manually during system recovery. Transactions identified as BEXE01 upwards are skipped during the recovery process.

Starting and ending BEXE05 transactions are generated in the ARCHIVE.FIL each time a batch process is executed. These transactions are helpful as troubleshooting tools when errors occur during batch processing.

Receiving ActivityThe ARCHIVE.FIL file is used as the basis for the PORR (Purchase Order Receiving Report) and POSR (Purchase Order Receiving Summary Report) tasks to generate lists of receiving activity during a specified time period. Only the transactions recorded in the ARCHIVE.FIL file are evaluated for these reports.

Retain the ARCHIVE.FIL file for the required period of time in order to generate these reports. Do not delete the ARCHIVE.FIL file as part of your daily maintenance tasks if you wish to generate reports that include a number of days' worth of receiving activity.

External History Data ExtractsThe ARCHIVE.FIL file is used as the basis for EXTERNAL: History data extracts.

Retain the ARCHIVE.FIL file for the required period of time in order to obtain these extracts. Do not delete the ARCHIVE.FIL file as part of your daily maintenance tasks if you wish to extract more than a days' worth of transaction history.

Supplemental Audit Trail FilesAudit trail files are also produced by the following screens and tasks. The files are created in the MFGSYS directory unless otherwise noted.

File(s) Created Description Screen/Task or Utility

APTP.FIL file containing 1099 information for each vendor; used during year-end processing for analyzing and generating 1099 informa-tion

APTP

EDISOPM.IMP EDISOPM.ERR

import file and log file of transactions that were unable to be imported using the SOPM Module

EDIM Module

GLHPPPYY.999 history file for unloaded G/L batches posted for an accounting period; PP is the account-ing period, YY is the year and 999 is the sequence number

GLHP

IMPORT.ERR log file of transactions that were unable to be imported

IMPT

XXX.LOG process log file where XXX is the batch Process ID

BEXE

MODCOMSA.FIL file containing sales and commission infor-mation from the Accounts Receivable Mod-ule; monitor size of file; back up and delete file when necessary

IVPR



See "History File Layouts" for more information about the files created by the APPG, ARPG, GLHP, and OVAR screens and tasks.

Fourth Shift SecurityAccess to Fourth Shift screens and tasks is established using the FCMT (Function Code Maintenance) and PASS (Password Maintenance) screens in the System Control Module. See the System Control manual for more information on Fourth Shift security.

Database BackupsDatabase backups are an essential part of your regular database maintenance. In the event of a system or media failure, complete recovery of the Fourth Shift databases and related data files is impossible without a current and complete database backup.

For more information, see "Database Backups" in the SQL Server Administration and Utilities manual.

Purging Outdated InformationAudit trail information can be accessed to examine transaction history and diagnose sources of error. Audit trail information, both on-line and external, accumulates as you use the system. Attention must be paid to controlling the amount of audit trail information stored at any one time.

The information about purging vary depending on your database server configuration. For more information, see "Purging Outdated Information" in the SQL Server Administration and Utilities manual.

Upgrade InformationRelease Instructions and Release Notes are provided to all Customer Support Program (CSP) subscribers along with the software and documentation for each system release.

MODCOMSL.FIL file containing Sales Analysis related activi-ties - depends on CNFG File Writing Con-figuration value

ARCR, CMTA, COAN, COMT, CPMT, CUID, CUST, INVA, ITMB, ITMC, IVIE, IVPR, OPSL, PICK, SHIP

RCVR.ERR log file for transactions that were unable to be reentered

RCVR

Task/Seq Num.Process Id

batch reports sent to a file rather than the printer

BEXE; Report Destination = 2

user-specified file file for online accounts payable history removed from your system for invoices, cash receipts and purchase order receipts

APPG

user-specified file file for online accounts receivable history removed from your system for invoices, cash receipts and credit memos

ARPG



• Release Instructions contain information about system preparation and installation procedures. These instructions guide you step-by-step through the upgrade process.

• Release Notes is a guide to the major changes and enhancements in the upgrade. You should review the changes before performing the installation. The guide includes information about both global and module-specific changes.

Additional Workstation LicensesYou can purchase additional workstation licenses to increase the number of users able to access the system. Use the following steps to obtain additional workstation licenses.

1. Determine the number of additional workstations, beyond the initial three, needed. For example, if a total of 12 workstation licenses is needed, nine additional workstation licenses should be purchased.

2. Place an order for the additional workstation licenses needed. Include your Fourth Shift serial number with your order.

The new Module Access Key diskette you are sent reflects the total number of licensed workstations and your serial number.

Installing Additional Workstation LicensesWorkstation licenses can be installed several ways:

• Use the Module Access Key when you run the SETUP program to install upgrades or additional modules.

• Use the FSLICENS utility to update the number of workstation licenses for your system. See "FSLICENS" in the Utilities and Tools manual for more information.

Computer Operation PrecautionsYou can avoid many system problems by taking some precautions in computer operations. These precautions and preventive measures focus on the care of your computer equipment and database.

• Install an uninterruptable power supply (UPS) to protect your computer equipment from power disturbances.

• Consider installing a power switch lock to protect your computer from manual power disturbances.

• Consider purchasing dust covers as well as anti-static devices to protect your computer equipment against dust and static electricity.

• Locate your computer equipment in an area that provides protection against accidents that may cause an unexpected shutdown. For example, place all computer cables in a place where people cannot trip over them. The selected area should also provide adequate light and electrical outlets.

• Keep your equipment properly maintained. If you begin to suspect a hardware malfunction, have it checked immediately.

• Perform frequent system backups to protect your data and ensure daily activity disruptions can be kept to a minimum.



• Graph the time your system is in operation and record breakdowns. This allows you to evaluate any performance and operation patterns and evaluate potential hardware problems.

Printing and ReportingFourth Shift produces a broad range of reports and external documents, using a number of different technologies.

• For details on batch process reporting, see Batch Processing in this System Administration manual.

• For details on printing external documents and preprinted forms, see the Fourth Shift Basics online Help.

Report FormatsFourth Shift generates reports and external documents using several different formats.

See “Reporting for SQL Server Systems” in the System online Help for more information.

Reprint Feature for SQL SystemsThe Reprint feature is provided via the FSReport.exe program using various command line parameters. BSETs can be created using the CMND/CONT tasks to generate the reprints. See the Fourth Shift FSReport Command Line Syntax later in this chapter.

FunctionalityThe reprint functionality includes the following:

• Rdl_parms

• DeleteTempData

Rdl_parmsThis function consists of a new remembered key for RDL reports. The remembered key is used to retain the report parameters that were defined for the previous (or most recently run) report on your client session.

• Reports can be generated by the following types of activities within a Fourth Shift session:

- F7

- Print Preview

- Specific screen or batch processes (listed below)

• The Fourth Shift Report Configurator displays a list of the RDL reports that can be reprinted.

• Rdl_parms works the same as all other Fourth Shift remembered keys:

- Per Client Session

If more than one FS session is running on a machine, the remembered key is unique to each session.

- Values are not retained from one client session to another

- Rdl_parms uses the same type of behavior as Order remembered key

Example



An order number is remembered and used on COMT, MOMT, POMT, etc., regardless of what the original order type that last updated the remembered key. The rdl_parms represents the last report generated based on one of the following activities:

• Print Preview

• An F7 is generated via screen activity

• A selected report via a batch process on BSET/BEXE

DeleteTempDataSpecific Batch reports have a new parameter added to allow the reprint process. The new parameter is set in the Properties—Parameters section in Reporting Services using the following options:

- Yes—Any temp data created during processing, while generating the report, will be deleted. This is the system default.

- No—After the report is generated, any temp data created during processing will be retained. Each ISR will overlay this default parameter and users will need to reset it after each ISR install, if they require that setting.

Important: Temp data that is retained must be purged manually using the FS Report Configuator—Purge TempTable tab.

DeleteTempData ReportsThe following list of reports use the DeleteTempData parameter.

Batch Reports Invoice Printing—IVPR

• ARSIVPR

• ARSIVPRF

A/R Statement—ARST

• ARSARST

Other Batch Reports

Supply Demand Analysis

• SDAB

MrpSdab

ABC Analysis

• ABCR

MgrAbcr

Screen Generated ReportsSDAL

MRPSDAL

A/P Checks

Note: Checks can be reprinted using the following methods:

- APCR—is used to reprint checks sent to a file or default printer.



- APCWReportFileName—is an optional variable in FS.CFG and used to send the checks to a file, which can be opened and reprinted to various assigned printers.

APCW Reports

The following APCW formatted reports are initiated via a screen process

• Canadian

APSAPCWCN1L

APSAPCWCN1S

• German

APSAPCWGM1L

APSAPCWGM1S

• United Kingdom

APSAPCWUK2S

APSAPCWUK2SF

• US

APSAPCWUS1L

APSAPCWUS1LF

APSAPCWUS1S

APSAPCWUS1SD

APAPCWUS1SF

A/P Cash Requirements/Payment ApprovalAPRQ screen initiated reports

• APSVENRD

• APSVENS

Other System Environments • VATT

SYSVATT

• Intrastat

ISTIXRU



Reprinting RDL ReportsImportant:

- The reprint functionality is not possible for WebUI sessions.

- Order acknowledgements in the SOPM module do not update the Rdl_parms remembered key.

SecurityBefore using the Reprinting feature, there are two areas of security that must be set up: Fourth Shift and Report Manager.

• Fourth Shift— Anyone using the reprint BSET/BEXE activity needs to be authorized to use the CMND and CONT functions.

• Report Manager—Security needs to be defined for any copies of RDL reports that are uploaded and used in the reprint activity.

The following steps apply to Report Manager only.

1. Select the Properties—Security setting for the report, once the RDL file is uploaded to the appropriate directory.

2. Click the Edit Item Security option.

3. Click the Add a New Role Assignment option.

4. Enter the name you want to authorize in the Group or User Name field.

5. Select one of the following roles:

- Browser

- FSReportUser

6. Click OK.



Reports that Use the DeleteTempData ParameterImportant:

- FSReport.exe from a CMND line will not update the rdl_parms remembered key.

- The BSET parameter line is limited to 60 characters (each line); the total number of CMND/CONT line characters is 512.

- w fsreport must be included as the first entry of the CMND line to allow the system to use a window to execute the commands.

The following steps are required for all reports:

1. Create a copy of the batch report to be reprinted.

2. Upload the report to Report Manager.

3. Set up the Data Source for the report and security authorization.

4. Change the following DeleteTempData settings.

- No—for the original report (example: ArsIVPR)

- Yes—for the copy (example: ArsIVPRcopy1)

The last reprint copy must be set to Yes—delete the temp data.

(Continue with the next steps for reports generated using the batch process)

1. Create the batch tasks that will run the batch process and set up the reprint tasks.

2. Use BEXE to generate the original batch report and the reprint activity.

Examples:

Batch Process Generated Reports

Note:

- This approach will also work for ABCR, ARST, and SDAB.

- The Log file displays all parameter selections.

IVPRI s100030 e100030

CMNDw fsreport –s http://machine.domain.com/ReportServer

CONT-r /SQL/ARSM/ArsIVPRCopy1

CONT-t #rdl_parms# -pa \\printserver\printer



Screen Generated Reports

Note: This approach will work for SDAL (F7/Print Preview), A/P checks, and APRQ processing.

1. Complete steps 1 through 4 (above) for:

- ApsApcwUS1S = No

- ApsApcwUS1SCopy1 = Yes

2. Create the batch tasks that will run the batch process and set up the reprint tasks.

3. Approve your payments and initiate APCW to generate the checks.

4. Run the BSET.

Example:

CMNDw fsreport -s http://machine.domain.com/ReportServer

CONT-r /SQL/APSM/ApsApcwUS1SCopy1


RDL Reports that Do Not Use the DeleteTempData ParameterNote: This approach will work for inventory reports and order related reports, including:

customer orders, manufacturing orders, purchase orders, etc.

1. Do one of the following:

- Run Print Preview

- Press F7 (for example, ITMB reports)

2. Run the BSET.

Examples:


CONT-r /SQL/INVM/InvITMB


(For reprinting a Purchase Order)


CONT-r /SQL/PURM/PurPop1




Fourth Shift FSReport Command Line Syntax

Report InfoNote: These parameters are used for generating reports; they should not be used with the

–o parameter.

Parameters Description

-s <reportServer>— This parameter defines the report server URL <report-Server> to be opened with. The virtual directory of the report server is also included.

Example: -s http://guoxp.softbrandsamer.com/ReportServer

-r <reportName> This parameter defines the report name string <report-Name> to be opened with. The report name is stored in the RS ReportServer database after the report is pub-lished.

Example -r /SystemName/INVM/InvItmb

The viewer will use the report name to build report URL for RS to render real time report.

Example: http://guoxp.softbrandsamer.com/reportserver?/INVM/InvItmb

-t <parameterCount> <parameter1>[<parameter2>] [<parameter3>] [<…>] [<parameterN>]

Optional, defines the parameter(s) to be passed to the report. The parameterCount must match the number of the parameter values.



File Access

Report Mode

If the Report Mode is not defined, the viewer will open the report to the preview window. Otherwise, either of the following modes can be used:


-o <reportFile> This parameter defines the populated report file <reportFile> to be opened. Typically, the format will be in PDF, TXT, MHTML, or RTF.

Example: -o SDAB01SDA.PDF

-l <logFileName> This parameter defines the log file name <logFile-Name>.

• If -l is defined, messages are written to the log file and no windows message pop ups are allowed.

• If –l is not defined, all messages will be shown on the pop-up window.


-v To display the report to the preview window.

-pd To print the report to the Default printer.

-pa <printer> To print the report to the defined <printer>, where <printer> is the Printer Name.

-ps To print the report with Printer Setup dialog.

-xd <outFile> [-f <format>] To export the report file to the disk file <outFile> with for-mat defined by [-f <format>]

• Where <format> will be Excel (Excel/XLS format), CSV (Comma Separated Value Format), MHTML (MIME HTML), PDF (Portable Document Format), TIFF (Tagged Image File), or XML (Extensible Markup Language format).

• If the -f <format> is not defined, the PDF format will be used as the default format.

-o <fileToSend> -xe <emailAddress> To send the report file <fileToSend> to the e-mail address list <emailAddress>.

• The e-mail address list <emailAddress> is a ‘;’ (semicolon) separated e-mail address string.

-o <fileToSend> -xs To send the report file <fileToSend> as an attachment and open up a send e-mail dialog window for user to fill in messages and send the e-mail.



Customizing Site HelpYou 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. Custom Site Help can also link to standard operating procedures or any available Internet or Intranet site.

Each Fourth Shift screen, task, or window can have a single site help file. Site help files are displayed when you click the Custom Site Help button from any help screen.

If no Custom Site Help exists, the About Site Help page is displayed.

Developing Custom Site Help ContentA site help file is a Hypertext Markup Language (HTML) source file. You can use any HTML authoring tool to write and create site help files.

Site help files can include any type of content supported by HTML, including text, graphics, hyperlinks, and scripts. Since the Fourth Shift help viewer uses components of Microsoft Internet Explorer, the help you write appears exactly as it would in an Internet browser.

Referencing External FilesIf you reference graphics, external scripts or style sheets in your HTML content, use a relative reference and assume that the site help file and the external file are in the same directory. For example, to include a graphic called MYGRAPHIC.GIF in your site help content, use a tag similar to the following:

<img src=mygraphic.gif>

If you want, you can reference the same style definitions used by Fourth Shift help in your site help. This allows you to maintain a consistent look to all of the help text your users see. To use standard Fourth Shift help styles, include a <LINK> tag that references the CUSTOMERDOCUMENT.CSS and CUSTOMERCATALOG.CSS style sheet files. The definitions for the standard Fourth Shift help styles are included in these style sheets.

Sample Custom Site Help FileA sample site help file, SampleSiteHelp.html is installed with Fourth Shift. This sample file describes the site help feature and includes basic instructions for creating and publishing site help. It is displayed when the Custom Site Help button is clicked on any help screen.

If there is no Custom Site Help for a particular screen, then the “About Site Help” page is displayed.

If you want your customizable site help files to match the look of Fourth Shift online help, you can use this file as a template for your help, along with the cascading style sheets (.CSS files). You may choose to modify CustomerDocument.css and CustomerCatalog.css for your own help files.

Note that the sample file has the extension .html. However, Custom Site Help files must end in .htm.

Site Help File NamesThe name of a site help file must match the function code of the screen or task, with an .HTM file extension. For example, the name of the site help file for the ITMB (Item Master) screen is ITMB.HTM, and the name of the site help file for the BOPR (Batch Order Print) task is BOPR.HTM.

Site help files for windows that cannot be accessed directly from a function code are named for the code used to assign security to the window on the PASS (Password Maintenance) screen, if applicable.



If you are not sure of the correct name for a site help file, you can view the list of names in Custom Site Help File Names. This topic lists the names of the corresponding site help files for each of the screens, tasks, and windows in the Fourth Shift system.

Note: In most cases, inquiry screens such as the ITMI (Item Master Inquiry) screen use the same site help files as the maintenance version of the screen. For these screens, you cannot create a special site help file for the inquiry-only versions of the screen. However, separate site help files for certain inquiry screens are allowed. Refer to Custom Site Help File Names to see which inquiry-only screens allow a separate site help file.

Publishing Site Help ContentTo make a site help file available to users, copy the file to the MFGSYS\H\SITE directory. The user then clicks the Custom Site Help button on the help topic.

Fourth Shift Transactional ModuleThe Fourth Shift Transactional Interface module (FSTM) allows you to update the Fourth Shift production database without using the traditional GUI or the Import feature. In FSTM, standard Fourth Shift data entry rules are enforced while using an API that can accept transactions from your other applications.

When you purchase FSTM, the FSTI Software Development Kit (SDK) is included. This SDK is a resource you can reference as you construct Fourth Shift archive format transactions (called FSTI transactions) that are to be processed into Fourth Shift using FSTM.

Note: For complete information about the FSTI Software Development Kit (SDK), please reference the Fourth Shift Transactional Interface Software Development Kit (FSTI SDK). This document is located in the mfgsys/fstm/user guide directory on your workstations licensed for FSTM.

FSTM requires the Fourth Shift Remoting Service. This service is installed on the database server automatically when you install Fourth Shift and have purchased the FSTM module. See "Fourth Shift Remoting Service" for more information about this service.

Fourth Shift Remoting ServiceThe Fourth Shift Remoting Service is used to send data to the Fourth Shift database as an alternative to the data import continuous recovery functionality. Applications can use this service to send import records to Fourth Shift and to receive processing information.

The Shop Floor Module requires that this service be running to perform update transactions.

The Fourth Shift Remoting Service is an integral part of the Fourth Shift Transactional Interface (FSTM) Module; see "Fourth Shift Transactional Interface" for more information about this module.

The Fourth Shift Remoting Service is its own server on the Administrative Tools > Services window on the server. It is started and stopped independently of the Fourth Shift server.

The Fourth Shift Remoting Service consumes a user license.



Fourth Shift Services and License ConsumptionFourth Shift Services uses several Microsoft Windows services to successfully run applications and complete transactions. Fourth Shift Remoting Service consumes a Fourth Shift license when it runs. This should be accounted for when determining the number of user licenses needed for your system.

ApplicationsMultiple Fourth Shift applications running on a workstation will consume only one user license. For Terminal Server, one license is consumed for each session.


Fourth Shift Release 7.50 Custom Site Help File Names

Custom Site Help File NamesEach site help file must have a specific name to be linked from the Fourth Shift screen help (Custom Site Help button). Each Custom Site Help file must have the file extension .HTM.

In most cases, the site help file name matches the function code of the screen or task. Use the table below (alphabetized by Fourth Shift screen name) to determine the site help file name to use for each Fourth Shift screen, task, or window.

Site Help File Name Fourth Shift Screen Name

A – Custom Site Help File NamesAP5E.HTM A/P 1099 Category Codes

AP1X.HTM A/P 1099 Category Summary

AP4E.HTM A/P 1099 Distribution

APTX.HTM A/P 1099 Distribution by Vendor

APTP.HTM A/P 1099 Processing

APAG.HTM A/P Account Aging

APTB.HTM A/P Aged Trial Balance

APRQ.HTM A/P Cash Requirements/Payment Approval

APCR.HTM A/P Check Reprint

APCP.HTM A/P Close Period Analysis

APCF.HTM A/P Configuration

APDS.HTM A/P Disbursements

APID.HTM A/P Invoice Distribution

APIE.HTM A/P Invoice Entry

APIH.HTM A/P Invoice History

API1.HTM A/P Invoice Matching Detail

AP1V.HTM A/P Invoice Payment Detail

APRG.HTM A/P Invoice Register

APIP.HTM A/P Invoice/Payment Audit

AP1O.HTM A/P Invoices by PO/Seqn

APIV.HTM A/P Invoices by Vendor

APPA.HTM A/P Manual Payment Application

APMQ.HTM A/P Module Communication

AP2H.HTM A/P Payment Application Detail

APAH.HTM A/P Payment Application History

APCA.HTM A/P Payment Assignment

APR1.HTM A/P Payment Detail



APCW.HTM A/P Payment Processing

APRC.HTM A/P Payment Reconciliation

APCK.HTM A/P Payment Register

APCV.HTM A/P Payment Void

AP3H.HTM A/P Payment Void Detail

AP4H.HTM A/P Payment Void Range

APIR.HTM A/P PO Receipts by Invoice

APIC.HTM A/P Invoice Creation

APIT.HTM A/P Invoice Template

AP2I.HTM A/P PO/Inv Variance by Invoice

APPD.HTM A/P Prior Period Disbursements

APPI.HTM A/P Purchase Price Variance by Item

APPV.HTM A/P Purchase Price Variance Report

APPG.HTM A/P Purge

APEX.HTM A/P Receipt Exceptions

APPO.HTM A/P Receipts by Purchase Order

AP1I.HTM A/P Received Item List

AP1E.HTM A/P Receiving Detail

APRE.HTM A/P Recurring Invoice

APRH.HTM A/P Recurring Invoice History

APRL.HTM A/P Requirements List

APUV.HTM A/P Unvouchered Report

APVT.HTM A/P VAT Register

APPH.HTM A/P Vendor Payment History

ARAG.HTM A/R Account Aging

ARTB.HTM A/R Aged Trial Balance

ARAD.HTM A/R Aging Definition

AR4A.HTM A/R Application Options

ARCD.HTM A/R Cash Deposits

ARRJ.HTM A/R Cash Receipts Journal

ARCR.HTM A/R Cash/Credit Memo Application

ARCP.HTM A/R Close Period Analysis

ARCF.HTM A/R Configuration

ARCJ.HTM A/R Credit Memo Journal




ARPH.HTM A/R Customer Payment History

IVRC.HTM A/R Invoice Creation

AREX.HTM A/R Invoice Exceptions

ARIH.HTM A/R Invoice History

AR2C.HTM A/R Invoice Payment Detail

ARIR.HTM A/R Invoice Register

ARIP.HTM A/R Invoice/Payment Audit

ARIC.HTM A/R Invoices by Customer

AR1H.HTM A/R Payment Application Detail

ARAH.HTM A/R Payment Application History

ARPD.HTM A/R Prior Period Cash Deposits

ARPG.HTM A/R Purge

IVRE.HTM A/R Recurring Invoice

IVR2.HTM A/R Recurring Invoice Header Detail

IVR1.HTM A/R Recurring Invoice Line Detail

ARSR.HTM A/R Service Charge Review

ARSC.HTM A/R Service Charges

ARBS.HTM A/R Statement Export

ARST.HTM A/R Statement Printing

ARTX.HTM A/R Tax Register

ABCR.HTM ABC Analysis Report

ACCX.HTM Access Extract

ACCT.HTM Account Verification Report

BKC1.HTM Accrual Basis Period Detail

cstu.HTM Actual Cost Update

AVIT.HTM Approved Vendors by Item

AVII.HTM Approved Vendors by Item Inquiry

NM1A.HTM Article Description

ASCX.HTM ASCII Extract

SH1P.HTM Available Customer Shipments

BATP.HTM Available to Promise

ATPS.HTM Available to Promise Server

B – Custom Site Help File NamesBKFL.HTM Backflushing




BKSV.HTM Backflushing Server

BRSA.HTM Backlog Rules Shipment Allocation

BKBL.HTM Bank Balance

BKTR.HTM Bank Balance Translation

BK1A.HTM Bank Browse

BKCB.HTM Bank Cash Book

BKCJ.HTM Bank Cash Journal

BKFT.HTM Bank Funds Transfer

BKMT.HTM Bank Master

BK2A.HTM Bank Payment Approval

BKRC.HTM Bank Reconciliation

GL1F.HTM Banking Configuration

BAMT.HTM Batch Assignment

BOPR.HTM Batch Order Print

BEXE.HTM Batch Process Execution

BSET.HTM Batch Process Setup

BS1T.HTM Batch Processes

BAPP.HTM Batch Selection Maintenance

SBOL.HTM Bill of Lading

PSC2.HTM Bill of Material Accuracy Results

BIL1.HTM Bill of Material Detail

OPS1.HTM Bill of Material Detail

BR3C.HTM Browse Setup (customer)

BR3I.HTM Browse Setup (item)

BR3O.HTM Browse Setup (order)

BR3S.HTM Browse Setup (ship to)

BR3V.HTM Browse Setup (vendor)

POAS.HTM Buyer Action by Item

OPC2.HTM Buyer/Planner Code Maintenance

BKC2.HTM Cash Basis Period Detail

C – Custom Site Help File NamesCSPG.HTM Cash Management Purge

CSCP.HTM Cash Mgmt Close Period Analysis

BKM3.HTM Cash Receipts




PCS2.HTM Cash Set Selection

PCS1.HTM Cash Set Selection Setup

CACF.HTM CIM Customizer Configuration

CMCF.HTM CIM Customizer Mapping Configuration

OVAR.HTM Close Order Analysis/Order Variance

CORV.HTM CO Receipt/Reverse Ln# Selection

CMTA.HTM Commission Code Table

CNFA.HTM Configuration of Interface Account Numbers

POC1.HTM Contract Header Detail

POC1A.HTM Contract Header Detail

CT6S.HTM Contract Item Detail

POC2.HTM Contract Item Detail/Pricing

CP1S.HTM Contract Purchase Orders

CT1S.HTM Contract Selection

CT3S.HTM Contract Summary

CBIL.HTM Copy Bill of Material

CPBK.HTM Copy Price Book

COMP.HTM Cost Comparison Report

CCAN.HTM Cost Control Action

CROV.HTM Cost Roll-Over

CROL.HTM Cost Roll-Up

SD2L.HTM Cost Selection

CNFC.HTM Cost Type Setup

MCS2.HTM Cost Update Selection (from MCST)

PCS4.HTM Cost Update Selection (from PCST)

CSL1.HTM Costed Bill Detail

CMLB.HTM Costed Multi-Level Bill

CSLB.HTM Costed Single Level Bill

CCFG.HTM Costing Configuration

CCMT.HTM Currency Code Maintenance

CCON.HTM Currency Conversion

CCEX.HTM Currency Exchange Rate Maintenance

CVAL.HTM Current Configuration Values

COCP.HTM Custom Order Copy




COSV.HTM Custom Order Save

CPM2.HTM Custom Product Component Detail

CPM1.HTM Custom Product Detail

CINV.HTM Custom Product Finished Inventory Report

LX1S.HTM Custom Product Line Item Location Selection

LX2S.HTM Custom Product Line Item Location Selection

CPMT.HTM Custom Product Maintenance

CWIP.HTM Custom Product WIP Report

BR1C.HTM Customer Browse

BR2C.HTM Customer Browse Detail

CCAT.HTM Customer Catalog

CUS2.HTM Customer Financial Detail

AR6C.HTM Customer Invoice List

CIMT.HTM Customer Item Maintenance

CUST.HTM Customer Master by Customer Id

CUS1.HTM Customer Name/Address Detail

COMT.HTM Customer Order

COAN.HTM Customer Order Action

COBK.HTM Customer Order Backlog Report

COBP.HTM Customer Order Export

COS1.HTM Customer Order Header Detail

COR1.HTM Customer Order Receipt/Reverse

COCD.HTM Customer Orders by Customer Id

AR6A.HTM Customer Payment List

COYE.HTM Customer Year-End Processing

CUPB.HTM Customers Using Price Book

CUPI.HTM Customers Using Price Book Inquiry

D – Custom Site Help File NamesTMPT_POP.HTM Data Conversion Table

XTPOP1.HTM Data Export Selection

IMPT.HTM Data Import

DVUD.HTM Data View Definition

DBSX.HTM dBase Extract

DEUP.HTM Deferred Update




SDA1.HTM Demand Peg Detail

BKM4.HTM Disbursements

SD1L.HTM Display Basis Setup

DIST.HTM Distributors by Vendor

DISI.HTM Distributors by Vendor Inquiry

CMND.HTM DOS Command Shell

E – Custom Site Help File NamesEDIB.HTM EDI Batch Marking

EDCF.HTM EDI Configuration

EDIX.HTM EDI Extract

EXLX.HTM Excel Extract

EXRU.HTM Exchange Rate Update

QUIT.HTM Exit Fourth Shift from a Batch Process

XT1T.HTM Extended Text

F – Custom Site Help File NamesFCST.HTM Forecast

GL2E.HTM Foreign Cash Reference

MENU.HTM Fourth Shift Master Menu

PROG.HTM Fourth Shift Program Execution

LOGON.HTM Fourth Shift Sign-On

FCMT.HTM Function Code Maintenance

G – Custom Site Help File NamesGL2A.HTM G/L Account Attributes

GLAG.HTM G/L Account Group

GL1T.HTM G/L Account Group/No List

GL1A.HTM G/L Account No List

GLAT.HTM G/L Account Top Down Inquiry

GLTP.HTM G/L Account Type Maintenance

GLAU.HTM G/L Account Update

GLAW.HTM G/L Account Where Used Inquiry

GLAV.HTM G/L Account/Organization Validation

GL1Q.HTM G/L Batch Detail




GLSI.HTM G/L Batch Status Inquiry

GLSS.HTM G/L Batch Submission Status

GLBL.HTM G/L Budget List

GLBR.HTM G/L Budget Roll

GLBD.HTM G/L Budget/Planning Type Definition

GLBU.HTM G/L Budget/Planning Update

GLCA.HTM G/L Chart of Accounts

GLCI.HTM G/L Chart of Accounts Inquiry

GLCF.HTM G/L Configuration

GLCO.HTM G/L Consolidation Process

GLGQ.HTM G/L Current Period Group Inquiry

GLDQ.HTM G/L Detail Account Inquiry

AP2E.HTM G/L Distribution (APSM Module)

AR2E.HTM G/L Distribution (ARSM Module)

AR2F.HTM G/L Distribution (ARSM Module)

CS2E.HTM G/L Distribution (CSHM Module)

CS2F.HTM G/L Distribution (CSHM Module)

GLHP.HTM G/L History Process

GLJE.HTM G/L Journal Entry

GLJD.HTM G/L Journal Entry Delete

GLEX.HTM G/L Journal Entry Exceptions

GLJI.HTM G/L Journal Entry Inquiry

GL1R.HTM G/L Journal Entry List

GLJL.HTM G/L Journal Entry List

GLJP.HTM G/L Journal Entry-Prior Period Adjustment

GLJR.HTM G/L Journal Entry-Recurring/Templates

GLM1.HTM G/L Master Account Detail

GL1E.HTM G/L Master Account Recap

GLMA.HTM G/L Master Accounts

GLMQ.HTM G/L Module Communication

GL1O.HTM G/L Org No List

GL2Q.HTM G/L Org/Acct Group List

GL2T.HTM G/L Organization Group/No List

GLOS.HTM G/L Organization Structure




GLOT.HTM G/L Organization Top Down Inquiry

GLOW.HTM G/L Organization Where Used Inquiry

GLPC.HTM G/L Period Close

GLR1.HTM G/L Recurring/Template Trans Detail

GLRC.HTM G/L Report Copy

GLRD.HTM G/L Report Definition

GL2D.HTM G/L Report Definition Error Message List

GL1D.HTM G/L Report List

GLRL.HTM G/L Report Listing

GLRP.HTM G/L Report Print

RTCF.HTM G/L Restructuring Configuration

RTCT.HTM G/L Restructuring Consolidation Translation

RTIN.HTM G/L Restructuring Data Integrity Test

RTEX.HTM G/L Restructuring Execution

RTMT.HTM G/L Restructuring Master Acct Translation

RTPR.HTM G/L Restructuring Preview and Verification

RTST.HTM G/L Restructuring Status

GL1C.HTM G/L Source Code List

GLSC.HTM G/L Source Code Maintenance

GL2C.HTM G/L Trans Description Definition

GLJ1.HTM G/L Transaction Detail

GLTG.HTM G/L Trial Balance/General Ledger

GL1U.HTM G/L Year/Types List

GASN.HTM Generate Advance Ship Notice

GTED.HTM Generate EDI Transactions

XT2T.HTM Global Extended Text

XT3T.HTM Global Extended Text

XT1S.HTM Global Extended Text Selection

H – Custom Site Help File NamesAUD1.HTM History Detail

I – Custom Site Help File NamesIHIR.HTM In-Inspection and On-Hold Inventory by Order

API2.HTM A/P Intrastat Transaction




IVI3.HTM A/R Intrastat Transaction

ITM7.HTM Intrastat Item

ITM8.HTM Intrastat Item

ISTH.HTM Intrastat Reporting History

ISMT.HTM Intrastat Mode of Transportation

ISMS.HTM Intrastat Member State

ISDT.HTM Intrastat Delivery Terms

ISCF.HTM Intrastat Reporting Configuration

ISCC.HTM Intrastat Commodity Code

CUS4.HTM Intrastat Customer

CUS5.HTM Intrastat Customer

VEN4.HTM Intrastat Vendor

VEN5.HTM Intrastat Vendor

IACR.HTM Inventory Accuracy Report

PSC1.HTM Inventory Accuracy Results

INVA.HTM Inventory Adjustment

ICCR.HTM Inventory Cycle Count Report

ITHR.HTM Inventory History and Activity Report

ITHC.HTM Inventory History Cost Report

SS2I.HTM Inventory History List

ITHP.HTM Inventory History Purge

ITHU.HTM Inventory History Update

IMTR.HTM Inventory Move

ST11.HTM Inventory Status

INVR.HTM Inventory Valuation Report

IVIA.HTM Invoice Adjustments

IVIE.HTM Invoice Entry and Maintenance

IVI2.HTM Invoice Header Detail

IVI1.HTM Invoice Line Item Detail

ARMQ.HTM Invoice Module Communication

IVPR.HTM Invoice Printing

IVEX.HTM Invoice Printing Export

IVRR.HTM Invoice Reprinting

IVRX.HTM Invoice Reprinting Export




IVRV.HTM Invoice Review

IVCO.HTM Invoices by Customer Order

IVRH.HTM Invoices by Recurring Reference

BR1A.HTM Item Availability

BR1I.HTM Item Browse

BR2I.HTM Item Browse Detail

ITCB.HTM Item Cost Book

AUDT.HTM Item History Audit

AUDP.HTM Item History Purge

LO1T.HTM Item Lot Receipt

ITM5.HTM Item Lot Trace and Serialization Detail

ITMB.HTM Item Master

ITM1.HTM Item Master Detail

ITM2.HTM Item Master Planning Detail

SDA3.HTM Item Master Planning Detail

IPPD.HTM Item Planning Parameters

ITPB.HTM Item Price Book

PSC3.HTM Item Responsibility Assigned Results

ITMC.HTM Item/Work Center Cost Data

VEIT.HTM Items Supplied by a Vendor

ISVI.HTM Items Supplied by Vendor

J K – Custom Site Help File NamesJEST.HTM Job Estimates and Performance

L – Custom Site Help File NamesLRRP.HTM Labor/Resource Reporting

PSC4.HTM Lead Times Assigned Results

SH2I.HTM Line Item Packaging

LMMT.HTM Location Master

LC1S.HTM Location Selection

LC2S.HTM Location Selection

LC3S.HTM Location Selection Setup

LM1T.HTM Lot Characteristics and Attributes

LT3S.HTM Lot Detail




LEXP.HTM Lot Expiration/Retest Evaluation

LMST.HTM Lot Master

LT1S.HTM Lot Selection

LT2S.HTM Lot Selection

LSDA.HTM Lot Size Days Analysis

LSD1.HTM Lot Size Multiple Detail

LVAL.HTM Lot Trace Bill Validation Report

LOTR.HTM Lot Trace Inquiry

LO2R.HTM Lot Trace Issue Detail

LO3R.HTM Lot Trace Receipt Detail

LTCF.HTM Lot Trace/Serialization Configuration

LHIS.HTM Lot Trace/Serialization History Offload

M – Custom Site Help File NamesMPED.HTM Maintain EDI Partner Data

MPIT.HTM Maintain Trading Partner Items

MOMT.HTM Manufacturing Order

MCST.HTM Manufacturing Order Cost Analysis

MOFR.HTM Manufacturing Order Follow-Up Report

MOM1.HTM Manufacturing Order Line Item Detail

MOR1.HTM Manufacturing Order Receipt/Reverse

BILLMASK.HTM Mask Setup

COMT_POP.HTM Mask Setup

IMTR_POP.HTM Mask Setup

INVA_POP.HTM Mask Setup

POMTMASK.HTM Mask Setup

BKR2.HTM Mass Reconciliation

MPSS.HTM Master Production Schedule Summary

MPSR.HTM Master Production Schedule Summary Report

MSMT.HTM Master Schedule Maintenance

MOA1.HTM Material Shortages Detail

MSCF.HTM Message Configuration

MS1F.HTM Message Configuration Detail

MORV.HTM MO Receipt/Reverse Ln# Selection

SUBM.HTM Module Menu




PLNG.HTM MRP Planning

MCCF.HTM Multi-Currency Configuration

MBIL.HTM Multi-Level Bill Inquiry

MUSE.HTM Multi-Level Where Used Inquiry

N – Custom Site Help File NamesBKM2.HTM Name, Address & Contacts

NMTA.HTM National Motor Freight Code Table

O – Custom Site Help File NamesLO6R.HTM Offline Prompt

IORD.HTM Open and Released Orders by Item

POVD.HTM Open and Released Orders by Vendor

POA2.HTM Open Order Detail

OPCF.HTM Operations Performance Configuration

OPC1.HTM Operations Performance Configuration Detail

OPFM.HTM Operations Performance Module Menu

OPMA.HTM Operations Performance Monthly Analysis

OPSL.HTM Option Selection

BR1O.HTM Order Browse

STA1.HTM Order Detail

ORDR.HTM Order Number Assignment Configuration

ORST.HTM Order Status Summary

SB3L.HTM Orders on Shipment

P – Custom Site Help File NamesSB1L.HTM Package Content

SHI1.HTM Packaging Detail

CONT.HTM Parameter Continuation Line

PASS.HTM Password Maintenance

APD1.HTM Payee Detail

APT1.HTM Payer Detail

APR2.HTM Payment Selection

PF1C.HTM Performance Data Update

PREV.HTM Period Review




PICK.HTM Picklist

PIC1.HTM Picklist Detail

PSC8.HTM Planned Shipments Not Past Due

MOAN.HTM Planner Action

PSC6.HTM Practical Schedules Planned

IVPP.HTM Preprinted Invoices Report

PBCT.HTM Price Book Contents

PBCI.HTM Price Book Contents Inquiry

PBMT.HTM Price Book Master

PBMI.HTM Price Book Master Inquiry

PBII.HTM Price Book Usage by Item

PRTX.HTM Printed Extract

PSCP.HTM Probable System Communication and Performance

BS2T.HTM Process Tasks

IPP1.HTM Projected Item Results

POMT.HTM Purchase Order

POCP.HTM Purchase Order Contract Purge

POCR.HTM Purchase Order Contract Report

POCT.HTM Purchase Order Contract/Price Quote

PCMT.HTM Purchase Order Cumulative Data

POBP.HTM Purchase Order Export

POM1.HTM Purchase Order Header Detail

CPM3.HTM Purchase Order Line Item Detail

POM2.HTM Purchase Order Line Item Detail

PL1P.HTM Purchase Order Line Items

POA3.HTM Purchase Order Receipt History

PORV.HTM Purchase Order Receipt/Reverse/Return

PORR.HTM Purchase Order Receiving Report

POSR.HTM Purchase Order Receiving Summary Report

PCST.HTM Purchase Order S-Line Cost Analysis

POA1.HTM Purchased Component Detail

POCF.HTM Purchasing Configuration

POYE.HTM Purchasing Year-End Processing

Q R – Custom Site Help File Names




BKR1.HTM Reconciliation Detail

PSC7.HTM Released Orders Scheduled When Needed

RPRT.HTM REPORTS

RVED.HTM Review EDI Transactions

REDI.HTM Review EDI Transactions Inquiry

S – Custom Site Help File NamesSPFR.HTM Schedule Performance Reports

CT2S.HTM Selection Setup

SN2T.HTM Serial Number List

SN1T.HTM Serial Numbers Shipped

CDIR.HTM Set Drive and Directory

SHIP.HTM Ship

BR1S.HTM Ship to Browse

BR2S.HTM Ship to Browse

SS1I.HTM Shipment Allocation List

SHPI.HTM Shipment Inquiry

SHPL.HTM Shipment Log

SH2P.HTM Shipment Order Detail

SH1I.HTM Shipments by Line Item

SH1IA.HTM Shipments by Line Item

SHCF.HTM Shipping Configuration

SREV.HTM Shipping Order Review

BILL.HTM Single Level Bill

BILI.HTM Single Level Bill Inquiry

WUSE.HTM Single Level Where Used Inquiry

SCMD.HTM Small Command Execution

SPRG.HTM Small Fourth Shift Program Execution

PSC5.HTM Standard Costs Assigned Results

COS2.HTM Standard Product Detail

BR2T.HTM Standard Text Detail

SSII.HTM Stock Status Inquiry by Item

SSIL.HTM Stock Status Inquiry by Location

STID.HTM Stockroom Action by Customer

STAD.HTM Stockroom Action by Date




ST4D.HTM Stockrooms

SUND.HTM Sundry Disbursements

SUPD.HTM Sundry Prior Period Disbursements

SUPR.HTM Sundry Prior Period Receipts

SUNR.HTM Sundry Receipts

SDA2.HTM Supply Peg Detail

SDAL.HTM Supply/Demand Analysis

SDAB.HTM Supply/Demand Analysis Report

CNFG.HTM System Installation Setup

RCVR.HTM System Recovery

T – Custom Site Help File NamesTX2A.HTM Tax Base Calculation Mask

TXTA.HTM Tax Code Table

TXCF.HTM Tax Configuration

T2MT.HTM Template Browse

TMPT.HTM Template Maintenance

STOP.HTM Terminate Batch Process

TEXT.HTM Text Review

TXWU.HTM Text Where Used

LO1R.HTM Trace Level Setup

BR1H.HTM Transaction History

TRUD.HTM Transaction Update

NEXT.HTM Transport to Function or Menu

U – Custom Site Help File NamesSD3L.HTM User Defined Value

V – Custom Site Help File NamesVATT.HTM Value Added Tax Code Table

API5.HTM VAT Summary (APSM Module)

API6.HTM VAT Summary (APSM Module)

IV4E.HTM VAT Summary (ARSM Module)

BR1V.HTM Vendor Browse

BR2V.HTM Vendor Browse Detail




VEN3.HTM Vendor Configuration

INV1.HTM Vendor Invoice Browse

VITI.HTM Vendor Item Inquiry

VEND.HTM Vendor Master by Vendor Id

VEN1.HTM Vendor Master Detail

VPFR.HTM Vendor Performance Report

QUOT.HTM Vendor Price Quotes by Item

QUOI.HTM Vendor Price Quotes by Item Inquiry

QSRC.HTM Vendor Price Quotes by Quote Source

VDSC.HTM Vendor Scheduling/Commitment Report

VD1T.HTM Vendor/Item Detail

VSDT.HTM Vendors Supplied by Distributor

VSDI.HTM Vendors Supplied by Distributor Inquiry

VDIT.HTM Vendors That Supply an Item

W X Y Z – Custom Site Help File NamesWACFSYSM.HTM Windowing Application Configuration

WIPL.HTM WIP Item List

WIPR.HTM WIP Report

WIPS.HTM WIP Summary by Value Report



Fourth Shift Release 7.50 Batch Processing

Batch ProcessingThe batch processing feature allows you to group a number of tasks together, including updates and reports, in a specific order. Once a batch process is set up, the process can be executed whenever necessary.

Batch processing requirements depend on the modules you have installed and the size of your database. Procedures should be established for your processing requirements.

Batch SetupBatch processes are set up using the BSET (Batch Process Setup) screen. The Function Codes for each task in the system transport you to the BSET screen.

Batch processes can contain several types of tasks including:

• Fourth Shift Tasks. These tasks update the Fourth Shift database, generate reports or extract Fourth Shift information.

• Command Line Tasks. The command line tasks are available to allow you to execute operating system commands from within the system. These command line tasks can also be used to access external applications using the CIM Customizer Module.

See Setting Up the Module in the System Control online manual for more information on the BSET screen and command line tasks.

Parameter Entry and IdentificationTasks may include required and/or optional parameters. Required parameters, such as date ranges, must be identified before you can execute a batch process. Optional parameters, such as printing a report, can be identified when needed.

Entering ParametersParameters are entered in the Parameters field on the BSET screen. Parameters can be continued onto additional lines by using the CONT (Parameter Continuation Line) task. The CONT task allows you to continue entering parameters that exceed the length of the first Parameters field.

Identifying Parameters: Fourth Shift TasksEach parameter for a task is identified by a unique character. This character can be an initial character or an independent character. For example:

• The AUDP (Item History Purge) task has several required parameters. Parameter 1 is identified by entering the initial character "E" before the ending purge date (E033104) and by entering the initial character “V” before a Y (yes) or N (no) for validation (VY).

• The ACCT (Account Verification Report) task has several optional parameters. Parameter 1 is identified by entering the independent character "C" for Customer Master account numbers. Parameter 2 is identified by the independent character "I" for Item Master account numbers.

Parameters for a Fourth Shift task can be entered in any order.



Identifying Parameters: Command Line TasksCommand line task parameters consist of two parts: a command and parameters. A command could be a DOS command such as COPY or the command for the CIM01 functionality to call external applications using the CIM Customizer Module (CSTM). Parameters are whatever is required by the command.

For example, the PROG task is used to call the CIM01 functionality using the program parameter 01 (external application identifier).

01 PROG CIM01 01

Parameters with Embedded SpacesIf you need to specify a parameter which includes a data value with an embedded space, use double quotes around the data value. For example, if you need to specify a customer identifier with a space the parameter would look similar to "CID 100" where C is the parameter character.

File Location SpecificationSome tasks read from, or write to, files outside the Fourth Shift system. The file locations, for both Fourth Shift and command line tasks, can be specified using several methods including:

• Specific Drive/Directory Locations. A specific path is the fully qualified directory location of a program file. A specific path could also include the drive letter as part of the directory identifier.

• Configuration Variable Keywords. Keywords correspond to the configuration variables for Fourth Shift directories. Keywords consist of the configuration variable surrounded by $ symbols. See the System Operation section of this manual for more information on configuration variables.

• Default Locations. Default locations vary based on whether you are using a Fourth Shift or command line task. See "Using Default Locations" in the Setting Up the Module section of the System Control online manual for more information.

Parameter ValidationParameters are verified by pressing F4 in the Parameters field. If you use the CONT task to continue the Parameters field entry, press F4 in the Parameters field of the primary task to verify the combination of the primary task and CONT parameters.

The LOG file produced when the batch process is executed contains the complete Parameters contents from all lines used by the task during execution. This enables you to verify your parameters entries if errors are encountered.

See Setting Up the Module in the System Control online manual for more information on validating parameters.

Task On-Line HelpThe BSET screen provides two types of on-line help: BSET screen help and task-specific help.



On-line help for the BSET screen is available when BSET is displayed in the Function field and the line marker is not positioned on a task in the Task Identification section. Press F3 or F2 to display on-line help for the BSET screen.

On-line help for specific tasks is available two ways.

• Identify the task in the Function field and enter the Process Id. Press ENTER. If other tasks are listed, press F6 to open a new line. Press F3 or F2 to display the on-line help for the task identified in the Function field.

• Identify the task in the Task field. Tab back to the Task field and press F4 to display the Task Description. Press F3 or F2 to display the on-line help for the task.

Batch Setup SuggestionsThe following suggestions might be helpful when setting up batch processes:

• Number tasks in five- or ten-digit increments. In this way, you can easily add tasks in the future, if necessary.

• Use a unique Seq Num for each task. Duplicate Seq Nums are not allowed.

• Accept Y in the Abort on Abnormal End field. In this way, tasks in a batch process only run if the previous task was successful.

• Use the first Seq Num to enter a description of the batch process. Enter any task in the Task field and a description of the batch process in the Parameters field. Tab to the Skip This Task field and enter Y so the task is ignored during processing. The batch process description is displayed in the Parameters field when you open the Batch Processes window:

• Use the CONT task to specify several different parameter combinations and use the Skip This Task field to identify which parameters to use. For example, enter several CONT task lines after the primary APTB (A/P Aged Trial Balance) task to identify the parameter options you use most often. Use Skip This Task = N to identify the desired parameters.

01 APTB A30/60/9005 CONT P I

Process Id Tasks First Task Parameters

AG1 2 ARAG A/R AGING TASKS

AG2 2 APAG A/P AGING TASKS

ATP 2 BATP ATP CALCULATIONS

AUD 2 AUDP HISTORY PURGE

CYC 5 ARIR CYCLE-END TASKS

DLY 8 DEUP DAILY TASKS

MCM 4 ARMQ MODULE COMMUNICATION

ORD 2 BOPR BATCH PRINTING

PRD 2 GLPC PERIOD-END CLOSE

PRG 3 ARPG PURGING TASKS



10 CONT F000000 T00050015 CONT U I M

The series of CONT tasks can be combined with the primary APTB task several ways. The primary task must always have Skip This Task = N. For example, you could identify the following sets of parameters by modifying the Skip This Task field for the parameters you wish to use:

Nesting Batch ProcessesYou can call one batch process from within another batch process by including the BEXC (Fourth Shift Batch Process Call) task as one of the sequenced tasks.

This allows you to reuse the parameter line for common or frequently-run tasks, by executing them as a separate process called by other processes. It also allows you to create a "master" batch process that strings together several smaller batch processes that you regularly run in a specific sequence.

Parent and Child ProcessesA batch process containing a BEXC task line is a parent process. When the BEXC task line in a parent process is executed, the entire child process that is called is executed. Once the child process is complete, the parent process continues with the line following the BEXC task line.

If a child process also contains a BEXC task line, it becomes a parent process also. Batch processes can be freely nested in this way, as long as the batch processes do not call each other in a way that would force the batch process to continue in an unending loop.

Batch ExecutionBatch processes are executed using the BEXE (Batch Process Execution) screen. For more information, see BEXE in the System Control online manual.

If you are using a multi-user configuration, make sure that the same batch process is not run on two or more different computers at the same time. Also see "Database Locking" for more information about batch processes and data locking.

All batch processes generate a process log file. Not all batch processes generate reports.

Seq Num with Skip This Task = N Parameters Used

01, 05 A30/60/90 P I

01, 05, 10 A30/60/90 P I F000000 T000500

01, 10, 15 A30/60/90 F000000 T000500 U I M

BX1 01 APMC02 GLMC03 IVMC04 BEXC PACX05 OVAR O1 U1 P M C D W5

ACX 01 ACCX VJANINVTRY DC:\ACCESS\JINVTRY.MDB02 ACCX VFEBINVTRY DC:\ACCESS\FINVTRY.MDB A03 ACCX VMARINVTRY DC:\ACCESS\MINVTRY.MDB A



Monitoring the Batch ProcessWhen you execute a batch process, the BEXE screen is replaced by the Batch Processing dialog box. Use this dialog box to monitor the status of the batch process.

The dialog box displays the Process Id, Report Destination, and Process Log Directory for the process that is running. It also displays information about the task currently being processed, including:

• the Seq Num and Task Id

• any parameters defined for the task

• the time and date the task was started

To view processing details provided by the current task, click Show Detail. The dialog box expands to display processing details, such as information about the individual data elements being processed. To stop viewing these details, click Hide Detail. Tasks generally run more quickly when processing details are hidden.

To stop the current task or the entire batch process, click Stop. If the current task cannot be interrupted, you can choose to stop or continue the batch process after the current task is complete. For detailed information on which tasks may be stopped during the process, see the "Batch Guidelines" section of this manual.

Batch Execution MessagesBatch execution messages are displayed at the bottom of the BEXE screen after a batch process completes. Several messages could be displayed:

• Process Completed Successfully. This message indicates all actions performed by the tasks in the batch process completed from beginning to end. Check the process log file to verify no problems were encountered during processing.

• Process Completed Successfully, Check Log for Errors. This message indicates all actions could not be performed by the tasks in the batch process. Check the process log file to identify the problems and rerun the batch process.

• Process Completed Unsuccessfully. This message indicates that the actions of the tasks in the batch process could not be completed. Check the process log file to identify the problems and rerun the batch process.

Process Log FileThe process log file is a record of processing steps for each task in the batch process. The process log file lists all tasks executed, whether completed or not, and other information about the task as it is executed. A batch process is identified as external if it contains one of the command line tasks, such as CMND (DOS Command Shell). A batch process is considered internal if a command line task is not included. Internal/external indicators are used for Customer Support purposes.

A process log file looks similar to this:

-------------------------------------------------------------------------Execution log for process DAYInitiated at 14:18:01 on 04/08/1998

Executing 01 BATP at 14:18:02 on 04/08/1998Parameters:



UP TO 2490 DEMANDS CAN BE PLANNED PER ITEMBATP Successfully Completed

Executing 05 SREV at 14:18:07 on 04/08/1998Parameters: SREV Successfully Completed

Execution of DAY terminated normally at 14:18:13 on 04/08/1998

-------------------------------------------------------------------------

There is a process log file for each Process Id executed. Each time the process is executed using the BEXE screen, information is added to the end of the existing log file. The process log file is identified as XXX.LOG, where XXX is the Process Id.

The process log file produced when a command line task is executed contains the complete Parameters contents from all lines used by the task during execution. This enables you to verify your parameters entries if errors are encountered.

Note: Do not look at a process log file, with an editor, when the batch process is writing to the process log file. The process log file must be available to complete the batch process successfully.

Review the process log file each time a batch process is completed. Once you have reviewed the log file, delete it from the fixed disk.

Batch ReportsReports generated by batch processes can either be printed directly or printed to disk as a file. Use the Report Destination field on the BEXE (Batch Process Execution) screen to make this choice.

Print DirectlyIf you choose to print a report directly (Report Destination = 1), the report is printed on the default printer set up on your workstation. Print Setup and Print Preview options are not available. Batch reports are designed to print at 66 lines per page.

Print to DiskBy default (Report Destination = 2), reports are generated as RDL, RTF (Rich Text Format) or plain text files in the location you specify on the BEXE screen. You can change the default directory listed on the BEXE screen by modifying the value of the AuxRptFiles configuration variable.

You cannot specify an output directory for specific batch reports by using the CDIR (Set Drive and Directory) task to change the working directory of the batch process.

Use Crystal Reports, Fourth Shift Report Viewer, Microsoft Word or Word Viewer, or a text editor to view or print report files. If you use Microsoft Word or Word Viewer, be sure to set the View option to Page Layout to view the header section of the report. For more information, see "Viewing Batch Process Reports" in the Fourth Shift Basics online manual.

Automatic Email for Batch ReportsIf a report is email enabled, then reports are distributed dependent upon the Report Destination and the report's Email/Print Preference for the customer or vendor. Email/Print Preference is defined on the Customer/Vendor Report Options screens (CROP/VROP).

For Report Destination = 1:



• If the Email/Print Preference is set to Print, then the report is printed on the default printer.

• If the Email/Print Preference is set to Email, then the processing works the same as if the Report Destination = 2 with an Email/Print Preference of Email.

• If the Email/Print Preference is set to Both, then the processing works the same as if the Report Destination = 2 with an Email/Print Preference of Both.

For Report Destination = 2:

• If the Email/Print Preference is set to Print, then the report is generated in a sub-folder named 'Print'.

• If the Email/Print Preference is set to Email, then the report is automatically sent as an attachment to subscribed customer or vendor contact email recipients, and the report is saved in a sub-folder named 'Email'.

• If the Email/Print Preference is Both, then the report is automatically sent as an attachment to email recipients and the report is saved in a sub-folder named 'Both'.

See Report File Names with Automatic Emails for more information.

Report File NamesWhen a report is generated as a file, the filename is built from four elements: the Task, Seq Num, Process Id, and Report Type. Together the Task, Seq Num, and Process Id become the file name, while the type of file generated becomes the file extension. For example:

• The file PORR01PUR.RTF is generated when PORR (Purchase Order Receiving Report) is the first task in the PUR batch process. The PORR01PUR.RTF file is generated the first time the PUR batch process is executed.

• The second time the PUR batch process is executed, the existing PORR01PUR.RTF file is saved as PORR01PUR.OLD and a new PORR01PUR.RTF file is generated.

• The third time the PUR batch process is executed, the existing PORR01PUR.RTF is overwritten. The second PORR01PUR.RTF file is saved as PORR01PUR.OLD and a new PORR01PUR.RTF is generated.

The only exceptions to this rule are reports generated by the BOPR (Batch Order Print) task. This task can generate multiple types of documents on a single line in a batch process. Therefore, the filenames for reports generated as a file by the BOPR task also include an indicator of the type of document.

Document Type IndicatorExample

(Process Id=BOP)

Order Acknowledgment C BOPR01C.BOP

Customer Order Picklist K BOPR01K.BOP

Customer Job Summary MJ BOPR01MJ.BOP

Manufacturing Order Picklist MK BOPR01MK.BOP

Manufacturing Order MO BOPR01MO.BOP

Customer Order Picklist (for manufactur-ing order)

MP BOPR01MP.BOP

Customer Order Routing MR BOPR01MR.BOP

Purchase Order P BOPR01P.BOP

Purchase Order Picklist S BOPR01S.BOP



Report Files for Automatic EmailsWith automatic email, batch runs generate report files that are sent as email attachments. Based on contact email configuration, for email-enabled reports where the Z option was specified for the batch run, all report files are stored under an extended report folder structure. Also, when building unique report filenames, the process must consider additional elements when automatic email is used.

Reports are saved in a folder structure under the folder specified by a Fourth Shift Configuration variable (AuxRptFiles or AuxDataFils).

First, a folder gets created based on the report type, sequence number, and batch process name, for example, BOPRC01BOP, where the BOPR task with the C option is specified as sequence number 01 for the batch task named BOP.

Under that folder, three subfolders are created based on the three Email/Print Preference options as setup on the Customer Report Options (CROP) or Vendor Report Options (VROP) screens:

• Email

• Print

• Both

Email configuration for customer or vendor contacts determines the results, and three additional elements are considered for the filename. For example, for emailing customer reports, each email will require that report file names contain the Customer Id. The Customer Order Acknowledgement report can be emailed based on the ship to address which may require a split of customer reports by Ship to Address Id. Also, if configured to send the email from or to the CSR assigned to the customer, the customer report files could be split apart further by CSR.

The additional filename elements are:

• Customer or Vendor Id

• Ship To/Delivery Location ID

• CSR or Buyer Id

Example:

• The email template for the BOPR Customer Order Acknowledgement report is configured such that the Sender is Derived From the CSR of the Customer Order. Also only one customer (Customer ID = 100010) is configured to receive emails of the Customer Order Acknowledgement report and is configured to have recipients based on the two Ship To/Delivery Locations (ShipTo Ids equal to LOC1 and LOC2).

• A run for BOPR Customer Order Acknowledgement report (C option) is configured with the Z option, one file is generated as the standard Fourth Shift Customer Order Acknowledgement for all non-email customers, and two files are generated for sending email from CSR CCC to customer 100010 on Ship To location LOC1 and Ship To location LOC2.

• Elements for Customer Id, Ship To Id, and CSR will be added to the end of the FileName depending on whether these elements are required to make them unique.

• The file names and locations for this run will be:

- \\FSSERVER\FSSHARE\Mfgsys\BOPR01CBOP\Print\BOPR01CBOP.PDF

- \\FSSERVER\FSSHARE\Mfgsys\BOPR01CBOP\Email\BOPR01CBOP100010 _LOC1_CCC.PDF

- \\FSSERVER\FSSHARE\Mfgsys\BOPR01CBOP\Email\BOPR01CBOP100010 _LOC2_CCC.PDF



Disk Space and Backup ConsiderationsIn order to generate report files successfully, there must be enough space on the disk and you must have the appropriate access rights.

Be certain to print or backup the report files before the next batch process execution to avoid any loss of information. Be sure you have set your printer to compressed print function if any of the reports require compressed print. Refer to your printer manual for information on adjusting your printer specifications.

Running Batch Process Reports with Net UI or WebUIIf you are using Net UI or WebUI, there are some considerations to be aware of when running batch process reports. Both generate reports on the server, and the reports are displayed on the remote client.

• If you are using WebUI, reports are generated on the Fourth Shift server.

- If Report Destination = 1, the report is not printed directly. Instead it is displayed to the user in a browser window, allowing the user to print the report on any local printer. Batch processes continue after the report is displayed.

- If Report Destination = 2, the report is printed to disk normally on the Fourth Shift server. The report is not displayed to the user in a browser. The user can access the file only through a LAN or dial-up connection.

For more information, see "Printing and Generating Reports" in the Using My Fourth Shift Workplace section of the Fourth Shift Basics manual.

• If you are using Net UI, reports are generated on the Net UI server. The Report Destination location refers to drives mapped on the Net UI server, not drives mapped on the client workstation. For example, specifying the C:\Reports directory refers to that directory on the Net UI server, not the client workstation's C: drive.

Both template-based reports and RTF-based reports can be viewed using the Fourth Shift Report Viewer.

Batch Process RecoveryTasks executed in a batch process generate archive records which are one of the following:

• non-recoverable

• recoverable

Non-Recoverable TasksNon-recoverable task archive records (BEXE00) must be reentered manually during system recovery by rerunning the task. Most Fourth Shift tasks are non-recoverable. For example, the PLNG (MRP Planning) task must be recovered manually by rerunning the task where it is recorded in the ARCHIVE.FIL file. A sample of an ARCHIVE.FIL file containing a non-recoverable task archive record would look similar to the following:

"CORV02","AAA",..."CORV05","AAA",..."CORV06","AAA",... "ITMB00","AAA",... "ITMB01","AAA",... "BEXE05","AAA","02/01/1995","014:35:15","0","R","PLN","Start batch process",...



--------------------------------------------------------------------------------------------..."BEXE00","AAA","02/01/1995","014:35:16","0","R","PLN","PLNG",...---------------------------------------------------------------------------------------------..."BEXE05","AAA","02/01/1995","014:41:58","0","R","BKF","End batch process",...

Recoverable TasksRecoverable task archive records are used during system recovery and do not require that you rerun the task. For example, the BKFL (Backflushing) task generates archive records for each backflushing transaction performed. During system recovery, each transaction is recovered in the order it was originally processed rather than by rerunning the BKFL task. A sample of an ARCHIVE.FIL file containing recoverable task archive records would look similar to the following:

"BEXE05","AAA","02/01/1995","014:41:58","0","R","BKF","Start batch process",..."CORV02","AAA",..."CORV05","AAA",..."BKFL03","AAA",... "CORV06","AAA",... "ITMB00","AAA",... "ITMB01","AAA",... "BKFL01","AAA",...

Recoverable task archive records are dispersed among all other transactions and must be recovered in the same order to ensure the integrity of your database. Data import macros are used for task transaction recovery the same way screen transactions are recovered.

Batch Prerequisites and FrequencyThere is no precise answer to the question "How often are batch tasks run?" A batch processing plan depends on the company and its goals. The following guidelines and examples are provided here to help you develop your own overall batch processing plan.

Batch GuidelinesBatch guidelines provide a summarized view of all the tasks currently in the system. Each batch guideline represents a group of tasks. The task groups are:

• manufacturing database updates

• manufacturing reports – no database update

• financial database updates

• financial reports – no database update

• interfaces and system administration

Tasks within each batch guideline are listed in processing sequence.

Information on each task includes:

• Function Code. The four-character identifier for the task and the name identification for the task as displayed on its corresponding Module Menu and on the BSET screen.



• The name identification for the task as displayed on its corresponding Module Menu and on the BSET screen.

• Function. A brief description of the task's purpose.

• Prerequisites. The specific requirements related to the task. Prerequisites most often refer to field values, setup, files and other tasks.

• Functional Responsibility. The function within the company which should make decisions concerning the task.

• Recommended Frequency. The rate at which the task is normally run. Rates are:

Year-end processing, which is a special case, is described under "Fiscal Year-End Processing."

• File Entry. The file for which entries are created as a result of running the task.

Identifier Function

A/P Accounts Payable

A/R Accounts Receivable

Acct Accounting

Costing Product Costing

G/L General Ledger

IC Inventory Control

Invoicing Invoicing

Mfg Manufacturing

Pur Purchasing

Sales Sales

Shipping Shipping

System Admin System Administration

Identifier Frequency

D Daily

W Weekly

M Monthly

Q Quarterly

Y Yearly

As needed use when necessary

system-defined determined by the System, such as by order lead time



• Rpt. An indication of whether the task produces a report.

• Stop. An indication of whether you can stop the task once the task has started running by clicking Stop in the Batch Processing dialog box.

Manufacturing Database UpdatesFollowing is a list of the manufacturing database update tasks in processing sequence. See the online help or online manuals for more information on each task.

DEUP (Deferred Update). Explodes and reschedules order dependent bills of materialPrerequisites: CNFG - Deferred Update = Y

TRUD (Transaction Update). Posts LRRP transactions to MOs, MODCOMGL.FIL or G/L entries if you are in Real-time.Prerequisites: DEUP (if Deferred Update = Y); BATCHUPD.FIL present

BKFL (Backflushing). Picks components based on E type receiptsPrerequisites: PICK DETAIL - Backflush = Y; DEUP (if Deferred Update = Y)

BKSV (Backflush Server). Explodes and reschedules order dependent bills of material and picks components based on E type receipts

Identifier Description

Y Report is produced

N No report is produced

Identifier Description

Y Yes, the task can be stopped

N No, the task cannot be stopped

Resp Freq File Entry Report Stop

Mfg D N/A N Y


Mfg D MODCOMGL.FIL; BATCH-UPD.OLDG/L entry (depending on sys-tem set up)

Y N


Mfg D MODCOMGL.FIL Y Y



Prerequisites: CNFG - Deferred Update = Y; PICK Detail - Backflush = Y; (DEUP processes automatically)

DEUP (Deferred Update). Explodes and reschedules order dependent bills of materialPrerequisites: CNFG - Deferred Update = Y

CSTU (Actual Cost Update). In an average actual costing system, rolls the order component costs into the order parent costs, creates G/L entries for variances, generates cost action messages, updates ITMC item cost recordsPrerequisites: CCAN - Cost Action = CST

OVAR (Close Order Analysis/Order Variance). Closes orders, creates GL entries for WIP & Variances, but prints a detailed analysis of variance

PLNG (MRP Planning)—net change. Plans orders, updates ATPPrerequisites: Check free space; DEUP (if Deferred Update = Y)

PLNG (MRP Planning)—regenerate. Delete old plans at end of forecast period


Mfg D MODCOMGL.FIL Y Y


Mfg D N/A N Y


Mfg, Pur D N/A N N


All D, W MODCOMGL.FIL or G/L entries,MODCOMIV.FIL or preprinted invoices(depending on the system set up)

Y Y


Mfg, IC, Pur D N/A N Y


Mfg, IC, Pur M N/A N Y



BATP (Available to Promise). Updates ATP (not required if PLNG runs)Prerequisites: Item ATP = Y or B

ATPS (Available to Promise Server). Updates ATP based on waiting period between processing runsPrerequisites: Item ATP = Y or B

BRSA (Backlog Rules Shipment Allocation). Allocates inventory for customer orders

PREV (Period Review). Reviews items/orders, creates messages for MOAN, POANPrerequisites: PLNG (if installed)

SREV (Shipping Order Review). Reviews COs for COAN, STAD, STID msgs; closes shipmentsPrerequisites: PLNG (if installed)

LEXP (Lot Expiration/Retest Eval). Identify/manage lots with expiration or retest datesPrerequisites: Shelf life defined for items; location with IC=A

CROL (Cost Roll-Up). Calculates costs from BOMPrerequisites: ITMC (ATL costs)


Sales D N/A N Y


Sales D N/A N Y


Sales D N/A Y Y


Mfg, Pur Order Lead Time

N/A N Y


Sales, Shipping D N/A N Y


IC W N/A Y Y




CROV (Cost Roll-Over). Move costs between cost typesPrerequisites: CNFC Cost Type definition

LHRL (Lot Trace/Serialization History Reload). Reloads lot trace data offloaded in prior releases. LHRL is included on SQL Server Systems onlyPrerequisites: Backup

ITHU (Inventory History Update). Creates and updates an inventory history record with activity and inventory history informationPrerequisites: Backup

AUDP (Item History Purge). Removes on-line, item-related transaction historyPrerequisites: Backup; ITHU (if historical information is being saved)

POCP (Purchase Order Contract Purge). Removes purchasing contract history

ABCR (ABC Analysis Report). Evaluates item ABC class; Updates item ABC class (optional)Prerequisites: PLNG (if installed)

Costing As Needed N/A N Y


Costing As Needed MODCOMGL.FIL N N


Sys Admin As Needed N/A N Y


All D, W (if Parameter 1 = H)M (if Parameter 1 = I)

N/A N Y


Mfg M N/A N Y


Pur As Needed N/A Y Y


Mfg, IC, Pur As Needed N/A Y Y



COYE (Customer Year-End Processing). Year-to-Date Report; Resets YTD values (optional)

POYE (Purchasing Year-End Processing). Year-to-Date Report; Resets YTD values (optional)

ITHP (Inventory History Purge). Removes on-line, inventory-related transaction history

Manufacturing Reports - No Database UpdateThe following chart lists the manufacturing report tasks in processing sequence. See the online help or online manuals for more information on each task.

COBK (Customer Order Backlog Report). Lists values of outstanding orders

BOPR (Batch Order Print). Prints selected picklists and/or orders in batch mode

WIPL (WIP Item List). Reports work-in-process inventory quantities for component items, based on order number for manufacturing orders and or purchasing (S-line) orders

WIPR (WIP Report). Reports work-in-process inventory, based on order number for manufacturing orders and purchasing (S-line) orders


Sales Y N/A Y Y


Pur Y N/A Y Y


System Admin Y N/A N Y


Sales W N/A Y Y


Mfg, Pur, Sales As Needed N/A Y Y


Mfg, Pur As Needed N/A Y N


Mfg, Pur As Needed N/A Y Y



WIPS (WIP Summary by Value Report). Reports work-in-process inventory values for parent items, based on order number for manufacturing orders, purchasing (S-line) orders or customer orders

CWIP (Custom Product WIP Report). Reports custom product work-in-process inventory, based on order number

CINV (Custom Product Finished Inventory Report). Reports custom product finished inventory, based on order number

COBP (Customer Order Export). Generates files of order acknowledgement informationPrerequisites: COMT

POBP (Purchase Order Export). Generates files of purchase order information Prerequisites: POMT

IACR (Inventory Accuracy Report). Reports differences between cycle counts & inv balancesPrerequisites: ABC Class fields; INVA (RC = C)

ICCR (Inventory Cycle Count Report). Reports physical inventory counts at each locationPrerequisites: ABC Class fields; INVA (RC = C)




Mfg, Pur As Needed N/A Y Y




Sales As Needed order acknowledgement files N N


Pur As Needed purchase order files N N


IC W N/A Y Y




INVR (Inventory Valuation Report). Analyzes value of material items in inventory

SPFR (Schedule Performance Report). Measures delivery performance for items

VPFR (Vendor Performance Report). Measures delivery performance; resets As of Date for performance (optional)

IHIR (Inventory OnHold/ Inspection). Identifies items on hold/in insp.; run before OVAR

MOFR (Mfg Order Follow-Up Report). Lists released manufacturing orders

SDAB (Supply/Demand Analysis Report). Reviews supply and demand information by itemPrerequisites: PLNG

MPSR (Master Production Schedule Summary Report). Lists supplies/demands for date rangePrerequisites: PLNG

IC W N/A Y Y


Acct, IC As Needed N/A Y Y


Mfg W,M N/A Y Y


Pur W,M N/A Y Y


Mfg, IC, Pur D, W N/A Y Y


Mfg As Needed N/A Y Y


Mfg, IC, Pur As Needed N/A Y Y


Mfg As Needed N/A Y Y



VDSC (Vendor Scheduling/Commitment Report). Lists firm-planned, open, released orders for vendors

COMP (Cost Comparison Report). Lists no cost or cost type differences for items

POCR (PO Contract Report). Prints purchase order contracts

PORR (PO Receiving Report). Lists items received within a specified time periodPrerequisites: ARCHIVE.FIL present

POSR (PO Receiving Summary). Lists financial impact of items receivedPrerequisites: ARCHIVE.FIL present

SHPL (Shipment Log). Lists shipping activity by customer and date

LVAL (Lot Trace Bill Validation Report). Lists parent items with incomplete trace chainsPrerequisites: lot trace items defined


Pur W N/A Y Y


Cost As Needed N/A Y Y


Pur D, W N/A Y Y


Pur D, W N/A Y Y


Pur D, W N/A Y Y


Ship D, W N/A Y Y


IC As Needed N/A Y Y



ITHR (Inventory History and Activity Report). Lists inventory and activity history information

ITHC (Inventory History Cost Report). Lists activity costs and item cost buildup information

Financial Database UpdateThe following chart lists the financial database update tasks in processing sequence. See the online help or online manuals for more information on each task.

ARMQ (Invoice Module Communication). Generates invoices and credit memosPrerequisites: MODCOMIV.FIL present or external <filename>.FIL in required format; check free space

IVRC (A/R Invoice Creation). Creates pre-printed invoices based on recurring invoice definitionsPrerequisites: Define recurring invoices on IVRE

IVPR (Invoice Printing). Prints approved invoices and credit memosPrerequisites: Invoice St = A

IVEX (Invoice Printing Export). Generates file of printed invoice informationPrerequisites: Invoice St = A

APMQ (A/P Module Communication). Transfers receipt information from Purchasing Module or external file




Cost As Needed N/A Y N


Invoice D <filename>.OLD Y N


Invoice D N/A Y Y


Invoice D MODCOMSA.FIL Y Y


Invoice D MODCOMSA.FIL N Y



Prerequisites: MODCOMAP.FIL present or external <filename>.FIL in required format; lot-trace item info extracted; check free space

APIC (A/P Invoice Creation). Creates A/P invoices based on A/P recurring invoice definitions, including updates to G/L and vendor balancesPrerequisites: Define recurring invoices on APRE

GLMQ (G/L Module Communication). Creates batches of financial transactions from mfg modules or external filePrerequisites: MODCOMGL.FIL present; <filename>.FIL in required format present; check free space

GLAU (G/L Account Update). Posts batches to the general ledgerPrerequisites: Batch Status = S

ARAG (A/R Account Aging). Assigns outstanding receivables to aging categories

APAG (A/P Aging). Assigns outstanding payables to aging categories


A/P D <filename>.OLD Y N


A/P D N/A Y Y


G/L D <filename>.OLD Y N


G/L D, W N/A Y N


A/R D N/A Y N


A/P D N/A Y N



ARSC (A/R Service Charges). Calculates and creates service charge invoicesPrerequisites: ARAG

ARST (A/R Statement Printing). Prints customer statementsPrerequisites: ARAG, ARSC

ARBS (A/R Statement Export). Generates statement filesPrerequisites: ARAG, ARSC

APCP (A/P Close Period Analysis). Reviews/closes A/P cash sets

ARCP (A/R Close Period Analysis). Reviews/closes A/R cash sets

CSCP (Cash Mgmt Close Period Analysis). Reviews/closes sundry cash setsPrerequisites: APCP, ARCP

ARPG (A/R Purge). Removes outdated A/R history from systemPrerequisites: Backup


A/R Stmt Cycle N/A Y N


A/R Stmt Cycle N/A Y Y


A/R Stmt Cycle Statement files N N


A/P M N/A Y Y


A/R M N/A Y Y


G/L M N/A Y Y


A/R M Purge file N Y



APPG (A/P Purge). Removes outdated A/P history from systemPrerequisites: Backup

GLPC (G/L Period-End Close). Performs administrative tasks at end of accounting periodPrerequisites: Backup, ARMQ, IVPR, GLMQ, GLAU

GLBR (G/L Budget Roll). Allows use of current budget, plan & actual for next yearPrerequisites: Usually after year-end close

GLTP (G/L Acct. Type Maintenance). Allows account types and category types to be changed

EXRU (Exchange Rate Update). Reviews and updates exchange rates

IXRU (Intrastat Exchange Rate Update). Updates exchange rates on Intrastat reporting transactions only

Financial Reports - No Database UpdateThe following chart lists the financial report tasks in processing sequence. See the online help or online manuals for more information on each task.

IVPP (Preprinted Invoices). Lists invoices needing attention before printing


A/P M Purge file N N


G/L M N/A Y N


G/L Y N/A N N


G/L As Needed N/A Y Y


Acct As Needed N/A Y N

Resp Freq File Entry Rpt Stop

Acct As Needed N/A N N




IVRR (Invoice Reprinting). Reprints existing invoicesPrerequisites: IVPR

IVRX (Invoice Reprinting). Regenerates existing invoice filesPrerequisites: IVPR

ARTB (A/R Aged Trial Balance). Identifies delinquent receivablesPrerequisites: ARAG

ARIR (A/R Invoice Register). Lists invoices for a period or invoice range

ARCJ (A/R Credit Memo Journal). Lists credit memos and applications

ARRJ (A/R Cash Receipts Journal). Lists cash receipts and applications

ARTX (A/R Tax Register). Lists invoices and federal, state, county & municipal taxes

Invoice D N/A Y Y


Invoice As Needed N/A Y Y


Invoice As Needed invoice files N Y


A/R As Needed N/A Y Y











APVT (A/P VAT Register). Lists VAT amounts by taxing authority

APRG (A/P Invoice Register). Lists invoices for a system input date range

APUV (A/P Unvouchered Report). Lists all unvouchered receipt amountsPrerequisites: APMQ

APPV (A/P Purchase Price Var). Identifies purchase price variancesPrerequisites: APMQ

APTB (A/P Trial Balance). Identifies payable amounts within aging categoriesPrerequisites: APAG

GLJL (G/L Journal Entry List). Lists batch detail and prints master account summaryPrerequisites: GLMQ

GLTG (G/L Trial Balance/General Ledger). Lists all accounts' starting/ending balances for a periodPrerequisites: GLAU


A/P As Needed N/A Y Y












G/L D, W N/A Y Y



APRL (A/P Requirements List). Lists approved invoices for paymentPrerequisites: APRQ

GLBL (G/L Budget List). Identifies budgeted balances for year and budget/plan type

GLRP (G/L Report Print). Prints user-designed financial reportsPrerequisites: GLRD Report Definition verified

Interfaces and System AdministrationThe following chart lists the interface and administrative tasks in processing sequence. See the online help or online manuals for more information on each task.

ACCX (Access Extract). Extracts informationPrerequisites: DVUD

ASCX (ASCII Extract). Extracts informationPrerequisites: DVUD

DBSX (dBASE Extract). Extracts information based on data viewPrerequisites: DVUD


A/P D, W N/A Y Y






All As Needed Access file N Y


All As Needed ASCII file N Y


All As Needed dBASE file N Y



EXLX (Excel Extract). Extracts informationPrerequisites: DVUD

PRTX (Printed Extract). Prints extracted info based on data viewPrerequisites: DVUD

RCVR (System Recovery). Assists in performing a system recoveryPrerequisites: RCVR.DAT present

IMPT (Data Import). Performs keyboard entry in batch modePrerequisites: Import and Macro files present. Template present (if applicable)

ACCT (Account Verification). Lists invalid G/L accounts used in the system

BEXC (Fourth Shift Batch Process Call). Runs a batch process from another batch process

RWFL (Row Flush). Runs a task to remove Archive transactions, Module Communication Exception Messages, Modcom transactions, Sales Analysis Incremental Load log data, and Email data (in both FSDBXX and msdb databases).


All As Needed Excel file N Y


All As Needed N/A Y Y


Sys Admin As Needed RCVR.ERR N Y


Sys Admin As Needed IMPORT.ERR N Y


Sys Admin As Needed N/A Y Y







CMND (DOS Command Shell). Accesses DOS from within systemPrerequisites: Path statement; USER directory

PROG (Fourth Shift Program Execution). Accesses DOS from within system—ProgramFiles pathPrerequisites: Path statement; USER directory

CDIR (Set Drive and Directory). Sets the working drive and directory for subsequent batch tasks

STOP (Terminate Batch Process). Stops batch processing but does not exit system

QUIT (Exit Fourth Shift from a Batch Process). Exits system and closes the database

NEXT (Transport to Function or Menu). Stops batch processing and transports to specified function code or menu

Batch ExamplesTasks can be combined into batches in a variety of ways. One extreme would be to set up a batch for each task and decide which batches to execute. The other extreme would be to set up all the tasks in one batch and skip tasks within a batch when not needed. The batch examples included here are:

• daily/weekly


Sys Admin As Needed N/A N N













• monthly

• period-end closing

• general ledger - as needed

See "Other Year-End Processing" in the Batch Processing section of this manual for tasks that are processed on a yearly basis.

Once batches are set up, they can be used as the basis for a checklist to organize when tasks should be run. The batch examples included here are in such a checklist format.

Daily/Weekly

SAMPLE BATCH TASK CHECKLIST

DAILY/WEEKLY

------- RUN TASK -------

SEQ TASK PARAMETERS M T W Th F

01 DEUP x x x x x

02 TRUD x x x x x

03 BKFL P x x x x x

04 CSTU TM R S030398 E031098 x x x x x

05 OVAR O10 U02 P M C D x x x x x

06 PLNG x x x x x

07 PREV I x x x x x

08 SREV x x x x x

09 IHIR IALL x

10 CROL T5 x

11 CROV C F5 T1 x

12 ITHU H x x x x x

20 ARMQ x x x x x

22 IVRC x x x x x

23 APMQ x x x x x

24 APIC x x x x x

25 GLMQ Y I x x x x x

27 GLMQ Y E x x x x x

30 ARAG R x x x x x

31 IVPP U L x x x x x

35 ARTB A30/60/90 x x x x x

36 ARIR D F021595 T123199 x x x x x

37 ARCJ F021595 T123199 I x x x x x

38 ARRJ F021595 T123199 I x x x x x



Monthly

40 APAG x x x x x

45 APTB A30/60/90 x x x x x

50 ABCR A80 B12 C8 I2 MM N E060195 x

51 ABCR A80 B12 C8 I2 MP N E060195 x

52 WIPL M S45 LM x

53 WIPS M S5 LM Y x

54 WIPR TM O5 x

55 CWIP S4 LXU x

56 CINV S45 x

57 COBK C D FALL x

58 IACR F010195 T011595 P2 A0 B05 C10 x

60 ICCR I CA2 D020195 Y x

61 ICCR I CB2 D010195 Y x

62 ICCR I CC2 D080195 Y x

71 MOFR S000 EZZZ T031595 x x

72 COMP B5 C0 x

73 PORR F021095 T123199 x x x x x

80 DBSX VREF DM:\XPORT\REF.DBF x

80 DBSX VADDRMSTR DM:\XPORT\ADDRMSTR.DBF x

81 DBSX VPLNG DM:\XPORT\PLNG.DBF x

82 DBSX VCOST DM:\XPORT\COST.DBF x

83 DBSX VVENDORS DM:\XPORT\VENDMSTR.DBF x

99 QUIT x x x x x


MONTHLY

SEQ TASK PARAMETERS RUN TASK

05 ITHU I x

10 AUDP S010180 E112095 VY IALL FALL x

20 ARPG HA:AR113095.HIS D113095 x

30 APPG E I D113095 HA:IVAP1195.HIS F000000 TZZZZZZ x

40 APPG E R D123195 HA:RCPT1195.HIS F000000 TZZZZZZ x

50 APPG E C1 D123195 HA:CHCK1195.HIS F000000 TZZZZZZ x

60 SPFR F020195 T022895 D0Z x



Period-End Closing

General Ledger - As Needed

70 VPFR F00000 TZZZZZ S1 S2 D x

80 ARTX AS F020195 T022895 D x


PERIOD-END CLOSING

BATCH 1


01 APCP P0295 U x

02 ARCP P0295 U x

03 CSCP P0295 U x

04 GLRP FMS01 P02 x

05 GLRP FMS02 P02 x

06 GLTG TP SA B0295 E0295 x

07 GLTG DP SA B0295 E0295 x

BATCH 2 P0295 U


01 GLPC P0295 x


GENERAL LEDGER--AS NEEDED


01 GLAU J x

02 GLTG TP SA B0295 E0295 x

03 GLTG DP SA B0295 E0295 x

04 GLTP F90000 T99000 CS x



Database LockingFourth Shift is designed to allow people throughout your company to share the most up-to-date manufacturing and financial information. Some restrictions are needed to ensure the database is changed by only one person at a time. This is done by restricting database access. There are several ways data can be restricted, or locked:

• screen-level locking

• locking summaries

• record-level locking

• range locking

Screen-Level LockingSystem tasks, and several financial screens, can restrict access to database information. The database is divided into four groups of data for screen-level restriction purposes. The four groups are:

• MFG (manufacturing)

• AP (accounts payable)

• AR (accounts receivable)

• GL (general ledger)

Each Fourth Shift function can affect access to each of these data groups. Possible restrictions are:

• Exclusive (E). No other users can access information in the data group while this function is executing.

• Shared (S). Other users can view and update information in the data group while this function is executing. All shared access functions must complete and release existing locks before a function needing exclusive access (E) can begin.

For example, the ASCX (ASCII Extract) task places shared locks on data groups based on the data view selected. This means the ASCX task must complete before the GLBR (G/L Budget Roll) task can begin and place an exclusive lock on the GL data group.

Note: All tasks used to extract data from Fourth Shift, place shared locks on one or more data groups. This prevents any other task requiring exclusive access from executing. Plan the use of extract tasks during a time when other users will not be running other tasks needing exclusive access.

• None (N). All information in the data group is available to all users while this function is executing.

Locking SummariesThe following summaries are a guide to the way screen-level restrictions are implemented in the system. The tasks and screens are combined as:

• Manufacturing Database Updates

• Manufacturing Reports – no database updates

• Financial Database Updates

• Financial Reports – no database updates



• Interfaces and System Administration

• Data Extracts by View

If more than one task is included in a batch process for a specific Process Id, the restrictions are combined when the batch process begins. This ensures that the data group is available when needed. The locks are then checked after each task is completed and released if not needed by the remaining tasks in the batch process.

See the "Batch Guidelines" for the necessary processing sequence.

For example, the following data groups are locked (shared or exclusive locks) when the APMQ, ARMQ, and GLMQ tasks are included in one batch process:

In this example, the AP, AR and GL data groups are locked as the ARMQ task processes. After the ARMQ task completes, the AR data group is unlocked because neither the APMQ nor GLMQ task requires the AR data group. Similarly, the AP data group is unlocked after the APMQ task completes because the GLMQ does not require the AP data group.

Manufacturing Database Updates

Data Groups Locked

Seq Num Task MFG AP AR GL

01 ARMQ S

05 APMQ E

10 GLMQ E

Func Code Name

Data Group

MFG AP AR GL

ABCR ABC Analysis Report E N N N

ATPS Available to Promise Server S N N N

AUDP Item History Purge E N N N

BATP Available to Promise S N N N

BKFL Backflushing S N N N

BKSV Backflushing Server S N N N

BRSA Backlog Rules Shipment Allocation S N N N

COYE Customer Year-End Processing E N N N

CROL Cost Roll-Up (I parameter) S N N N

CROL Cost Roll-Up (R, N, P parameters) E N N N

CROV Cost Roll-Over E N N N

CSTU Actual Cost Update S N N N

DEUP Deferred Update E N N N

ITHP Inventory History Purge S N N N

ITHU Inventory History Update S N N N



Manufacturing Reports

LEXP Lot Expiration/Retest Evaluation S N N N

LHRL Lot Trace/Serialization History Reload E N N N

OVAR Close Order Analysis/Var E N N N

PLNG MRP Planning E N N N

POCP Purchase Order Contract Purge S N N N

POYE Purchasing Year-End Processing E N N N

PREV Period Review E N N N

SREV Shipping Order Review S N N N

TRUD Transaction Update E N N N

Func Code Name

Data Group

MFG AP AR GL

BOPR Batch Order Print S N N N

CINV Custom Product Finished Inventory Report E N N N

COBK Customer Order Backlog Report N N N N

COBP Customer Order Export E N N N

COMP Cost Comparison Report E N N N

CWIP Custom Product WIP Report E N N N

IACR Inventory Accuracy Report E N N N

ICCR Inventory Cycle Count Report E N N N

IHIR Inventory On Hold/Insp N N N N

INVR Inventory Valuation Report N N N N

ITHC Inventory History Cost Report S N N N

ITHR Inventory History and Activity Report S N N N

LVAL Lot Trace Bill Validation Report S N N N

MOFR Mfg Order Follow-Up Report N N N N

MPSR Master Production Schedule Summary Report S N N N

POBP Purchase Order Export E N N N

POCR Purchase Order Contract Report S N N N

PORR PO Receiving Report N N N N

POSR PO Receiving Summary N N N N

SDAB Supply/Demand Analysis Report E N N N

SHPL Shipment Log S N N N

SPFR Schedule Performance Report E N N N



Financial Database Updates

VDSC Vendor Scheduling Report S N N N

VPFR Vendor Performance Report S N N N

WIPL WIP Item List E N N N

WIPR WIP Report E N N N

WIPS WIP Summary by Value Report E N N N

Func Code Name

Data Group

MFG AP AR GL

APAG A/P Aging N E N N

APCP A/P Close Period Analysis N E N N

APIC A/P Invoice Creation N N N N

APMQ A/P Module Communication N E N N

APPG A/P Purge N E N N

APRL A/P Requirements List N S N N

ARAG A/R Account Aging N N E N

ARBS A/R Statement Export N N E N

ARCP A/R Close Period Analysis N N E N

ARMQ Invoice Module Communication N N S N

ARPG A/R Purge N N E N

ARSC A/R Service Charges N N E E

ARST A/R Statement Printing N N E N

BKCJ Bank Cash Journal Specifications N N N N

BKTR Bank Balance Translation N E E E

CSCP Cash Mgmt Close Period Analysis N E E N

CSPG Cash Management Purge N E E N

EXRU Exchange Rate Update E E E E

GLAU G/L Account Update N N N E

GLBR G/L Budget Roll N N N E

GLMQ G/L Module Communication N N N E

GLPC G/L Period-End Close N E E E

GLTP G/L Account Type Maintenance N E E E

IVEX Invoice Printing Export N N S N

IVPR Invoice Printing N N S N

IVRC A/R Invoice Creation N N N N



Financial Database Updates (Screens)

Financial Reports

IXRU Intrastat Exchange Rate Update N N N N

RTEX G/L Restructuring Execution E E E E

RTIN G/L Restructuring Data Integrity Test

N N N E

RTPR G/L Restructuring Preview and Veri-fication

E E E E

Func Code Name

Data Group

MFG AP AR GL

BKMT Bank Master N E E E

GLCO G/L Consolidation Process N N N E

GLHP G/L History Process N E E E

CCON Customer/Vendor Currency Conver-sion

E E E E

Func Code Name

Data Group

MFG AP AR GL

APCR A/P Check Reprint N E S S

APPV A/P Purchase Price Variance Report N N N N

APRG A/P Invoice Register N S N N

APTB A/P Trial Balance N N N N

APUV A/P Unvouchered Report N N N N

APVT A/P VAT Register N E N N

ARCJ A/R Credit Memo Journal N N S N

ARIR A/R Invoice Register N N S N

ARRJ A/R Cash Receipts Journal N N S N

ARTB A/R Aged Trial Balance N N N N

ARTX A/R Tax Register N N S N

GLBL G/L Budget List N N N N

GLJL G/L Journal Entry List N N N S

GLRP G/L Report Print N N N S

GLTG G/L Trial Balance/General Ledger N N N S

IVPP Preprinted Invoices Report N N N N



Interfaces and System Administration

Data Extracts by ViewThis locking summary identifies the data groups locked when a data extract is completed using the Master View: Sub View combination listed.

IVRR Invoice Reprinting N N S N

IVRX Invoice Reprinting Export N N S N

Func Code Name

Data Group

MFG AP AR GL

ACCT Account Verification Report E E E E

ACCX Access Extract S S S S

ASCX ASCII Extract S S S S

CMND DOS Command Shell n/a n/a n/a n/a

CONT Parameter Continuation Line n/a n/a n/a n/a

DBSX dBASE Extract S S S S

EXLX Excel Extract S S S S

IMPT Data Import n/a n/a n/a n/a

PROG Fourth Shift Program Execution n/a n/a n/a n/a

PRTX Printed Extract S S S S

QUIT Exit Fourth Shift from a Batch Process n/a n/a n/a n/a

RCVR System Recovery n/a n/a n/a n/a

RWFL Database Table Row Purge n/a n/a n/a n/a

SAIL Sales Analysis Incremental Load n/a n/a n/a n/a

STOP Terminate Batch Process n/a n/a n/a n/a

Master View Sub View

Data Group

MFG AP AR GL

Cash Mgmt all S S S S

Customer all S N N N

External all S S S S

General Ledger G/L Accounts N N N S

General Ledger all but G/L Accounts view S S S S

Item all S N N N

Location all S N N N

Lot Trace all S N N N



Record-Level LockingRecord-level locking ensures that only one user is updating a specific set of information at one time. For example, multiple users can be updating information on the APIE (A/P Invoice Entry) screen for the same vendor, but only one user can update a particular invoice for the vendor.

Record-level locking works much the same in both the manufacturing and financial databases. When a record is locked in the manufacturing database, the following message is displayed:

DATA TEMPORARILY IN USE...PLEASE TRY AGAIN

When a record is locked in the financial database, the message indicates the user currently locking the record. For example, the message from the APIE screen would look similar to this:

USER ID XXXX CURRENTLY UPDATING/VIEWING THIS INV/DR MEMO

Range LockingRange locking ensures that only one user is updating a specific range of information but allows other users to access the remaining information not included in the range.

Accounts PayableSeveral Accounts Payable screens restrict access to vendor information such as invoices. These screens are:

• APDS (A/P Disbursements)

• APRQ (A/P Cash Requirements/Payment Approval)

• APCV (A/P Payment Void)

• APCW (A/P Payment Processing)

• APTP (A/P 1099 Processing)

The vendors within the range specified for each screen are restricted from access. For example, one user could process payments for vendors A-F using the APCW screen while another user

Miscellaneous Currency_Def Data S N N N

Miscellaneous Currency_Exrt Data S N N N

Miscellaneous Data View S N N N

Miscellaneous Global ExtndTxt S N N N

Miscellaneous IT-Hist views S N N N

Miscellaneous Name & Adr Data S N N N

Miscellaneous Text Data S S S S

Miscellaneous VAT Data S N N N

Order all S N N N

Payables all S S S S

Receivables all S S S S

Shipping all S N N N

Vendor all S N N N



updates vendor G using the APIE screen and still another user enters disbursements for vendors H-Z using the APDS screen.

Accounts ReceivableInvoice printing tasks (IVPR and IVRR) and invoice file generation tasks (IVEX and IVRX) in the Accounts Receivable Module, restrict access to customer information. If more than one workstation is printing invoices, the invoice number for a specific customer range might not be assigned sequentially since one master list is being accessed by more than one customer range.

Shipment AllocationThe BRSA (Backlog Rules Shipment Allocation) task restricts access to stockroom information. The stockroom range specified for the BRSA task is restricted from access by other workstations.

Module-Specific ConsiderationsThere are several ways using the system in multi-user mode can affect the functionality of other Fourth Shift modules. The following tips will assist you as you use your system.

System Control Module-Data ImportSystem broadcast messages sent to a workstation can disrupt a data import process. If a workstation will be running a data import, it is recommended that these messages be blocked. Use this procedure before you sign onto the system if you are using a Novell Netware network.

From the system prompt at the workstation, type: CASTOFF ALL and press ENTER. The following message is displayed:

Broadcasts from the console and other stations will now be rejected.

and you are returned to the system prompt.

Broadcast messages are blocked until you log into the network again or until you type: CASTON and press ENTER.

System Control Module-Data ExportTasks used to extract data, such as the ASCX (ASCII Extract) task, place shared locks on each data group based on the data view selected. This prevents any other task requiring exclusive access, such as the GLMQ (G/L Module Communication) task, from executing. Plan the use of extract tasks during a time when users will not be running other tasks needing exclusive access.

General Ledger ModuleBatch ProcessingA number of general ledger tasks may require a significant amount of time based on the amount of information being processed. The tasks that perform general ledger processing that might require a significant amount of time are:

• GLAU (G/L Account Update)

• GLBR (G/L Budget Roll)

• GLMQ (G/L Module Communication)

• GLPC (G/L Period Close)

The tasks that print general ledger reports that might require a significant amount of time are:

• GLBL (G/L Budget/Planning List)



• GLJL (G/L Journal Entry List)

• GLRP (G/L Report Print)

• GLTG (G/L Trial Balance/General Ledger)

Establish a time for general ledger processing so that the interruption of normal business operations is minimized. The timeliness of information is also critical when printing general ledger reports in a batch mode. The G/L Journal Entry List, for example, should be printed when financial transactions from A/P, A/R or invoicing are not currently being added to the system. The G/L Journal Entry List can potentially show inaccurate totals due to the addition of new data entered during the printing process.

For example, the GLJL report has started printing when a user begins to add cash receipts on the ARCR screen. These cash receipts create automatic transactions added to an existing unposted ARCR batch. If the GLJL report has already printed the batch header for the unposted ARCR batch, the batch total in the header does not equal the total debits and credits based on the transaction detail now including a new transaction.

On-Line ProcessingGeneral ledger information is protected to ensure integrity by controlling the maintenance of key information. Your activities on the following screens are affected by these controls.

• On the GLSC screen, more than one user cannot maintain the same Batch Source Code.

• On the GLJE screen, more than one user cannot maintain the same journal entry.

• On the GLJE, GLSS and GLDQ screens, you cannot change the Acctg Prd or Batch Status of the same batch another user is viewing.

Fiscal Year-End ProcessingFiscal year-end processing involves closing out the general ledger. The fiscal year-end flow is as follows:



IVMC Process all shipped orders

Approve / print invoices

Transfer purchase order receiptsAPMC

Process MODCOMGL.FIL and MODCOMEX.FIL filesGLMC

Close cash books

Load consolidated activity from subsidiariesGLCO

Adjust and submit batches

Perform account updateGLAU

Run trial balanceGLTG

Print G/L financial reportsGLRP

Are reports and trial balance correct?No

Yes

Database backup

IVPRIVRV

CSCPARCPAPCP

GLSSGLJE



Other Year-End ProcessingOther year-end processing includes closing out year-to-date totals for vendors, customers and items, and establishing budgets and plans for the next year. These processes should be completed at the end of the calendar year and are not directly tied to fiscal year-end closing activities. The other year-end processing flow is as follows:

GLCO

GLCF

GLCA

GLOS

GLPC

GLJP

unload consolidated activity for parent

define new fiscal year-end dates;verify RE & suspense accounts defined

verify RE & suspense accounts active

verify RE organization exists

database backup

GLMAGLJE

period- and year-end close

verify RE entries

add adjusting entries, if necessary

database backup



The ITHP (Inventory History Purge) task transfers on-line inventory history from your system to a user-defined file and then deletes the history from on-line access. Inventory history is purged for the accounting year specified. The ITHP task can be run at any time, and only the inventory history for the accounting year specified is purged.

use update option; YTD customer and CO valuesCOYE

use update option; zero YTD vendor and PO values

process 1099 informationAPTP

roll budgets/plans or actualsGLBR

establish new budgets/plansGLBU

database backup

POYEVPFR

fiscal year-end processing


Fourth Shift Release 7.50 Database Backups


Database BackupsFourth Shift data is stored in both your production database, and in some cases, supplemental databases that must included in each daily backup so that the databases are synchronized.

The following table identifies the additional backup requirements when you are using one of the modules listed.

The SAAM Module (SQL Server systems only) allows you to store data in a separate SQL Server database.

SQL Server configurations use a specific database for calculation and display data. This database contains no data required for backup, however, the format of the database must match the appropriate release of the production database. Backup should be included after each release or ISR installation.

See the module online manual for additional information about system administration tasks related to module features.

Application Location Database

Fourth Shift Explorer MFGSYS\SYSTEM FSEXPLR.MDBEXPLPUB.MDB

RBPM MFGSYS/SYSTEM FS_RBPM.MDB

Application Database TypeDatabase Name

(XX is the system identchar)

SAAM SQL Server SADBXX

Application Database TypeDatabase Name

(XX is the system identchar)

System-wide SQL Server FSDBXXtemp

Fourth Shift Release 7.50 Add-On Modules/Licenses

Add-On Modules/LicensesAdding modules to an existing system should include careful planning and a formal implementation plan. There are several modules which require preprocessing steps in order to prepare your system for operation with the new module.

Use the following as a guide to the preparation, installation and post-installation tasks you should include in your implementation planning.

Installing Add-On ModulesAdd-on modules are new modules that you wish to install and begin to use with your existing system. Each module online manual contains a module-specific implementation plan. This module implementation section will assist you in preparing for, and setting up, the new module.

1. Review Preinstallation Considerations

2. Start Module Installation

Action Completed

Review the preinstallation considerations listed in this section. Complete any actions needed.

Print and review the "Setting Up the Module" section for the module from the online manual. Click the Start button, and then point to Programs. Point to the folder that contains the Fourth Shift group, and then click Online Manuals to access the online manuals viewer which allows you to print an entire section.

Action Completed

Obtain the CD-ROM for the release you have installed. The release identifier is dis-played when you sign onto Fourth Shift.

Retrieve the new module access key diskette you received when you purchased your new module.

Verify that the database server process is running.

Sign onto your Microsoft Windows system from the workstation where you will com-plete the installation. This workstation must have access to the server where the module will be installed.

Insert the CD-ROM into the drive.

Run the SETUP program in the root of the CD-ROM. Click Next.

Select the installation type: Update release level or add modules to an existing system. Click Next.

Choose the installation element you wish to install: Module program update/addi-tion. Click Next.

Select your Configuration File. Click OK.

Insert the new Module Access Key diskette into the diskette drive.



3. Install New Module

4. Complete Workstation InstallationSome modules require a workstation installation. If the module you are adding is not listed once you start the workstation installation, no installation is required at the workstation level.

Accept your existing serial number. Click Browse to retrieve the new module access key from the diskette.

Click Next.

Action Completed

Review the list of modules displayed. The modules you have not yet installed are selected.

Deselect any modules you do not wish to install.

Click Next.

Verify the current settings before beginning actual installation process. Click Back to return to select or deselect a module.

Click Next.

Select the file if you wish to review installation results.

Click Finish.

Review the installation information file displayed.

Action Completed

Go to the workstation where the module installation is required.

Run the SETUP program from the M:\MFGSYS\CLIENT directory. Click Next.

Select your Configuration File. Click OK.

Select the new module. Click Next.

Verify the current settings before beginning actual installation process. Click Back to return to select or deselect a module.

Click Next.

You may be prompted to reboot your system in order to activate your new environ-ment settings. Click OK.

Select the file if you wish to review installation results.

Click Finish.

Review the information file displayed.

Repeat the workstation instructions on each workstation.



5. Complete Module Implementation

Cash Management Module ConsiderationsImplementation of the Cash Management (CSHM) Module should take into account the timing of the overall process. For example, your prior accounting period should be closed and all batches with current period cash account activity should be posted.

The implementation of the CSHM Module requires a cross functional team of system administration/support and finance. The system administrator alone will not be qualified to complete the processing steps necessary to implement the module.

After you install the CSHM Module to an existing system, the UPDTCSHM utility must be completed before using the Cash Management Module in order to synchronize the current G/L balance with the current accrual bank balance. This program is different from most other update programs because a series of manual validations and entries are required between phases.

Carefully review the "Setting Up the Module" section of the Cash Management online manual and complete the necessary preparation before installing the Cash Management Module.

Be sure to create a complete system backup before installing the Cash Management module. If you encounter difficulty during implementation, you can return to this backup if necessary.

Action Completed

Use the "Setting Up the Module" section of the module online manual to assist you in implementing the module.

Complete all steps in the "Loading Your Data" section of the module online manual.


Fourth Shift Release 7.50 System Administration Appendix

System Administration Appendix

File Manipulation MessagesFile manipulation messages occur when the system tries to write a transaction into the ARCHIVE.FIL, MODCOM*.FIL, item history and lot trace history files. The file manipulation messages look similar to the following:

IN WRITHIS |10| ERROR IN CALL TO MODCOM STATUS = XXXXThe following table identifies the source of the problem for each of the STATUS=XXXX values displayed.

Usual Cause• invalid network rights

• loss of network connection

• insufficient disk space

• another user is using the file outside the system

File Identifier Problem encountered

1000-1999 Failure Opening Archive File

2000-2999 Failure Writing to Archive File

3000-3999 Failure Writing to Item History

4000-4999 Internal Fourth Shift error

5000-5999 Failure Writing to MODCOMGL.FIL

6000-6999 Failure Writing to MODCOMIV.FIL

7000-7999 Error Writing to Item History

9000-9999 Error Closing MODCOMGL.FIL

10000-10999 Error Closing MODCOMAP.FIL

11000-11999 Error Closing MODCOMIV.FIL

12000-15999 Error Creating Lot Trace History

30001 Internal Fourth Shift error

30002 Error Opening MODCOMGL.FIL file in the ModComFiles location

30003 Error Opening MODCOMAP.FIL file in the ModComFiles location

30004 Error Opening MODCOMIV.FIL file in the ModComFiles location

30005 Error Opening MODCOMGL.FIL file in the AuxMirrorFiles location

30006 Error Opening MODCOMAP.FIL file in the AuxMirrorFiles location

30007 Error Opening MODCOMIV.FIL file in the AuxMirrorFiles location





Resolution1. Verify you are logged onto the network. Check your network mapping and rights to make sure

you have access to the files.

2. Verify there is sufficient disk space available in the MFGSYS directory where the file is located.

3. Verify that no other user is accessing the file outside the system. For example, someone could be reviewing the file with a word processor or printing the file.

4. Copy the file to a temporary name such as *.SAV. Go back into the system and create another transaction that would update the file.

5. If the transaction completes successfully, exit the system.

- If the file is a MODCOM*.FIL, rename the new file to a temporary name such as MODCOM*.NEW. Then, rename the MODCOM*.SAV file back to MODCOM*.FIL.

- Sign onto the system and process the module communication file. Rename the MODCOM*.NEW file MODCOM*.FIL and continue with normal operation.

- If the file is the archive file (ARCHIVE.FIL), make a backup of the ARCHIVE.FIL file. Delete the ARCHIVE.FIL and ARCHIVE.SAV files. Continue normal operation.

6. If you are unable to resolve the problem, contact Fourth Shift Customer Support.

Program Messages

ERROR CHANGING DIRECTORIES (CHDIR) TO directoryUsual Cause• insufficient network rights

• network communication problem

• directory removed and the FS.CFG file was not updated

Resolution1. Check your network mapping and rights to make sure you have access to the files.

2. Check wiring and network interface card connections at the servers and the workstation experiencing the problem.

3. Verify the drive/directory specified in the configuration file is the same as the drive/directory specified in the FS.CFG file.

EXECUTION FAILED ERROR <message>PROGRAM EXECUTION FAILED ERROR <message>

Usual Cause• insufficient memory

• missing file

Resolution1. Record the exact message.

2. Verify that sufficient memory is available at the workstation. If there is not sufficient memory available, reboot the workstation which encountered the error to reset the available memory



and verify the amount again. Memory requirements are listed in the Installing and Implementing Fourth Shift manual

3. Go to the MFGSYS\E or MFGSYS\SYSTEM directory and determine if the file specified in the message exists in this directory.

4. Verify that the configuration file on the workstation that encountered the error identifies the correct location for the ProgramFiles or SystemDir configuration variable.

5. If you were running a batch process containing several tasks when the message occurred, your database may be damaged. Contact Fourth Shift Customer Support for additional assistance in repairing your database.

PROGRAM WROTE TO DS:ØUsual CauseThis message is displayed as you sign off the system to indicate a problem was detected within an application program. This usually indicates an internal system problem. This message is information only and does not indicate a problem with your database. Others users can continue using the system.

Resolution1. Record the exact messages displayed on your screen.

2. Record the operations you had performed before receiving the message.

3. Contact Fourth Shift Customer Support to help identify and resolve the problem.

REQUIRED PROGRAM filename MISSING (ProgramFiles)Usual CauseThis message is displayed when a specific program file cannot be located in the location list specified by the ProgramFiles configuration variable.

Resolution1. Verify the file specified exists in one of the locations specified by the ProgramFiles

configuration variable.

2. If the file specified does not exist in the locations listed, determine if the files should be moved or another location added to the list for the ProgramFiles configuration variable.

3. Sign onto the system again and repeat the transaction you were working on when the message was displayed to determine if the problem is resolved.

REQUIRED SCREEN filename MISSING (ScreenFiles)Usual CauseThis message is displayed when a specific screen file cannot be located in the location list specified by the ScreenFiles configuration variable.

Resolution1. Verify the file specified exists in one of the locations specified by the ScreenFiles

configuration variable.

2. If the file specified does not exist in the locations listed, determine if the files should be moved or another location added to the list for the ScreenFiles configuration variable.

3. Sign onto the system again and repeat the transaction you were working on when the message was displayed to determine if the problem is resolved.



STACK OVERFLOW: STACK SIZE = number, USAGE = numberUsual CauseThis message indicates an unusual system problem.

Resolution1. Record each of the messages exactly as they are displayed on your screen. These messages

assist Fourth Shift Customer Support in locating the source of the problem.

2. Record the activities you were trying to complete when the error occurred.

3. Contact Fourth Shift Customer Support for further assistance.

UNABLE TO FIND CONFIGURATION FILEUsual Cause• -C parameter used incorrectly

Resolution1. Verify the drive/directory location and filename specified for the configuration file are correct.

Verify the file exists in the directory specified.

2. If you were using the –C parameter with the FSGUIAPP command, verify that you used the drive/directory and filename for the configuration file specified.

UNABLE TO LOAD DATABASE DLLYou have tried to sign onto the system using your Microsoft Windows environment and the required driver is not installed at your workstation. This driver must be installed before you can access the system from within Microsoft Windows. See the Installing and Implementing Fourth Shift online manual for instructions on installing the driver into your Microsoft Windows environment.

UNBALANCED ENQUEUE/DEQUEUE numberUsual CauseThis message indicates an unusual system problem. This message does not indicate a problem with your database and other users can continue using the system.

Resolution1. Record the exact message.

2. Record the operations you had performed before receiving the message.

3. Contact Fourth Shift Customer Support for further assistance in resolving the problem.

Configuration Variable and File Quick ReferenceFiles used in the operation of the system can be identified by default location or configuration variable based on the standard system configuration. This section includes the following lists:

• Configuration Variables by Filename

• Files by Configuration Variable

The lists identify the following types of information:

• Filename. The filename identifies the default filename used for files created, updated or referenced by normal system operation.



• Default Directory. The default directory identifies the location of the file based on the standard system configuration.

• Primary Search Variable. The primary search variable identifies the first variable location(s) used to define the location of the file. A secondary search variable is used, if one exists, when the primary search variable is not defined in the configuration file. All primary search variables, that do not have secondary search variables available, are required.

• Secondary Search Variable. The secondary search variable identifies the required configuration variable used if the primary search variable is not defined.

Configuration Variables by Filename

Filename Default DirectoryPrimary Search

VariableSecondary

Search Variable

*.CSS MFGSYS\H HelpFiles none

*.DLL MFGSYS\SYSTEM SystemDir none

*.EXE MFGSYS\E ProgramFiles none

FS_APPS WinProgFiles none

MFGSYS\SYSTEM SystemDir none

*.FMX MFGSYS\S ScreenFiles none

*FSMSS.INI C:\WINDOWS FSIniFileName none

*.GIF MFGSYS\H HelpFiles none

*.MAC MFGSYS\I ImportFiles none

*.MSG MFGSYS\S ScreenFiles none

*.RDL MFGSYS\REPORTS ReportsDir none

*.TBL MFGSYS\I ImportFiles none

*.TLG FSUSER UserDir none

*.TPL MFGSYS\I ImportFiles none

*.TTF MFGSYS\FONTS FontsDir none

*.WRK MFGSYS WorkDir none

APTP.FIL MFGSYS AuxDataFiles none

APPG user-specified filename

user-specified filename AuxDataFiles none

ARBS user-specified filename


ARCHIVE.EXE no longer delivered; see ARCHIVE.BAT

n/a n/a

ARCHIVE.FIL MFGSYS ArchiveFile AuxDataFiles

ARCHIVE.OLD MFGSYS ArchiveFile AuxDataFiles

ARCHIVE.SAV MFGSYS ArchiveFile AuxDataFiles

ARCREORG.EXE root directory FSScripts none



ARPG user-specified filename


BATCHUPD.FIL MFGSYS AuxDataFiles none

BATCHUPD.OLD MFGSYS AuxDataFiles none

CFG2DOS.EXE root FSScripts none

CHOOSE2.EXE MFGSYS\E (16-bit)MFGSYS\SYSTEM (32-bit)

ProgramFilesSystemDir

none

COBP user-specified filename


DBDEF.DAT MFGSYS AuxRefDataFiles none

EDICN*.LOG EDIM EDIMFiles none

EDIIMPT.HIS MFGSYS AuxDataFiles none

EDITDF*.HIS EDIEXCEL EDIINTRN EDIExcelFilesEDIInternalFiles

none

EDIXFER.DAT MFGSYS AuxDataFiles none

EDIXFER.HIS MFGSYS AuxDataFiles none

EDIXFER.LOG EDIM EDIMFiles none

FCMTDATA.LST MFGSYS AuxDataFiles none

FS_TABLE.EXE MFGSYS\E ProgramFiles none

FSCHECK.EXE MFGSYS\E ProgramFiles none

FSHELP.HDB MFGSYS\H HelpFiles none

FSLICENS.EXE root directory FSScripts none

FUNCFILE MFGSYS AuxRefDataFiles none

GLHP*.* MFGSYS AuxDataFiles none

HISDEF.DAT MFGSYS AuxRefDataFiles none

IDXFILE.DAT MFGSYS PriceOrderIndexFile none

IMEDImport.log MFGSYS AuxDataFiles none

IMPORT.ERR MFGSYS AuxLogFiles AuxDataFiles

INSTALL.HIS MFGSYS AuxDataFiles none

IRSTAX.999 MFGSYS AuxDataFiles none

IVEX user-specified filename


IVRX user-specified filename


LOGON.LOG MFGSYS AuxDataFiles none

XXX.LOG MFGSYS AuxLogFiles AuxDataFiles


VariableSecondary

Search Variable



Files by Configuration Variable

MAINT.DBF FS_APPS\D WinDataFiles none

MODCOM*.MC MFGSYS ModComFiles AuxDataFiles

MODCOM*.OLD MFGSYS ModComFiles AuxDataFiles

MODCOMAP.FIL MFGSYS ModComFiles AuxDataFiles

MODCOMEX.FIL MFGSYS ModComFiles AuxDataFiles

MODCOMGL.FIL MFGSYS ModComFiles AuxDataFiles

MODCOMIV.FIL MFGSYS ModComFiles AuxDataFiles

MODCOMSA.FIL MFGSYS ModComFiles AuxDataFiles

MODCOMSL.FIL MFGSYS ModComFiles AuxDataFiles

PARAM.EXE FS_APPS (16-bit)MFGSYS\SYSTEM (32-bit)

WinProgFilesSystemDir

none

PATH.FIL MFGSYS AuxDataFiles none

PEGSDESC MFGSYS AuxRefDataFiles none

POBPuser-specified filename


RCVR.DAT MFGSYS AuxDataFiles none

RCVR.ERR MFGSYS AuxLogFiles AuxDataFiles

RCVR.IDX MFGSYS\I ImportFiles none

SCUST*.DAT MFGSYS\SCREENS ScreensDir (in FSMSS.INI)

none

SDAB.ALL MFGSYS AuxLogFiles AuxDataFiles

SHOPCAL.DAT MFGSYS AuxDataFiles none

Task/Seq Num.OLD user-specified filename AuxRptFiles AuxDataFiles

Task/Seq Num.Pro-cess Id

user-specified filename AuxRptFiles AuxDataFiles

TRANSLOG.DAT MFGSYS AuxRefDataFiles AuxDataFiles

ZEROTRAN.FIL MFGSYS ModcomFiles AuxDataFiles

Primary Search Variable Filename Secondary Search Variable

ArchiveFile ARCHIVE.FIL AuxDataFiles

ARCHIVE.OLD AuxDataFiles

ARCHIVE.SAV AuxDataFiles

AuxDataFiles APPGuser-specified file

none


VariableSecondary

Search Variable



APTP.FIL none

ARPGuser-specified file

none

BATCHUPD.FIL none

BATCHUPD.OLD none

CUUUPPYY.U99 none

EDIXFER.DAT none

EDIXFER.HIS none

FCMTDATA.LST none

FCMTREP.LST none

GLHP*.* none

IMEDImport.log non

INSTALL.HIS none

IRSTAX.999 none

PATH.FIL none

RCVR.DAT none

WACF1.DAT none

WACF2.DAT none

AuxLogFiles IMPORT.ERR AuxDataFiles

XXX.LOG AuxDataFiles

RCVR.ERR AuxDataFiles

SDAB.ALL AuxDataFiles

AuxRefDataFiles DBDEF.DAT none

FSTABLES.SQL none

FUNCFILE none

HISDEF.DAT none

PEGSDESC none

TRANSLOG.DAT none

AuxRptFiles Task/SeqNum.Process Id AuxDataFiles

Task/Seq Num.OLD AuxDataFiles

ClientDir SETUP.EXE none

*.EXE, *.DLL for workstation install

none

EDIExcelFiles EDI*.HIS none

translation program none




EDIInternalFiles mapping files none

EISMDocoFiles *.WRI none

FontsDir *.TTF none

FSIniFileName *fsmss.ini none

FSScripts ARCHIVE.EXE none

ARCREORG.EXE none

CFG2DOS.EXE (16 bit) none

FSLICENS.EXE none

Help Files *.CSS none

*.GIF none

ImportFiles *.MAC none

*.TBL none

*.TPL none

RCVR.IDX none

ModComFiles MODCOM*.OLD AuxDataFiles

MODCOM*.MC AuxDataFiles

MODCOMAP.FIL AuxDataFiles

MODCOMIV.FIL AuxDataFiles

MODCOMGL.FIL AuxDataFiles

MODCOMSA.FIL AuxDataFiles

MODCOMSL.FIL AuxDataFiles

ZEROTRAN.FIL AuxDataFiles

PriceOrderIndexFile IDXFILE.DAT none

PricingFiles FS_RBPM.MDB none

ProgramFiles *.EXE none

ScreenFiles *.FMX none

*.MSG none

SystemDir *.EXE none

*.DLL none

UserDir *.MRB none

*.MRX none

*.TLG none

*.WSM none

WinProgFiles *.OVL none




Configuration Variable Quick ReferenceThe following table lists the configuration variables (Keyword=Value), required or optional indicator and the value in the standard configuration.

PARAM.EXE none

WinXportFiles *.00* none

*.DBF none

WorkDir *.$$$ none

*.WRK none

Configuration Variable Required/ Optional Standard ConfigurationKeyword Value

APCWReportFileName location + filename

optional none

ArchiveFile location optional AuxDataFiles

AutoCalculateATP yes/no optional no

AutoCustIdAssign yes/no optional no

AuxDataFiles location required MFGSYS

AuxLogFiles location optional AuxDataFiles

AuxRefDataFiles location required MFGSYS

AuxRptFiles location optional AuxDataFiles

CELSLotSizes number optional 0

ClientDir location required MFGSYS\CLIENT

CreateExtArchiveRecords yes/no optional yes

DatabaseServerPort number required 2056

DBClientName string optional none

DBServerName string required name of database server

DefaultOrderLineUnitPriceZero yes/no optional no

EmbeddedRevPrefix string required if the ENGM Module is installed

REV

EDIExcelFiles location required if EDIM Module is installed

EDIEXCEL

EDIInternalFiles location required if EDIM Module is installed

EDIINTRN




ENGMPromoteOption1 True/ False optional False

ENGMPromoteToExisting True/ False optional False

FontsDir location required MFGSYS\FONTS

FSReportMaxProcesses number optional 15

FSReportTotalWaitSeconds number optional 300

FSReportWaitSeconds number optional 5

FSScripts location required root directory

HelpFiles location list required MFGSYS\H

ImportFiles location required if SYSM Mod-ule is installed

MFGSYS\I

LockserverPort number required 2056

MaxUsers number required stand-alone=1multi-user=workstation licenses installed at initial installation

ModComFiles location optional AuxDataFiles

NetworkServerName string required for Microsoft Win-dows NT con-figuration

UNKNOWN

PriceOrderIndexFile location optional MFGSYS

PricingFiles location required if RBPM Mod-ule is installed

MFGSYS

ProgramFiles location list required MFGSYS\E

RecordLogin yes/no optional no

RecordLoginNetStats yes/no optional no

ReportsDir location required MFGSYS\REPORTS

ReportSecurity string required FS

RouterSheetPrintDefault Y/N optional Y

RtfBarCodeFontName string optional C39P24DnTt

RtfBarCodeFontSize number optional 20

RtfReportFontName string optional Courier New

RtfReportFontSize number optional 10

RtfReportFontSizeCompress number optional 7

RtfReportLineSpacing number optional 240

RtfTwipsFooterY number optional 720




RtfTwipsGutter number optional 720

RtfTwipsHeaderY number optional 720

RtfTwipsMarginBottom number optional 720

RtfTwipsMarginLeft number optional 720

RtfTwipsMarginRight number optional 720

RtfTwipsMarginTop number optional 720

RunMode string required Stand-alone=singleMulti-user=anyMulti-user split database=multi

SAAMDir location required if SAAM Mod-ule is installed

MFGSYS\SAAM

ScreenFiles location list required MFGSYS\S

ScreenTimeout number optional stand-alone=Øwindowing appl=300multi-user=300

ScreenTimeoutExit yes/no optional no

SQLMSS location required MFGSYS\SQLMSS

SystemDir location required MFGSYS\SYSTEM

SystemIdentChar string; requires 2 characters

optional MR

UserDir location required user-specific directory

UsePathFil location optional MFGSYS\PATH.FIL

UserTempDir location optional UserDir\TEMP

WebNUIMDir location required if NUIM Module is installed

MFGSYS\WEB\NUIM

WinDataFiles location required FS_APPS\D

WinProgFiles location list required FS_APPS

WinXportFiles location required XPORT

WorkCenterDelimiter string required if ENGM Module is installed

[

WorkDir location required MFGSYS




Fourth Shift Print FilesThe Fourth Shift printing feature is used to produce reports as either RDL (report definition language) or RTF (rich text format) files. The following tables list the available reports or options:

• Report Definition Language (RDL) Files—sorted by Report File Directory, Report File Name, screen, and a brief description

• Rich Text Format (RTF) Files—sorted by Module, screen, and a brief description

Report Definition Language (RDL) FilesFor information about updating and publishing RDL files with the RSPublish utility, see the SQL Reporting—Publishing RDL Files topic in the System online Help.

Report File Directory and Report File Name

Fourth Shift

Screen Report Description

/APBM/ApbCupb.rdl CUPB Customers Using Price Book

/APBM/ApbPbct.rdl PBCT Price Book Contents

/APBM/ApbPbii.rdl PBII Price Book Usage By Item

/APBM/ApbPbmt.rdl PBMT Price Book Master

/APSM/Aps1099.rdl APTP Form 1099-MISC

/APSM/Aps1099s.rdl APTP A/P Vendor 1099 Distribution Summary

/APSM/Aps1099se.rdl APTP A/P 1099 Exception Report

/APSM/Aps1099st.rdl APTP A/P 1099 Vendor Tax Flag Report

/APSM/Aps1099se.rdl APTP A/P 1099 Exception Report and Unprocessed Records

/APSM/Aps1099v.rdl APTP A/P 1099 Distribution by Vendor

/APSM/ApsApah.rdl APAH A/P Payment Application History

/APSM/ApsApca.rdl APCA A/P Payment Assignment

/APSM/ApsApck.rdl APCK A/P Payment Register

/APSM/ApsApcr.rdl APCR Remittance and Overflow

/APSM/ApsApcv.rdl APCV A/P Payment Void

/APSM/ApsApcwCN1L.rdl APCW A/P Check Printing/Export- Canadian Long Voucher, Text

/APSM/ApsApcwCN1S.rdl APCW A/P Check Printing/Export - Canadian Short Voucher, Text

/APSM/ApsApcwGM1L.rdl APCW A/P Check Printing/Export – German Long Voucher, Text

/APSM/ApsApcwGM1S.rdl APCW A/P Check Printing/Export – German Short Voucher, Text

/APSM/ApsApcwUK2S.rdl APCW A/P Check Printing/Export – UK Short Voucher, Text

/APSM/ApsApcwUK2Sf.rdl APCW A/P Check Printing/Export – UK Short Voucher, Form



/APSM/ApsApcwUS1L.rdl APCW A/P Check Printing/Export – Long Voucher, Text

/APSM/ApsApcwUS1Lf.rdl APCW A/P Check Printing/Export – Long Voucher, with Form

/APSM/ApsApcwUS1S.rdl APCW A/P Check Printing/Export – Short Voucher, Text

/APSM/ApsApcwUS1Sd.rdl APCW A/P Check Printing/Export – Short Voucher, for Dot Matrix Printer

/APSM/ApsApcwUS1Sf.rdl APCW A/P Check Printing/Export – Short Voucher, with Form

/APSM/ApsApex.rdl APEX A/P Receipt Exceptions

/APSM/ApsApih.rdl APIH A/P Invoice History

/APSM/ApsApir.rdl APIR A/P PO Receipts by Invoice

/APSM/ApsApit.rdl APIT A/P Invoice Template

/APSM/ApsApiv.rdl APIV A/P Invoice by Vendor

/APSM/ApsApmq.rdl APMQ A/P Module Communication by Queue Exception

/APSM/ApsApph.rdl APPH A/P Vendor Payment History

/APSM/ApsAppi.rdl APPI A/P Purchase Price Variance by Item

/APSM/ApsAppo.rdl APPO A/P Receipts by Purchase Order

/APSM/ApsAprc.rdl APRC A/P Payment Reconciliation

/APSM/ApsApre.rdl APRE A/P Recurring Invoice

/APSM/ApsAprh.rdl APRH A/P Recurring Invoice History

/APSM/ApsAprq.rdl APRQ A/P Cash Requirements/Payment Approach Detail & Summary

/APMS/ApsAptb.rdl APTB A/P Aged Trial Balance

/APMS/ApsApuv.rdl APUV A/P Unvouchered A/P PO Receipt Detail

/APSM/ApsAPVT.rdl APVT A/P VAT Register

/ARSM/ArsArah.rdl ARAH A/R Payment Application History

/ARSM/ArsArex.edl AREX A/R Invoice Exceptions

/ARSM/ArsAric.rdl ARIC A/R Invoice by Customer

/ARSM/ArsArih.rdl ARIH A/R Invoice History

/ARSM/ArsArmq.rdl ARMQ A/R Module Communication by Queue Exception

/ARSM/ArsArph.rdl ARPH A/R Customer Payment History

/ARSM/ArsArsr.rdl ARSR A/R Service Charge Review

/ARSM/ArsArst.rdl ARST A/R Statement - Text

/APMS/ArsArtb.rdl ARTB A/R Aged Trial Balance

/ARSM/ArsIvco.rdl IVCO A/R Invoice by Customer Order

/ARSM/ArsIvia.rdl IVIA A/R Invoice Adjustment


Fourth Shift




/ARSM/ArsIvie.rdl IVIE A/R Invoice Entry

/ARSM/ArsIvii.rdl IVII A/R Invoice Inquiry

/ARSM/ArsIvpr.rdl IVPR Invoices/Credit Memos - Text

/ARSM/ArsIvprf.rdl IVPR Invoices/Credit Memos - with Form

/ARSM/ArsIvre.rdl IVRE A/R Recurring Invoice

/ARSM/ArsIvrh.rdl IVRH A/R Recurring Invoice History

/ARSM/ArsIvrv.rdl IVRV A/R Review

/BILM/BilBili.rdl BILIL Single Level Bill Inquiry

/BILM/BilBill.rdl BILL Single Level Bill

/BILM/BilMbil.rdl MBIL Multi-Level Bill

/BILM/BilMuse.rdl MUSE Multi-Level Where Used

/BILM/BilWuse.rdl WUSE Single Level Where Used

/CPMM/CpmJobs.rdl CPMT Customer Job Summary

/CPMM/CpmPick.rdl PICK or CPMT

Customer Product Order Picklist

/CPMM/CpmRout.rdl CPMT Customer Order Routing

/CSHM/CshBkbl.rdl BKBL Bank Balance

/CSHM/CshBkcb.rdl BKCB Bank Cash Book

/CSHM/CshBkcj BKCJ Bank Cash Journal Summary Report

/CSHM/CshBkmt.rdl BKMT Bank Master

/CSHM/CshBkrc.rdl BKRC Bank Reconciliation

/CUSM/CusCcat.rdl CCAT Customer Catalog

/CUSM/CusCimt.rdl CIMT Customer Item Maintenance

/CUSM/CusCmta.rdl CMTA Commission Table

/CUSM/CusCmti.rdl CMTI Commission Table Inquiry

/CUSM/CusCoan.rdl COAN Customer Order Action

/CUSM/CusCocd.rdl COCD Customer Order by Customer ID

/CUSM/CusCop1.rdl COMT Customer Order Acknowledgement

/CUSM/CusCop1f.rdl COMT Customer Order Acknowledgement - with Form

/CUSM/CusCorl.rdl CORV CO Receipt Label

/CUSM/CusCpak.rdt SOPM Consolidated Packing List used in SOPM

/CUSM/CusCuid.rdl CUID Customer Master by ID

/CUSM/CusCuii.rdl CUII Customer Master by ID Inquiry

/CUSM/CusCusi.rdl CUSI Customer Master by Name Inquiry


Fourth Shift




/CUSM/CusCusl.rdl *Reporting Services

Mailing Labels for Customer

/CUSM/CusCust.rdl CUST Customer Master by Name

/CUSM/CusItpb.rdl ITPB Item Price Book

/CUSM/CusItpi.rdl ITPI Item Price Book Inquiry

/CUSM/CusPick.rdl PICK or SHIP Customer Order Picklist

/ENGM/EngEbll1.rdl EBLL Engineering Single Level Bill with Reference Designators

/ENGM/EngEbll2.rdl EBLL Engineering Bill of Material with Reference Designator Text

/ENGM/EngEcmp1.rdl ECMP Engineering Comparison Bill of Material

/ENGM/EngEcms1.rdl ECMS Engineering Comparison of Summarized Bills of Material

/ENGM/EngEcrl1.rdl ECRL Engineering Multi-Level Cost Bill of Material

/ENGM/EngElta1.rdl ELTA Engineering Lead Time Analysis

/ENGM/EngEmlb1.rdl EMLB Engineering Multi-Level Bill of Material

/ENGM/EngEmwu1.rdl EMWU Engineering Multi-Level Where Used Bill of Material

/ENGM/EngEsmb1.rdl ESMB Engineering Summarized Bill

/ENGM/EngEwus1.rdl EWUS Engineering Where Used Bill of Material

/ENGM/EngPbll1.rdl PBLL Production Bill of Material with Reference Designators

/ENGM/EngPbll2.rdl PBLL Production Bill of Material with Reference Designator Text

/ENGM/EngPcmp1.rdl PCMP Production Comparison Bill of Material

/ENGM/EngPcms1.rdl PCMS Production Comparison of Summarized Bills of Material

/ENGM/EngPcrl1.rdl PCRL Production Multi-Level Cost Bill of Material

/ENGM/EngPlta1.rdl PLTA Production Lead Time Analysis

/ENGM/EngPmlb1.rdl PMLB Production Multi-Level Bill of Material

/ENGM/EngPmwu1.rdl PMWU Production Multi-Level Where Used Bill of Material

/ENGM/EngPsmb1.rdl PSMB Production Summarized Bill

/ENGM/EngPwus1.rdl PWUS Production Where Used Bill of Material

/GLOBAL/OrdBoxl_C.rdl PICK Customer Order Box Labels

/GLOBAL/OrdBoxl_M.rdl PICK Manufacturing Order Box Labels

/GLOBAL/OrdBoxl_P.rdl PICK Purchase Order Box Labels

/GLOBAL/OrdFedx_C.rdl PICK Customer Order FedEx Airbill

/GLOBAL/OrdFedx_M.rdl PICK Manufacturing Order FedEx Air Bill

/GLOBAL/OrdFedx_P.rdl PICK Purchase Order FedEx Air Bill


Fourth Shift




/GLOBAL/OrdPack_C.rdl PICK Customer Order Packing List

/GLOBAL/OrdPack_M.rdl PICK Manufacturing Order Packing List

/GLOBAL/OrdPack_P.rdl PICK Purchase Order Packing List

/GLSM/GlsGlag.rdl GLAG G/L Account Group

/GLSM/GlsGlat.rdl GLAT G/L Account to Down Inquiry

/GLSM/GlsGlaw.rdl GLAW G/L Account Where Used Inquiry

/GLSM/GlsGlca.rdl GLCA G/L Chart of Accounts

/GLSM/GlsGlci.rdl GLCI G/L Chart of Account Inquiry

/GLSM/GlsGldq.rdl GLDQ G/L Detail Account Inquiry

/GLSM/GlsGlex.rdl GLEX G/L Journal Entry Exceptions

/GLSM/GlsGlgq.rdl GLGQ G/L Current Period Group Inquiry

/GLSM/GlsGlmq.rdl GLMQ G/L Module Communication by Queue Exception

/GLSM/GlsGlos.rdl GLOS G/L Organization Structure

/GLSM/GlsGlot.rdl GLOT G/L Organization Top Down Inquiry

/GLSM/GlsGlow.rdl GLOW G/L Organization Where Used

/GLSM/GlsGlrd.rdl GLRD G/L Report Definition

/GLSM/GlsGlrl.rdl GLRL G/L Report List

/GLSM/GlsGlsi.rdl GLSI G/L Batch Submission Status Inquiry

/GLSM/GlsGlss.rdl GLSS G/L Batch Submission Status

/GLSM/GlsGltg.rdl GLTG G/L Trial Balance

/GLSM/GlsGltg.rdl GLTG General Ledger-Detail (Posted)

/GLSM/GlsGltg.rdl GLTG General Ledger-Summary (Posted)

/INVM/InvAloc.rdl *Reporting Services

Over-Allocations by Item

/INVM/InvItbi.rdl ITBI Item Cost Book Inquiry

/INVM/InvItcb.rdl ITBC Item Cost Book

/INVM/InvItci.rdl ITCI Item/Work Center Cost Data Inquiry

/INVM/InvIthc.rdl ITHC Inventory History Cost Report

INVM/InvIthr.rdl ITHR Inventory History and Activity Report

/INVM/InvItmb.rdl ITMB Item Master

/INVM/InvItmc.rdl ITMC Item/Work Center Cost Data

/INVM/InvItmi.rdl ITMI Item Master Inquiry

/INVM/InvLmmt.rdl LMMT Location Master


Fourth Shift




/INVM/InvLocl.rdl *Reporting Services

Bar Code Labels for Locations

/INVM/InvSsii.rdl SSII Stock Status Inquiry by Item

/INVM/InvSsil.rdl SSIL Stock Status Inquiry by Location

/ISTM/IstIxru.rdl IXRU Intrastat Exchange Rate Update

/LOTM/LotLmsi.rdl LMSI Lot Inventory Transaction History Inquiry

/LOTM/LotLmst.rdl LMST Lot Inventory Transaction

/MCMM/McmExru.rdl EXRU Exchange Rate Simulation

/MGRM/MgrAbcr.rdl ABCR ABC Analysis Report

/MGRM/Mgriacr.rdl IACR Inventory Accuracy Report

/MGRM/Mgrinvr.rdl INVR Inventory Valuation Report

/MGRM/MgrOvad.rdl OVAR Closed Order Analysis/Order Variance - Detailed Report

/MGRM/MgrOvae.rdl OVAR Order Reconciliation Report

/MGRM/MgrOvas.rdl OVAR Closed Order Analysis/Order Variance - Summary Report

/MMAM/MmaMexp1.rdl MEXP Material Exposure Profile

/MMAM/MmaPBLL1.rdl PBLL Bill of Material

/MMAM/MmaPcmp1.rdl PCMP Comparison Bill

/MMAM/MmaPlta.rdl AMBL Lead Time Analysis Changes

/MMAM/MmaPmlb1.rdl PMLB Multi-level Bill of Material

/MMAM/MmaPsmb1.rdl PSMB Summarized Bill of Material

/MOMM/MomIord.rdl IORD Open and Release Orders

/MOMM/MomMoan.rdl MOAN Planner Action

/MOMM/MomMop1.rdl MOMT Manufacturing Order

/MOMM/MomMord.rdl MORV MO Receiving Document

/MOMM/MomMorl.rdl MORV MO Receipt Label

/MOMM/MomMosh MOSH Material Shortages Detail

/MOMM/MomOrst.rdl ORST Order Status Summary

/MOMM/MomPick.rdl PICK or MOMT

Manufacturing Order Picklist

/MRPM/MrpFcst.rdl FSCT Forecast

/MRPM/MrpMsmt.rdl MSMT Master Schedule Maintenance

/MRPM/MrpSdab.rdl SDAB Supply/Demand Analysis

/MRPM/MrpSdal.rdl SDAL Supply Demand Analysis


Fourth Shift




/OPFM/OpfIppd1.rdl IPPD Item Planning Parameter - Summary Report

/OPFM/OpfIppd2.rdl IPPD Item Planning Parameter - Detail Report

/PRCM/PrcCcan.rdl CCAN Cost Control Action Report

/PRCM/PrcCmlb.rdl CMLB Cost Multi-Level Bill

/PRCM/PrcCslb.rdl CSLB Cost Single-Level Bill

/PRCM/PrcMcst.rdl MCST Manufacturing Order Cost Analysis

/PRCM/PrcPcst.rdl PSCT Purchase Order S-line Cost

/PRCM/PrcWIPR.rdl WIPR WIP Report

/PRCM/PrcWIPS.rdl WIPS WIP Summary by Value Report

/PURM/PurDisi.rdl DISI Distributors By Vendor - Inquiry

/PURM/PurDist.rdl DIST Distributors By Vendor

/PURM/PurPick.rdl PICK Purchase Order Picklist

/PURM/PurPoan.rdl POAN Buyer Action

/PURM/PurPoas.rdl POAS Buyer Action

/PURM/PurPop1.rdl POMT Purchase Order

/PURM/PurPop1f.rdl POMT Purchase Order - with Form

/PURM/PurPord.rdl PORV PO Receiving Document

/PURM/PurPorl.rdl PORV PO Receipt Label

/PURM/PurPovd.rdl POVD Open and Release Order by Vendor

/PURM/PurVdii.rdl VDII Vendors that Supply an Item - Inquiry

/PURM/PurVdit.rdl VDIT Vendors that Supply an Item

/PURM/PurVeid.rdl VEID Vendor Master by VendorID

/PURM/PurVeit.rdl VEIT Items Supplied by a Vendor

/PURM/PurVend.rdl VEND Vendor Master by Name

/PURM/PurVeni.rdl VENI Vendor Master by Name Inquiry

/PURM/PurVenl.rdl *Reporting Services

Mailing Labels for Vendor

/PURM/PurViti.rdl VITI Vendor Item Inquiry

/PURM/PurVsdi.rdl VSDI Vendors Supplied by Distributor - Inquiry

/PURM/PurVsdt.rdl VSDT Vendors Supplied by Distributor

/RTSM/RtsRtmt.rdl RTMT G/L Restructuring Master Account Translation

/SAAM/SA_Cecc.rdl *Reporting Services

Commission Earned by Commission Code (SAAM only)


Fourth Shift




/SAAM/SA_Cefp.rdl *Reporting Services

Commission Earned by Fiscal Period (SAAM only)

/SAAM/SA_Clts.rdl *Reporting Services

CO Line Transactional Summary

/SAAM/SA_Col.rdl *Reporting Services

Customer Order Listing (SAAM only)

/SAAM/SA_Cpca.rdl *Reporting Services

Custom Product Line Data

/SAAM/SA_Cpcs.rdl *Reporting Services

Custom Product Component Summary

/SAAM/SA_Dar.rdl *Reporting Services

Daily Activity Report (SAAM only)

/SAAM/SA_Dtr.rdl *Reporting Services

Daily Totals Report (SAAM only)

/SAAM/SA_Fcecc.rdl *Reporting Services

Paid-in-full Commission Earned by Commission Code (SAAM only)

/SAAM/SA_Fcefp.rdl *Reporting Services

Paid-in-full Commission Earned by Fiscal Period (SAAM only)

/SAAM/SA_Gpci.rdl *Reporting Services

Gross Profit by Customer by Item (SAAM only)

/SAAM/SA_Gppli.rdl *Reporting Services

Gross Profit by Product Line by Item (SAAM only)

/SAAM/SA_Ocod.rdl *Reporting Services

Open Customer Order Detail (SAAM only)

/SAAM/SA_Ocol.rdl *Reporting Services

Open Customer Order Listing (SAAM only)

/SAAM/SA_Pabr.rdl *Reporting Services

Profit Analysis by Region (SAAM only)

/SAAM/SA_Pacc.rdl *Reporting Services

Profit Analysis by Customer Class (SAAM only)

/SAAM/SA_Qsci.rdl *Reporting Services

Quantity Sold by Customer By Item (SAAM only)

/SAAM/SA_Sabr.rdl *Reporting Services

Sales Analysis by Region (SAAM only)

/SAAM/SA_Sacc.rdl *Reporting Services

Sales Analysis by Customer Class (SAAM only)

/SAAM/SA_Sbap.rdl *Reporting Services

Summary of Booked Amount by Period (SAAM only)


Fourth Shift




/SAAM/SA_Siap.rdl *Reporting Services

Summary of Invoiced Amount by Period (SAAM only)

/SAAM/SA_Ssa.rdl *Reporting Services

Summary of Shipments (SAAM only)

/SAAM/SA_Ssap.rdl *Reporting Services

Summary of Shipped Amount by Period (SAAM only)

/SAAM/SA_Ytds.rdl *Reporting Services

Year-To-Date Sales by Customer (SAAM only)

/SFRM/SfrCapc1.rdl CAPC Capacity Planning - Work Center Load

/SFRM/SfrCels1.rdl CELS Cost Estimate by Lot Size

/SFRM/SfrDisp1.rdl DISP Dispatch List

/SFRM/SfrDisp2.rdl DISP Dispatch List - Period Load Only

/SFRM/SfrItsh1.rdl ITSH Item Shortages

/SFRM/SfrItsh2.rdl ITSH Item Shortages - With Order Detail

/SFRM/SfrLocn1.rdl LOCN Location Index

/SFRM/SfrLocn2.rdl LOCN Location Index - Status of Open / Released Orders

/SFRM/SfrLocn3.rdl LOCN Location Index - Order Progress Against Routing

/SFRM/SfrOcmp1.rdl OCMP Order Completion Status

/SFRM/SfrOcst1.rdl OCST Order Cost Variance

/SFRM/SfrOcst2.rdl OCST Order Cost Variance - Summary

/SFRM/SfrOcst3.rdl OCST Order Cost Variance - Order Detail

/SFRM/SfrRout1.rdl ROUT Router / Traveler - Routing List

/SFRM/SfrRout2.rdl ROUT Router / Traveler - Outside Services

/SFRM/SfrRout3.rdl ROUT Router / Traveler - Tools

/SFRM/SfrRout4.rdl ROUT Router / Traveler - Material List

/SFRM/SfrRout5.rdl ROUT Router / Traveler - All Types

/SFRM/SfrRouting.rdl ROUT Sub-report of Router

/SFRM/SfrRouting01.rdl ROUT Sub-report of Router



/SFRM/SfrShor1.rdl SHOR Shortages by Order

/SFRM/SfrShor2.rdl SHOR Shortages by Order - Other Orders Requiring Item

/SFRM/SfrWmst1.rdl WMST Work Center Master

/SHPM/ShpBol.rdl SBOL Bill of Lading


Fourth Shift




/SHPM/ShpBoxl.rdl SHIP Box Labels - Text

/SHPM/ShpBoxlf.rdl SHIP Box Labels - with Form

/SHPM/ShpBoxlt.rdl SHIP Box Labels - Text for Thermal Printer

/SHPM/ShpBoxltf.rdl SHIP Box Labels - with Form for Thermal Printer

/SHPM/ShpCpick.rdl STID or STAD

Consolidated Picklist

/SHPM/ShpCpicke.rdl STID or STAD

Consolidated Picklist Exception

/SHPM/ShpFedx.rdl SHIP Federal Express Domestic Airbill

/SHPM/ShpInvs.rdl SBOL Shipping Invoice Summary

/SHPM/ShpNmta.rdl NMTA National Motor Freight Code Table

/SHPM/ShpPack.rdl SHIP Packing List

/SHPM/ShpShpi.rdl SHPI Shipment Inquiry

/SHPM/ShpStad.rdl STAD Stockroom Action

/SHPM/ShpStid.rdl STID Stockroom Action Report

/SHPM/ShpSumm.rdl *Reporting Services

Shipping Summary

/SHPM/ShpVBol.rdl SBOL VICS Itemized Bill of Lading

/SOPM/SopCpikI.rdl SHIP (SOPM only)

Consolidated Picklist by Item

/SOPM/SopCpikL.rdl SHIP (SOPM only)

Consolidated Picklist by Location

/SOPM/SopOpik.rdl SHIP (SOPM only)

Order Based Picklist

/SYSM/SysAudt.rdl AUDT Item History Audit

/SYSM/SysBset.rdl BSET Batch Process Setup

/SYSM/SysCcex.rdl CCEX Currency Exchange Rate Maintenance

/SYSM/SysCcmt.rdl CCMT Currency Code Maintenance

/SYSM/SysCnfa.rdl CNFA Configuration of Interface Account Numbers

/SYSM/SysFcmt.rdl FCMT Function Code Report

/SYSM/SysOacf.rdl OACF Order Number Assignment Configuration

/SYSM/SysPass.rdl PASS Password Maintenance

/SYSM/SysText.rdl TEXT Text Review

/SYSM/SysTxta.rdl TXTA Tax Code Table

/SYSM/SysTxwu.rdl TXWU Text Where Used


Fourth Shift




*Reporting ServicesAll reports, including those not available from a Fourth Shift screen, can be accessed through one of the following:

• For SQL Server 2005 and 2008 R2, access reports with Reporting Services > Report Manager.

• For SQL Server 2005, access reports with SQL Server Management Studio, choose the Report Server for server type and connect to Reporting Services.

Rich Text Format (RTF) Files

/SYSM/SysVatt.rdl VATT Value Added Tax Code Table

Module

Fourth Shift

Screen Description

APSM AP1I A/P Received Item List

APSM AP2E G/L Distribution

APSM AP3H A/P Payment Void Detail

APSM APDS A/P Disbursements

APSM APIP A/P Invoice / Payment Audit

APSM APPA Payment Remittance

APSM APPD A/P Prior Period Disbursements

APSM APPD Print Payment Remittance

APSM APPD Print Summary Report

APSM APTX A/P 1099 Distribution

GLSM GLRC Alt-F4 Report List

GLSM GLAG Alt-F4 Browse Window

GLSM GLAT Alt-F4 Browse Window

GLSM GLAV Organization Approval/Disapproval

GLSM GLAV Alt-F4 Browse Window

GLSM GLCO G/L Consolidation Exception Report

GLSM GLCO G/L Consolidation Load Audit Report

GLSM GLCO G/L Consolidation Unload Audit

GLSM GLDQ G/L Detail Account Inquiry

GLSM GLGQ Alt-F4 Browse Window

GLSM GLHP Batch Reloaded


Fourth Shift




GLSM GLHP Batch Unloaded

GLSM GLJD Header Alt-F4 Browse Window

GLSM GLJE G/L Journal Entry

GLSM GLJE Header Alt-F4 Browse Window

GLSM GLJI G/L Journal Entry Query

GLSM GLJP G/L Journal Entry – Prior Period

GLSM GLJP Header Alt-F4 Browse Window

GLSM GLJR G/L Journal Entry -

GLSM GLJR Header Alt-F4 Browse Window

GLSM GLMA G/L Master Accounts

GLSM GLOS Alt-F4 Browse Window

GLSM GLOW Alt-F4 Browse Window

GLSM GLSC G/L Source Code Maintenance

LOTM LOTR Lot Trace Inquiry Report

ARSM AR2E G/L Distribution

ARSM ARCD A/R Cash Deposits

ARSM ARIP A/R Invoice/Payment Audit

ARSM ARPD A/R Prior Period Cash Deposits

CPMM JEST Job Estimates and Performance

CPMM OPSL Single Level Configuration Bill of

CPMM COCP Customer Order Copy

GLAM GLEX G/L Journal Entry Exceptions

MRPM MPSS Master Production Schedule

PURM POCI Purchase Order Contract/Price

PURM POCT Purchase Order Contract Report

PURM VEIT Items Supplied by Vendor

PURM VETI Items Supplied by Vendor Inquiry

CSHM CS2E G/L Distribution

CSHM SUND Sundry Disbursement

CSHM SUNR Sundry Receipt

CSHM SUPD Sundry Prior Period Disbursement

CSHM SUPR Sundry Prior Period Receipt

CSTM BAMT Batch Assignment

Module

Fourth Shift

Screen Description



Batch RTF Files

RTSM RTCT G/L Restructuring Consolidation

RTSM RTMT G/L Restructuring Master Account

SHPM AUTO Automated Packaging Exception

SHPM AUTO Automated Shipping Exception

Module

Fourth Shift

Screen Description

APSM APAG A/P Balance by Aging Category

APSM APCP A/P Period Close Audit

APSM APMQ A/P Module Communication

APSM APPV Purchase Price Variance

APSM APRG A/P Invoice Register

APSM APRL A/P Payment Requirements List

APSM APRG A/P Invoice Register

ARSM ARAG A/R Account Aging Summary

ARSM ARCJ A/R Credit Memo Journal

ARSM ARIR A/R Invoice Register

ARSM ARRJ A/R Cash Receipts Journal

ARSM ARCP A/R Close Period

ARSM ARTX A/R State Tax Register

ARSM ARMQ Invoice Module Communication

ARSM IVPP Pre-Period Invoices Report

CPMM CINV Custom Product Finished Inventory

CPMM CWIP Custom Product WIP Report

CSHM BKTR Bank Cash Transaction Update

CSHM CSCP Cash Management Close Period Analysis

CSHM CSPG Cash Management Purge Report

CUSM COBK Backlog Report by Customer

CUSM COYE Customer Year End Processing

EXPM PRTX Printed Extract

GLSM GLRP G/L Report Print

Module

Fourth Shift

Screen Description



GLSM GLTP G/L Account Type Exception

GLSM GLTP G/L Account Type Maintenance

GLSM GLAU G/L Audit Report

GLSM GLAU Balance Limit Exceeded

GLSM GLAU Bank Balance Update Report

GLSM GLAU Batches Posted-Headers Only

GLSM GLAU Batches Rejected

GLSM GLAU G/L Journal Entry

GLSM GLAU Master Account Numbers Created

GLSM GLAU Net Change Report

GLSM GLAU Reversal Journal Entries (JEs) Created

GLSM GLAU Suspense Listing

GLSM GLBL G/L Budget List Detail

GLSM GLBL G/L Budget List Summary

GLSM GLBL G/L Budget List Combined

GLSM GLBL G/L Budget List Worksheet

GLSM GLMQ G/L Module Communication

GLSM GLMQ Invalid Account Number Report

GLSM GLMQ Suspense Listing

GLSM GLMQ Update batches

GLSM GLMQ Zero Amount Transaction Report

GLSM GLPC G/L batches Posted-Headers only

GLSM GLPC G/L batches Audit Report

GLSM GLPC G/L batches Exception Report

GLSM GLPC Retained Earnings Organizations Report

GLSM GLPC G/L Master Account Numbers

GLSM GLPC Net Change Report

LOTM LEXP Lot Expiration/Retest Evaluation

LOTM LHIS Lot Trace Serialization

LOTM LVAL Lot trace Bill Validation

MGRM ABCR ABC Analysis Report

MGRM IACR Inventory Accuracy Report

MGRM ICCR Inventory Cycle Count Report

Module

Fourth Shift

Screen Description



MGRM SPFR Manufacturing Schedule

MGRM SPFR Master Schedule Performance

MOMM CLOA Order Reconciliation Report

MOMM IHIR In-Inspection and On-Hold

MOMM MOFR Manufacturing Order Follow-up

MRPM MPSR Master Product Schedule

PRCM COMP Cost Comparison Report

PRCM CSTU Actual Cost Update Report

PRCM WIPL WIP Item List

PURM POCP Purchase Order Contract Purge

PURM POCR Purchase Order Contract Report

PURM PORR Purchase Order Receiving Report

PURM POSR Purchase Order Receiving

PURM VDSC Vendor Schedule Report

PURM VPFR Vendor Performance Report

PURM POYE Purchasing year End

RPTM BKFL Backflush Issue Reconciliation

RTSM RTEX Master Account Merging Financial

RTSM RTIN Data Integrity Error Report

RTSM RTPR Account Cross Reference (Current)

RTSM RTPR Account Cross Reference (New)

RTSM RTPR New Chart of Account

RTSM RTPR New G/L Organization Structure

RTSM RTPR Open/Closed/Inactive Master

RTSM RTPR Organization Group Disposition Report

RTSM RTPR Organization Cross Reference

RTSM RTPR Partially Qualified Organization List

RTSM RTPR Retained Earnings Organization Boundary

RTSM RTPR Sample Log File

RTSM RTPR Unauthorized Master Account Merging

RTSM RTPR Untranslatable Accounts Report

RTSM RTPR Untranslatable Organizations

RTSM RTPR Master Account Merging Financial

Module

Fourth Shift

Screen Description







SHPM SHPL Shipment Log

SYSM ACCT Account verification Report

Module

Fourth Shift

Screen Description



Active Users List Tool

Active Users List HelpActive Users List utility displays the current active user list of Fourth Shift, Net UI, Engineering, Sales Order Processing, Shop Floor, Shop Calendar, FSTI, FS Explorer, and WebUI modules. It shows information of all users who are connected to the Fourth Shift Lock Server, including their Windows account, IP address/session.

This function is useful for identifying users logged in before rebooting or updating the server or for determining license usage and counts.

The Active Users List is intended for system administrators and is available in the Fourth Shift Tools, and as a Windows application as a web page in the Portal Admin group with My Fourth Shift Workplace. It does not require a Fourth Shift license to run.

Using the Active Users List FunctionOn the ServerGo to: Program Files > Fourth Shift Tools > Active Users List

The file resides in M:\MfgSys\System\ActiveUsers.exewhere M: is an example mapped drive letter.

In My FourthShift WorkplaceGo to the Fourth Shift Active Users List portal in the Portal Admin group.

The file resides in C:\InetPub\wwwroot\FSPortals\ActiveUsers.aspxwhere C: is an example drive letter.

On a Client WorkstationTo run the Active Users List function on a client workstation, create a shortcut on the Desktop:

1. Copy the shortcut for ActiveUsersList from the server and paste it to the Desktop on the client.

2. Verify that shortcut points to the correct mapped drive on the client.

FieldsThe following user information is obtained from the Lock Server defined in the Fourth Shift configuration file (fs.cfg) on the server to which the current Fourth Shift system is attached. This information is grouped by different FS systems.

Fourth Shift SystemThe system identification of each Fourth Shift system connected to the Lock Server for this server. Each Fourth Shift system is listed in a separate section.

Sequence NumberThe generated row number that allows the user to count how many users are logged in.

UserIn alphabetical order, the username of the user who is online and consuming a license in the Fourth Shift system.



Windows AccountThe Windows account name of the user who is online and consuming a license in the Fourth Shift system.

License NameThe name used to register the Fourth Shift license with the Lock Server.


Documents

System Administration ADMMworthen.xdatasync.com/support/PrintDoc/ADMM.pdfFourth Shift Release 7.50 System Administration 6 Standard Directories and Files The standard environment contains