Fourth Shift Overnight process

Overnight Command Script File

A typical overnight process consists of a batch or command script file usually called AutoDay.cmd to execute the following tasks Close all services: The 2 Fourth Shift services (Main and Fin) are stopped using net stop command. This is to ensure all users are out of the system and to clear any remaining locks on the Fourth Shift database.

NOTE: The output of all tasks are redirected to \LOGS\System.log this produces a log of all overnight processes
Backup Pre-Bexe folder copy: The Fourth Shift system root and all sub-folders are copied to a backup Pre-Bexe folder:Fourth Shift Data Export Module(EXPM)

SQL Pre Bexe backup (using ISQL or OSQL): Fourth Shift SQL database (FSDM) full back up to a file copied to Pre-Bexe folder

Archive processing: The Fourth Shift transactional log file called Archive.fil can be extremely useful for recovery requirements and possibly reporting. The archive file is moved to \Archive folder and rename with a date stamp reference:Fourth Shift Access Extract Task(ACCX)

Restart services and run overnight processes (-I parameter): The Fourth Shift services are restarted using the NET START command and the Fourth Shift overnight batch execution(BEXE) is run automatically using the I parameter of FSGUIAPP.EXE. The FSGUIAPP.EXE is the main client application file and the I parameter enables key strokes to be sent to the client application. The Fourth Shift batch execution (BEXE) task is usually called DAY:

Fourth Shift XP batch execution: Old 16bit applications still require dbase extract files to be executed nightly to update reference information for example advance price book and approved vendor sourcing. These Dbase extract tasks are contained in a Fourth Shift batch execution(BEXE) called XP:

NOTE: Due to a timing bug it is necessary to stop and start the Fourth Shift services between Fourth Shift batch execution (EXEC) tasks run automatically from a command script

Close all services: The 2 Fourth Shift services (Main and Fin) are stopped using net stop command. This is to ensure all users are out of the system and to clear any remaining locks on the Fourth Shift database.

Backup Post-Bexe folder copy: The Fourth Shift system root and all sub-folders are copied to a backup Post-Bexe folder

SQL Pre Bexe backup (using ISQL or OSQL): Fourth Shift SQL database (FSDM) full back up to a file copied to Pre-Bexe folder

Start all services: restart the Fourth Shift Services using NET START command to complete the Fourth Shift overnight process

Modcom Processing

Modcom files are text transactional log files providing an interface between the manufacturing and financial parts of the Fourth Shift system. Modcom represents modular communication files and contain all the manufacturing transactions that have a financial impact. There are 3 main modcom files usually found in \Mfgsys:

Modcomap.fil: Accounts Payable modcom file containing purchasing financial information
Modcomiv.fil: Accounts Receivable modcom file containing customer and shipment financial information
Modcomgl.fil: General ledger modcom file containing all manufacturing transactions that have a financial impact

There are 3 Fourth Shift batch execution tasks(BEXE) tasks which process the modcom files into the financial part of Fourth Shift:

APMC: processes the Modcomap.fil file into Fourth Shift
IVMC: processes the Modcomiv.fil file into Fourth Shift
GLMC: processes the Modcomgl.fil file into Fourth Shift

There are various issues that can result in the Modcom file not processing. If this occurs then the Modcom file that has failed is renamed with a MC extension. This can cause confusion because subsequent processes will only process the associated MC extension regardless of new modcom file files which may be available. The .MC modcom file will be renames to an old extension if processed correctly. The new incoming .FIL modcom files will be processed
There are 3 other modcom files:

Modcomsa.fil and Modcomsl.fil are used with Sales Analysis Module
ModcomEx.fil: Is a user method for importing general ledger transactions into the financial part of Fourth Shift

Use the Fourth Shift General Ledger submission screen (GLSS) to review batches created when processing modcom information into Fourth Shift.

The Fourth Shift Overnight Batch Execution Task(BEXE)

Usually day, week and monthly (EOP) Fourth Shift overnight batch execution tasks (BEXE) are defined to support MRP, Financial and reporting requirements. Examples of these BEXE tasks are shown in system administrator-batch pre-requisites-Batch Examples

A common query is can a particular Fourth Shift batch execution (BEXE) task be executed during the day. The answer depends on Fourth Shift locking. All Fourth Shift batch execution (BEXE) locking requirements are detailed in system administrator database locking

Fourth Shift locks on data groups:

S: Shared (S): Other users can view or access information in the data group while this function is being executed
Exclusive (E): No other user can access information in the data group while this function is executing

Fourth Shift Batch Execution Tasks

Typical Manufacturing Bexe tasks

Mrp planning – PLNG,PREV,SREV
Costs management – CROL,CROV
Back flushing – BKFL
Order Variance – OVAR
ABC analysis – ABCR
Inventory history update – ITHU
Manufacturing reports – IACR,ICCR,INVR,MOFR,PORR,WIPR,WIPL,WIPS

Typical Financial Bexe tasks

Modcom processing -IVMC,APMC,GLMC
Aging -APAG,ARAG
Purging -APPG,ARPG
Period close -APCP,ARCP,GLPC
Invoice printing –IVPR,IVEX,IVRR,IVRX
Statement printing –ARST
Exchange rate update –EXRU
Financial reports –APCR,APPV,APTB,ARTB,GLTG,APUV,GLRP