The SYSPRO 8 Readiness Check is a diagnostic program that you run on your SYSPRO 7 Update 1 SQL database(s) to identify any issues that may cause the conversion process to fail. It verifies your system environment and company databases to ensure that the conversion to SYSPRO 8 is as simple as possible.
![[Note]](images/note.png)
|
|
|
Please ensure that you are on port 36 to ensure that you have all of the latest enhancements to this program. |
|
If you are currently running SYSPRO 7 Update 1 (ISAM), you can (on a separate environment) migrate your data to SYSPRO 7 Update 1 (SQL) and then run the SYSPRO 8 Readiness Check.
|
|
|
|
You cannot run this program from an ISAM company. All companies must be converted to SQL before they can be converted to SYSPRO 8. |
|
The SYSPRO 8 Readiness Check displays a row of information regarding your system-wide database. In addition, an additional row is shown; one for each company. This is determined by reading the company control files (ADMCTL) in the WORK folder.
Each entry is initially shown with a white flag icon to indicate that it has not yet been validated. You can select multiple entries and then run the validation on these entities.
The SYSPRO 8 Readiness Check then performs a number of system and company validation checks.
|
|
|
|
Ensure that the auto close option is not enabled for any SYSPRO database as this can cause problems when trying to bulk insert or process cross-database updates. |
|
| System check | Description | Importance | ||||
|---|---|---|---|---|---|---|
| SQL version | The SYSPRO 8 Readiness Check verifies your current version of SQL.
SYSPRO 8 supports SQL versions from 2008 R2 onwards.
|
Critical
Requires addressing prior to conversion |
||||
| Crystal version | The SYSPRO 8 Readiness Check verifies the System Setup program
(Reporting tab) to determine if Crystal 2013 is
selected.
|
Warning
Requires addressing prior to conversion |
||||
| Microsoft Office Components | The SYSPRO 8 Readiness Check doesn't check these components, but will display
the following message: Office components (Excel, Word and Outlook) SOI only supports versions from Microsoft Office 2010 onwards |
Information only
Any operators required to make use of Microsoft Office components integrated with SYSPRO 8 will need to upgrade their Office suite. |
||||
| Client Server Communications | If you are using CCI as your
method of communication between client server, the following error
is displayed: SYSPRO CCI Service Not Supported in SYSPRO 8 |
Warning
This means that when you install SYSPRO 8, you must use the SYSPRO client-server communications service, as CCI is no longer supported. |
||||
| Custom Form Data Format | If you are using the legacy format for custom form data, the
following error is displayed: Custom forms must be converted to the '+' table format before converting to SYSPRO 8 |
Critical
Requires addressing prior to conversion. Therefore, you must use the Custom Form admin tool to migrate your Custom Form data format. |
||||
| ISAM file checks for system database | The SYSPRO 8 Readiness Check will attempt to open all of the ISAM files that
require conversion to SQL in the system database. If there is an error on one or more of these files, the following message is displayed: One or more system ISAM files require re-indexing before converting to SYSPRO 8 All files with errors are then shown in the listview. |
Critical
Files require reindexing prior to conversion. This will ensure that they are valid before the SYSPRO 8 data migration proceeds. |
||||
| System database | The SYSPRO 8 Readiness Check verifies the existence of any tables that may
have the same name as a SYSPRO 8 table to be created. If one or more are found then the following message will appear: One or more SQL tables exist in the database which are reserved for the ISAM file conversion. These need to be renamed or deleted before converting to SYSPRO 8 All tables with issues are then shown in the listview. |
Critical
Requires addressing prior to conversion as it may prevent the correct creation of new tables. You may need to investigate why there is a table in the system-wide database with the same name as a table created when migrating to SYSPRO 8. |
||||
| Database collation | If (prior to the migration) your database's collation was configured
as case insensitive the migration may result in errors, as information
contained in the ISAM files is case sensitive. For example: You may have two stock codes of ABC and abc; this will cause the conversion to fail with a duplicate entry in the InvMaster table. Therefore the SYSPRO 8 Readiness Check verifies that the collation for the system database is case sensitive. This is achieved by scanning the collation name for _CI which implies case insensitive. If the collation for the database is not case sensitive then the following error is shown: Database collation. The database collation 'xxxxxxxxx' is case insensitive. This must be changed to a case sensitive collation before converting to SYSPRO 8. (Where xxxxxxxx is the current collation) |
Critical
Requires addressing prior to conversion. You can change the collation on a database by using either of the following methods:
For detailed information on how to do this using either method: Set or Change the Database Collation Alternatively, you can change the database collation to a Case Sensitive collation (_CS in the name), or to a binary collation (_BIN2 in the name). For example: Latin1_General_BIN2 or Latin1_General_CS_AS |
||||
| Database compatibility level | A compatibility level that is less than 100 is
not supported in SYSPRO 8, therefore the SYSPRO 8 Readiness Check verifies the compatibility
level of your SQL database. If the compatibility level for the database is found to be less than 100 then the following error is shown: Database compatibility level The compatibility level of 'nn' is not supported in SYSPRO 8.
|
Critical
Requires addressing prior to conversion. You can change the compatibility level on a database by using either of the following methods:
For detailed information on how to do this using either method: View or Change the Compatibility Level of a Database |
||||
| Custom programs | The SYSPRO 8 Readiness Check reviews the following areas to establish whether
any custom COBOL programs are called:
If any are found the following warning message is displayed, along with details as to where they are defined: Custom programs Custom programs are in use. Please ensure that a compatible version is available before converting to SYSPRO 8. |
Critical
Requires addressing prior to conversion. Please speak to your third party vendor to ensure that there is a version of the software which is compatible with SYSPRO 8. |
||||
| System Check DB | The SYSPRO 8 Readiness Check will cycle through all the companies that are
licensed to use SYSPRO Report Writer, checking
to ensure that their primary data paths are all the same.
If multiple report writer definition locations are found, then the following message is displayed: Report Writer Definition Definitions exist in folders other than the primary data folder. These need to be relocated for the system conversion to take them into account. Multiple definitions need to be consolidated using the import/export functionality. The reason for checking this is that in SYSPRO 8 all companies use the same set of Report Writer Definitions as defined in the SYSPRO 8 system database. |
Critical
Requires addressing prior to conversion. If there are multiple report writer definitions residing in multiple folders, then these must be consolidated into a single set of definition files and these files must all reside in the primary data folder. Reports for each company can be consolidated into a single set by exporting the definition from the source definition set (Maintain Report > File > Export Report) and then imported to the target definition set (Browse on Reports > File > Import Report from > Text). |
||||
| System check | Description | Importance | ||||
|---|---|---|---|---|---|---|
| C-ISAM | If the company selected is validated as being C-ISAM, the
following error message is displayed: Company must be converted to SQL before converting to SYSPRO 8 |
Critical
Requires addressing prior to conversion. No further checks are made. |
||||
| SYSPRO version | If the company selected is validated as being on a version of
SYSPRO prior to SYSPRO 7 Update 1, the
following error message is displayed: Company must be converted to SYSPRO 7 Update 1 before converting to SYSPRO 8 |
Critical
Requires addressing prior to conversion. No further checks are made. |
||||
| Company database existence | If the company database doesn't exist, the following error
message is displayed: Company database does not exist in the SQL instance |
Critical
Requires addressing prior to conversion. No further checks are made. |
||||
| Company control file | If the SYSPRO 8 Readiness Check encounters a problem accessing the control
file, the following error message is displayed: Error accessing the company control file |
Critical
This is highly unlikely but must be addressed prior to conversion. Reindexing should resolve the issue. |
||||
| Web based applications | If the company is licensed for Web based applications, a row
with the following informational message is
displayed: Not supported in SYSPRO 8 |
Information only
Legacy web-based apps not supported in SYSPRO 8. |
||||
| Preactor | If the company is licensed for Preactor, a row with the
following informational message is displayed: Not supported in SYSPRO 8 |
Information
only
Preactor integration is not available in SYSPRO 8. |
||||
| DFM | If the company has DFM installed, the following informational
message is displayed: Before converting to SYSPRO 8 ensure that no documents are currently queued for DFM |
Information only
This is a reminder to ensure that all documents have been processed before starting the SYSPRO 8 migration. |
||||
| ISAM file checks for company database | The SYSPRO 8 Readiness Check will attempt to open all of the ISAM files that
are to be converted to SQL in each company database. If there is an error on one or more of them, the following error message is displayed: One or more company ISAM files require reindexing before converting to SYSPRO 8 All files with errors are then shown in the listview. |
Critical
Files require reindexing prior to conversion |
||||
| Company database tables | The SYSPRO 8 Readiness Check checks for the existence of any tables that may
have the same name as new tables in SYSPRO 8. If one or more are found, the following error message is displayed: One or more SQL tables exist in the database which are reserved for the ISAM file conversion. These need to be renamed or deleted before converting to SYSPRO 8 All tables with issues are then shown in the listview. |
Critical
Requires addressing prior to conversion as it may prevent the correct creation of new tables |
||||
| Lot archive files |
One or more Lot Archive files are either not found or require reindexing before converting to SYSPRO 8 Each file with issues is then included in the listview. |
Critical / Warning
If these files are not found this is only a warning message, as they can be made available and converted once you are in SYSPRO 8. However, if one or more of these files require reindexing, then this is critical and needs to be addressed prior to converting. |
||||
| Sales order, ECC BOM and WIP Job archive files |
There is no reindexing for these files, therefore the SYSPRO 8 Readiness Check just ensures that they are available and will display the following message if any files are not found: One or more archive files not found Each file not found is then included in the listview. |
Warning
If these files are not found, you can make them available and convert once you are in SYSPRO 8 |
||||
| Database collation | If (prior to the migration) your database's collation was configured
as case insensitive the migration may result in errors, as information
contained in the ISAM files is case sensitive. For example: You may have two stock codes of ABC and abc; this will cause the conversion to fail with a duplicate entry in the InvMaster table. Therefore the SYSPRO 8 Readiness Check verifies that the collation for the system database is case sensitive. This is achieved by scanning the collation name for _CI which implies case insensitive. If the collation for the database is not case sensitive then the following error is shown: Database collation. The database collation 'xxxxxxxxx' is case insensitive. This must be changed to a case sensitive collation before converting to SYSPRO 8. (Where xxxxxxxx is the current collation) |
Critical
Requires addressing prior to conversion. You can change the collation on a database by using either of the following methods:
For detailed information on how to do this using either method: Set or Change the Database Collation Alternatively, you can change the database collation to a Case Sensitive collation (_CS in the name), or to a binary collation (_BIN2 in the name). For example: Latin1_General_BIN2 or Latin1_General_CS_AS |
||||
| Database compatibility level | A compatibility level that is less than 100 is
not supported in SYSPRO 8, therefore the SYSPRO 8 Readiness Check verifies the compatibility
level of your SQL database. If the compatibility level for the database is found to be less than 100 then the following error is shown: Database compatibility level The compatibility level of 'nn' is not supported in SYSPRO 8.
|
Critical
Requires addressing prior to conversion. You can change the compatibility level on a database by using either of the following methods:
For detailed information on how to do this using either method: View or Change the Compatibility Level of a Database |
||||
| Custom programs | The SYSPRO 8 Readiness Check reviews the following areas to establish whether
any custom COBOL programs are called:
If any are found the following warning message is displayed, along with details as to where they are defined: Custom programs Custom programs are in use. Please ensure that a compatible version is available before converting to SYSPRO 8. |
Critical
Requires addressing prior to conversion. Please speak to your third party vendor to ensure that there is a version of the software which is compatible with SYSPRO 8. |
||||
-
Use the Company Maintenance program to determine the Company data format. For companies in an ISAM data format, use the ISAM to SQL Migration Wizard program to migrate the data into a SQL database format.
Operator access to the following activities within this program can be restricted. You configure this using the Operators program.
| Activity | Description | ||||
|---|---|---|---|---|---|
| Main menu - 'Run any program' function |
Controls whether an operator can launch a SYSPRO program by selecting the Run a program option from the SYSPRO Button, or by pressing Ctrl+R from within the SYSPRO Main Menu.
|
||||