SYSPRO 8 2024 Update Guide

In response to evolving security challenges and the need for improved performance, we have upgraded the SYSPRO Reporting Services architecture for SAP Crystal Reports 2020. This update includes Service Pack 4 (SP4) for server-side and Service Pack 35 (SP35) for client-side, and it is available for SYSPRO 8 2023 onwards.

This upgrade is a big step forward in boosting the security and efficiency of your reporting environment. Our main focus with this upgrade is to address critical vulnerabilities related to the Log4j component and to modernize the underlying Java infrastructure. By implementing these changes, we are ensuring that your reporting tools are not only more secure, but also align with current technological standards.

The key benefits of this upgrade include:

• Enhanced Security: The upgrade mitigates vulnerabilities linked to the Log4j component, a widely reported security concern. By rebuilding the server and client service packs, we have strengthened our defenses against potential threats, providing a safer environment for your data.

• Modernized Java Infrastructure: The update removes dependencies on outdated Java versions. Specifically, it replaces the old JAVA 66 (JRE) with a more current version, eliminating obsolete technology and reducing the risks associated with older software.

• Improved Compliance and Licensing: By including an updated Java Development Kit (JDK), this upgrade addresses licensing issues and ensures compliance with the latest industry standards. This change simplifies the installation process and resolves concerns related to old technology vulnerabilities.

With this upgrade, SYSPRO continues to put security and operational efficiency at the forefront of your reporting capabilities. By addressing these critical areas, we aim to provide you with robust, reliable tools that enhance your overall experience and protect your data.

View the following article for details on the processes to follow when updating your reporting software:

Read more...

Before commencing with an update to the latest release:

• Ensure to check the sizes of your transaction log directories and shrink the transaction logs if required.
  This will ensure that you have enough disk space available for the database updates when they occur.

• Ensure to uninstall any Diagnostic Hotfixes before attempting to update your release of SYSPRO 8.

• As time progresses, certain products may become retired as they are replaced by newer capabilities. Therefore, if you have an installed product that has been retired in the latest release, the application will prompt you to uninstall the retired product before proceeding with the update.

  Once you have successfully uninstalled the retired product, you can proceed with updating to the latest release.

1. Run the SYSPRO Installer Application on the SYSPRO Application server.

2. Once connected to the SYSPRO Deployment Service, enter your InfoZone login credentials (and customer code if applicable). Ensure that you use the correct credentials as subsequent notifications rely on this information.

3. From the home screen select the SYSPRO ERP Software option.

4. Identify the deployment group you want to update and select the Update button. This creates a text file (SYSPRO_Deployment_Release_Update.txt) in the SYSPRO Deployment Downloads folder, providing details about the machines belonging to the group, as well as the software installed on each of those machines. Software updates must be applied to all machines in a group to complete the process otherwise the deployment group remains listed as Update in progress.

5. Select SYSPRO 8 2024 as the release to update.

   • If the SYSPRO 8 Reporting Host Service is installed, the app verifies if any version of the SYSPRO Reporting Software is also installed and if its supported by the selected release.

     A system message is displayed if the app detects an installed version of SYSPRO Reporting Software that is not supported by the selected release (or if its unable to detect the current version).

     Select the Reporting Software option to access the Reporting Software screen, from where you can uninstall your current Reporting Software and install the correct version as required.

     Once you have ensured that you have the correct version of Reporting Software installed, enable the Reporting software updated, continue Release Update option within this message box and select the Continue function to proceed with the release update.

6. From the Product Updates available for Release screen, select the products you want to update for the new release, followed by the Continue option.

7. After accepting the license terms and conditions, a summary of all products to be installed is displayed.

8. Select Begin Install to proceed with the installation of all selected products.

9. Update any additional servers in your deployment group that require an update (listed as update in progress).

10. Log in to SYSPRO 8 as an Administrator. A minor database update is performed to your system-wide tables and to each company-specific table.

    • The duration of the minor database update depends on the number of records in the latest database.

    • This database update applies to all companies listed within the SysproAdmin table (i.e. not just the company selected for your login).

    • You will be able to see the version of SYSPRO that you are using in the bottom left of the main menu.

You are now ready to start using SYSPRO 8 2024.

We've introduced the ability to flag instances and companies as either production or non-production within SYSPRO.

This enhancement enhances visibility of instance and company types and supports the licensing of non-production instances for sandbox environments.

Additionally, the SYSPRO Production and Non-Production Instance Level and Company Level Flags improve audit controls, ensure adherence to end-user license agreements (EULA), and provide resistance control for production-use instances and companies.

Change Details

The company name will be parsed to determine whether to set the production or non-production flag against it when the related license is imported.

A license often contains two company names:

• one named using the licensed business’ name

• one using TEST FOR, TEST CO or TEST COMPANY (depending on the territory’s conventions).

The company is therefore determined to be a non-production company when TEST is used in the company name within the license.

Affected Programs

The production/non-production flag will be visible within the following programs:

• Company Setup

• Company Maintenance

• About SYSPRO

SYSPRO has introduced eNet Runtime Operator Linked Licensing to enhance posting auditability, integration control, and prevent misuse.

This architectural change ensures that third-party software providers post as SYSPRO operators flagged for runtime posting. The key benefits of this feature include:

• Full Traceability:

  Enforces traceability by operator code, ensuring that specific operator codes are used for all e.net access, including setup, maintenance transactions, and queries.

• Simplified Configuration:

  Eases configuration between third-party software provider products and SYSPRO, as the operator code does not require checking the operator password. Additionally, operator password rules, including expiry, can be disregarded.

Change Details

Third-party software providers are required to request tokens which allow them to access specific functional areas within SYSPRO for performing queries and posting transactions.

Configuration

1. A new Linked operators option can be set for various Run Time Products when e.net Run Time Licenses are issued.

2. Once a license is imported, the Linked operators option can be enabled against each company.

3. Operators can then be flagged for runtime posting by enabling the Run time integration option in the Operator Maintenance program.

   Enabling this option will prevent concurrent and/or guest-type logins.

Trade promotion control records within the SYSPRO database architecture have been redesigned for greater scalability. This addresses the need to cater for the locking and, by extension, queuing of processes of the current control tables while a process retrieves and uses the next keys held in these tables.

Change Details

The following changes have been made in SYSPRO 8 2024:

• The next Trade Promotion Journal column is now defined on the ArNextKeys table with a KeyType of TPMJNL.

• The ArNextKeyAudit table can be used to assist with the auditing process by:

  • Tracing the next numbers allocated by operator and program name

  • Indicating the current posting period, the new key that was issued and the date and time of the transaction.

  • Identifying the transaction status C - completed indicates that the transaction was posted successfully, whereas a status of O - Open indicates missing journal or next numbers.

  • Explaining missing transaction numbers in the transactional tables.

Accounts Payable control records within the SYSPRO database architecture have been redesigned for greater scalability. This addresses the need to cater for the locking and, by extension, queuing of processes of the current control tables while a process retrieves and uses the next keys held in these tables.

Change Details

The following changes have been made in SYSPRO 8 2024:

• The next key columns have been removed from the ApControl table and are now defined on the new ApNextKeys table.

• The ApNextKeyAudit table can be used to assist with the auditing process by:

  • Tracing the next numbers allocated by operator and program name.

  • Indicating the current posting period, the new key that was issued and the date and time of the transaction.

  • Identifying the transaction status (C - completed indicates that the transaction was posted successfully, whereas a status of O - Open indicates missing journal or next numbers.

  • Explaining missing transaction numbers in the transactional tables.

• In addition, the Lowest Unprocessed Journal numbers (used for locating unprinted journals and unposted GL integration records) have been removed from these control records. These were originally introduced to speed up the processing time in C-ISAM environments and have no value in SQL.

  Using the capabilities in SQL enables SYSPRO to locate unprinted journals and unposted GL integration records quickly and easily, making the Reset lowest unprocessed journal functionality in the AP Period End program redundant.

To allow for increased flexibility when naming custom data objects and fields, as well as alias names within Business Activity Queries, the character limit has been increased to allow for 30-character names.

The SYSPRO Data Dictionary has been enhanced to support custom data. The new Merge User Defined Objects into Data Dictionary utility allows you to include custom data objects (i.e., forms, tables, columns and indexes) and register them in the SYSPRO Data Dictionary.

These new data dictionary definitions are supported by the Business Activity Query (BAQ) builder, which now also caters for longer custom object names and aliases (up to 30 characters).

In addition, the Data Model feature offers the following:

• All custom forms and user object definitions are included in newly created company databases, thereby keeping them in sync across companies and simplifying the company creation process.

• All generic data capabilities or business objects have equal access to both standard SYSPRO data and custom data.

Read more...

This topic outlines the programs and business objects that have been added or deleted for each release of SYSPRO 8.

Read more...

This topic outlines the table changes that have been made for each release of SYSPRO 8.

Read more...