R800D Release Notes

Fourth Shift
Interim Service Release 8.00D

Release Notes
Fourth Shift 8.00D Release Notes
Fourth Shift Release Notes

Release 8.00D
Important Notices
Copyright © 2023 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.
© 2023, INFOR. Page 2

Contents
Fourth Shift 8.00D Release Notes ......................................................................................................... 6
Release 8.00D Upgrade Requirements ............................................................................................... 6
Platform Considerations ....................................................................................................................... 6
Database Platforms .......................................................................................................................... 6
Operating Systems ........................................................................................................................... 6
System-wide Modifications in This Release ......................................................................................... 7
Report Changes ............................................................................................................................... 7
Screen Changes That May Affect Customizations .......................................................................... 7
System Control Module Modifications in this Release ....................................................................... 12
Manufacturing Module Modifications in this Release ......................................................................... 12
Fourth Shift 8.00C Release Notes ....................................................................................................... 14

Release 8.00C Upgrade Requirements ............................................................................................. 14
Platform Considerations ..................................................................................................................... 14
Database Platforms ........................................................................................................................ 14
Operating Systems ......................................................................................................................... 14
Microsoft’s Edge and Google Chrome’s web browser support ...................................................... 15
Microsoft Office 2016 and Office 365............................................................................................. 15
System-wide Modifications in This Release ....................................................................................... 16
Report Changes ............................................................................................................................. 16
Screen Changes That May Affect Customizations ........................................................................ 16
Financial Module Modifications in this Release.................................................................................. 16
WEBUI Module Modifications in this Release .................................................................................... 18
Fourth Shift 8.00B Release Notes ....................................................................................................... 19

Release 8.00B Upgrade Requirements .............................................................................................. 19
Report Changes ............................................................................................................................. 20
Fourth Shift 8.00A Release Notes ....................................................................................................... 21

Release 8.00A Upgrade Requirements .............................................................................................. 22
Internet Explorer ............................................................................................................................. 22
DCOM Changes ............................................................................................................................. 23
Fourth Shift WebUI Enhancement ................................................................................................. 23
ConnectivityToolkit Enhancements ................................................................................................ 23

Microsoft’s Edge and Google Chrome’s web browser support ...................................................... 24
Data Import Macro and FSTI Macro Changes ............................................................................... 25
Report Changes ............................................................................................................................. 25
Foundation Business Views Changes ........................................................................................... 26
New Batch Mode Generation of Outbound 855 CO Acknowledgements ...................................... 27
New ALT- F4/GUI and WebUI Ctrl-B/Browsers ............................................................................. 27
New Audit Records for CROV E (Exchange) to Cost Type 0 ........................................................ 28
New Reference Fields Added to COMT (Order Entry) Line Detail ................................................ 28
New IMTR Moves of Shipping Inventory to another Shipping Location ........................................ 28
New ALT- F4/GUI and WebUI Ctrl-B/Browsers ............................................................................. 28
New APCR (A/P Check Reprint) Email Check Remittance Advice ............................................... 29
New G/L Transaction Reference Field and Flow Employee ID of PICK Transactions to G/L ....... 29
New Data-Only Parameter Option for BEXE Reports .................................................................... 30
Fourth Shift 8.00 Release Notes .......................................................................................................... 30

Release 8.00 Upgrade Requirements ................................................................................................ 31
Internet Explorer ............................................................................................................................. 31
Microsoft Office 2016 Support ....................................................................................................... 32
Security .......................................................................................................................................... 32
Fourth Shift WebUI Enhancement ................................................................................................. 32
ConnectivityToolkit Enhancements ................................................................................................ 32
DCOM Changes ............................................................................................................................. 33
Adobe Document Cloud Supported ............................................................................................... 33
Batch Setup Parameter Validation Enhancement ......................................................................... 33
Fourth Shift Installation Enhancement ........................................................................................... 33
Fourth Shift Explorer Removal ....................................................................................................... 34
Fourth Shift SQL Server Database Primary Keys .......................................................................... 34
Windows Authentication Enhancement ......................................................................................... 34
Data Import Macro and FSTI Macro Changes ............................................................................... 35
Foundation Business Views Changes ........................................................................................... 36
Report Changes ............................................................................................................................. 37
Native 64-Bit Services .................................................................................................................... 38
Cost Rollover Database Locking Changes .................................................................................... 38
Employee ID Added to PICK Transactions .................................................................................... 39
Inventory Valuation Report Enhancement ..................................................................................... 39
Sales Order Processing Archive Transactions Enhancement ....................................................... 39
Lot Trace History Reload Function Removal ................................................................................. 40
OVAR Retention of Additional Closed Order Variance Fields ....................................................... 40

New Accounts Payable Aged Trial Balance Report Sort Options ................................................. 40
Future Aging Category Added to the Accounts Receivable Trial Balance Report ........................ 41
Bank Routing and Account Number Fields Expand to 50 Characters ........................................... 41
CNFA Separate Accounts for Applied Overhead ........................................................................... 41
G/L Journal Entry-Recurring/Templates Enhancement ................................................................. 41
General Ledger Account Validation for (G-Type) Purchase Orders and Inventory Adjustments .. 42
Companion Applications ..................................................................................................................... 44
Appendix: How to Make Existing FSTI Programs Work With Fourth Shift Release 8.00 .................. 45
How to Make .NET FSTI Programs Work ...................................................................................... 45
How to Make Unmanaged FSTI Programs Work .......................................................................... 46

Fourth Shift Release 8.00D includes enhancements and improvements to your Fourth Shift
system, allowing your company to run more efficiently and effectively. These upgraded features
are provided for modules included in your Support Services agreement. This Release Notes
document describes new functionality in existing modules, allowing you to process data more
quickly and improve access to your data for effective decision making.
It is important that all users be familiar with changes in this release. This document is intended to
help you become familiar with improvements and significant changes included in the release. The
Release Instructions also include many options and updates when installing or upgrading your
system. It is important to review these documents and test the impact of these changes on your
environment and your production data.
Additional documentation is located in the downloaded compressed file that supports this release:
• README.txt file contains information about fixes in Fourth Shift Release 8.00D.
• R800D_Release_Instructions.pdf contains instructions to upgrade your system to Fourth
Shift 8.00D.
IMPORTANT:
Because of the feature additions included with this release, it is important that all users be familiar
with the changes as described in this document. There are also many system and administrative
changes in Release 8.00D that will impact maintenance of the system. A thorough system test of
your customizations, import transactions, reports, and companion applications is highly
recommended before running Release 8.00D as your production system.
Release 8.00D Upgrade Requirements
You must have 7.50F or higher installed before upgrading to Fourth Shift Release 8.00D.
Platform Considerations
Database Platforms
Fourth Shift 8.00D is compatible with Microsoft SQL Server 2012 Service Pack 4, Microsoft SQL
Server 2014 Service Pack 2, Microsoft SQL Server 2016 Service Pack 1, SQL Server 2017
Cumulative Update 4, SQL Server 2019 and SQL Server 2022.
Operating Systems
Fourth Shift 8.00D supports Windows Server 2012 R2, Windows Server 2016, Windows Server
2019 and Windows Server 2022 for the Fourth Shift Server, the SQL Database server, the
Reporting Services server and the My Fourth Shift Workplace server.
Fourth Shift 8.00D supports the following Fourth Shift client workstations:
• Windows 11
• Windows 10
• Windows Server 2012 R2
• Windows Server 2016

Fourth Shift 8.00D no longer supports the following platforms that were supported at Release
7.50:
• Windows XP
• Windows 7, 32 bit and 64bit
• Windows 8
• SQL Server 2005
• SQL Server 2008 R2
System-wide Modifications in This Release
Report Changes
Customized 7.50 reports can still work with 8.00D because SSRS RDL is backward compatible,
but all customized reports should be verified as part of your upgrade testing.
Report File Name
A/P NEC Aps1099NEC.rdl
A/P Aged Trial Balance ApsAptb.rdl
A/P Unvouchered Report ApsApuv.rdl
Screen Changes That May Affect Customizations

Fields have been added or removed from the following screens. These changes may affect your
screen customizations including those made using Connectivity Toolkit (CTKM), Screen
Customizer (SCRM), and CIM Customizer (CSTM).
Screen Changes
System Installation setup (CNFG) Added Reason Code Control
Configuration of Interface Account When Reason Code Control parameter in CNFG is set to
Number (CNFA) P (Product line Control), a new transport/short cut key F9
which will invoke Product Line Reason Code screen is
displayed
Inventory Adjustment (INVA) Reason Code field length is changed from 1 to 2 alpha
numeric value. WebUI also updated with increased size.
INRC – Reason Code Definition New master screen added
Product Line Reason Code (CNFA New master screen added

child screen)
 Fourth Shift F3 HTML Help for Workplace and FS GUI

Fourth Shift Application Help in Workplace supports by Google Chrome and Microsoft Edge
browsers.
 Report Model (SMDL) Removal

Removed this as Microsoft marked this as deprecated feature.
 Planning Rebuild Tool (Auto Trigger Precaution Job/Scheduler)
Once the Tables Mfg_DFSFNSF and Mfg_SUBDF have reached 90% capacity of key values,
then the system will auto trigger an alert email notification. Notification is sent to the
respective recipients, defined in the auto batch job. The recommended action is to run the
rebuild tasks using the Rebuild automation tool.
Batch job can be scheduled periodically (daily/weekly/monthly) based on the customer’s
PLNG Activity and send notifications based on table usage when exceeding 90%. This auto
trigger precaution mail script is going to be added into 80000ISR.sql file.
 FS Database Objects Check Tool

This tool compares Fourth Shift standard database objects against the customer database. It
will help to identify if the issue the customer is having is related to a customization.
 Logging Master Record Modifications
Screen Changes
CNFG Audit logging for changes done to Reason Code

Control parameter in CNFG screen. Archive record is
created with “CNFG01” key.
INRC – Reason Code Definition Below keys are used while adding audit logging when
add/modify/delete operations are performed in INRC
screen.
Add: INRC01
Modify: INRC02
Delete: INRC03
Product Line Reason Code (CNFA Below keys are used while adding audit logging when
child screen) add/modify/delete operations are performed in Product
Line Reason Code screen.
Add: CNFA04
Modify: CNFA05
Delete: CNFA06

 FS Report Server Configuration Update Through Backup Manager

After restoring the Fourth Shift database through Backup Manager, currently the user is required
to open Report configuration tool and needs to mass update the report configuration values like
Web Server Name, System Name and Output path, with this enhancement the values will be
automatically updated by the Backup Manager Tool.
 Windows Server 2022 Support

Fourth Shift server installation support for Windows Server 2022.
 Windows 11 Client Support

Fourth Shift client installation support for Windows 11 Client.
 Database Schema and Scripts Changes

Additions and modifications to the existing schema, tables, stored procedures, indexes, jobs and
views:

Name Change Details

Type
FS_InventoryAdjustmentRea New
Column Name Data Type Description
sonCode table
ReasonCode varchar(2) User-Defined Reason
Code
ReasonCodeDescription varchar(30) Reason Code Description
Active Bit Set the reason code
being Active/Inactive
1 = Yes; 0 = No
AllowProductLineOverrid Bit Allow change if control is
e at the product line level
1 = Yes; 0 = No
ManualInputOfAccount Bit Cause INVA to require
manual input master
account
1 = Yes; 0 = No
MasterAccountNumber varchar(20) Master Account No
ReasonCodeUsed Bit The reason code can be

deleted if it has not been
used in INVA transaction
1 = Yes; 0 = No.
Currently, not in use.
FS_ProductLineReasonCode New
table Column Name Data Type Description
Active bit Set the reason code

being Active/Inactive
1 = Yes; 0 = No
ManualInputOfAccount bit Cause INVA to require
manual input master
account
1 = Yes; 0 = No
MasterAccountNumber varchar(20) Master Account No
ProductLineKey Int Associated product line
key
InventoryAdjustmentRea Int Associated INRC reason
sonCodeKey code key
ProductLineReasonCode rowversion Row-version of the
RowVersion reason code
ProductLineReasonCode Init Product line reason code
Key
[Mfg_PARAMETR].[CLBODY Table Configure the reason code control level of char type with
].[position 35] Column length as 1.
FS_SystemConfig View view will be added one more field to fetch new parameter
Reason Code Control
FS_HistoryInventoryAdjustm View The length of the column ChangingBalanceReasonCode to

ent expanded from 1 to 2.
usp_InsertInventoryAdjustme Stored Creating new INRC reason code.

ntReasonCode Procedure
usp_UpdateInventoryAdjustm Stored Updating an existing INRC reason code.

entReasonCode Procedure
usp_DeleteInventoryAdjustm Stored Deleting an existing INRC reason code.

entReasonCode Procedure

usp_GetInventoryAdjustment Stored Retrieving an existing INRC reason code.

ReasonCode Procedure
usp_InsertProductLineReaso Stored Creating new Product line reason code.

nCode Procedure
usp_UpdateProductLineReas Stored Updating an existing Product line reason code.

onCode Procedure
usp_DeleteProductLineReas Stored Deleting an existing Product line reason code.

onCode Procedure
usp_GetProductLineReason Stored Retrieving an existing Product line reason code.

Code Procedure
SAAM table changes Update SA_tbl.sql: Size increased from 1 to 2 char as

table [SA_InventoryAdjustment].[ChangingBalanceReasonC
column ode] [char] (1 length) -> (2 length)
Mfg.sql: Size increased from 1 to 2 char.

[SA_InventoryAdjustment].[ChangingBalanceReasonC
ode] [char] (1 length) -> (2 length)
[SAS_InventoryAdjustment].[ChangingBalanceReason
Code] [char] (1 length) -> (2 length)
SA80000ISR.sql
Expand length of
[SA_InventoryAdjustment].[ChangingBalanceReasonC
ode] to two characters for separate SAAM database
install.
FSDictionary Document Details about new tables and columns

ation
80000ISR.sql New Job Auto trigger precaution mail script when tables
script and Mfg_DFSFNSF and Mfg_SUBDF are reached 90% of
schedule usage of key values.

System Control Module Modifications in this Release
 New CNFG Configuration Parameter: Reason Code Control

A new configuration input parameter REASON CODE CONTROL is added in CNFG screen.
This parameter specifies the way pre-defined reason codes are configured while creating
inventory adjustment records (INVA). The available options are
:
N = No control: This would be the default option which results in INVA retaining its
previous behavior. Reason code takes up to two alpha-numeric value.
S = System level control: pre-defined reason codes associated with account number
can be configured in INRC screen and same codes can be used while creating
inventory adjustment records in INVA screen.
P = Product line control: pre-defined reason codes associated with account number
can be configured to product line in the CNFA F9=Product Line Reason Code
screen. User can select the reason code records which are added in the INRC
screen. These pre-defined codes can be used while creating inventory
adjustment records in INVA screen.
 PASS Screen: Added a Confirm Action Ctrl+Enter

In PASS screen, when there is a change in one of the header fields (Minimum Expiration,
Maximum Expiration, Expiration Notice, Minimum Password Length, Maximum Retries) and
Enter key is pressed, a new message advising user to “press Ctrl + ENTER key” to be shown
on the status bar. Earlier, merely pressing Enter key was enough to save the header field
changesChanges are now saved when the user confirms Ctrl + ENTER.
 New Transport/shortcut Key for Product Line Reason Code Screen is

Added to CNFA Screen
When Reason Code Control parameter in CNFG is set to P (Product line Control), a new
transport/short cut key F9, which will invoke Product Line Reason Code screen, is displayed.
Manufacturing Module Modifications in this Release
 New Master INRC Screen to Pre-define System Wide Reason Codes

The new INRC screen is used to maintain reason code master records. These reason codes
are used in INVA and Product Line Reason Code screens. The default reason codes ("C"
and "S") will be added automatically. User can perform operations such as add, modify, view,
delete and marking active and inactive on reason code records. Master account number can
be associated for each reason code record.
Browse windows are provided for reason code and account number fields. When Reason
Code Control value in CNFG screen is set to “S”, then use reason codes defined in INRC
screen.
 New Master Product Line Reason Code (CNFA Child) Screen to Pre-
Define Product Line Wide Reason Codes
The Reason codes can be configured per product line using this new screen. The Product
Line Reason Code screen can be accessed when Reason Code Control configuration in
CNFG is set to “P” (Product control level). Selecting a product line in the CNFA screen and
pressing F9 key will navigate to Product Line Reason Code screen where INRC master
reason codes are selected and same can be associated to the selected product line. Initially,
this screen will be empty. User can perform operations such as add, modify, view, delete and
marking active and inactive.
Browse window is provided for Reason Code and Master Account Number fields. When
Reason code control CNFG configuration is set to “P”, then INVA screen can use these
reason codes configured per product line.
 Using Pre-Defined Reason Codes in INVA Screen

This release allows INVA screen to use reason codes defined in INRC and Product Line
Reason Code based on CNFG configuration. When the Reason Code Control parameter in
CNFG is set to “N” (No Control), the system will retain previous behavior. Field length for the
reason code field is up to two alpha numeric value.
When Reason Code Control parameter in CNFG is set to “S” (System Control), user can use
reason codes configured in INRC screen. A pop-up (Alt + F4) browse screen in INVA
Reason Code field allows user to select pre-defined reason codes. The default reason codes
(“C” and “S”) will be configured automatically.
When Reason Code Control parameter in CNFG is set to “P” (Product line Control), user can
use reason codes configured in Product Line Reason Code (CNFA) screen. A pop-up (Alt +
F4) browse screen in INVA Reason Code field allows user to select pre-defined reason
codes. The default reason codes (“C” and “S”) will be configured automatically.
Browse window is provided for Reason Code field when the configuration is set to System
Control and Product Line Control.

Fourth Shift 8.00C Release Notes
Fourth Shift Release 8.00C includes enhancements and improvements to your Fourth Shift
• README.txt file contains information about fixes in Fourth Shift Release 8.00C.
• R800C_Release_Instructions.pdf contains instructions to upgrade your system to Fourth
Shift 8.00C.
IMPORTANT:
changes in Release 8.00C that will impact maintenance of the system. A thorough system test of
recommended before running Release 8.00C as your production system.
Release 8.00C Upgrade Requirements
You must have 7.50F or higher installed before upgrading to Fourth Shift Release 8.00C.
Database Platforms
Fourth Shift 8.00C is compatible with Microsoft SQL Server 2012 Service Pack 4, Microsoft SQL
Cumulative Update 4 and SQL Server 2019.
Operating Systems
Fourth Shift 8.00C supports Windows Server 2012 R2, Windows Server 2016 and Windows
Server 2019 for the Fourth Shift Server, the SQL Database server, the Reporting Services server
and the My Fourth Shift Workplace server.
Fourth Shift 8.00C supports the following Fourth Shift client workstations.
• Windows 8.1
• Windows 10
Fourth Shift 8.00C no longer supports the following platforms that were supported at Release
7.50.

• Windows XP
• Windows 8
• SQL Server 2005
Microsoft’s Edge and Google Chrome’s web browser support

At Fourth Shift Release 8.00C, WebUI is now supported with Microsoft Edge and Google Chrome
with the following exceptions:
• CKTM Module (Connectivity Tool Kit). Customers are encouraged to move to Microsoft
Edge with Internet Explorer (IE) mode. The CKTM UI Editor can be launched with
Microsoft Edge in IE mode. IE mode is not supported native by Google Chrome’s web
browser. An IE Tab extension is required, available from Google Chrome
(https://chrome.google.com/webstore?hl=en).
Note: IE Mode or an IE tab extension is only required for CKTM development. It is not
required for general users that are utilizing customizations. We advise the testing of all
developed customizations for Google Chrome or Microsoft Edge compliance.
• Save Layout Link to update the frame sizes and locations of a current portal functionality
is not supported.
• WebUI Screen Help is not supported. Fourth Shift help can be accessed through Help
menu | Print Library.
• WebUI Chart Builder functionality used to create and maintain user defined charts,
graphs and tables is not supported.
• WebUI CTRL T keyboard shortcut used to transport to supplemental screens functionality
is not supported with Google Chrome’s web browser.
Google Chrome provides a product standard Ctrl + T shortcut which is used to open a
new browser tab. Google Chrome users should consider alternative approaches for tab
selection; mouse action or shortcut Ctrl + <number> to navigate to specific tab, see
example.
Microsoft Office 2016 and Office 365
• Fourth Shift Customers can take advantage of Microsoft Office 2016 and Office 365 for
Fourth Shift 8.00C as the supported Office platform. Fourth Shift uses the Office Access
database to manage external data, Office Excel sheet to perform data import and export
on Fourth Shift screens and reports, Office Word document preview / print Rich Text
Format (RTF) Fourth Shift reports, Office Word and Excel to access different export
formats SQL Server Reporting Services reports, and Office Outlook to manage emails.
• History Views Performance has been enhanced.
Report Changes
Customized 7.50 reports can still work with 8.00C because SSRS RDL is backward compatible,
Report File Name
A/P MISC Aps1099.rdl
A/P Summary Aps1099s.rdl
A/P Detail Aps1099v .rdl
A/P NEC Aps1099NEC.rdl

Screen Changes
APTP • 1099 Form Opened for MSC or NEC.

• State No increased to 10 digits.
ITMB • Last Inventory Consumed Date.

• Last Inventory Transaction Date.

 DISPLAY THE LAST INVENTORY ACTIVITY
Added two date fields at the item-level (ITMB-F9 screen):
Last inventory consumed date: Field shows the last time an item was truly “consumed”
whether in the form of being issued to an order or shipped to a customer.
Last inventory transaction date: Field shows the last time ANY inventory transaction (issue,
receipt or adjustment) has occurred.
Last consumed date and last transaction date database fields will be populated by the date
when specific PICK, BKFL, BKSV, SHIP, CROV, PORV, MORV, INVA, CPMT, or COMT
transaction happens.
Financial Module Modifications in this Release

 1099 MISC and New NEC Form changes according to new format of IRS
Document (supplied by US Government)

Fourth Shift Release 8.00C adds a new feature by add/Change the Category codes for
1099 forms with respect to MISC and New NEC Form shared by IRS in 2020.
• State Code now accept up to 10 Digits in APTP Screen instead of 2 digits
• Preprinted forms Category code positions changed for MISC and New NEC
Form.
• Selection of processing method R, by selecting detail or summary and print or file
considered after new changes for MISC and New NEC in APTP Screen.
• Generates files IRSTAXMSC and IRSTAXNEC for MISC and NEW NEC form.
Before Year 2020 From Year 2020

1099 Category 1099 Category
CATEGORY Code Description FORM Code FORM Code
Rents MSC 1 MSC 1
Royalties MSC 2 MSC 2
Other Income MSC 3 MSC 3
Federal Income Tax Withheld MSC 4 MSC 4
Fishing Boat Proceeds MSC 5 MSC 5
Medical and Health Care Payments MSC 6 MSC 6
Substitute Payments MSC 8 MSC 8
Foreign Tax Paid** MSC 9
Crop Insurance MSC 10 MSC 9
Attorney Proceeds MSC 14 MSC 10
Excess Golden Parachute MSC 13 MSC 13
Non Qualified Deferred MSC 14
State Tax Withheld MSC 16 MSC 15
Reimbursed Expenses/NON1099 MSC RR MSC RR
Non-Employee Comp* MSC 7 NEC 20
Federal Income Tax Withheld * - - NEC 21
State Tax Withheld * - - NEC 22
** Foreign Tax Paid was eliminated as it is not reported on 1099MSC or 1099NEC
*When selecting a CC code in the 1099 distribution window (shown below), the 1099
Form will automatically default to MSC. When you enter or select codes 20,21, or 22 in
the Cc field, the system will automatically change the 1099 Form to NEC, code 20 to code
01, code 21 to code 4, and code 22 to code 5.
Note: Upgrade process will update 1099 Category Codes to the new codes, on AP Invoices
/payments that have the current year listed in the Tax Year field.
Example: if user upgrades on 01-Oct-2021 then Category codes update with the new Category
codes for AP invoices/payments with the tax year 2021 only, if user upgrades on 15-Jan-2022
then Category codes update with the new Category codes for AP Invoices/payments with the tax
year 2022 only.
 Customer/Vendor payment terms allow discount days till due date.

Fourth Shift Release 8.00C adds a new feature by adding allow to provide the discount till
due date (net days).
 AP Bank Transfer Form Print Invoice Comments

Fourth Shift Release 8.00C adds a new feature in APCW/APDS Bank Transfer Form
prints the comments.
WEBUI Module Modifications in this Release
 Upgrade Report Viewer Control
Fourth Shift Release 8.00C changes Report viewer control 11.0 with 14.0 Using 14.0
Report viewer control will overcome after Preview “Print” error in latest Report Server
versions like SSRS 2019 and able to print from other browsers Edge and Chrome.

Fourth Shift 8.00B Release Notes
Fourth Shift Release 8.00B includes enhancements and improvements to your Fourth Shift
• README.txt file contains information about fixes in Fourth Shift Release 8.00B.
• R800B_Release_Instructions.pdf contains instructions to upgrade your system to Fourth
Shift 8.00B.
IMPORTANT:
changes in Release 8.00B that will impact maintenance of the system. A thorough system test of
recommended before running Release 8.00B as your production system.
Release 8.00B Upgrade Requirements
You must have 7.50F or higher installed before upgrading to Fourth Shift Release 8.00B.
Database Platforms
Fourth Shift 8.00B is compatible with Microsoft SQL Server 2012 Service Pack 4, Microsoft SQL
Cumulative Update 4 and SQL Server 2019.
Operating Systems
Fourth Shift 8.00B supports Windows Server 2012 R2, Windows Server 2016 and Windows
Server 2019 for the Fourth Shift Server, the SQL Database server, the Reporting Services server
and the My Fourth Shift Workplace server.
Fourth Shift 8.00B supports the following Fourth Shift client workstations.

• Windows 8.1
• Windows 10 Fall Edition
Fourth Shift 8.00B no longer supports the following platforms that were supported at Release
7.50.

• Windows XP
• Windows 8
• SQL Server 2005
Fourth Shift 8.00B as the supported Office platform. Fourth Shift uses the Office Access
• History Views Performance has been enhanced.
Report Changes
Customized 7.50 reports can still work with 8.00B because SSRS RDL is backward compatible,
Report File Name
CO Picklist CusPick.rdl
A/P Check Printing/Export – Long Voucher, with Form ApsApcwus1l.rdl
Order Reconciliation Report Detail MgrOvad
PO Receiving Document PurPord
Shipping Packing List ShpPack


Screen Changes
LHIP - Lot Trace/Serialization History New two parameters added for entering lot number input
Purge file name and log validation message

LHIP new parameter to be able purging lot trace history by Lot Numbers
Fourth Shift Release 8.00B adds a new feature by adding two new parameters in LHIP Screen.
New Parameter “I”
• The new parameter “I” followed by the text file name. The text file contains lot numbers
and one lot is per line. The LHIP will only review these given lot numbers in the text file,
instead of all lots in the database. The parameter “I” is optional. The LHIP will work as
prior version if user does not provide the parameter “I”.
Logging of new messages in log file
• Which may tell why the lot cannot be purged. So that user can run LOTR function to do
cross-reference with the logged messages. There was hidden debug parameter “LX” to
log debug information in the LHIP log file, the X is 1 or 2 for the level of debug
information. We may utilize this “L” parameter to log more information, which tells the
reason that lot number cannot be purged. We will expose this parameter to help user
identify the lot purging process. This parameter is optional, too.

NA
Fourth Shift 8.00A Release Notes
Fourth Shift Release 8.00A includes enhancements and improvements to your Fourth Shift
• README.txt file contains information about fixes in Fourth Shift Release 8.00A.
• R800A_Release_Instructions.pdf contains instructions to upgrade your system to Fourth
Shift 8.00A.
IMPORTANT:
changes in Release 8.00A that will impact maintenance of the system. A thorough system test of
recommended before running Release 8.00A as your production system.

Release 8.00A Upgrade Requirements
You must have 7.50C or higher installed before upgrading to Fourth Shift Release 8.00A.
Database Platforms
Fourth Shift 8.00A is compatible with Microsoft SQL Server 2012 Service Pack 4, Microsoft SQL
Server 2014 Service Pack 2, Microsoft SQL Server 2016 Service Pack 1 and SQL Server 2017
Cumulative Update 4.
Operating Systems
Fourth Shift 8.00A supports Windows Server 2012 R2 and Windows Server 2016 for the Fourth
Shift Server, the SQL Database server, the Reporting Services server and the My Fourth Shift
Workplace server.
Fourth Shift 8.00A supports the following Fourth Shift client workstations.
• Windows 7, 32 bit and 64 bit

• Windows 8.1
• Windows 10 Fall Edition
Fourth Shift 8.00A no longer supports the following platforms that were supported at Release
7.50.

• Windows XP
• Windows 8
• SQL Server 2005
Internet Explorer
Fourth Shift 8.00A requires Internet Explorer 11.
The following Internet Explorer versions are not supported at Release 8.00A
• Internet Explorer 9
Fourth Shift 8.00A as the supported Office platform. Fourth Shift uses the Office Access
DCOM Changes
The use of Microsoft’s Distributed Component Object Model (DCOM) has been eliminated with
Fourth Shift Release 8.00A. FSGuiApp.exe is no longer registered for DCOM, and
FSCreateObject.exe has been replaced with FSCreateObject.dll. All code formerly acquiring
mapped-drive access via DCOM now accomplishes this using FSCreateObject’s InitializeConfig
function. Any custom code (introduced via Connectivity Toolkit) will need to be similarly updated,
using the existing code as an example (See FSWebUI\FSWebUI.inc and
FSWebUI\BuiltIns\ShowSSIIInDataGrid.asp). However, this is only necessary when the My
Fourth Shift Workplace server is accessing the Fourth Shift server via a user network drive
mapping (when the servers are separate). If My Fourth Shift Workplace is installed locally on the
Fourth Shift server (and is accessing Fourth Shift via an aliased drive letter), then these
modifications are optional.
Configuration of identities formerly assumed via DCOM is now accomplished with settings
configured within Internet Information Services (IIS) and is entirely handled by the My FS
Workplace installation and repair process. The Workplace installation and repair processes will
prompt for the WebUI User Account and will automatically apply this to the appropriate
FSWPAppPool and web application settings.
A new tab has been added to the FSIntegrate utility, located in KB 1879029, to configure multiple
instances for Workplace and the FSTM module.
Fourth Shift WebUI Enhancement

The INFOR SoHo grid has been introduced to the Fourth Shift Finders web user interface
(Workplace). This is a significant enhancement to Workplace Finders. The grid supports many
robust capabilities.
• Full grid with number of rows returned displayed in the grid footer
• Paging
• Sort by clicking column headings
• Able to resize column widths
• Able to change order of columns by drag–n-drop
• Able to choose columns to display/hide
• Filter grid results by entering criteria in fields under column headings
o Equal, Greater Than, Less Than or Equal, Contains, Starts With, etc.
• Export to Excel
Note: Fourth Shift Workplace is best viewed at a screen resolution of 1280 x 960 pixels
or higher.
ConnectivityToolkit Enhancements
ExecuteSQL and ShowQueryInDataGrid
ExecuteSQL and ShowQueryInDataGrid functions were updated in 8.00A to once again allow
access by default, but only in a limited secure way. These functions were disabled by default in
8.00 because there was no secure mode of operation. In 8.00A, these functions introduce a more
secure mode of operation, active by default, by allowing sensitive parameters such as query text
to be stored in a secured file hosted on the server. This is similar to the way the CustomField and
SelectExternal functions operated securely even in the 8.00 release.
New sample text files ExecuteSQL.txt and ShowQueryInDataGrid.txt demonstrate and document
how parameters may be securely specified for the respective functions. There are also two large
blocks of text comments in each of ExecuteSQL.asp and ShowQueryInDataGrid.asp, the second
introduced with the word “WARNING”, explaining the parameters that are available and how to
use the parameters in either the new secure mode, or the old insecure mode. Although all secure
and insecure parameters are still available and documented, the default behavior is to present an
error if sensitive parameters are passed on the URL in an insecure way, as opposed to storing
them in the text file on the server.
PlayInputStream
The fsPlayInputStream function has been updated for security reasons. If any customizations are
relying on this function, they may need to be updated. If the function is being called in a way that
retrieves input data from a database, it will need to be updated to refer to a TXT file and section
name instead.
Note: At Fourth Shift Release 8.00A WebUI Help is not supported with the Microsoft’s Edge web
browser and with Google Chrome’s web browser. Fourth Shift WebUI Help is supported on
Internet Explorer
Parameterized Queries for ExecuteSQL, ShowQueryInDataGrid, CustomField and

SelectExternal
In order to enhance the security of these functions, a restriction has been introduced on the way
replaceable parameters are specified in queries used with these functions. Now, when a
parameter like “%1” is specified in a query it must not be embedded in a string. For example,
instead of specifying a query like:
• select = GenericKey, GenericData FROM GenericFieldData WHERE GenericKey =

'PCD_%1'
It will be necessary to separate the “%1” from the string in which it is embedded like this:
• select = GenericKey, GenericData FROM GenericFieldData WHERE GenericKey =

'PCD_' + '%1'
This allows the '%1' to be replaced with a placeholder (namely, a question mark) at runtime so
that a proper parameterized SQL query can be sent to ADO to execute the query in a more
secure way.
Microsoft’s Edge and Google Chrome’s web browser support

At Fourth Shift Release 8.00A, WebUI is now supported with Microsoft Edge and Google Chrome
with the following exceptions:
• WebUI Help is not supported with the Microsoft’s Edge web browser and with Google
Chrome’s web browser. Fourth Shift WebUI Help is supported on Internet Explorer 11.
• Save Layout Link to update the frame sizes and locations of a current portal functionality
is not supported with the Microsoft’s Edge web browser and with Google Chrome’s web
browser. Fourth Shift WebUI Save Layout Link is supported on Internet Explorer 11.

• WebUI CTRL T keyboard shortcut used to transport to supplemental screens functionality

is not supported with Google Chrome’s web browser. The WebUI CTRL T keyboard
shortcut is supported with Internet Explorer 11 and Microsoft’s Edge browsers.
• WebUI Chart Builder functionality used to create and maintain user defined charts,
graphs and tables is not supported with the Microsoft’s Edge web browser and with
Google Chrome’s web browser. Fourth Shift WebUI Chart Builder is supported on
Internet Explorer 11.
• CKTM Module (Connectivity Tool Kit) is not supported with the Microsoft’s Edge web
browser and with Google Chrome’s web browser. The WebUI CKTM Module
(Connectivity Tool Kit) is supported with Internet Explorer 11.
• Customer customizations should all be tested and may not be compatible.
Data Import Macro and FSTI Macro Changes

Your existing FSTI programs may need modification in order for them to function properly with
Fourth Shift 8.00A. Please see the Appendix of this document for more information.
The following Data Import Macros have been updated in Release 8.00A. Details about the
macros can be found in the “Data Import Macros and Data Dictionary” section of the online help.
Macro ID Action Description of Changes
COCF01 Allow Movement of Shipping Field #15 added for Allow

Inventory Movement of Shipping Inventory
COMT09 Change CO Line Item Detail Field #66 added as Reference

Line #1

Line #2

Line #3
ETPT04 Seq Num (new) Field #13 added
GLJE06 Change Batch Transaction Field #19 Reference #11 added

Detail
GLJP06 Change Batch Transaction Field #19 Reference #11 added

Detail
GLJR13 Change Recurring/Template Field #12 Journal Entry Reversal

Transaction Detail added
GLJR06 Add Template Journal Entry Field #12 Journal Entry Reversal
Header added
GLJR07 Change Template Journal Entry Field #12 Journal Entry Reversal
Header added
Report Changes
Customized 7.50 reports can still work with 8.00A because SSRS RDL is backward compatible,
Report File Name

Print Remittance or Overflow ApsApcr.rdl
Report File Name

Print Remittance or Overflow ApsApcr.rdl
A/P Unvouchered Report ApsApuv.rdl
A/R Aged Trail Balance ArsArtb.rdl
G/L Trial Balance/General Ledger GlsGltg.rdl
Value Added Tax Table SysVatt.rdl
Foundation Business Views Changes

The following changes have occurred within the Foundation Business Views:
The FS_HistoryPick and NoLock_FS_HistoryPick Foundation Business Views have been
updated to include the Employee ID field to aid in custom reports or data extract of this
information. Employee ID is also included in audit screen (AUDT), archive file, macro/transaction
layouts for import and FSTI (Fourth Shift Transactional Interface) and the Fourth Shift Report
Model. A new view has been added called FS_HistoryCostRollOver to display new CROV E
(Exchange) type AUDT (Audit) records.
- FS_COLineData – added COLineReference1, COLineReference2, and

COLineReference3.
- FS_DemandData – added COLineReference1, COLineReference2, and
COLineReference3.
- FS_HistoryCOLine – added COLineReference1, COLineReference2, and
COLineReference3.
- FS_HistoryCostRollOver (New View) – TransactionDate, TransactionTime,
TransactionFunctionCode, UserID, IsInventoryHistoryUpdated, CROVMethod,
ItemNumber, DebitAccount, CreditAccount, TransactionAmount, TotalInventoryQuantity,
CostTypeOld, CostTypeNew, CostCodeOld, CostCodeNew, AtThisLevelMaterialCostOld,
AtThisLevelLaborCostOld, AtThisLevelVariableOverheadCostOld,
AtThisLevelFixedOverheadCostOld, AtThisLevelMaterialCostNew,
AtThisLevelLaborCostNew, AtThisLevelVariableOverheadCostNew,
AtThisLevelFixedOverheadCostNew, RolledMaterialCostOld, RolledLaborCostOld
RolledVariableOverheadCostOld, RolledFixedOverheadCostOld,
RolledMaterialCostNew, RolledLaborCostNew, RolledVariableOverheadCostNew,
RolledFixedOverheadCostNew, InventoryAccount, SalesAccount,
CostOfGoodsSoldAccount, SetupCost, ItemLocalUnitPrice, CostFamily,
ForeignCostCode, VatProductCode, ProductLine, HistoryCostRollOverRowVersion,
HistoryCostRollOverKey
- FS_APInvoiceGLDistribution – TransactionReference11
- FS_APDisbursementGLDistribution – TransactionReference11
- FS_ARInvoiceGLDistribution – TransactionReference11
- FS_CashReceiptGLDistribution – TransactionReference11
- FS_ARInvoiceLineGLDistribution – TransactionReference11
- FS_GLBatchDetail – TransactionReference11
- FS_GLTemplateBatchDetail – TemplateTransactionReference11
- FS_GLRecurringBatchDetail – RecurringTransactionReference11
- FS_GLRecurringBatchHeaderData – IsRecurringBatchToBeReversed
- FS_GLTemplateBatchHeaderData – IsTemplateBatchToBeReversed
- FS_GLRecurringTemplateBatchDetail – RecurringTemplateTransactionReference11
- FS_GLRecurringTemplateBatchHeaderData-IsRecurringTemplateBatchToBeReversed
- FS_OrderEntryConfig – AllowMovementOfShippingInventory
The definition of the column TaxLocalAmount of FS_ARInvoiceHeader was updated.

The definition of the column TaxForeignAmount of FS_ARInvoiceHeader was updated.


Screen Changes
COMT (Order Entry) Standard Product 1. Display length for text fields #49, #50. #51, and #52
Detail screen (COS2) changed to 35 characters. There max length will
remain 60 characters.
2. Three new reference fields #54, #55, and #56 are
added. The display length of each reference field is
28 characters and their max length is 50 characters.
G/L Recurring/Template Trans Detail New field Reference #11 added

screen (GLR1),
G/L Transaction Detail screen (GLJ1) New field Reference #11 added
Order Entry Configuration screen (COCF) New field Allow Movement of Shipping Inventory (Y/N)
added
G/L Journal Entry-Recurring/Templates New field Reversal (Y/N) added

(GLJR)
New Batch Mode Generation of Outbound 855 CO Acknowledgements

Fourth Shift Release 8.00A Electronic Data Interchange module can now generate Outbound 855
Customer Order Acknowledgement transactions in batch mode. Any EDI Trading Partner
customer that is configured for Outbound 855’s and has an ACK (CO Acknowledgement)
message on the COAN (Customer Order Action Message) screen will generate an outbound
record when EXED is executed. Outbound 865 Customer Order Change Acknowledgement
transactions will be generated if changes to a customer order occur and an Outbound 855 CO
Acknowledgement previously had been generated.
New ALT- F4/GUI and WebUI Ctrl-B/Browsers

On Fourth Shift screens, there are some frequently used and important fields that have the GUI
Alt-F4/Browser and WebUI Ctrl-B/Browse feature. On GUI with the Alt-F4 key or
Tools->Browse/Detail, or on WebUI with the Ctrl-B key, a user can find and select a pre-defined
record to improve the operation efficiency.
Fourth Shift Release 8.00A will implement new features relating to GUI Alt-F4/Browser and
WebUI Ctrl-B/Browser. The enhanced browsing capabilities will be implemented on the
Commission Code, and National Motor Freight Code fields.
• The Commission Code browser is implemented in Order Entry on the Customer Master
Name/Address Detail, and the Order Entry header and Line Detail screens. In Custom
Products the Commission Code browser is implemented on the Custom Product Detail
screen.
• The National Motor Freight Code browser is implemented on Item Master Detail and
Shipping Bill of Lading screens.

Note: The new browsers are not implemented in the Sales Order Processing Module
New Audit Records for CROV E (Exchange) to Cost Type 0

Fourth Shift Release 8.00A implements the creation of new AUDT (Audit) records for the CROV E
(Exchange) batch task to Cost Type 0. The batch task of CROV E to cost type 0 will transfer the
item costs between cost type 0 and another parameter specified cost type. AUDT records will
always be added each time a CROV E task is run to Cost Type 0. This new feature should help
in the analysis of item cost transaction activity. The AUDT records will be similar to the audit
records for ITMC (Item Cost Maintenance).
New AUDT (Audit) records for CROV transactions will also be written when the CROV C (Copy)
or CROV R (Roll-over) from parameter that targets cost type 0. This would only be applicable if
Cost type 0 did not exist for all items in the system prior to this batch task execution.
New Reference Fields Added to COMT (Order Entry) Line Detail

Fourth Shift Release 8.00A adds three new user defined reference fields on the COMT (Order
Entry) Standard Product Detail screen. The COMT Standard Product Detail screen is used to
view and maintain detail information for a line item on a customer order. This new feature is
available for COMT Ln# Typ’s A, C, 1, 2, and 3.
Note: The new reference fields do not apply to Ln# Typ X for the Custom Products module.
New IMTR Moves of Shipping Inventory to another Shipping Location

Fourth Shift Release 8.00A adds a new feature to allow the movement of shipping inventory (IC =
S) from one shipping location to another shipping location. This is a configurable Yes or No
option in the COCF (Order Entry Configuration) screen.
• The shipping IMTR move To location must be a match to the CO/LN# associated with
the IMTR move From shipping location.
• The Shipping IMTR move To location can be an existing IC=S (shipping) location or a
new IC=S location.
• The IMTR movement of shipping inventory must move the entire allocated shipping
From inventory to the shipping To inventory location.
New ALT- F4/GUI and WebUI Ctrl-B/Browsers

On Fourth Shift screens, there are some frequently used and important fields that have the GUI
Alt-F4/Browser and WebUI Ctrl-B/Browser feature. On GUI with the Alt-F4 key or
Tools->Browse/Detail, or on WebUI with the Ctrl-B key, a user can find and select a pre-defined
record to improve the operation efficiency.
Fourth Shift Release 8.00A will implement new features relating to GUI Alt-F4/Browser and
WebUI Ctrl-B/Browser. The enhanced browsing capabilities will be implemented on Tax Codes,
Batch number, Invoice Number and Commission Code fields.
• The Tax Code browser popup is implemented on Federal, State, County and Municipal
tax code fields. A user can input a value as before, or press Alt-F4 to select from the tax
code table. This new browser is on the Accounts Receivable Invoice Header and the
Recurring Invoice Header Detail screens. The Tax Code browser popup also has been
implemented on the Customer Master Customer Name/Address Detail screen.

• The Tax Code browser popup is implemented on Fourth Shift Vat Systems. A user can
input a value as before, or press Alt-F4 on the Vat Code field to select tax code from the
Tax Code browser. This new Tax Code browser is on the Vendor Master Detail screen,
Vat Summary Code pop-up from the Accounts Payable Invoice Entry and A/P Invoice
Distribution screens.
• The Alt-F4 General Ledger batch number browser is available on the G/L Journal Entry
and G/L Journal Entry Inquiry screen, G/L Journal Entry Delete and General Ledger
Journal Entry-Prior Period Adjustment screens. The G/L batch number browser allows
you to sort by batch number, batch status, batch source code and G/L accounting period.
• The Commission Code browser is implemented in Accounts Receivable Invoice Entry
and Maintenance and the Recurring Invoice screens.
New APCR (A/P Check Reprint) Email Check Remittance Advice

Companies are moving to electronic output (ACH - Automated Clearing House). Fourth Shift
Release 8.00A has enhanced the Accounts Payable APCR check remittance advice report to
support all pay forms available and email this output as a batch process using (EDD Electronic
Document Distribution) standards. The remittance report now includes the following:
• APCR now supports reprinting remittance output of all pay forms. The five pay forms are:
o B = BOE (Bill of Exchange)
o C = Check
o D = Bank Draft
o G = GIRO/BACS (Bankers Automated Clearing System)
o T = Bank Transfer
• The Vendor payee address is now part of the APCR remittance report.
• New remittance report parameters now comply with the EDD (Electronic Document
Distribution) standards. The report can be generated based on ETPT (email template)
specifications. It can be generated to exclude external recipients.
• The remittance report will be split up by vendor so that the file can be directed to different
location depending on the preference defined in VROP for each vendor.
New G/L Transaction Reference Field and Flow Employee ID of PICK

Transactions to G/L
An additional G/L Transaction Reference Field has been added to several G/L Transaction
screens. Fourth Shift Release 8.00A further enhances a feature added at Fourth Shift Release
8.00 when the PICK and PICK Detail screens added a new Employee ID field. This 20-character
Employee ID field will now flow the Employee ID of the PICK transaction to a new G/L reference
field using modcom processing.
The new reference field 11 will update the following screens:
• GLJE (G/L Journal Entry) Transaction Detail

• GLJI (G/L Journal Entry Inquiry) Transaction Detail
• GLJD (G/L Journal Entry Delete) Transaction Detail
• GLJP (G/L Journal Entry-Prior Period Adjustment) Transaction Detail
• GLJR (G/L Journal Entry-Recurring/Templates) Transaction Detail
• GLJR (G/L Journal Entry-Recurring/Templates) has been modified to set the new
reference field on the G/L transactions when creating an actual G/L journal based upon
the recurring journal or template journal.

• GLSC (G/L Source Code Maintenance) has had the 11th reference field Employee ID
added in the G/L Trans description definition pop-up window for PICKC, PICKC1, PICKM,
and PICKP batch source codes.
• GLCO (G/L Consolidation Process) has been modified to set the new reference field of
the loaded consolidation transactions and the unloaded consolidation transaction file.
• GLHP (G/L History Process) has been modified to set the new reference field of the
loaded G/L transactions and the unloaded G/L transaction history file.
• GLPC (G/L Period Close) has been modified to set the new reference field on the G/L
transactions when creating an actual G/L journal based upon the recurring journal or
creating a retained earnings G/L journal entry.
• GLAU (G/L Account Update) has been modified to set the new reference field on the G/L
transactions when creating a new batch with reversing entries for a previously posted
batch whose Batch Reversal is Y.
New Data-Only Parameter Option for BEXE Reports

A new parameter option has been added for specified financial batch tasks to allow the
generation of summarized data-only reports. This data-only option will allow reports to be
generated without headers and summary information for easier exporting into Excel or other
Fourth Shift supported reporting format. If the new OMIT HEADERS parameter option is defined
on BSET, the report header, summary information of the group or reports are removed from the
report. The following financial reports will have this new feature.
• APTB (Accounts Payable Aged Trial Balance Report)

• APUV (Accounts Payable Unvouchered Report)
• ARTB (Accounts Receivable Aged Trial Balance Report)
• GLTG (General Ledger Trial Balance/General Ledger Report)
Fourth Shift 8.00 Release Notes
Fourth Shift Release 8.00 includes enhancements and improvements to your Fourth Shift system,
allowing your company to run more efficiently and effectively. These upgraded features are
provided for modules included in your Support Services agreement. This Release Notes
• README.txt file contains information about fixes in Fourth Shift Release 8.00.
• R800_Release_Instructions.pdf contains instructions to upgrade your system to Fourth
Shift 8.00.
IMPORTANT:
changes in Release 8.00 that will impact maintenance of the system. A thorough system test of


recommended before running Release 8.00 as your production system.
Release 8.00 Upgrade Requirements
You must have 7.50C or higher installed before upgrading to Fourth Shift Release 8.00.
This document includes information as of the date of publication. For current compatibility
information, refer to the Product Compatibility Guide available on http://www.inforxtreme.com.
Database Platforms
Fourth Shift 8.00 is compatible with Microsoft SQL Server 2012 Service Pack 3, Microsoft SQL
Server 2014 Service Pack 2, and Microsoft SQL Server 2016 Service Pack 1.
Operating Systems
Fourth Shift 8.00 supports Windows Server 2012 R2 and Windows Server 2016 for the Fourth
Shift Server, the SQL Server Database server, the Reporting Services server and the My Fourth
Shift Workplace server.
Fourth Shift 8.00 supports the following Fourth Shift client workstations.
• Windows 7, 32 bit and 64 bit
• Windows 8.1
• Windows 10
Fourth Shift 8.00 no longer supports the following platforms that were supported at Release 7.50.
• Windows XP
• Windows 8
• SQL Server 2005
Internet Explorer
Fourth Shift 8.00 requires Internet Explorer 11.
The following Internet Explorer versions are not supported at Release 8.00:

Microsoft Office 2016 Support

Fourth Shift customers can take advantage of Microsoft Office 2016 for Fourth Shift Release 8.00
as the supported Office platform. Fourth Shift uses the Office Access database to manage
external data, Office Excel sheet to perform data import and export on Fourth Shift screens and
reports, Office Word document to preview / print Rich Text Format (RTF) Fourth Shift reports,
Office Word and Excel to access different export formats of SQL Server Reporting Services
reports, and Office Outlook to manage emails.
Security
With this release, specific efforts have occurred to identify and remediate or mitigate potential
security risks or vulnerabilities in the Fourth Shift product. For those utilizing My Fourth Shift
Workplace, there are a few of areas that require specific consideration and potential action by
your IT organization. These are enumerated below. Specifics details on each can be found in
the My Fourth Shift Workplace section of the Release Instructions.
• The ExecuteSQL and ShowQueryInDataGrid Connectivity Toolkit built-in functions are

disabled by default, but can be enabled.
• The CustomField and SelectExternal Connectivity Toolkit built-in functions have disabled
the ability to pass SQL queries as parameters by default, but this capability can be
enabled.
• My Fourth Shift Workplace can be configured to be even more secure by disabling the
ability for a frame in a portal to reference a web site outside of the Workplace server.
This capability continues to be enabled by default.
Fourth Shift WebUI Enhancement

SSII (Stock Status by Item) and SSIL (Stock Status by Location) Web User Interface
Enhancement
SSII and SSIL now take advantage of the Infor grid control and offer the Fourth Shift user an
enhanced ability to display and filter inventory by items and locations. All the rows will be sent to
the client – not just one page at a time. This will use the same INFOR DataGrid, as has been
used by Finders. At the bottom of the grid, a footer shows how many rows of data are being
included in the results.
Grid columns are sizeable, movable, and can be sorted in ascending or descending sequence.
An option using the Setting icon allows the grid to return to the default layout, but the sort
sequence will be maintained until the user either refreshes the screen or changes to a different
sort sequence.
The columns also have a dropdown menu of the types of filters that can be applied to that type of
data and the value to be used. More than one filter can be applied to the grid rows. For example,
the Inventory Value column can be filtered using qualifiers such as Equals, Greater than, Less
than, etc.
The screens utilize keyboard activity of Arrows (Up/Down, Right/Left) and Tabs (Forward,
Backward), remembered fields, and links to other Fourth Shift functions.
The Settings icon also provides the ability to export the grid detail to an Excel spreadsheet.
This enhancement applies only to the web user interface; the traditional Fourth Shift user
interface is unchanged.
ConnectivityToolkit Enhancements
Connectivity Toolkit customizations that use the built-in ShowQueryInDataGrid function will now
perform significantly faster, as processing of the ADO record set has been optimized.

Date fields in the record set are now defined in the grid as dates rather than simple text. This
improves the display so that they are shown in yyyy/mm/dd format. It also means that filtering
these columns is enhanced and now will include a date picker in the filter value field.
DCOM Changes
The use of Microsoft’s Distributed Component Object Model (DCOM) has been reduced and
simplified with Fourth Shift Release 8.00. With the removal of the Windows-based FS Explorer
(see below), there is no longer an FSExplrX DCOM object, and the FSTIApp DCOM object has
also been removed from the Fourth Shift Transactional Interface (FSTI) Remoting Service.
The configuration of DCOM has been simplified and is now handled by the installation. The
Workplace installation process will prompt for the WebUI User Account and will automatically
apply this to the FSCreateObject and FSGUIApp DCOM objects.
Adobe Document Cloud Supported

Fourth Shift uses Adobe Acrobat and Adobe Reader to view and print Fourth Shift generated PDF
format reports. At Release 8.00, Adobe DC (Document Cloud) is now a supported Adobe
platform.
Batch Setup Parameter Validation Enhancement

The BSET screen parameter validation functionality has been enhanced to allow the use of
additional special characters in batch setup parameters. You may now enter certain special
characters in BSET parameters that could not be used prior to this release.
For example, an item range parameter will not accept item number 123”456 even though this is a
valid item number which can be created in the Item Master (ITMB) screen. To accommodate field
values with imbedded double quotes, you can now enter another double quote in front of an
imbedded double quote (two double quotes) as an indication that one of the double quotes is part
of the field’s value. The parameter validation parsing will not use it as a delimiter for the
parameter, but recognize it as part of the field’s value string.
Example Parameter: M F”123 “ abc” Parameter: M F”123 “” abc”

(WIPS) TXXXXXX TXXXXXX
Parsing result: Parsing result:
Error M
F123 “ abc
TXXXXXX
A few things of note:

Tilde (~) is never an allowed character, because it is the reserved separator character for Fourth
Shift transaction history records.
Comma (,) is an allowed character in a Fourth Shift field, such as an item number of ,123ABC.
But the combination of a double quote followed by a comma (“,) is not allowed because this
combination would create a conflict in archive and module communication transactions. For
example, parameters for WIPS task of F”,123 ABC” T”XXXXX would result in an error (“Field
cannot contain a quote followed by a comma”).
Fourth Shift Installation Enhancement

The Release 8.00 installation process has been updated to the latest version of InstallShield, and
the installation process has been optimized for easier deployment. Some of the enhanced
features of the Release 8.00 installation include the ability to:
• Install any future Fourth Shift major or ISR release directly on a clean system (no need to
perform a base version install and then upgrade to an ISR version).
• Repair a broken install at this release level.
• Maintain (Add/Remove) features within an installation at this release level.
• Cleanly un-install this release.

• Move to another server, picking up an existing FS.CFG through an upgrade-like process.
• Upgrade directly from 7.50C or higher.
• Reduce system-wide registration of components in the Global Assembly Cache (GAC)
and registry to allow for improved isolation of multiple instances and multiple products
using the same components.
• Perform an unattended installation using command-line parameters. This feature allows
installation without needing to interact with the installation user interface and is
particularly useful when the workstation installation needs to be performed on a large
number of workstations. For more details on how to run an unattended workstation
install, see the Fourth Shift 8.00 Release Instructions.
Fourth Shift Explorer Removal

The Windows-based FS Explorer has been removed at Release 8.00. FS Explorer no longer
appears on the GUI toolbar, the default toolbar, and the Customize Toolbar option.
Fourth Shift SQL Server Database Primary Keys

Fourth Shift 8.00 establishes a primary key for each table in the Fourth Shift database, which
enables the use of SQL Server capabilities such as Transactional Replication. While this project
does not specifically provide scripts or installation support for Transactional Replication, the
primary key on each table removes the roadblock that has limited the investigation and use of this
SQL Server feature by Fourth Shift customers.
Windows Authentication Enhancement

Windows Authentication is being introduced with the 8.00 release as an extension to the existing
Fourth Shift security model rather than a replacement. This approach provides the best
alternative for those who are content with the current model AND those who wish to take
advantage of Windows authentication. By extending the security model rather than replacing it,
whether utilizing Windows or Fourth Shift authentication, all of your existing Fourth Shift user
security permissions are retained and utilized.
The current model has been extended by optionally allowing a Windows account to be specified
for a Fourth Shift user ID, along with a choice of which type of authentication is desired for an
individual user. There are three options available.
• F=Fourth Shift Authentication (This is the default and all existing Fourth Shift User IDs
are set to this value as part of the upgrade process. It indicates that only the existing
Fourth Shift User ID and Password is required for login.)
• W=Windows Authentication (This indicates that a Windows account and password are
required for Fourth Shift login. Once the initial login has occurred, Fourth Shift security
will “take over” and screen/form access will be directed by the Access Code permissions
specified for the related Fourth Shift User ID.)
• A=Automatic login utilizing Windows Authentication (If the Windows account used to
login to the machine has been associated with a Fourth Shift User ID with this setting, the
login requirement will be bypassed when the user launches the Fourth Shift application.
Similar to the Windows Authentication (W) option above, at this point Fourth Shift
Security will “take over” and screen/form access will be dictated by the Access Code
permissions specified for the related Fourth Shift User ID. You can think of this method
as a form of single sign-on.)
Note: This does imply/require that a Windows account can be associated with one and only
one Fourth Shift User ID on the Password Maintenance (PASS) screen.
The PASS screen allows this choice to be made on a user-by-user basis. You are able to
set up a mix of Windows and Fourth Shift authenticated users.
Data Import Macro and FSTI Macro Changes

Your existing FSTI programs may need modification in order for them to function properly with
Fourth Shift 8.00. Please see the Appendix of this document for more information.
The following Data Import Macros have been updated in Release 8.00. Details about the macros
can be found in the “Data Import Macros and Data Dictionary” section of the online help.
APPD06 Change Disbursement Payee Field #26 Route field length

Detail changed to 50
APPD06 Change Disbursement Payee Field #27 Acct field length

APDS06 Change Disbursement Payee Field #26 Route field length

APDS06 Change Disbursement Payee Field #27 Acct field length

CIMT01 Customer Item Maintenance Fields #9 and #14 were reversed
CNFA03 Change Interface Account Field #37 Applied Var. Overhead

Number Configuration added
Field #27 changed to Applied
Fixed Overhead
GLCF00 Change G/L Configuration-Initial Field #25 Validate PO Exp added

Configuration Field #27 Validate Inv Adj added
GLCA03 Change G/L Account Attributes Field #22 Allow PO Exp added
Field #23 Allow Inv Adj added
PICK00 Add Component to Order- Field #37 Employee ID added

Dependent Bill
PICK01 Delete Component from Order- Field #37 Employee ID added

Dependent Bill
PICK02 Issue End Item; CP Order- Field #37 Employee ID added

Backflush Components
PICK04 Issue Component Field #37 Employee ID added
PICK05 Reverse Issue Component Field #37 Employee ID added
PICK08 Issue End Item Field #37 Employee ID added
PICK09 Reverse Issue Component Field #37 Employee ID added
PICK12 Issue Component Field #37 Employee ID added
PICK13 Reverse Issue Components Field #37 Employee ID added
PICK14 Issue End Item to Shipping Field #37 Employee ID added

Location; CP order (Backflush
Components)
PICK17 Reverse Issue End Item from Field #37 Employee ID added
Shipping Location; CP Order
(On Hand Qty > 0)
PICK18 Issue End Item to Shipping Field #37 Employee ID added

Location; C Order


Issue End Item to Shipping
Location; CP Order
Shipping Location
Shipping
PICK40 Attach Existing Text-End Items; Field #34 Employee ID added

CP Order (Backflush
Transactions)
Change Pick Detail End Item;
CP Order (Backflush
Transactions)
PICK41 Change Pick Detail-End Item; C Field #34 Employee ID added

Order Component = R and
Resource Component = 2 or 3
(Issue Transactions)
PICK42 Change Pick Detail-Component Field #34 Employee ID added

(first-level); CP Order-
Component Type = N, X or T
(Issue Transactions)

(first-level); CP Order-
Component = N, X or T (Issue
Transactions)

(first level); CP Order-
Component = V or W (Reverse
Issue Transactions)

(first-level); CP Order
Component Type = N, X or T
(Reverse Issue Transactions)
PICK47 Change Pick Detail Field #34 Employee ID added
PICK48 Change Pick Detail Field #34 Employee ID added
SOCI10 Enter Customer Item Inherits Customer Preferences

Preferences
SOPC13 Modify Customer Preferences Inherits Trade Class Preferences
VEID03 Change Vendor Master Detail Field #75 Route Num field length
changed to 50
Field #76 Bank Acct field length
changed to 50
Foundation Business Views Changes

The following changes have occurred within the Foundation Business Views:
- FS_GLAccountGroup – added columns IsGLAccountValidForPOLines and
IsGLAccountValidForInventoryAdjustments
- FS_GLConfig – added columns ValidatePOLineGLAccounts and
ValidateInventoryAdjustmentOffsetAccounts
- FS_HistoryPick – added column EmployeeID
- FS_ProductLine – added columns AppliedFixedOverheadAccount and

AppliedVariableOverheadAccount
- FS_UserAccessData – new table with columns Authentication, WindowsAccount,
UserAccessKey, UserAccessDataRowVersion, and UserAccessDataKey
Report Changes
All Report Definition Language (RDL) files have been updated for Fourth Shift 8.00, as the report
designer was upgraded to the latest version for SQL Server 2012. Customized 7.50 reports can
still work with 8.00 because SSRS RDL is backward compatible, but all customized reports
should be verified as part of your upgrade testing.
The Microsoft Excel 2007-2010 (XLSX) report export option is now supported. The limit of the
number of records that can be exported has increased from 65,536 to 1,048,576.
The HTML report export option was removed.
The following reports have been updated for defects and enhancements of the applications.
These changes may affect report customizations.
Report File Name

Customers Using Price Book ApbCupb.rdl
Price Book Master ApbPbmt.rdl
A/P Recurring Invoice ApsApre.rdl
A/P Invoice by Vendor ApsApiv.rdl
A/P Vendor Payment History ApsApph.rdl
A/P Check Printing/Export – UK Short Voucher, form ApsAcwuk2sf.rdl
A/P Check Printing/Export – Long Voucher, with Form ApsApcwus1l.rdl
A/P Check Printing/Export – Short Voucher, text ApsApcwus1sf.rdl
A/P Check Printing/Export – Canadian Long Voucher, text ApsApcwcn1l.rdl
A/R Aged Trial Balance ArsArtb.rdl
A/R Invoices/Credit memos: - with Form ArsIvprf.rdl
A/R Invoices/Credit memos ArsIvpr.rdl
A/R Invoices Inquiry ArsIvii.rdl
A/R Invoices/Credit memos: - with Form ArsIvprf.rdl
A/R Invoice Entry ArsIvie.rdl
A/R Recurring Invoice ArsIvre.rdl
Bank Cash Journal Summary Report CshBkcj.rdl
Customer Order Picklist CusPick.rdl
Production Bill of Material with Reference Designator Text EngPbll2.rdl
Bill of Material MmaPBLL1.rdl
Production Bill of Material with Reference Designators EngPbll1.rdl
Manufacturing Order Packing list OrdPack_M.rdl
G/L Report List GlsGlrl.rdl
Location Master InvLmmt.rdl
Exchange Rate Update IstIxru
Inventory Valuation Report MgrInvr.rdl
Master Schedule Maintenance MrpMsmt.rdl
Purchase Order S-line Cost PrcPcst.rdl
Manufacturing Order Cost Analysis PrcMcst.rdl
Distributors By Vendor PurDist.rdl
PO Receiving Document PurPord.rdl
Report File Name

Open Customer Order Detail SA_Ocod.rdl
Custom Product Cost Analysis SA_Cpca.rdl
CO Line Transaction Summary SA_Clts.rdl
Custom Product Component Summary SA_Cpcs.rdl
Location Index SfrLocn1.rdl
Bill of Lading ShpBol.rdl
Item History Audit SysAudt.rdl
Currency Code Maintenance SysCcmt.rdl
Password Maintenance SysPass.rdl

Screen Changes
Accounts Payable Payee Detail (APD1) Route field length changed to 50

Acct field length changed to 50
Accounts Payable Intrastat (API1) Extended Customs Price field, which now allows the “ – “
character to be entered
Password Maintenance (PASS) New fields Authentication and Windows account added
Master Account Number Detail (CNF1) Applied Overhead Field changed to Applied Var Ovhd
New field Applied Fixed Ovhd added
General Ledger Configuration (GLCF) New field Validate PO Exp added

New field Validate Inv Adj added
General Ledger Account Attributes GL2A) New field Allow PO Exp added
New field Allow Inv Adj added
Picklist (PICK) New field Employee Id added
Picklist Detail (PIC1) New field Employee Id added
Native 64-Bit Services

The following Fourth Shift services are built as native 64-bit for improved memory usage.
• MAINXX – used by manufacturing applications to communicate with SQL Server

• FINXX - used by financial applications to communicate with SQL Server
• Fourth Shift Lockserver
Cost Rollover Database Locking Changes

The Cost Rollover (CROV) batch task no longer requires an exclusive manufacturing database
lock when using CROV parameters Roll-over ( R ), Copy ( C ) and Delete ( D ). The batch task

still maintains an exclusive lock on the manufacturing database when the Exchange ( E )
parameter is used.
Employee ID Added to PICK Transactions

The PICK and PICK Detail screens have a new Employee ID field. The purpose of the new
feature is geared primarily towards the picking of “resources”. This enables you to track
specifically who is performing labor activities by requiring them, through process or a WebUI
customization, to specify an employee ID on a transaction. This 20-character field is an
informational field only, and there are no other limitations to field input.
The FS_HistoryPick and NoLock_FS_HistoryPick Foundation Business Views have been
updated to include the Employee ID field to aid in custom reports or data extract of this
information. Employee ID is also included in audit screen (AUDT), archive file, macro/transaction
layouts for import and FSTI (Fourth Shift Transactional Interface) and the Fourth Shift Report
Model.
Inventory Valuation Report Enhancement

The Inventory Valuation Report (INVR) provides a method of reporting inventory as it relates to
G/L accounts, value, and inventory categories. Two new report filters have been added to the
parameter options. The INVR report can now be generated with a parameter (U) that excludes
items that have no inventory. INVR can also be generated based on the item’s specific item
status of Engineering (E), Active (A), Phased Out (P) or Obsolete (O) using the new (S)
parameter.
Both parameters are optional and can be used alone or in conjunction with other INVR
parameters.
Sales Order Processing Archive Transactions Enhancement

The Sales Order Processing (SOP) module now supports import and archive file layouts for a
number of additional transactions which can be used by either SOP Import or by SOP
Transactional Interface (SOPTI).
New SOP Archive transactions
Macro ID Action
SOPG00 Add Group
SOPG01 Update Group
SOPG02 Delete Group
SOPU00 Add User
SOPU01 Update User
SOPU02 Delete User
SOPU03 Add user to Group
SOPU04 Delete User From Group
SOPT00 Add Trade Class
SOPT01 Modify Trade Class
SOPT02 Delete Trade Class
SOPC14 Customer Move
SOPI00 Update Item Alternate Units of Measure
SOPI01 Update Item Alternate Description
SOPB00 Add Shipping Allocation Batch
SOPB01 Update Shipping Allocation Batch
SOPB02 Delete Shipping Allocation Batch

SOPB03 Insert Shipping Allocation to Batch
SOPB04 Delete Shipping Allocation from Batch
SOPP00 Add Order Number Prefix
SOPP01 Update Order Number Prefix Setting

Macro ID Action
SOPP02 Delete Order Number Prefix
Lot Trace History Reload Function Removal

The Lot Trace History Reload (LHRL) functionality was designed for customers of Fourth Shift to
reload Lot Trace History dBase data after converting to Release 7.40. At Release 8.00 LHRL is
no longer needed and has been removed from the LOTM (Lot Trace /Serialization Module).
OVAR Retention of Additional Closed Order Variance Fields

Fourth Shift release 7.50D contained an enhancement which retained point-in-time standard
cost information for an order when the order was closed (Status=‘6’) by OVAR and also
changed the MCST and PCST (Manufacturing and Purchase Order Cost Analysis) screens
to display this cost information rather than the current standard cost. This information is now
stored in the Fourth Shift database in the FS_ClosedDemandSupplyCost table.
This enhancement expands on that starting point by also retaining the issued costs with
breakout (material, labor and overhead) for the order’s components. These fields have not
been added to any screens, but rather are just permanently persisted in the
FS_ClosedDemandSupply table to retain this information for more comprehensive future
variance analysis and queries. In addition, yield percentage of the parent item is also now
persisted in the FS_ClosedOrderLineVariance table at this same point and for similar
reasons.
This applies to manufacturing orders and S-type purchase orders, similar to the 7.50D
enhancement.
New Accounts Payable Aged Trial Balance Report Sort Options

The Accounts Payable Aged Trial Balance (APTB) task prints an aged trial balance of accounts
payable excluding available discounts for a minimum A/P balance within a selected vendor range
up to a specified invoice date. APTB breaks down the total accounts payable into current, past or
future aging categories and shows on hold and unapplied balances for each vendor. Parameters
specified for the APTB task are for reporting purposes only.
Additional sort options have been added to allow sorting/grouping by certain vendor master
properties including:
• Vendor Name
• Vendor Currency Code (report uses 00000 to signify local currency code)
• Vendor Payment Form
• Vendor Classes
These new sort options are mutually exclusive, only one of them can be used at one time. If
specified, the newly added sort option will be the highest sort and the original sort level, Vendor
ID, will be the secondary sort. For example, if Vendor Class is specified, the report will be sorted
by Vendor Class with individual vendors listed by Vendor ID within each Vendor Class. Lower
level sorting did not change.
When sort option Vendor Currency Code, Vendor Class, or Vendor Payment Form is specified,
the content of the report will be sorted by this field with a summary of the aging data in local
currency at the end of each unique sort value (for example, all vendors with a Vendor Class of
“1”). A page break will also occur at the end of each of these groupings. When sort option Vendor
Name is specified, the summarization will not occur by Vendor Name, but instead the report will
simply be sorted by Vendor Name, and a summary will occur for each Vendor ID, since Vendor
Name is not guaranteed to be unique and could possibly result in combining unrelated vendor
information. This is handled similarly in the Accounts Receivable Trial Balance (ARTB) for the
Customer Name sort option.

You may also specify Optional Selection Criteria for the Vendor Currency Code, Vendor Class,
and Vendor Payment Form sort options. When the Optional Selection Criteria is specified, the
report will only include those records which meet the criteria. For example, if you specify Vendor
Class as the sort option and provide selection criteria of “1”, only vendors with a Vendor Class of
“1” will be included in the report.
Future Aging Category Added to the Accounts Receivable Trial Balance

Report
The ARTB (A/R Aged Trial Balance) task prints an aged trial balance of accounts receivable
for a minimum A/R balance within a selected customer range, up to a specified cutoff date.
With this enhancement, the A/R Aged Trial Balance will now identify the total, current, past or
future aging categories, unapproved/on hold and unapplied balances for each customer.
A new Past or Future parameter specifies whether aged balances should be calculated for
past (P) or future (U) due aging categories. Multiple ARTB tasks can be set up if you wish to
see the report based on both aging categories. Parameters specified for the ARTB task are
for reporting purposes only.
Future Due Amounts identify the amounts owed on a customer account based on the original
amounts, payment amounts, discount amounts, and the payment due date. Future Due
Amounts are used for cash planning purposes and are grouped into aging categories.
If a past or future aging option is not specified, ARTB will default to “past”. This allows the
ARTB batch tasks that existed in your system prior to the 8.00 upgrade to continue to work
as before.
Bank Routing and Account Number Fields Expand to 50 Characters

The VEID (Vendor Master Detail) bank routing number and bank account number fields have
been expanded from 30 to 50 characters. This change was made to accommodate electronic
banking format changes that are exceeding the current limitation of 30 characters. This change
also flows to the Accounts Payable Payee Detail screen from A/P Disbursements (APDS), A/P
Prior Period Disbursements (APPD), A/P Manual Payment Application (APPA), and A/P Payment
Void (APCV) for disbursements, payments, and payment history.
CNFA Separate Accounts for Applied Overhead

The Configuration of Interface Account Numbers (CNFA) screen is where you designate by
product line which accounts should be used when transactions are passed from manufacturing to
general ledger. The default accounts listed provide the offsetting debit/credit entries needed when
transactions are posted to the general ledger.
Fourth Shift already did support separating fixed overhead cost and variable overhead cost for an
item, but it ultimately posted both values to the same Applied Overhead account in the general
ledger (by product line). This enhancement allows you to provide separate accounts if you wish to
track these overhead categories separately in your general ledger. The Applied Overhead
account field on CNFA has been replaced by two account fields: Applied Fixed Overhead and
Applied Variable Overhead.
With the release 8.00 installation, both of these field values are populated with the account
number that was previously specified for the single Applied Overhead account (for each product
line). Therefore Fourth Shift 8.00’s “out-of-the-box” behavior is identical to prior behavior. If you
wish to separate these values into different accounts for subsequent material receipts, you can
modify these values accordingly.
G/L Journal Entry-Recurring/Templates Enhancement

GLJR (G/L Journal Entry-Recurring/Templates) is used to create and maintain recurring and
template journal entries for future use on the GLJE (G/L Journal Entry) screen. Recurring
journal entries can be transferred initially using the GLJR screen and are subsequently
generated automatically by the GLPC (G/L Period Close) task processes. Template journal
entries can contain partial transactions and can be used numerous times during an
accounting period.
Prior to this release, GLJR allowed changing most of the information on a recurring journal
entry before any active batches are created based upon it. If an active batch was created
based upon a recurring journal entry, no information other than Journal Entry Status and
Cycles fields on the recurring journal entry could be changed.
With this release, more changes are allowed, regardless of whether active batches have
been generated, and any changes made only affect future journal entries. The following
changes are now supported:
• Updates to Journal Entry Status, Description, Cycles, and Default Master Account
Number.
• Addition of new lines.
• Deletion of existing lines, with one exception. You may not delete the last line from a
recurring journal. (With no lines, this recurring journal would otherwise become useless,
since GLPC ignores recurring journals which have no lines.)
• Updates to existing lines, including Master Account Number, Transaction Description,
Debit Amount, and Credit Amount fields on the line and ten Reference fields on the line
detail screen.
Validation occurs on each of these updates, similar to when creating a new recurring journal.
All business rules are checked, and errors must be corrected before updates are processed.
In addition, GLPC continues to verify if a recurring journal entry is in balance when it
generates the first general ledger journal entry based on this recurring journal entry. If it is
not in balance, GLPC fails and provides error messages in its log and exception report.
General Ledger Account Validation for (G-Type) Purchase Orders and

Inventory Adjustments
The Inventory Adjustment (INVA) and Expense-Type Purchase Order (POMT with Order Line
Type of “G”) screens require the end user to enter an account number to be used for one side of
its related general ledger journal entries. In prior releases, Fourth Shift would accept any valid
master account number, no matter how illogical it might be from a finance perspective (for
example, perhaps the end user provides a cash account or tax account). This enhancement gives
you the option to control which account types may be specified for these two types of
transactions.
Two system-level configuration options have been added to the General Ledger Configuration
(GLCF) screen, which allow you to indicate whether stricter control is desired for either of these
transactions. The options are set to N (No) by default, so Fourth Shift 8.00’s “out-of-the-box”
behavior is identical to the prior behavior described above.
If you choose the option of stricter control, you must also indicate which account types (the
AAAAA portion of the account segment) are allowed for each. The account segment indicates the
type of account, while other segments represent levels (such as organization, department, etc.),
thus only requiring it to be indicated once, regardless of the number of organizations,
departments, etc. that may exist in your environment.
This is indicated on the General Ledger Chart of Accounts (GLCA) screen, Account Attributes
pop-up (GL2A). Once again, these options are set to N (No) by default and can be configured in
conjunction with the system-level settings described above.
These settings also control which accounts are displayed in G/L Account browse for the general
ledger account number fields on both the INVA and POMT (Order Line Type G) screens.
Two new filter options "Allow PO Expense" and "Allow Inventory Adjustment" have been added to
the GL Master Account Finder of My Fourth Shift Workplace web user interface to filter the G/L
master account data. But, similar to before, only those G/L master accounts that have already
been used on a transaction are listed in this finder. Initial use of a G/L master account still
requires manual entry as before, regardless of these new options.
An error message is displayed and the transaction is stopped if the account entered is not one of
the allowed account types specified on GLCA.

Companion Applications
The following products and versions are required for compatibility with Fourth Shift 8.00, but are
not included with the Fourth Shift 8.00 installation image. Additional geographic specific modules
will also be tested for compatibility as country/language releases are made available. Information
about other Infor products related to Fourth Shift is available in the Product Compatibility Guide
available on http://www.inforxtreme.com.
Document Management System (DMS) 2.3
Intelligent Night Automated Processing (INAP) 7.50.3

An additional hot fix available from Fourth Shift Support Services via KB 1879029, is
required as an update to the INAP server in order to work with Fourth Shift 8.00.
Ledgersoft 5.00.01
VisiBar 5.5D
The FSIntegrate utility, available from Fourth Shift Support Services via KB 1879013, is
required to configure VisiBar 5.5D for use with Fourth Shift 8.00.
VisiWatch 2.6.2
required to configure VisiWatch 2.6.2 for use with Fourth Shift 8.00.
China Local Modules
Fixed Assets (FAMM) 2.5
Chinese Financial Report (FRPM) 2.20
INAP Lite 3.3

required to configure INAP Lite 3.3 for use with Fourth Shift 8.00.
VATIP 1.4D
An additional hot fix available from Fourth Shift Support Services via KB 1903652, is
required as an update to VATIP 1.4D in order to work with Fourth Shift 8.00.

Appendix: How to Make Existing FSTI Programs

Work With Fourth Shift Release 8.00
Your existing Fourth Shift Transactional Interface (FSTI) programs may need modification in
order for them to function properly with Fourth Shift 8.00.
How to Make .NET FSTI Programs Work

For .NET code programs built to use FSTI from an older release, if you need to use FSTI after
upgrading to 8.00, but do not have the code to rebuild the program, the solution is to use a
configuration file.
For example, assume you have an old .NET FSTI program named FSScriptPlayer.exe, which
references FSTI assemblies from version 7.5.0.63. To make this work on 8.00 (assuming the
version of 8.00 FSTI assemblies installed is 8.0.0.123), you would add a configuration file named
FSScriptPlayer.exe.config.
The content of this configuration file would look similar to this:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="FourthShift.SDKLibrary"
publicKeyToken="541b4aff0f04b60a"
culture="neutral" />
<codeBase version="8.0.0.123"
href="file://m:\mfgsys\system\FourthShift.SDKLibrary.dll"/>
<bindingRedirect oldVersion="7.0.0.0-8.0.0.999"
newVersion="8.0.0.123"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="FourthShift.TransactionClient"
href="file://m:\mfgsys\system\FourthShift.TransactionClient.dll"/>
<bindingRedirect oldVersion="7.0.0.0 - 8.0.0.999"
<dependentAssembly>
<assemblyIdentity name="FourthShift.Transactions"
href="file://m:\mfgsys\system\FourthShift.Transactions.dll"/>
<bindingRedirect oldVersion="7.0.0.0 - 8.0.0.999"
<dependentAssembly>
<assemblyIdentity name="FourthShift.TransactionProxy"
href="file://m:\mfgsys\system\FourthShift.TransactionProxy.dll"/>
<bindingRedirect oldVersion="7.0.0.0-8.0.0.999"
</assemblyBinding>
</runtime>
</configuration>
Note:
1. <codeBase> is used to locate the FSTI assembly. The value of <href> should reference the
actual path to installed FSTI components. If FSScriptPlayer.exe is in the same directory as
the FSTI components, the <codeBase> element is not necessary.
2. The version and newVersion attributes should reflect the version of the installed release.
For .NET code programs built to use FSTI from an older release, if you need to use FSTI after
upgrading to 8.00, but you do have code to rebuild the program, you can either use the
configuration file without rebuilding the program, or you can open the project and change the Path
of the references to refer to the installed version of the FSTI files (for example,
M:\MfgSys\System\FourthShift.SDKLibrary.dll, where M: is the mapped drive for your Fourth Shift
system) and then rebuild.
Make sure FSTI assemblies (FourthShift.SDKLibrary.dll, FourthShift.TransactionClient.dll,
FourthShift.Transactions.dll, and FourthShift.TransactionProxy.dll) are in the same folder as the
program you built.
For an ASP.NET program, you’ll need to copy FourthShift.SDKLibrary.dll,
FourthShift.TransactionClient.dll, FourthShift.Transactions.dll, and
FourthShift.TransactionProxy.dll files from M:\MfgSys\System to the bin directory of the website.
How to Make Unmanaged FSTI Programs Work

For programs built to use FSTI via a COM interface from an older release, a manifest file is
required (for VB6 or VC++ programs).
For example, assume you have an old program named FSTIInsertItemSample.exe. A manifest
file named FSTIInsertItemSample.exe.manifest is required. Add the below content to the manifest
file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="Softbrands.FourthShift.FSTIInsertItemSample"
type="win32"
/>
<description>FSTIInsertItemSample manifest file</description>
<dependency>
<dependentAssembly>
<assemblyIdentity name="FourthShift.TransactionClient" version="8.00.0.123"
publicKeyToken="541b4aff0f04b60a" processorArchitecture="x86"></assemblyIdentity>
</dependency>
</assembly>
For VC++ programs that use the FSTI COM interface, if you have the code to rebuild the
program, you can embed the manifest file.
To embed the manifest file using Visual Studio, you should add the manifest file to the C++
project and rebuild.
In the cases below, you’ll have to register FSTI assemblies file in the Global Assembly Cache
(GAC) and also register the assembly for COM interop:
1. For VC++ programs that use the FSTI COM interface and have an embedded
manifest file, but you don’t have the code to rebuild the program.
2. Classic ASP applications.
Here is how to complete the necessary registrations.
Register FourthShift.TransactionClient.dll in the GAC by dragging it from M:\MfgSys\System and
dropping it to C:\Windows\Assembly.

This step is necessary when VC++ or VB6 FSTI client applications are not in the same folder as
FSTI assembly files. To avoid the need to register files in the GAC, you can either put client
applications in m:\mfgsys\system, where FSTI assembly files are located, or you can copy FSTI
assembly files to the client application’s folder.
Keeping the client application and FSTI assembly files in the same location can avoid the need to
register assemblies in the GAC.
Register FSTIClient COM class:
1. Open as Administrator a Command Prompt window.
2. Change to the m:\mfgsys\system directory.
3. Run C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm
FourthShift.TransactionClient.dll
FourthShift.Transactions.dll provides transaction objects. If your old programs use CDF strings
directly instead of using transaction objects, the COM interface of this assembly does not need to
be registered (the regasm step is unnecessary for FourthShift.Transactions.dll only in this case).
But if your old programs do use transaction objects, you must also register the transaction
classes for COM interop.
The steps to perform this registration are:
1. Open as Administrator a Command Prompt window.
2. Change to m:\mfgsys\system directory.
3. Run C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm
FourthShift.Transactions.dll
Note: If you are running the FSTI application on a workstation which is different from the Fourth
Shift server, add M:\Mfgsys\System (where M: is the mapped drive for your Fourth Shift system)
to the PATH environment variable on that machine. Restart the machine to apply the changes,
and then execute the FSTI application.

R800D Release Notes

Uploaded by

Copyright:

Available Formats

R800D Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R800D Release Notes

Uploaded by

Copyright:

Available Formats

Fourth Shift

Interim Service Release 8.00D

Fourth Shift Release Notes

© 2023, INFOR. Page 2

Fourth Shift 8.00C Release Notes ....................................................................................................... 14

Fourth Shift 8.00B Release Notes ....................................................................................................... 19

Fourth Shift 8.00A Release Notes ....................................................................................................... 21

ConnectivityToolkit Enhancements ................................................................................................ 23

Fourth Shift 8.00 Release Notes .......................................................................................................... 30

© 2023, INFOR. Page 4

© 2023, INFOR. Page 5

Fourth Shift 8.00D Release Notes

Release 8.00D Upgrade Requirements

© 2023, INFOR. Page 6

System-wide Modifications in This Release

Screen Changes That May Affect Customizations

System Installation setup (CNFG) Added Reason Code Control

INRC – Reason Code Definition New master screen added

Product Line Reason Code (CNFA New master screen added

 Fourth Shift F3 HTML Help for Workplace and FS GUI

 Report Model (SMDL) Removal

 Planning Rebuild Tool (Auto Trigger Precaution Job/Scheduler)

 FS Database Objects Check Tool

 Logging Master Record Modifications

CNFG Audit logging for changes done to Reason Code

© 2023, INFOR. Page 8

 FS Report Server Configuration Update Through Backup Manager

 Windows Server 2022 Support

 Windows 11 Client Support

 Database Schema and Scripts Changes

© 2023, INFOR. Page 9

Name Change Details

ReasonCodeUsed Bit The reason code can be

Active bit Set the reason code

FS_HistoryInventoryAdjustm View The length of the column ChangingBalanceReasonCode to

usp_InsertInventoryAdjustme Stored Creating new INRC reason code.

usp_UpdateInventoryAdjustm Stored Updating an existing INRC reason code.

usp_DeleteInventoryAdjustm Stored Deleting an existing INRC reason code.

© 2023, INFOR. Page 10

usp_GetInventoryAdjustment Stored Retrieving an existing INRC reason code.

usp_InsertProductLineReaso Stored Creating new Product line reason code.

usp_UpdateProductLineReas Stored Updating an existing Product line reason code.

usp_DeleteProductLineReas Stored Deleting an existing Product line reason code.

usp_GetProductLineReason Stored Retrieving an existing Product line reason code.

SAAM table changes Update SA_tbl.sql: Size increased from 1 to 2 char as

Mfg.sql: Size increased from 1 to 2 char.

FSDictionary Document Details about new tables and columns

© 2023, INFOR. Page 11

System Control Module Modifications in this Release

 New CNFG Configuration Parameter: Reason Code Control

 PASS Screen: Added a Confirm Action Ctrl+Enter

 New Transport/shortcut Key for Product Line Reason Code Screen is

Manufacturing Module Modifications in this Release

 New Master INRC Screen to Pre-define System Wide Reason Codes

 Using Pre-Defined Reason Codes in INVA Screen

© 2023, INFOR. Page 13

Fourth Shift 8.00C Release Notes

Release 8.00C Upgrade Requirements

• Windows Server 2003