infor sunsystems upgrade guidewebasset.uxceclipse.com.au/wp-content/uploads/2017/...7 about this...

Infor SunSystems Upgrade Guide

Infor SunSystems 6.3

Copyright © 2016 Infor

Important Notices

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.

Publication Information

Release: Infor SunSystems v6.3

Publication date: August 31, 2016

Document code: V630A

Contents

About this upgrade guide .......................................................................................................... 7

Contacting Infor ................................................................................................................... 7

Chapter 1 Upgrading SunSystems ............................................................................................... 1

Upgrade paths ..................................................................................................................... 1

Upgrade tasks ..................................................................................................................... 2

Technical support ................................................................................................................ 2

Chapter 2 Preparing the upgrade environment ............................................................................ 3

Introduction .......................................................................................................................... 3

Preparation tasks for the upgrade environment .................................................................. 3

Software requirements ........................................................................................................ 4

Database sizing following upgrade ..................................................................................... 5

Creating a maintenance plan .............................................................................................. 5

User-developed indexes and triggers ................................................................................. 6

Companion products – plan to upgrade .............................................................................. 6

Custom SSC installations .................................................................................................... 6

SunSystems reporting ......................................................................................................... 7

Creating a test environment ................................................................................................ 7

English-only upgrade........................................................................................................... 7

Chapter 3 Completing the prerequisite tasks ............................................................................... 9

Windows user account for upgrading .................................................................................. 9

SunSystems domain groups ............................................................................................... 9

Prerequisite checklist .......................................................................................................... 9

DBCC CHECKDB Command ............................................................................................ 11

Take database backups .................................................................................................... 11

Reviewing Payment Profiles ............................................................................................. 12

Form layout files ................................................................................................................ 12

Save Custom Forms .......................................................................................................... 12

List SSC changes in Props.xml ......................................................................................... 13

Exporting Transfer Desk profiles ....................................................................................... 13

List custom settings for SunSystems Web ....................................................................... 13

Obtaining the latest version of Database Utilities ............................................................. 14

Completing Cleardown tasks ............................................................................................ 14

Running the Pre-Upgrade Check ...................................................................................... 15

Removing redundant work tables ..................................................................................... 15

Running the Structural Integrity Check ............................................................................. 15

Running the Referential Integrity Check – SunSystems Business Unit Group only ........ 16

Running the Query Database File Groups check on the Domain database .................... 16

Running the Query Database File Groups check on a SunSystems Business Unit

Group ................................................................................................................................. 17

Checking user activity ....................................................................................................... 17

Uninstalling SunSystems .................................................................................................. 17

Upgrading to Microsoft SQL Server 2014 or 2016............................................................ 17

Auto Shrink and Recovery Model options ......................................................................... 18

Data Access option ........................................................................................................... 18

Installing Oracle Java Standard Edition Development Kit (32-bit) .................................... 18

Installing Apache Tomcat 8 ............................................................................................... 18

Chapter 4 Running the upgrade procedure ................................................................................ 20

Upgrade tasks ................................................................................................................... 20

Running Database Utilities ................................................................................................ 21

The SunSystems v6.3 ISO ................................................................................................ 22

Running the SunSystems installer .................................................................................... 22

Upgrading the security database ...................................................................................... 22

Upgrading the domain database ....................................................................................... 23

Upgrading a business unit group ...................................................................................... 24

Installing the SunSystems application .............................................................................. 26

Serializing SunSystems .................................................................................................... 26

Validating Filters ................................................................................................................ 26

Validating Business rules .................................................................................................. 27

SunSystems Reporting Services (SRS)............................................................................ 28

Upgrading Custom forms .................................................................................................. 28

Granting Function Permissions to BUA ............................................................................ 29

Upgrading menus .............................................................................................................. 30

Chapter 5 Completing the configuration tasks ........................................................................... 31

Post upgrade tasks ............................................................................................................ 31

General post-upgrade tasks .............................................................................................. 32

Synchronising BU Groups ................................................................................................. 32

Checking the filter log file .................................................................................................. 33

Checking the drill log file ................................................................................................... 33

5

Checking the forms log file ................................................................................................ 33

Checking Ports .................................................................................................................. 33

Recreate Indexes .............................................................................................................. 34

Checking the data dictionary filegroup settings log .......................................................... 34

Importing Transfer Desk profiles ....................................................................................... 34

Including custom SQL scripts for the creation of new business units .............................. 35

Migrating Custom Reports ................................................................................................ 35

Creating reports ................................................................................................................. 35

Reinstalling SunSystems Web .......................................................................................... 36

Granting Function Permissions for Report Models (RMD), Report Designer (RED) and

Report Schedules (RMC) .................................................................................................. 36

Installing languages........................................................................................................... 37

Installing a Language Pack ............................................................................................... 37

Amending the base language ........................................................................................... 37

Regenerating menus with a new language ....................................................................... 38

Synchronizing Report Models ........................................................................................... 39

Specifying a language for a user ...................................................................................... 39

Configuring online help ..................................................................................................... 39

Appendix A Database administration ......................................................................................... 41

SunSystems Database Utilities > Create .......................................................................... 41

SunSystems Database Utilities > Upgrade ....................................................................... 42

SunSystems Database Utilities > Domain DB Utilities ..................................................... 43

SunSystems Database Utilities > SunSystems DB Utilities ............................................. 44

SunSystems Database Utilities > Form Actions ............................................................... 45

SunSystems Database Utilities > Security DB.................................................................. 45

Appendix B Tips on installing and configuring Microsoft SQL Server ........................................ 46

Installation ......................................................................................................................... 46

MS SQL Server Tempdb files ........................................................................................... 46

Instance properties ............................................................................................................ 46

Database properties .......................................................................................................... 46

Maintenance plans ............................................................................................................ 47

Scheduled tasks ................................................................................................................ 47

Appendix C Pre-upgrade checking examples ............................................................................ 50

Structural Integrity Check .................................................................................................. 50

Pre-Upgrade Checks ......................................................................................................... 51

Referential Integrity Check – SunSystems Data ............................................................... 53

Appendix D Database upgrade – example procedure ............................................................... 54

Appendix E Example report equivalence .................................................................................... 56

7

About this upgrade guide This upgrade guide describes the process to upgrade to a SunSystems 6.3 environment. It provides

details of all stages of the upgrade process, from investigating the requirements for your

SunSystems 6.3 installation and understanding the prerequisites, to the upgrade process, and the

configurations required in a post-upgrade environment. The steps to building a comprehensive test

environment are covered extensively.

Intended audience

This document is intended for system administrators, consultants and Channel Partner consultants

involved in deploying and maintaining SunSystems. Due to the numerous implementation options for

SunSystems, only experienced consultants should perform the upgrade process.Related

documents

You can find the documents in the SunSystems product documentation section of the Infor Xtreme

Support portal, as described in "Contacting Infor".

What’s New (New functions and features)

Infor SunSystems Installation Guide

Infor SunSystems Architecture and Planning Guide

Guide to Migrating Data from SunSystems 4

Contacting Infor

Infor provides a centralized upgrade service that can help enable a faster and more efficient upgrade

to SunSystems v6.3.

For more information, please contact your Infor account representative. You can also contact Infor

Customer Care at [email protected], or submit a general request via Infor Xtreme at

www.inforxtreme.com.

If you have questions about Infor products, go to the Infor Xtreme Support portal at

www.inforxtreme.com.

If we update this document after the product release, we will post the new version on this website.

We recommend that you check this Web site periodically for updated documentation.

If you have comments about Infor documentation, contact [email protected].

mailto:[email protected]

http://www.inforxtreme.com/

http://www.inforxtreme.com/

mailto:[email protected]

Chapter 1 Upgrading SunSystems 1

This document describes the upgrade process and manual tasks required to upgrade to

SunSystems 6.3, from the preceding two SunSystems versions:

SunSystems 6.2.1

SunSystems 6.1.1 (PS23 or later)

Functionality changes are cumulative. For example, functionality changes contained in SunSystems

6.2.1 are carried over into the next release, SunSystems 6.3, and so on.

Due to the numerous implementation options for SunSystems, only experienced consultants should

perform the upgrade process.

Upgrade paths

This document covers the upgrade path to SunSystems 6.3, from SunSystems 6.2.1 and

SunSystems 6.1.1 (patch set 23 or later). Versions older than SunSystems 6.1.1 will require a multi-

step upgrade process, via intermediary releases. Refer to previous Upgrade Guides for details.

The upgrade paths table outlines the upgrade path for each SunSystems version:

Upgrade paths

Current version Interim version 1 Upgraded version

v6.2.1 v6.3

v6.1.1 v6.3

v5.4.1 v6.1.1 v6.3

v5.3 v6.1.1 v6.3

Note: Versions older than v5.3 require more than one interim version. Review the upgrade

documentation before proceeding.

Users of SunSystems 4 can migrate directly to SunSystems 6.3 using the Data Migration Wizard (WDM). See the Guide to Migrating Data from SunSystems 4.

Note: Oracle installations must migrate to a Microsoft SQL Server environment before

upgrading.

Upgrade tasks

The SunSystems upgrade process is outlined:

Task References

Ensure you are aware of, and have made plans for,

every item in the upgrade environment checklist,

including creating a test environment

“Preparing the upgrade

environment” on page 11

Complete the prerequisite tasks in the test

environment

“Prerequisite checklist” on page

18

Complete the upgrade tasks in the test environment

“Upgrade checklist” on page 25

Complete the configuration tasks in the test

environment

“Configuration checklist” on

page 38

Implement the proven upgrade process in your live

environment

Technical support

SunSystems Support and Maintenance Services are provided either directly from one of the SunSystems support centres, or via one of many channel partners.

Chapter 2 Preparing the upgrade

environment 2

Introduction

These tasks must be completed before running the upgrade process.

Preparation tasks for the upgrade environment

The tasks to prepare the upgrade environment are listed:

Task References

Check the software requirements for upgrading to

SunSystems 6.3

“Upgrade paths” on page 7

“Software requirements” on

page 10

Plan for the average database size increase if

upgrading from a version older than SunSystems

v621

“Database sizing following

upgrade” on page 11

If you do not have a system maintenance plan,

consider creating one

“Creating a maintenance plan”

on page 14

If you have any user developed indexes and triggers,

or customized functions, stored procedures, or views

used for reports, you must review their requirements

with respect to new functionality available in

SunSystems 6.3.0. The functions, procedures,

triggers or views may need to be reapplied after the

upgrade.

“User developed indexes and

triggers” on page 14

The SunSystems upgrade sets the base language to

1, which is an English-only version. Other languages

must be installed using the Language Deployer after

the upgrade has completed. Ensure the language

required is available for deployment.

Ensure all SunSystems installation prerequisites have

been fulfilled

SunSystems installation guide

Task References

If you are using a companion product, ensure you

have completed the Companion product checklist

“Companion products” on page

15

If you are using a custom SSC integration, ensure

you complete every task on the Custom SSC

integration checklist

“Custom SSC integrations” on

page 15

Ensure you have completed every task on the

SunSystems reporting checklist

“SunSystems reporting” on page

15

Create a test environment “Creating a test environment” on

page 16

Software requirements

To upgrade directly to SunSystems 6.3, the existing version of SunSystems must be one of:

SunSystems 6.2.1 SQL Server

SunSystems 6.1.1 SQL Server + patch set 23 or later

Patch sets can be downloaded from www.inforxtreme.com.

Note: Unless specified, the upgrade process does not require SunSystems to be on a specific

patchset.

Microsoft SQL Server requirements for SunSystems v6.3

Software Notes

Microsoft SQL Server

2016, Standard edition or

above

Features to include: Database

Server, Reporting Services (Native),

and Management Tools

Microsoft SQL Server

2014, Standard edition or

above

Features to include: Database

Server, Reporting Services (Native),

and Management Tools

Note: Oracle installations must migrate to a Microsoft SQL Server environment before

upgrading.

Preparing the upgrade environment

5

Database sizing following upgrade

Note: This section is only relevant if you are upgrading from a version of SunSystems older

than v621. It is not relevant if you are upgrading from SunSystems v621.

Versions of SunSystems older than v6.2.1 will show a significant database size increase after

upgrading to SunSystems v6.3, as they are migrated to unicode. The databases will, on average,

increase in size by 50%.

This table shows the increase in size of databases and log file, from an example upgrade of SunSystems 5.4.1 to SunSystems 6.2.1. The scale of increase will also be seen after upgrading to SunSystems v6.3:

File name 5.4.1 Size pre-upgrade 6.2.1 Size post-upgrade

Security database (.mdf) 4.3MB 4.3MB

Security database log (.ldf) 0.8MB 1.3MB

Domain database (.mdf) 51MB 420MB

Domain database log (.ldf) 23MB 176MB

BU Group (.mdf) 5GB 10GB

BU Group log (.ldf) 1GB 1GB

Observations

The SunSystems Security database will remain the same size. The SunSystems Domain

database will increase by, on average, a factor of 8.

Caution: The BU Group database will almost double in size.

The increase in size of the log files is not significant.

You must take this indication of average size increase into account when planning your SunSystems

upgrade.

Creating a maintenance plan

If you do not have a maintenance plan that checks the structure of your database, consider creating

one. In SQL Server, a database maintenance plan can include tasks such as taking backups of the

SunSystems databases, backups of the transaction log, managing indexes and resolving issues with

internal data storage.

Any outstanding integrity issues with the current database could cause the upgrade to complete

unsuccessfully.

User-developed indexes and triggers

You are aware that all user-developed indexes and/or triggers on tables must be verified after

upgrade. Infor can take no responsibility for these changes.

The same applies to any custom views, custom procedures, custom functions and so on. All of these

must be reviewed after upgrade, to ensure they still perform the task they were written for.

Caution: New functionality in SunSystems v6.3 may replace some user objects.

Companion products – plan to upgrade

If you use Bill of Materials Manager or Withholding Tax, no specific action is required for upgrade as

these companion products are part of the automated upgrade process.

If you use any of the other companion products, for example, Collect or Recurring Invoicing, then

separate upgrade processes are required. Refer to the upgrade guides that are available for each

application.

Caution: Ensure the version of the companion product you are using is compatible with

SunSystems v6.3 and that serialization is correct.

If you have any companion products installed, for example, Collect or RI, you must ensure that they have the relevant upgrade path available, along with any serializations required. You must also verify that any product that works with SunSystems data is compatible with Microsoft SQL Server 2016 or Microsoft SQL Server 2014, as appropriate.

Caution: If you do not have a maintenance plan that checks the structure of your database, it is

recommended you run DBCC CHECKDB on your database prior to running the upgrade.

Caution: If you have any customized functions, stored procedures, triggers or views used for

reports, you should review their requirements with respect to new functionality available in

SunSystems v6.3.0. If necessary, reapply the functions, procedures, triggers or views,

after the upgrade.

Custom SSC installations

Investigate if any custom SSC integration has been developed on the customer’s installation and

how that would be upgraded.

Integrations using SunSystemsConnectClient.dll, located in …\Infor\SunSystems\, will need to

manually copy the new SunSystems 6.3 version into the custom projects.

In previous versions of SunSystems, integrations were required to obtain a Security Voucher which

was then provided in calls to SSC. The same voucher could be used indefinitely without issue,

unless the SSC Windows Service was restarted.

In SunSystems 6.3, security vouchers expire after 24 hours, when they become invalid.

Preparing the upgrade environment

7

Therefore, we recommend that integrations in SunSystems 6.3 obtain a new voucher at a regular

interval, for example, every 12 hours. However, we do not advise that integrations ‘re-authenticate’

each time a call is made to SSC, as this will have an adverse impact on performance.

SunSystems reporting

Upgrading from SunSystems 6.1.1 (PS23 or later)

During the installation of SunSystems Reporting server, all example reports in the example reports

folder will be overridden.

Before uninstalling SunSystems 6.1.1, we recommend that all reports are exported through Report

Administrator. If required, you may create another Microsoft SQL Server backup of the report model.

After SunSystems Reporting Services (SRS) is installed as described in the Procedure section within

this guide, new SRS equivalents of all example reports will be available in the report store on the

server. A list of equivalent examples is provided in Appendix E of this guide. You may choose to

deploy these as they are, or to modify them to match the customization in your previous version.

Taking backup copies of these files is made easier if an appropriate naming convention has been

used.

Upgrading from SunSystems 6.2.1

Following the installation of SunSystems v6.3, you will need to upgrade the report model using

Report Models (RMD), then migrate the reports to SunSystems 6.3 using Report Manager (RMA)

Migrate. Reports are maintained in SunSystems v6.3 using Report Models (RMD).

Creating a test environment

English-only upgrade

Upgrade to test environment – test will be English only, wait for language packs

Prior to a live upgrade, it is strongly recommended that the entire upgrade process be proven in a

test environment.

Create a test environment as follows:

1 Copy all live SunSystems databases to another test server. As a minimum, you must copy the

Security, Domain, and BU Group databases. The test server must be separate from the live

server to avoid impacting the performance of the live system.

2 You will need to re-link the domain and business unit group servers after you have moved them.

Go to Database Utilities > Domain DB Utilities > Re-link all the SunSystems Business Unit

Groups to a SunSystems Domain. See Appendix A page 48.

3 Install the current version of SunSystems on a test server with the same directory/file structure

as the live server. The test server must be separate from the live server to avoid invalidating

registry entries on the live system. The directory/file structure of the test server must be the

same as that of the live server to ensure accurate replication of .ini file settings. The installation

of the current version of SunSystems ensures accurate replication of registry settings and

Windows/system files.

4 Copy the complete live SunSystems directory and file structure, including all contents, onto the

installation created in step 3. This ensures accurate replication of all customization to forms,

reports, menus, etc.

The test environment must use the same software versions as the live environment, including patch

sets, hot fixes etc.

It is advisable to include a client machine in the test environment.

Caution: Upgrading a live environment without proving the upgrade process in a test environment is

not recommended as any failure and need to revert to backup will result in significant

downtime.

One advantage of recreating your system in a test environment is that, on successful completion of the upgrade and testing, you can overlay the newly compiled and upgraded forms onto your live system. This can significantly reduce any downtime that can result from the upgrade process.

Completing the prerequisite tasks

9

Chapter 3 Completing the prerequisite

tasks 3

Introduction

You must complete the prerequisites checklist to ensure a successful upgrade of SunSystems.

These tasks are required for the upgrade, but can be completed a little while beforehand.

Windows user account for upgrading

The Windows user account to be used for the upgrade must have Administrator rights over all

locations where SunSystems components are installed.

SunSystems domain groups

The domain groups to be used must already exist. The upgrade uses new default domain group

names. Therefore, if you wish to continue using the existing domain group names, you must re-enter

them during the upgrade process, rather than accept the defaults.

Prerequisite checklist

Before running the upgrade, complete the prerequisite checklist:

Task References

If you do not have a maintenance plan that checks the

structure of your database, it is recommended you run

DBCC CHECKDB on your database before upgrading

“DBCC CHECKDB” on page 19

Ensure the Windows user account for upgrading has

sufficient rights “Windows user account for

upgrading” on page 19

Task References

Ensure the domain groups to be used already exist “SunSystems domain groups”

on page 19

Take database backups “Take database backups” on

page 19

Payment profiles “Payment profiles” on page 19

Form layout files “Form layout files” on page 20

Save custom forms “Save custom forms” on page

20

List SSC changes in Props.xml “List SSC changes in

Props.xml” on page on page 20

Export Transfer Desk profiles “Exporting Transfer Desk

profiles” on page 21

List custom settings for SunSystems web “List custom settings for

SunSystems web” on page 21


page 19

Ensure you have the latest version of Database Utilities. “Obtaining the latest version of

Database Utilities” on page 21

Complete all cleardown tasks “Completing Cleardown tasks”

on page 21

Run Database Utilities > Upgrade > Pre-Upgrade

Check

“Running the Pre-Upgrade

Check” on page 22

Run Database Utilities > Upgrade > Remove work

tables

“Removing redundant work

tables” on page 23

Run Database Utilities > Domain DB > Structural

Integrity Check – Domain

“Running the Structural

Integrity Check” on page 23

Run Database Utilities > SunSystems DB > Structural

Integrity Check

“Running the Structural

Integrity Check” on page 23

Run Database Utilities > SunSystems DB >

Referential Integrity Check – SunSystems Business

Unit Group only

“Running the Referential

Integrity Check – SunSystems

Business Unit Groups only” on

page 24

Run Database Utilities > Domain DB > Query

database file groups

“Running the Query Database

File Groups check on the

Domain database” on page 24


11

Task References

Run Database Utilities > SunSystems DB > Query

database file groups

“Running the Query database

File Groups check on a

SunSystems Business Unit

Group” on page 24


page 19

Ensure all users are logged off “Checking user activity” on

page 24

Uninstall SunSystems. Retain your databases. “Uninstalling SunSystems” on

page 25

Upgrade SQL Server to SQL Server 2014, or SQL

Server 2016

“Upgrading to Microsoft SQL

Server 2014 or 2016” on page

25

Set Auto Shrink and Recovery Model database options

to Off and Simple, respectively

“Auto Shrink and Recovery

Model options” on page 25

Ensure the data access option in Microsoft SQL Server

is set to true.

“Data access option” on page

25

Install Oracle Java Standard Edition Development Kit

(32-bit)

“Installing Oracle Java

Standard Edition Development

Kit (32-bit)” on page 26

Installing Apache Tomcat 8 “Installing Apache Tomcat 8”

on page 26

DBCC CHECKDB Command

If you do not have a maintenance plan that checks the structure of your database, it is

recommended you run DBCC CHECKDB on your database prior to running the upgrade.

Take database backups

Backup your databases and server files, including custom forms and menus.

Reviewing Payment Profiles

Caution: This is a critical step in the prerequisites tasks. Failure to work through this step may result

in one or more unusable Business Units after the upgrade has been applied.

Review your payment profiles in Payment Profiles (PYP).

For each Profile, click on the Options tab: if the Payment Report Format Code is blank, you must

apply an appropriate Payment Report Format Code to the Payment Profile.

Caution: Blank values are invalid in SunSystems 6.3, and will result in validation failures in

Document Format Code differences, when synchronizing a business unit.

Form layout files

Ensure all source form files have been checked into the server.

Save Custom Forms

Note: Custom Forms can be upgraded from SunSystems v6.2.1 to v6.3 directly from the

SunSystems navigator.

The Upgrade Custom Forms process upgrades custom forms to reflect changes made to the

SunSystems Data Dictionary. This includes, for example, the deletion of obsolete data items. Details

of all changes are recorded in FormUpgradeMaster.log. Where updates are considered necessary

but insufficient information is available for automatic update, no change is made and the details are

recorded in FormUpgradeDetail.log.

The log files are located in C:\ProgramData\Infor\logs\Install\CustomerUpgrade in the

~\FormsPre, ~\FormsPost, and ~\Logs subfolders.

1. Export your custom forms. Go to Database Utilities > Form Action > Export forms from a

SunSystems Domain.

2. Select Source Forms (SFL only).

3. Deselect SASI Forms.

4. Highlight all Function Names in the Select the Function Name grid.

5. Click Next.

6. Specify the folder where the forms are to be exported to.


13

List SSC changes in Props.xml

Any sections of props.xml that have been updated since installation of your current SunSystems

are copied into user_props.xml. For example, a section will have changed if the default port

numbers have been reset, or the SOAP settings edited. Entries in the user_props.xml file take

precedence over the system defaults provided in props.xml, which is overwritten during the

installation process.

The props.xml file is located in the ~\ssc\lib\properties directory in the SunSystems root directory,

and the user_props.xml file is located in the ~\ssc\lib directory.

In your current version of SunSystems, make a note of any custom settings that have been applied

in Property Editor. Property Editor is deprecated in SunSystems 6.3. These custom settings will

need to be applied manually using Configuration Manager in SunSystems 6.3. See the Online Help

for more information.

Exporting Transfer Desk profiles

Export your Transfer Desk profiles:

1. Use the Configuration Export function in Transfer Desk.

2. Ensure that the export has processed successfully, by manually checking that the repository

export file has been created.

Caution: If the repository export file has not been created, or if any errors were reported during the

export, you should repeat step 1, and not continue with step 2 until the export

has completed successfully. This is because in the cleardown, all of the Transfer Desk

objects (for example profiles, transformations, and data types) are deleted, and can only

be recreated subsequently using the exported data, or manually.

Use the Configuration Cleardown function in Transfer Desk.

List custom settings for SunSystems Web

SunSystems Web is reinstalled with SunSystems 6.3, rather than being upgraded. This means

nothing is required to be upgraded or carried over to the test system.

As part of reinstallation, your existing server-custom.properties file will be deleted and a default

version of the server-custom.properties file created. Therefore, you must make a note of any

custom setting within the server-custom.properties file and reapply them in the new installation.

Obtaining the latest version of Database Utilities

Database Utilities is available as a separate application, from Infor Xtreme.

Whenever Database Utilities is updated, the latest version will be made available from Infor Xtreme.

Download the Database Utilities application from this location before performing updates on your

SunSystems database.

Completing Cleardown tasks

Note: Failure to complete these cleardown tasks may cause the upgrade process to fail. For

example, while data exists in Data Audit, the upgrade process will not continue.

It is recommended that you complete the cleardown tasks. These items are checked during the Pre-

Upgrade, Structural and Referential integrity checks. If any of the pre-upgrade checks fail, the

upgrade is prevented from progressing.

Upgrading from SunSystems 6.2.1:

Clear Data Audit

o If you use Data Audit functionality, ensure that all Data Audit entries are cleared down using Data Audit Cleardown (DACD or DAL). If you have data auditing enabled on any tables you must ensure that you have run the function Data Audit Cleardown (DACD or DAL).

Clear outstanding ION transactions

Upgrading from SunSystems 6.1.1 or older:

Clear Data Audit

o If you use Data Audit functionality, ensure that all Data Audit entries are cleared down using Data Audit Cleardown (DACD or DAL). If you have data auditing enabled on any tables you must ensure that you have run the function Data Audit Cleardown (DACD or DAL).

Clear held journals

o All held journals must be cleared or posted before running an upgrade. This task can

be achieved by using the SunSystems function Ledger Entry - Held Journals (LEH).

Clear all outstanding authorizations by approving or rejecting the authorization sets

o All outstanding authorizations must have been processed through to completion. This

task can be achieved by using the SunSystems functions Authorizations (AUT) or

Authorizations Originator’s In Tray (AOT).

Ensure there are no duplicate bank sub code and supplier code combinations

o If upgrading from SunSystems 6.1 or older, you cannot have more than one row with

the same supplier code and bank sub code combination in the bank details table.


15

This task can be achieved by using the SunSystems function Bank Details Setup

(BNK).

o Caution: If the error “duplicates data found” is encountered when managing

migration to 6.3, you will need to resolve the issue and restart the upgrade process.

Check there are no invalid Document Format Codes on Payment Profiles.

Running the Pre-Upgrade Check

This check must be run before performing an upgrade. The check prevents the upgrade from

progressing if it returns existing entries of outstanding transactions. If you have completed the

Cleardown Tasks, then the Pre-Upgrade Check should complete successfully.

This check must be run on each SunSystems Business Unit Group. See Appendix A for details and

Appendix D for an example.

Open Database Utilities and select Upgrade > Pre-Upgrade Checks to run the check.

In the event of warnings or errors, a message displays “one or more steps have encountered an

error or warning, please review for details.” Click OK > Futher Details. You can view comments

in the Utilities Progress Monitor.

On completion of the check, you can vew details in the Pre-Upgrade Check log:

C:\ProgramData\Infor\SunSystems\Logs\Install\Pre-upgradecheck.log

Removing redundant work tables

Remove all work tables. All work tables older than a month will be deleted. You may amend the

parameters so that all work tables are deleted. Removing temporary work tables and views from the

database can greatly improve the performance of the Upgrade Business Unit section of the upgrade

process.

1 Open Database Utilities and select Upgrade > Remove work tables.

2 Take a database backup.

Running the Structural Integrity Check

Note: Any issues found reported after the Structural Integrity Check has completed must be

resolved before the upgrade process can continue.

You must run the Structural Integrity Check on the Domain database and all business unit groups.

This performs a structural integrity check of all tables in the selected SunSystems Business Unit

Group. This is the same check that is performed as part of the upgrade process.

Open Database Utilities and select Domain DB Utilities > Structural Integrity Check.

Or, select SunSystems DB Utilities > Structural Integrity Check.

In the event of warnings or errors, a popup message warns: “One or more steps have encountered

an error or warning, please review the grid for details, you may need to scroll up the grid to see

further details.”

Click OK > Futher Details. View comments in the Utilities Progress Monitor.

Fix the issue, then run the Structural Integrity Check again.

If this function does not complete successfully, you must contact Infor Support / ICS – as this may

indicate that the database integrity has been compromised.

Running the Referential Integrity Check – SunSystems Business

Unit Group only

This utility checks the integrity of the database. It can be run at any time, but we strongly

recommend it is run before you upgrade, so that any errors can be identified.

To run the check, open Database Utilities and select SunSystems DB Utilities > Referential

Integrity Check – SunSystems Business Unit Group only.

Note: Depending on the size of the data, this may take a considerable amount of time.

See Appendix C for details of the SunSystems database utilities, and Appendix D for some pre-

upgrade integrity check examples.

Running the Query Database File Groups check on the Domain

database

This option lists all of the filegroups Running the SunSystems installer referenced in the

SQL_OBJ_REGISTRY table.

Caution: If you use filegroups it is recommended to check that all referenced filegroups exist on the

new machine otherwise the upgrade will fail.

Caution: You must select the domain database to run this validation.

Open Database Utilities and select Domain DB Utilities > Query database file groups.


17

Running the Query Database File Groups check on a

SunSystems Business Unit Group

This check must be run for all business unit groups.

Open Database Utilities and select SunSystems DB Utilities > Query database file groups.

See Appendix A for details of this function.

Checking user activity

Ensure all users are logged off and that there are no active users.

1 Open User Manager.

2 Select Settings > User Activity.

3 Clear down any remaining active users.

Uninstalling SunSystems

1. Ensure all SunSystems users have logged off, that all sessions are closed and all work has been

saved.

2. Open Control Panel and select Programs and Features.

3. Select SunSystems and click uninstall.

Upgrading to Microsoft SQL Server 2014 or 2016

If you are using either Microsoft SQL Server 2008 or 2012, you must upgrade to Microsoft SQL

Server 2014 or 2016. To do this, you can either upgrade Microsoft SQL Server using the upgrade

wizard, or backup the SunSystems databases and restore into a new installation of Microsoft SQL

Server.

Note: Microsoft SQL Server 2014 and Microsoft SQL Server 2016 do not give the sysadmin role

to NT AUTHORITY\SYSTEM (Local System). If you are upgrading a standalone

environment, then this role must be added to the SYSTEM login in Microsoft SQL Server.

1 Take a backup of all databases.

2 Run the upgrade wizard to upgrade to 2014, or 2016. This upgrades both software and

databases. Alternatively, install a new version of Microsoft SQL Server 2014 or 2016 and restore

the SunSystems database into the new version.

See Appendix B Tips on installing and configuring Microsoft SQL Server.

Auto Shrink and Recovery Model options

Before initiating the upgrade process, but after the backups have been taken, you must ensure that

the Auto Shrink option is set to Off, and the Recovery Model option is set to Simple. This aids the

performance of the upgrade process.

Caution: You must ensure that the compatibility mode is set to 100 or above. This is mandatory for

the Domain database. If compatibility mode remains at 80, then the upgrade process will

fail.

Data Access option

Ensure that the installation of Microsoft SQL Server has the data access option set to true. An

example command:

exec sp_serveroption <instance name> ‘data access’ ‘true’

This must be run on all instances where the SunSystems domain and SunSystems data databases

reside.

Installing Oracle Java Standard Edition Development Kit (32-bit)

You must use the latest version to ensure your environment has the most recent security updates for

Oracle Java Development Kit (32-bit).

1. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Click Java Platform, Standard Edition > JDK > Download.

3. Download version for Windows x86.

Note: Oracle JDK for Windows x64 is not supported.

4. Run the installer.

5. Add the installation location to the environment variable SUNSYS_JAVA_HOME.

Installing Apache Tomcat 8

You must use the latest version of Apache Tomcat 8 to ensure your environment has the most

recent security updates.

1. Go to https://tomcat.apache.org/download-80.cgi

2. Select Binary Distributions > Core > zip (pgp, md5,sh1).

Note: You must use the core zip, not the Windows zip.

http://www.oracle.com/technetwork/java/javase/downloads/index.html

https://tomcat.apache.org/download-80.cgi


19

3. Unzip and save the files to ~\Program Files\.

4. Run the installer.

5. Add the installation location to the environment variable SUNSYS_TOMCAT_HOME.

Chapter 4 Running the upgrade

procedure 4

Complete the upgrade procedure on all machines where SunSystems components are installed.

Caution: If the database has 'active' auditing, then all active triggers are removed during the

upgrade and reapplied after the upgrade has completed.

Upgrade the databases first, on the machine you want the SunSystems Domain database to be on.

The databases must be upgraded in this order:

1 Security database

2 Domain database

3 Business Unit groups

Caution: For best performance on a multi-tier environment, we recommend that you install the

SunSystems Security Server on the same machine as the SunSystems Domain Database.

Caution: You must ensure that AlwaysOn Availability Groups are disabled before upgrading the

SunSystems databases.

Upgrade tasks

Task References

Ensure all prerequisite tasks have been completed. “Prerequisite checklist” on

page 17

Open the SunSystems v6.3 ISO. Run the SunSystems

installer and select SqlServerDatabaseUtilities

Alternatively, ensure you have the latest version of

Database Utilities by visiting Xtreme and downloading

the latest version.

“The SunSystems v6.3 ISO” on

page 29

“Running the SunSystems

installer” on page 29

“Obtaining the latest version of

Database Utilities” on page 21

If required, run Database Utilities > Domain DB

Utilities > Re-link all the SunSystems Business Unit

Groups to a SunSystems Domain

“Re-link all the SunSystems

Business Unit Groups to a

SunSystems Domain” on page 50

Running the upgrade procedure

21

Task References

Run Database Utilities > Upgrade > Pre-Upgrade

Checks

See Appendix C for examples

“Running the Pre-Upgrade

Checks” on page 22

Run Database Utilities > Upgrade > Remove Work

Tables

“Removing redundant work

tables” on page 23

Take a backup of the SunSystems databases. “Take database backups” on

page 19

Run Database Utilities > Upgrade > A SunSystems

Security database

“Upgrading the security

database” on page 29


Domain database

“Upgrading the domain

database” on page 30


Business Unit Group

“Upgrading a business unit

group” on page 31

Install the SunSystems v6.3 application “Installing the SunSystems

application” on page 33

Apply serialization “Serializing SunSystems” on

page 33

Complete validation checks including checking the filter

log for orphans, Business Rules Check log,

“Validating filters” on page 33

“Validating Business Rules” on

page 34

Install SunSystems Reporting Services “SunSystems Reporting

Services (SRS)” on page 35

If you have upgraded from SunSystems 6.1.1, you will

need to upgrade custom forms

“Upgrading custom forms” on

page 35

Grant function permissions to BUA “Granting function permissions

to BUA” on page 36

Run menu migration “Upgrading menus” on page 37

Running Database Utilities

The latest version of Database Utilities is available to download, from Xtreme.

Before running an upgrade, or performing any activity on a SunSystems database, ensure you have

the current version of Database Utilities by visiting the website.

The SunSystems v6.3 ISO

The SunSystems 6.3 DVD ISO available for download from the Infor download centre:

https://infor.subscribenet.com

Run a Product Search for SunSystems 6.3 and download InforSunSystems63.iso onto your server.

Running the SunSystems installer

Run the SunSystems installer:

Note: If the installer does not load, open Task Manager. If the process mshta.exe is

running, close it.

1 Click setup.hta to run the SunSystems installer.

2 Click Install SunSystems Software > Next.

3 Select Database Utilities.

Upgrading the security database

1 Go to SunSystems Database Utilities > Upgrade > A SunSystems Security database. See

Appendix A, page 30, 47 for details.

2 Specify the Security Database settings. Select the security database Instance Name and

database name.

3 View the Progress Monitor. The setup program carries out these automated tasks:

Caution: The automated database upgrade process affects standard SunSystems tables only. It

does not affect any non-standard tables created outside of SunSystems.

Security: Object existence checks

Security: Add logins to SQL Server

Security: Configure database access - SunSystemsSecurity

Security: Upgrade schema SECUPGRADE621-630.INI

Security: Update procedures

Security: Update language metadata

After the database upgrade has completed, review any issues reported, and resolve them.

Caution: Scroll through the upgrade screen to ensure that you identify any issues which do not stop

the upgrade but produce a log file.

If any issues are reported, you should restore the security database. The issues must be resolved

and the upgrade process restarted from the beginning, including the prerequisites.

https://infor.subscribenet.com/


23

Upgrading the domain database

1 Go to SunSystems Database Utilities > Upgrade > A SunSystems domain database. See

Appendix A, page 30, 47 for details.

2 Specify the Domain datasource settings. Select the datasource name, instance name and

database name for the domain database that you want to upgrade.

3 View the Progress Monitor. The setup program carries out the following automated tasks:



Domain: Add logins to SQL Server

Domain: Prepare database access

Domain: Object existence checks

Domain: PreCheck DB integrity

Domain: Upgrade schema DOMUPGRADE621-630.INI

Domain: Data/Index file group check

Domain: Update metadata

Domain: Remove old dictionary tables

Domain: Rename data dictionary tables

Domain: Drop old constraints

Domain: Create new dictionary tables

Domain: Add data dictionary constraints

Domain: Load data dictionary tables

Domain: Install language metadata

Domain: Update base language metadata

Domain: Update language metadata

Domain: Load data dictionary language tables

Domain: Copy forward third party data

Domain: Add data dictionary indexes

Domain: Remove old dictionary tables

Domain: Disable SSC hiearchy node

Domain: Create generated data dictionary

Domain: Generated menu

Domain: Create DOMN_GEN_DATA triggers

Domain: Remove data from difference tables

Domain: Load data to difference tables

Domain: Refresh difference tables’ version

Domain: Apply post upgrade scripts

Domain: Filter FDD selection

Domain: Finalise database

Domain: Forms load

Domain: Delete previous patch history

Domain: Enable Broker

Domain: Post upgrade DB integrity check

After the database upgrade has completed, review any issues reported, and resolve them.

Caution: Scroll through the upgrade screen to ensure that you identify any issues which do not stop

the upgrade but produce a log file.

If any issues are reported you should restore the domain database. The issues must be resolved

and the upgrade process restarted from the beginning, including the prerequisites.

Upgrading a business unit group

Caution: When upgrading from SunSystems 6.1.1, only user labels from the first business unit

group are migrated. In addition, if you have USER_TEAMS enabled, then only User Team

Codes from the first business unit group are retained.

Note: We recommend that each Business Unit Group contains a maximum of 100 Business

Units. Exceeding this number has an adverse affect on the performance of the upgrade.

Note: The concept of Financials Only business units has been removed for SunSystems 6.3, so

Financials Only business units are converted to complete business units.

This procedure must be run for all business unit groups.

1 Go to SunSystems Database Utilities > Upgrade > A SunSystems Business Unit Group.

See Appendix A, page 31, 47 for details.

2 Specify the Domain datasource settings. Select the datasource name, instance name and

database name for the domain database that you want to upgrade.

3 Specify the SunSystems database details. Select the business unit group that you want to

upgrade.

4 Specify the Group account settings. Specify the existing windows groups to be used by

SunSystems.

5 View the Progress Monitor. The setup program carries out the following automated tasks for

each Business Unit Group:



SunSystems: Object existence checks

SunSystems: Create missing financial only BU table

SunSystems: Pre-Upgrade checks

Remove audit triggers

Remove integration triggers


25

Remove balance triggers

SunSystems: Create GS views to domain tables

SunSystems: Create SUN views to domain tables

SunSystems: Upgrade database ‘SYSUPGRADE621-630.INI’

SunSystems: Upgrade database ‘BUSUPGRADE621-630.INI’

SunSystems: Update database, apply ‘SYSUPDATE.INI’

SunSystems: Update database, applly ‘BUSUPDATE.INI’

SunSystems: Load integration data

SunSystems: Add ‘BUGROUP2’ to domain

SunSystems: Update system base language

SunSystems: Update business unit base language

Post upgrade system tasks

Post upgrade BU tasks

Business rules check

Drill to investigate

SunSystems: Add logins to SQL Server

SunSystems: Configure database access


Post upgrade DB integrity check

Add audit triggers

Reapply integration triggers

Reapply balance triggers

SunSystems: Delete previous patch history

SunSystems: Finalise database

SunSystems: Configure database access


Post upgrade DB integrity check

Add audit triggers

Reapply integration triggers

Reapply balance triggers

SunSystems: Delete previous patch history

SunSystems: Finalise database

SunSystems: Configure multi database flag

Note: During the upgrade of SunSystems versions older than v6.2.1, a section of the business

unit upgrade script splits out data from one table, ZZZ_SSRFMSC, where ZZZ is the

business unit code, to multiple new tables e.g. ZZZ_LDG_DEFN. At the end of this script

the data from the ZZZ_SSRFMSC table will be retained in the ZZZ_SSRFMSC_SAVE

table.

Following completion of the database upgrade, review any issues reported, and resolve them.

Caution: Scroll through the upgrade screen to ensure that you identify any issues such as business

rules check, which do not stop the upgrade but produce a log file.

If any issues are reported, you should restore the business unit group database. The issues must be

resolved and the upgrade process restarted from the beginning, including the prerequisites.

Installing the SunSystems application

There is no upgrade utility for SunSystems Security, application, or client installation. You should

uninstall each of these from Add/Remove Programs in Control Panel.

After uninstalling, perform a fresh installation of SunSystems Application Server/Client following the

SunSystems v6.3 Installation Guide.

Serializing SunSystems

To serialize SunSystems, go to Windows File Explorer on your standalone server, and run the

serialization file.

After you have installed the SunSystems application and clients, you must reserialize for

SunSystems v6.3. In a multiple server deployment, this must be completed on each application

server and for each Business Unit Group (database).

Note: Languages are stored in the domain database. Therefore, when upgrading the domain

database, you must ensure that all languages required for your Business Unit Groups

have been selected.

Validating Filters

There are two validations regarding filters that are performed during the upgrade process:

Filter DDD Selection

This process checks the filter selection and filter sort tables to see if the filter has any orphaned

entries to the data dictionary. The log file details the filter name, base form item reference, filter

control Id and the filter type code. The final column details whether the orphan is a filter selection or

a sort one.

Drills to Investigate


27

This process interrogates the table ZZZ_DRILL_ASSOCIATES and reports if any of the twenty-one

item references that are possible on a row are orphaned. The log details the Business Unit Code,

Filter Type Code, Drill description and the Column that has the orphaned reference.

Validating Business rules

There is a specific part of the upgrade that deals with business rules, called Business Rules Check.

This validation attempts to cross check any business rule table that could have a reference to a data

dictionary item, to determine whether it has changed in any way. The log file produced gives details

of two types of checks for each column:

Orphaned – This is when the data dictionary reference in the column refers to a non-existent

data dictionary entry. This is probably due to the entry in the data dictionary being removed.

Changed – This is when the item number in the data dictionary has changed. For example, the

business rules reference is RF152 00000005; this equates to ZZZ_ACNT column

ACNT_CODE. If the column changed its number from 5 to 10 this would be identified in the log

file as OLD_VAL = 5 and NEW_VAL = 10.

The following business rule table column combinations are validated:

PMD_RULE_DETL – columns LIT_1, LIT_2

CODE Column contains the value from RULE_CODE column

LINE_NUM column contains the value from LINE_NUM column

PMD_DATA_ITEM – column DATA_ITEM

CODE Column contains the value from DATA_ITEM column

LINE_NUM column contains the value from DATA_SUB_ITEM column

PMD_LOOKUP_TABLE_DEFN – columns DATA_ITEM_1, DATA_ITEM_2, DATA_ITEM_3

CODE Column contains the value from LOOKUP_CODE column

PMD_RECON_PROFILE – columns MATCH_CRITERIA – 1 through 10

CODE Column contains the value from PROFILE_CODE column

PMD_RECON_PROFILE – columns SELECTION_CRITERIA – 1 through 10

CODE Column contains the value from PROFILE_CODE column

Caution: No automatic changes are made to the data; these changes must be made manually.

1 The customer’s business rules should be reviewed as to whether they should be rewritten more

logically and efficiently. Are they fulfilling the customer’s requirements?

2 If chosen to be upgraded the user inspects the Business Rules upgrade log files to establish

which manual amendments are required.

3 Using the business rules functions in SunSystems (e.g. event profiles, rule sets), manual

amendments are made to ones flagged in the upgrade log files. This may require deleting

current event profile or rule set and recreating them. This stage of the process is done using

business rules functions in the upgraded system. There are 2 refactoring projects planned for

business rules which need to be considered from the upgrade point of view.

SunSystems Reporting Services (SRS)

SunSystems Reporting Services (SRS) is based on Microsoft SQL Server Reporting Services. Over

200 example reports are provided for use as templates to replicate reports based on the examples in

previous versions and to illustrate how SRS meets other common reporting requirements. A full list

of equivalents is provided in Appendix E – Example Report Equivalence.

SRS is imported as part of the upgrade process.

For details on upgrading the report model and migrating custom reports to SunSystems 6.3 from

SunSystems 6.2.1, see Migrating Custom Reports in Post-Upgrade Tasks.

Upgrading Custom forms

Custom forms are upgraded after the database upgrade has completed.

Prerequisites

SunSystems client is installed on the machine on which you are running the Upgrade

Custom Forms process.

If you are upgrading from SunSystems 6.1.1, the pre-upgrade Custom forms are in the

Business Unit Group.

The custom forms upgrade process is run from the Database Utilities Upgrade tab and during the

process you need to provide the folder location of the exported custom forms.

Note: The custom forms upgrade procedure selects the appropriate custom forms for upgrade.

This means it does not upgrade filters and forms for functions removed from the new

version.

1 From Database Utilities, select Domain DB Utilities > Load difference tables.

2 Enter the Database Server and Business Unit Group (SunSystems Data database name) and

version of forms to be upgraded.

3 From Database Utilities, select Upgrade > Custom forms.

4 Select the SunSystems Domain datasource and Business Unit Group name. The SunSystems

database details are entered.

5 Browse for the location of the folder containing exported custom forms.

6 Select the database instance location and Business Unit Group to be upgraded.

7 The upgrade custom forms process will make as many automated amendments to the forms as

possible, to reduce the application consultant’s time required for manual amendments in Form

Designer. Refer to FormUpgradeMaster.log to see the list of all successfully upgraded forms,

and all forms requiring manual amendments. The log file is found in

~\ProgramData\Infor\Logs\SunSystems\Install\CustomerUpgrade\Logs.

8 When the upgrade of the custom forms has completed, you must import the forms back into the

SunSystems database using Database Utilities > Form Actions > Import forms in to a

SunSystems Domain.


29

9 The manual amendment of forms should be completed by an application consultant, as the

forms must be individually checked out and amended in Form Designer. See

FormUpgradeDetail.log, found in

~\ProgramData\Infor\Logs\SunSystems\Install\CustomerUpgrade\Logs.

Note: It is likely that forms will need to be redesigned in order to utilise the updated Infor SoHo

user interface.

10 Each form that has been manually amended must be checked in and locally compiled in Form

Designer, to ensure the amendment has been successful. You may need to redesign some

forms.

Caution: A form may not be fully upgraded if it contains a field associated with any of the following

functions:

BCS Budget Check Setup

CAA Corporate Allocation Calendar

CAD Corporate Allocation Setup

CAR Corporate Allocation Ratios

CAS Corporate Allocation Sources

CAT Corporate Allocation Target

DYB Daybook Setup

FDU Asset Timing Rules

FNL Financial Analysis Layouts (FNL)

FRH Financial Column Headings

FSL Financial Statement Layouts (FSL)

FSR Statement Line Contents (FSR)

FTC Financial Table Columns Record (FTC)

FTF Financial Table Format Record (FTF)

FTR Financial Table Row Record (FTR)

JNP Journal Presets

LEQ Ledger Sequences

LES Ledger Setup

TXD Tax Details

PYP Payment Profiles

Granting Function Permissions to BUA

In User Manager you must ensure that an operator group is granted the function permissions to

Business Unit Administration (BUA). Check that the user you initially log into SunSystems with

belongs to this group.

Upgrading menus

Any deprecated functions are automatically removed from custom menus.

Caution: We strongly recommend that you add the BUA function to an Administrator group in

User Manager, before proceeding.

Completing the configuration tasks

31

Chapter 5 Completing the configuration

tasks 5

Post upgrade tasks

Task References

Complete the general post-upgrade tasks “General post-upgrade tasks” on

page 39

Synchronize BU Group “Synchronizing BU Groups” on

page 39

Check the filter log file for filters listed for investigation “Checking the filter log file” on

page 40

Check the drill log file for drills listed for investigation “Checking the drill log file on

page 40

Check the forms log file for forms listed for

investigation

“Checking the forms log file” on

page 40

Checking the ports “Checking ports” on page 40

Recreate indexes “Recreate indexes” on page 40

Check the data dictionary filegroup settings log “Checking the data dictionary

filegroup settings log” on page

41

Import Transfer Desk profiles “Importing Transfer Desk

profiles” on page 41

If you have view-based reports, you can use custom

SQL scripts in the creation of new business units.

“Including custom SQL scripts

for the creation of new business

units” on page 41

If upgrading from SunSystems 6.1.1, upgrade custom

reports

Migrate custom reports “Migrating custom reports” on

page 42

Task References

Use Report Designer to customize example reports “Creating reports” on page 42

Reapply custom settings for SunSystems web “Reinstalling SunSystems web”

on page 43

Grant function permissions for DAR, RED and RMC “Granting function permissions

for Report Models (RMD), Report

Designer (RED) and Report

Schedules (RMC)” on page 43

Install languages “Installing languages” on page

43

“Installing a Language Pack” on

page 43

“Amending the base language”

on page 43

“Synchronizing Report Models”

on page 46

“Specifying a language for a

user” on page 46

Reapply customised functions and stored procedures “Reapplying customized

functions and stored

procedures” on page 46

Configure online help to access SunSystems help “Configuring Online Help” on

page 46

General post-upgrade tasks

If necessary, return the Auto Shrink and Recovery Model database options to their original values as

they were prior to carrying out the upgrade prerequisites.

Caution: It is recommended that Autoshrink be set to Off.

Ensure that all of the SunSystems databases have their compatibility levels set to your installed

version of MS SQL Server for optimum performance.

Synchronising BU Groups

If you have more than one BU Group, then all BU Groups will be set to offline in BUA.


33

Synchronise BU Groups.

Synchronize each business unit in each BUGroup. When all of the business units have been

synchronized, click Convert to convert the Store BUG to a Live BUG. Repeat this for each BU

Group.

See the SunSystems Administrator Help for details of “Synchronizing a Business Unit”.

Checking the filter log file

Each filter is checked during the upgrade process and logs are produced. Filter selection lines that

reference non-existent function entries are deleted. Details of all deletions are recorded in

FiltersToBeInvestigated.log, located in the folder selected earlier. Any filters in these logs require

attention within Filter Designer (FLD).

Checking the drill log file

Each Drill is checked during the upgrade process and logs are produced. Drills that reference non-

existent filters and/or non-existent filter types are recorded in Drillstobeinvestigated.log, located in

the folder selected earlier.

Checking the forms log file

1 Work through any forms listed in FormUpgradeDetail.log, and use Form Designer to make all

necessary amendments. Ensure all forms are checked back into the server after amendment.

2 Use Form Designer to open any customized forms for the Control Desks Override Batch

Parameters (CDOBP) function. If upon opening a form a message is displayed advising that a

control has been removed, add the control to the form. When the control is added all the

available data item options are shown in the control. If all options are not required, from the Edit

menu select Data Item Values and restrict options as required.

Caution: If the cause of problems is not immediately obvious when forms are opened in Form

Designer, it is recommended that offending data items are deleted and then reapplied.

Checking Ports

Ensure that any non-default port numbers configured on an existing system remain intact following

the installation of SunSystems v6.3.

Recreate Indexes

Verify, and where necessary recreate, any user-developed indexes and/or triggers on tables.

Checking the data dictionary filegroup settings log

When upgrading to SunSystems v6.3, existing filegroups for data dictionary tables are retained

where the information is available. However, if this is not possible, the default filegroups are used.

Therefore, if you use filegroups, it may be necessary to move data dictionary tables to the filegroups

you require manually.

You are advised to check the data dictionary filegroup settings in InstallLog.txt, located in the

destination folder you specify during installation. Determine which, if any tables are affected and if

the default location is satisfactory. For example, if the default filegroup is used the InstallLog.txt

contains line(s) similar to the following:

D-MM-YYYY HH:MM:SS Default filegroup settings used: table AAAA assigned to Data

Filegroup BBBB and Index CCCC

If the default location is not satisfactory move the tables manually using SQL Server Management

Studio.

Caution: Filegroup settings are held on SQL_OBJ_REGISTRY, the installation uses these settings to

determine where the data dictionary tables are located. Therefore, if you move tables

manually you must also update this table or a new table is created during the next

upgrade.

Importing Transfer Desk profiles

Import your Transfer Desk Profiles that were exported prior to upgrade by using the Configuration

Import function in Transfer Desk. This process also upgrades your profiles.

Caution: If you did not carry out a repository cleardown prior to upgrading, you should run

Configuration Cleardown before performing the Import. To do this, you must be a member

of the SunSystems Connect group.

Caution: When using Configuration Import to import profiles from previous versions of SunSystems,

there may be cases where profiles are not imported. This is due to differences in

parameter values between SunSystems versions. For example, in SunSystems 6.3, a

parameter may take the values 0/1 but in previous versions took the values Y/N.

As the structure of some payloads has changed in SunSystems 6.3, there may also be

issues with filters and transformations.


35

Including custom SQL scripts for the creation of new business

units

You can include custom SQL scripts into the creation of a new business unit. This can be very

useful, especially if you have developed view-based reports. To do this:

Create the view. Instead of your named business unit such as PK1 use the business unit

ZZZ.

Save this file in the PROCS folder. The default location for this folder is C:\Program

files\Infor\SunSystems\_SQL.

Create a file called BUS_CUSTOM_UPDATE.INI directly in the_SQL folder. This file should contain

the following line: 0,PROCS\ZZZ_MYVIEW.SQL where ZZZ_MYVIEW.SQL is the name of the

saved file in the PROCS folder.

Migrating Custom Reports

1. In SunSystems 6.3, use Report Models (RMD) to upgrade the report model.

2. Use Report Manager (RMA) to import your reports to SunSystems 6.3. It will highlight which

reports have failed.

3. Use Report Designer (RED) to review the migrated reports, and to highlight the changes of the

stored procedure in the SunSystems Domain database.

Creating reports

1. Identify the SunSystems v6.3 example reports you wish to deploy (with or without

customization).

2. Use Report Administrator to create and configure security for the desired folder structure and

copy the examples to those folders.

3. Use Report Designer to customize examples to your own requirements, or to create new reports

from scratch.

Caution: We recommend that process reports be deployed to the Central Files folder for ease of

configuration of Document Format records. The same approach can be adopted for

Reference data reports if you wish to run them from the form menu.

Caution: You should not configure an operational deployment of SunSystems Reporting to

reference the reports in the example folders, as these may be overwritten by future

upgrades or patch sets.

(see Installation Guide section on Reporting)

To complete the setup of SunSystems Reporting, refer to the SunSystems Reporting Services

section in the SunSystems Installation Guide.

Reinstalling SunSystems Web

SunSystems Web is reinstalled with SunSystems 6.3 rather than upgraded. This means nothing is

required to be upgraded, or carried over to the test system.

1 If you made a note of any custom settings within the server-custom.properties file prior to

initiating the upgrade process, you must reapply them in the new installation.

2 Ming.leTM considerations: In Infor Application Deployments > Infor SunSystems, amend the

application version and host name (if changed).

3 Test SunSystems Web through a browser and Ming.leTM (if being implemented).

Granting Function Permissions for Report Models (RMD), Report

Designer (RED) and Report Schedules (RMC)

To access Report Models (RMD), Report Designer (RED) and Report Schedules (RMC) you must

enable function permissions and add shortcuts for these functions to your User Group’s menu.

Access to these functions is controlled via membership of special Reporting security groups.

Therefore, to access these functions, users must belong to a user group with function permissions

enabled for Report Models and Report Designer, and also belong to the relevant special Reporting

security group.

Membership of the relevant special Reporting security group is specified by user, providing only

selected users with access to Report Models and Report Designer. This can result in a user group

containing users both with and without access to these functions.

Following completion of the upgrade, administrators may manually enable Function Permissions,

and create menu shortcuts only for users with access to Report Models and Report Designer.

However, others within the same user group, who are not members of the relevant special Reporting

security group, will still be able to see the function in their menu but will receive a message denying

access if they click on the function shortcut.

To reduce the possibility of this occurring, do not create the menu items for the entire user group but

rather just enable function permissions so shortcuts can be added as Favourites by users who are

members of a relevant special Reporting security group.

Nevertheless, such shortcuts can still be added to Favourites by non-members of the special

Reporting security groups. To avoid this, it is preferable to create separate user groups for members

and non-members of the relevant special Reporting security group.

You will need to add function permissions to a Scheduler’s user group before they are able to

access Report Schedules (RMC) from the menu. If only some members of the user group are

provided with access to schedules, and those without access do not wish to see it on a default menu


37

or to be able to add it to Favourites, then again, we recommend that the separate user groups are

created for members and non-members.

Installing languages

The SunSystems upgrade sets the base language to 1, which means SunSystems is upgraded as

English-only. Other languages must be installed using the Language Deployer after the upgrade

has completed. Ensure the language required is available for deployment.

Note: SunSystems can support up to 99 language versions; the base language and 98 additional

languages.

Language installation tasks

Task References

Install a language using the relevant Language Pack “Installing a Language Pack” on

page 44

Amend the base language and update the base

language descriptions

“Amending the base language”

on page 44

Regenerate menus to display the new language

“Regenerating menus with a new

language” on page 45

Synchronize report models “Synchronizing Report Models”

on page 46

Specify a language for each user in User Manager “Specifying a language for a

user” on page 46

Installing a Language Pack

Refer to the Language Pack Installation Note for instructions on how to install your specific

language. The language must be included in the serialization details.

Note: If you make changes to existing business units you must synchronize business units. Go

to Report Models (RMD) and click Synchronize.

Amending the base language

1 Go to SunSystems navigator and open Business Unit Administration (BUA).

2 Select a Business Unit or Business Unit Group to amend.

Note: All business units in the Business Unit Group must be offline.

3 Select Actions > Advanced > Amend a Base Language

4 Complete this information:

Business Unit Group

Automatically populated with the selected Business Unit Group.

Business Unit Code

Automatically populated with the selected Business Unit.

Language Code

Select a language from one of the installed languages.

Update System Text

Select Yes to update system text using the language defined for each Business Unit.

Existing text will be overwritten. The default value is No.

5 Click OK.

6 Check that these columns contain the correct language:

- XXX_DRILL_ASSOCIATES(DRILL_DESCR)

- XXX_ROLE(DESCR)

- XXX_NUM_STREAM_HDR(DESCR)

- XXX_NUM_STREAM(DESCR)

- XXX_FIN_RPT_COL_HDGS(HEADING_1,HEADING_2,HEADING_3,HEADING_4)

- XXX_BDGT_DEFN(DESCR)

- XXX_ALLOCN_IND(NAME,S_HEAD)

- XXX_TXN_REF_FMT(DESCR)

7 Repeat for each business unit group.

Regenerating menus with a new language

1 Go to SunSystems navigator and open User Group Menu Designer (UGM).

2 Select a user group.

3 Select Menu > Change Language.

4 Select a language and click OK.

5 Select Menu > Synchronise to Permissions. This must be run for each modified user group.


39

6 Click Save to save your changes, then exit User Group Menu Designer.

Synchronizing Report Models

If data changes are made to existing Business Units, they must be synchronized in Report Models.

Note: Only Live Business Units can be synchronized.

1 Go to SunSystems navigator and open Report Models (RMD).

2 Select the Business Units to be updated.

3 Click Synchronize.

If the process completes successfully, the status is set to Synchronized and the Last Change Date

Time and Last Changed By columns are updated. If the synchronization is unsuccessful, the status

is set to Failed Synchronization.

Specifying a language for a user

1 Go to User Manager.

2 Select a user.

3 Select Edit User… > Operator.

4 Click Language to select a language.

5 Click OK.

Reapplying customized functions and stored procedures

Reapply any verified customized functions, stored procedures, triggers or views used for reports. Some functionality may be superceded by updates to SunSystems 6.3.0.

Configuring online help

In SunSystems 6.3, online help is available to read from a dedicated help server, docs.infor.com.

After installation, use Configuration Manager to set the location for the help server. You can

reference docs.infor.com, which provides the latest version of SunSystems help. Alternatively, you

can install a copy of the help on a local server.

1. In SunSystems Navigator, go to CGM > Online Help.

2. Configure the machine settings:

Scope

Select the servers for which the machine settings are relevant. To apply machine settings to all

servers, select DEFAULT. To apply machine settings to a specific server, select the servername.

Basic Help Locale

Select the locale of the help. The default value is en-us.

URL of Help

Specify the absolute or the relative URL from SunSystems. The default value is

https://docs.infor.com.

3. Save your changes.

4. Use the Restart Services application to reset the SunSystems services.

https://docs.infor.com/


41

Appendix A Database administration A

Database administration is implemented through Database Utiltiies.

To access Database Utilities, run the SunSystems v6.3 ISO and go to Install SunSystems > New

Installations & SunSystems v6 upgrades > Database Utilities.

Note: You can also navigate the DVD. Go to SqlServerDatabaseUtilities and run

DBUTILITY.exe.

Alternatively, download the latest Database Utilities from www.inforxtreme.com.

SunSystems Database Utilities > Create

A new SunSystems Domain database

The steps required to create a new SunSystems domain database on the local machine. Refer to the

SunSystems Installation Guide for full details.

A new SunSystems Business Unit Group

The steps required to create a new SunSystems Business unit group. Within this section you have

the option to create a live, store or archive business unit group. Refer to the SunSystems Installation

Guide for full details.

A new SunSystems Security database

The steps required to create a new security database. Refer to the SunSystems Installation Guide

for full details.

A pre-configured SunSystems Business Unit Group

Import the PK1 database. The data in the databases is identical but the databases all have a different collation. Refer to the SunSystems Installation Guide for full details.

SunSystems Database Utilities > Upgrade

Pre-Upgrade Checks

Check a SunSystems Business Unit Group to ensure that there are no outstanding pre-upgrade

checks that need to be processed before an upgrade is run. The check prevents the upgrade from

progressing if any pre-upgrade check fails.

The checks performed when upgrading from SunSystems 6.2.1:

Checks for the existence of any entries in the data audit

The checks performed when upgrading from SunSystems 6.1.1:

Checks for the existence of any held journals

Checks for the existence of any entries in the data audit

Checks for the existence of any outstanding authorizations

Checks for duplicate bank sub code and supplier code combinations

Checks for invalid Document Format Codes on Payment Profiles

Remove work tables

This will remove work tables and views from the database which can greatly improve the

performance of the Upgrade Business Unit section of the upgrade process.

A SunSystems Security database

Upgrade the security database.

A SunSystems Domain database

Upgrade the domain database.

A SunSystems Domain database forcing all scripts to be reapplied

Upgrade the Domain database and force all scripts to be applied to the database whether they have

changed or not. This will be slower to run and should only be used under instruction from Infor

Support or your channel partner.

A SunSystems Business Unit Group

Upgrade a Business Unit Group database. From the table, select the Business Unit groups you want

to upgrade.


43

A SunSystems Business Unit Group forcing all scripts to be reapplied

Upgrade a Business Unit group database and force all scripts to be applied to the database whether

they have changed or not. This will be slower to run and should only be used under instruction from

Infor Support or your channel partner.

Custom forms

Upgrade your custom forms. Refer to the Introduction section for the supported upgrade paths.

SunSystems Database Utilities > Domain DB Utilities

Add a SunSystems Business Unit Group to a SunSystems Domain

Add an existing business unit group to an existing domain.

Remove a SunSystems Business Unit Group from a SunSystems Domain

Removes a SunSystems database from a SunSystems domain and optionally delete the database if

it is held on the local machine. Refer to the SunSystems Installation Guide for full details.

Recover Business Unit Links

Reset all your business unit links between the SunSystems Domain database and the attached

SunSystems Data databases.

Business Unit groups parameter maintenance

Change the name of a Business Unit Group.

Query Database file groups

List the filegroups referenced in the SQL_OBJ_REGISTRY table.

Caution: If you use filegroups, we recommend that you check that all references to filegroups

actually exist on the new machine, otherwise the upgrade will fail.

Re-link all the SunSystems Business Unit Groups to a SunSystems Domain

Re-link the existing SunSystems Business Unit Groups to the existing SunSystems domain

database. This utility allows you to move the SunSystems domain database and SunSystems

Business Unit Groups from one server to another.

This works for all versions of SunSystems that are covered in the Introduction section.

Caution: If the Microsoft SQL Server master database uses a binary sort order, then the case of the

domain groups must be consistent with the case of the group names in Active Directory.

For example, if the group names in Active Directory are in uppercase, then the domain

groups must be also be specified using uppercase, e.g.: INFOR\username.

Load Difference tables

Reload the data dictionary difference tables in a specified SunSystems database with the data

dictionary differences from a previous version of SunSystems. This information is required for a

Custom Upgrade and is used in conjunction with the custom form upgrade process. The option

enables you to create a SunSystems database, either from scripts or by attaching a preconfigured

database, and to upload the difference tables for the version that you are upgrading from. You must

specify the log file folder location and the domain database information. A list of SunSystems

databases that are in the domain database is displayed. Select the required database and the

version of the data to be loaded in the difference tables.

Structural Integrity Check – Domain

Perform a structural integrity check of all tables in the selected SunSystems Domain database. This is the same check that is performed as part of the upgrade process.

Data Integrity Check – Domain

Check the referential integrity of the data between tables in the domain database and report any issues found in the DOMN_RI_ERR table.

SunSystems Database Utilities > SunSystems DB Utilities

Structural integrity check

Perform a structural integrity check of all tables in the selected SunSystems Business Unit Group

database. This is the same check that is performed as part of the upgrade process.

Referential Integrity Check – SunSystems Business Unit Group only

Check the integrity of a SunSystems Business Unit Group and report any issues found. These

results should not stop an upgrade from running but should be addressed.

Note: This check should be run before you upgrade, so that any errors can be identified before a

full upgrade. The check takes longer to complete for larger databases.

Query database file groups

List the filegroups referenced in the SQL_OBJ_REGISTRY table.

Caution: If you use filegroups, we recommend that you check that all references to filegroups

actually exist on the new machine, otherwise the upgrade will fail.


45

SunSystems Database Utilities > Form Actions

Import forms into a SunSystems Domain

Imports forms into a SunSystems domain database.

Force Import forms into a SunSystems Domain

Imports forms into the Domain database even if they may have been previously imported.

Export forms from a SunSystems Domain

Exports forms from a SunSystems domain database.

Remove forms from a SunSystems Domain

Removes forms from a SunSystems domain database.

SunSystems Database Utilities > Security DB

Grant permission to Security DB

Grants the Windows Service Groups access to the Security database.

Appendix B Tips on installing and

configuring Microsoft SQL Server B

Installation

Microsoft SQL Server and SunSystems databases should ideally be installed on three different disk

sets as follows:

Operating system, including SQL server

Temp database, Domain database and Security database

SunSystems database.

Caution: The tempdb database should have one file defined per CPU in use. This helps to alleviate

contention in the tempdb database.

MS SQL Server Tempdb files

It recommended that you have one Tempdb file per processor. This is considered best practice, and

significantly reduces the contention in Tempdb. Microsoft SQL Server 2016 attempts to do this by

default. Further information can be found at http://msdn.microsoft.com/en-us/library/ms175527.aspx

Instance properties

Parallelism

As default, leave this set with a wait time of 5 seconds. In some installations, the settings are

modified by either increasing the wait time or by reducing the number of processors, as this may

improve performance under certain circumstances.

Database properties

Files

Autogrowth: An initial setting of 10 percent with unrestricted growth should be set. This

should be reviewed on a regular basis.

http://msdn.microsoft.com/en-us/library/ms175527.aspx


47

Options

Recovery Model: Unless your disaster recovery plan includes backing up the transaction log

more than once a day, set this to Simple as a default.

Auto close: Set to False.

Auto Create statistics: Set to True.

Auto Shrink: Set to False.

Auto Update Statistics: Set to True.

Maintenance plans

1. Backup, including deletion of backups, over x days old – daily.

2. Check database integrity – daily.

3. Rebuild Index Task – once a week: In SQL Server you can rebuild indexes whilst the database is

in use. Consider the fill factor that you may wish to use.

4. Shrink Database Task – once a week. If you perform the shrink task, you must then reindex the

database.

5. Update Statistics Task – once a week.

Scheduled tasks

Two maintenance procedures that are accessible from Business Unit Administration (BUA) in

SunSystems can be run as scheduled tasks.

Clear Work Tables

Drops temporary work tables and views. If run prior to the upgrade, temporary work tables and views

do not need to be removed during the Business Unit upgrade, so performance of this section of the

upgrade is improved. Clear Work Tables runs the stored procedure SSP_DROP_WORK_TABLES

and it is recommended that it is configured as a scheduled task.

1. Go to Business Unit Administration (BUA) and select the business unit.

2. Select Actions > Advanced > Clear Work Tables.

3. Specify the Business Unit Code.

4. In Transfer Desk Retain Days specify the number of days to retain the transfer desk temporary

data.

5. In Control Desk Retain Days specify the number of days to retain the control desk temporary

data.

6. In Recon Mgr Retention Days specify the number of days to retain the reconciliation manager

temporary data.

7. In Control Desk Iface Retain Days specify the number of days to retain the control desk

interface data.

8. Click Run to clear the work tables.

Housekeeping

Deletes entries in the ZZZ_LDG_DETAIL table. It can take a long time to complete, so it is

recommended to set this up as a scheduled task. Housekeeping runs the stored procedure

SSP_HOUSEKEEPING.

1. Go to Business Unit Administration (BUA) and select the business unit.

2. Select Actions > Advanced > Housekeeping.

3. Specify the same business unit code as specified in Business Unit Administration (BUA).

4. In Ledger Dtls Retention Months specify the number of months to retain the ledger details.

a Ledger detail rows are cleared only if the source transaction is complete and the value

POSTED_TO_LI_IND is 1, 3 or 8. These tables are cleared:

ZZZ_LDG_DETAIL_LI_XREF

ZZZ_LDG_DETAIL_LAD

ZZZ_LDG_DETAIL

5. In Interface Tbls Retention Weeks specify the number of weeks to retain the interface tables

data. These tables are cleared:

ACNT_PYMT_IFACE

ASSET_DISPOSAL_IFACE

ASSET_STATUS_IFACE

CALC_DEP_IFACE

CASH_SUMMARY_IFACE

DAYBOOK_IFACE

GEN_PYMT_IFACE

LDG_REVAL_IFACE

PMD_RDS_IFACE

PMT_RPTG_IFACE_TBL

TAX_RPTG_IFACE_FIN

PMD_RPTG_IFACE_TBL

TAX_RPTG_IFACE_SC

TAX_RPTG_IFACE_SOP

PMD_RPTG_IFACE_TBL


49

TRIAL_BAL_IFACE

TXN_MATCH_IFACE

VOID_PYMT_IFACE

6. In Del Fin Rpts Retention Weeks specify the number of weeks to retain the financial reporting

tables data. These tables are cleared:

FIN_ANL_RPT

FIN_STMNT_RPT

FIN_TBL_RPT

7. Select the Del BU Tmp Tbl Retention Flag to retain business unit temporary tables data.

8. In Del BU Tmp Tbl Retention Weeks specify the number of weeks to retain the business unit

temporary tables data. These tables are cleared:

BUCPY_STD_TEXT

BUCPY_TEMP_DAG

BUCPY_TEMP_FILTER

BUCPY_TEMP_OPR

BUCPY_TEMP_OPR_GRP

BUCPY_XFER_TBL_LIST

BU_TEMPLATE_PARAMS

9. In Del BU Wrk Tbl Retention Weeks specify the number of weeks to retain the Data Dictionary

difference tables data. These tables are cleared:

ZZZ_AUTHORISTN_SET_BANK

ZZZ_AUTHORISTN_SET_PAY

ZZZ_BILLING_LINK_ADJUST

ZZZ_COSTING_ITEM_COSTS

ZZZ_COSTING_UD_COSTS

ZZZ_COSTING_WORK

ZZZ_COSTING_KEY_INFO

ZZZ_CURRENTLY_SELECTED

ZZZ_DOC_FMT_HLD

ZZZ_GEN_INVY_CNT_WRK_1

ZZZ_LINK_CHECK

ZZZ_NOTE_DETAIL_TEMP

ZZZ_NOTE_LDG_TEMP

ZZZ_NOTE_TEMP

ZZZ_PSTG_ERR_MSG

ZZZ_PSTG_ERR

ZZZ_PSTG_WRK_TBL_NOTE

ZZZ_PSTG_WRK_TBL

ZZZ_SAPYDDB

ZZZ_SAPYPAY

ZZZ_VCHR_WRK

10. In Del Other Tbl Retention Weeks, specify the number of weeks to retain the business unit

work table data. These tables are cleared:

DAG_TEMP

OPR_BU_PERD

OPR_SESSION

RECON_MGR_TEMP_LAD

RECON_MGR_TEMP

11. Click Run to start the housekeeping process. These tables are cleared:

DDE_USER_LABEL_WRK

OFCD_WORK_FILE

RI_ERR

Appendix C Pre-upgrade checking

examples C

Structural Integrity Check

Example:


51

In the SunSystems Database Utilities - Progress Monitor, the following error is displayed in the

Details dialog:

Template Generation, Corrupt Business Unit: TST (-1)

This is one type of error that might be reported when you run this check. TST is the business unit

code in this example.

The reason behind this error is that a business unit (TST) has been set up but not created. The

easiest way to resolve this is to delete the business unit. Other types of errors are more serious

because it will indicate that a table or column has been deleted or modified. If this is the case, this

must be reported to your regional support office.

If just foreign keys issues are reported then these will be resolved as part of the upgrade process, and will not stop the upgrade from processing. If you have any issues with this, please contact your regional support office.

Pre-Upgrade Checks

Example Pre-upgradeCheck.log for SunSystems 6.1.1 upgrade:

ERROR 14:09:55,710 - [Pre-upgradeCheck.log]

BUC TABLE NAME DATA

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

PK1 Data Audit All Data Audit

data must be cleared down before the upgrade can continue

PK1 Held Journals Hold Ref

Number = 10 Transaction Reference test




Number = 14 Transaction Reference


Number = 5 Transaction Reference Ref21







PK1 Authorisations Ref Number =

13 Comment aca by ll1

PK1 Authorisations Ref Number =

15 Comment maching

PK1 Authorisations Ref Number = 2

Comment teate


Comment teate


Comment Ledger Import journal requires authorization. Journal was

imported on 2016-10-27 at 17:52:30. Journal Type: FGJ


Comment payment for authorization by LL1

PK1 Invalid Payment Report Format Code under Payment

Profiles Profile Type=BANK

PK1 SUN_DATA blocks - PK1_LDG_DEFN Error Code:245

, Error Message:Conversion failed when converting the varchar value

'haggfgaa' to data type int.

PK1 SUN_DATA blocks - PK1_BDGT_DEFN Error Code:547

, Error Message:The INSERT statement conflicted with the CHECK constraint

"CK__PK1_BDGT___STATU__72DD1525". The conflict occurred in database

"SunSystemsData_v611", table "dbo.PK1_BDGT_DEFN_TEST", column 'STATUS'.

PK1 SUN_DATA blocks - PK1_FIN_RPT_COL_HDGS Error Code:547

, Error Message:The INSERT statement conflicted with the CHECK constraint

"CK__PK1_FIN_R__STATU__7D5AA398". The conflict occurred in database

"SunSystemsData_v611", table "dbo.PK1_FIN_RPT_COL_HDGS_TEST", column

'STATUS'.

PK1 SUN_DATA blocks - PK1_JNL_PRESETS Error

Code:8114 , Error Message:Error converting data type varchar to

numeric.

PK1 SUN_DATA blocks - PK1_CORP_ALL_BAL_CHNG Error Code:245

, Error Message:Conversion failed when converting the varchar value

'P00078d' to data type int.

ERROR 14:09:57,632 - [Pre-upgradeCheck.log]

BUC TABLE NAME DATA

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






53

Before an upgrade will complete, any issues that are reported here must be cleared using the

SunSystems application. If you have any issues with clearing this report using the SunSystems

application, please contact your regional support office.

Referential Integrity Check – SunSystems Data

Example:

In the SunSystems Database Utilities - Progress Monitor, the following error is displayed in the

Details dialog:

Referential integrity errors exist. See table RI_ERR in SU_DATADB for details.

You must review any entries in this table (RI_ERR), which resides in the SunSystems Database. The data should be tidied up but it is not important for the upgrade process. Any data that appears here could affect the running of SunSystems.

Appendix D Database upgrade – example

procedure D

If you are upgrading a standard installation from SunSystems v6.1.1 or v6.2.1 to SunSystems v6.3,

the following example database upgrade steps are recommended. The exact procedure is likely to

be different for each SunSystems installation; these steps are intended as a general guide and

should not be considered a definitive list:

1. Restore SunSystems Data databases in SQL 2014 or SQL 2016 – ensuring that the compatibility

mode is set to the database level of the originating system. For example, SunSystems 6.3

should be sql2014.

2. Restore SunSystems Domain database in SQL 2014 or SQL 2016 - ensuring that the

compatibility mode is set to the database level of the originating system.

3. Ensure that the installation of sql server has its data access option set to true. Example

command:

- exec sp_serveroption <instance name>, 'data access', 'true'

4. Run Database Utilities > Domain DB > Re-link SunSystems Business Unit Groups to a

SunSystems Domain. Ensure each business unit group is relinked.

5. Check the Microsoft SQL Server Recovery Model and set to Simple if not already on all

databases involved in the upgrade.

6. Run Database Utilities > Upgrade > Pre-Upgrade Checks.

7. Run Database Utilities > Upgrade > Remove work tables.

8. Run Database Utilities > Domain DB > Structural Integrity Check - Domain.

9. Run Database Utilities > SunSystems DB > Structural Integrity Check.

10. Run Database Utilities > SunSystems DB > Referential Integrity Check – SunSystems

Business Unit Group Only.

11. Run Database Utilities > Domain DB > Query Database file groups.

12. Run Database Utilities > SunSystems DB > Query Database file groups.

13. Take a fresh backup of the databases. If issues occur during the upgrade process you do not

have to repeat steps 1 to 13 again.

14. Run Database Utilities > Upgrade > A SunSystems Security Database.

15. Run Database Utilities > Upgrade > A SunSystems Domain Database.


55

16. Run Database Utilities > Upgrade > A SunSystems Business Unit Group. Multiple business

unit groups can be upgraded simultaneously.

17. If any issues occur, restore the backups taken in step 13. Resolve the issues and then rerun

steps 14 to 16.

Appendix E Example report equivalence E

Caution: Most of the SunSystems Enterprise report files are exact equivalents of the corresponding

SunSystems v5 reports; however, the report file names and descriptions that are listed in

italics are close matches to the v5 counterparts.

SunSystems 5.4.1 File Name Short Description SunSystems Enterprise File Name (.srdl)

Description

AccountingVoucher_86.rod Accounting Voucher FTAV1 Accounting Voucher

AccountTaxListingSales.rox Tax Listing Summary FPTR1 Tax Listing Summary

Acnt_Anal_CDR_nonBU.rox Account Listing for any Business Unit FTAL1 Account Listing with Analysis

Acnt_Anal_CDR_nonBU-CV4_5.rox Account Listing for any Business Unit with 4th currency

FTAL1 Account Listing with Analysis

Acnt_Anal_CDR_PKP.rox Account Listing for PKP FTAL1 Account Listing with Analysis

Acnt_Detail_CDR_PKP.rox Account Detail Listing for PKP FTAL2 Account Detail Listing

Acnt_Detail_CDR_Streamlined.rox Streamlined Account Listing FTAL2 Account Detail Listing

Acnt_List_Arch.rox Account Listing including Archived Transactions

n/a n/a

Act_Bud_Var.rox Actual vs Budget Variance Analysis FTVA1 Account Variance Analysis

AddressBook.rox Address Book Static Data XRAS1 Address Setup

AgedAnalBackDueBaseDet_CDR.rox Aged Analysis Detail FTGA1 Aged Analysis Detail Listing

AgedAnalBackDueBaseDet_CDR _Streamlined.rox

Streamlined Aged Analysis Detail FTGA1 Aged Analysis Detail Listing

AgedAnalBackDueBaseRank _CDR.rox

Aged Analysis Summary Ranked FTGA1 Aged Analysis Detail Listing

AgedAnalBackDueBaseSum_CDR.rox Aged Analysis Summary FTGA1 Aged Analysis Detail Listing

AgedAnalForDueBaseDet_CDR.rox Forward Aged Analysis Detail FTGA2 Aged Analysis Detail - Forward

AgedAnalForDueBaseDet_CDR _Streamlined.rox

Streamlined Forward Aged Analysis Detail

FTGA2 Aged Analysis Detail - Forward

AgedAnalForDueBaseSum_CDR.rox Forward Aged Analysis Summary FTGA2 Aged Analysis Detail - Forward

Allocation-Calendar.rox Allocation Calendar Static Data CRAC1 Corporate Allocation Calendar Setup

Allocation-Setup.rox Allocation Detail Static Data CRAL1 Corporate Allocation Setup

AllocationsListing.rox Account Allocation Listing FPAA1 Account Allocation Listing

AnalysisLayouts.rox Analysis Layouts Static Data FRAL1 Financial Analysis Layout Setup

Asset_book.rox Fixed Asset Book ATAB1 Asset Book Listing

Asset_Register_PKP.rox Asset Register Listing for PKP ATAR1 Asset Register Listing

Asset_Status_CDR.rox Asset Status Listing APAS1 Asset Status Listing


57


Description

AssetBudRec2.rox Asset Budget Record Static Data ARAB1 Asset Budget Setup

AssetNotes.rox Asset Notes Static Data ARAR2 Asset Note Setup

AssetPostingPresets.rox Asset Posting Presets Static Data ARAR3 Asset Posting Preset Setup

AssetRecords2.rox Asset Record Static Data ARAR1 Asset Record Setup

AuthAuditTrail.rod Authorization Audit Trail FTAA1 Authorization Audit Trail

BankDetails.rox Bank Details Static Data XRBD1 Bank Details Setup

BankJournalListing_86.rod Bank Journal Listing FTBL1 Cash in Bank Journal Listing

BatchHist.rox Inventory Batch History ITBH1 Inventory Batch History

burstexample.rox Actuate specific bursting example FTAL3 Account Listing with Bursting

BusinessUnit.rox Business Unit Static Data XRBU1 Business Unit Setup

CashJournalListing_86.rod Cash Journal Listing FTCL1 Cash Journal Listing

CDRCreditNote.rox Sales Credit Note SPCN1 Sales Credit Note Document

CDRInvoiceReg.rox Purchase Invoice Register PTIR1 Purchase Invoice Register

CDRMoveList.rox Inventory Movement Listing ITML1 Inventory Movement Listing

CDRPIListing.rox Purchase Invoice Listing PTIL1 Purchase Invoice Listing

CDRPOListing.rox Purchase Order Listing PTOL1 Purchase Order Listing

CDRPRNListing.rox Purchase Returns Listing PTRL1 Purchase Returns Listing

CDRPurchaseOrder.rox Purchase Order PPPO1 Purchase Order Document

CDRSalesAck.rox called from order entry SPOA1 Sales Order Acknowledgement

CDRSalesInvoice.rox Sales Invoice SPSO1 Sales Invoice Document

CDRSIListing.rox Sales Invoice Listing STIL1 Sales Invoice Listing

CDRSOListing.rox Sales Order Listing STOL1 Sales Order Listing - Full

CDRSRNListing.rox Sales Returns Listing STRL1 Sales Returns Listing

ChartofAccounts.rox Chart of Accounts Static Data FRCA1 Chart of Accounts Setup

ConversionDaily.rox Daily Conversion Rates Static Data XRDC1 Currency Daily Conversion Rate Setup

ConversionError.rox Conversion Error Listing FPRE1 Conversion Error Listing

ConversionPeriod.rox Period Conversion Rates Static Data XRPC1 Currency Period Conversion Rate Setup

CorpAlloc.rox Corporate Allocation Run CPAR1 Corporate Allocation Run

CreditCheckHistory.rox Credit Check History STCC1 Credit Check History

CurrencyCodes.rox Currency Codes Static Data XRCC1 Currency Code Setup

Customer.rox Customer Static Data XRCS1 Customer Setup

CustRtnsList.rox Sales Returns Listing by Customer STRL2 Sales Returns Listing by Customer

CustSalesList.rox Sales Listing by Customer STCS1 Sales Listing by Customer

DataAccessGroup.rox Data Access Group Setup XRDA1 Data Access Group Setup

DepreciationTables.rox Depreciation Tables Static Data ARDT1 Depreciation Table Setup

DepreciationTablesHeadings.rox Depreciation Tables Headings Static Data

ARDH1 Depreciation Table Heading Setup

DepreciationTimingRules.rox Depreciation Timing Rules Static Data

ARDR1 Depreciation Timing Rule Setup

EP_RS_Report.rox Event Profile Details XPEP1 Event Profile Details


Description

ExpdItems.rox Inventory Expired Items Listing ITEI1 Inventory Expired Items Listing

FA3.rox Financial Analysis Summary FPFA1 Financial Analysis Output with 12 columns

fa3-12.rox Financial Analysis Summary with 12 columns

FPFA1 Financial Analysis Output with 12 columns

FA3-wide.rox Financial Analysis Summary with wide columns

FPFA1 Financial Analysis Output with 12 columns

FA-transactions.rox Financial Analysis Transactions FPFA1 Financial Analysis Output with 12 columns

Formula.rox Formula Static Data XRFS1 Formula Setup

FS2.rox Financial Statements Summary FPFS1 Financial Statements Output with 12 columns

fs2-12.rox Financial Statements Summary with 12 columns

FPFS1 Financial Statements Output with 12 columns

fs2-wide.rox Financial Statements Summary with wide columns


FS-transactions.rox Financial Statements Transactions FPFS1 Financial Statements Output with 12 columns

FS-transwide.rox Financial Statements Transactions with wide columns


FT3.rox Financial Tables Output FPFT1 Financial Tables Output with 12 columns

FT3-12.rox Financial Tables Output with 12 columns

FPFT1 Financial Tables Output with 12 columns

FT3-WIDE.rox Financial Tables with wide columns FPFT1 Financial Tables Output with 12 columns

GeneralLedgerListing_86.rod General Ledger Listing FTGL1 General Ledger Listing

HistoricInvyEval.rox Historic Inventory Evaluation ITHI1 Historic Inventory Evaluation

HistoricInvyEval-Cost.rox Historic Inventory Evaluation at Cost ITHI2 Historic Inventory Evaluation at Cost

InvCntListing.rox Inventory Count Listing IPIC1 Inventory Count Listing

invinq.rox Inventory Quantity ITIQ1 Inventory Quantity Listing

InvyCntEval.rox Inventory Count Evaluation ITIC1 Inventory Count Evaluation

InvyEval.rox Inventory Evaluation ITIE1 Inventory Evaluation

IRMAuditTrail.rox Inventory Revaluation Audit Trail ITIR1 Inventory Revaluation Audit Trail

IRMProfile.rox Inventory Revaluation Profile IRIR1 Inventory Revaluation Profile

IRMReval_Base_Detail.rox Inventory Revaluation Base Currency Detail

ITIR2 Inventory Revaluation Base Currency Detail

IRMReval_Base_Summary.rox Inventory Revaluation Base Currency Summary


IRMReval_Rptg_Detail.rox Inventory Revaluation Reporting Currency Detail


IRMReval_Rptg_Summary.rox Inventory Revaluation Reporting Currency Summary


IRMRevalException.rox Inventory Revaluation Exception Listing

ITIR3 Inventory Revaluation Exception Listing

Item.rox Item Static Data IRIS1 Item Setup

ItemCostssummary.rox Item Cost Summary IRIS2 Item Cost Summary


59


Description

ItemReference.rox Item Reference IRIS3 Item Reference Details

JH_Authstn.rox Held Journal Authorisation FTHJ1 Held Journal Detail Listing

JH-Analysis.rox Held Journal Analysis FTHJ1 Held Journal Detail Listing

JH-Detail.rox Held Journal Listing FTHJ1 Held Journal Detail Listing

JL-Detail-PymtStamp.rox Journal Listing FTJL2 Journal Detail Listing

JL-Detail-Unbal.rox Unbalanced Journal Listing FTJL2 Journal Detail Listing

Jnl_Anal_CDR_nonBU.rox Journal Listing for any Business Unit FTJL1 Journal Listing with Analysis

Jnl_Anal_CDR_nonBU-CV4_5.rox Journal Listing for any Business Unit with 4th currency

FTJL1 Journal Listing with Analysis

Jnl_Analysis_CDR_PKP.rox Journal Listing for PKP FTJL1 Journal Listing with Analysis

Jnl_Detail_CDR_PKP.rox Journal Detail Listing for PKP FTJL2 Journal Detail Listing

JournalAuditTrail.rod Journal Audit Trail FTJA1 Journal Audit Trail

JournalPostings.rox Journal Postings Listing FTJL3 Journal Postings Audit Listing

JrnlDefs.rox Journal Type Static Data FRJT1 Journal Type Setup

JrnlPresets.rox Journal Presets Static Data FRJP1 Journal Preset Setup

LedgerSetup.rox Ledger Setup Static Data FRLS1 Ledger Setup

LEMemoReceipt.rox Ledger Entry Memorandum Receipts FTJL4 Ledger Entry Memorandum Receipts

LIsummary.rox Ledger Interface Summary Listing ORLI1 Ledger Interface Setup

Locnsummary.rox Location Summary ORLS1 Location Setup

LQ1.rox Financials Ledger Inquiry FPLQ1 Ledger Inquiry Output

LQ2.rox Financials Journal Inquiry FPJQ1 Journal Inquiry Output

LQ3.rox Financials Asset Inquiry FPAQ1 Asset Inquiry Output

MObyLocPickingList.rox Movement Order Picking List by Location

IPPL1 Movement Order Picking List by Location

MObyLocTxnPickingList.rox Movement Order Picking List by Location with transaction reference generation

n/a n/a

MObyTxnPickingList.rox Movement Order Picking List with transaction reference generation

n/a n/a

MODespatchNote.rox Movement Order Despatch Note IPDN1 Movement Order Despatch Note

MOTXNDespatchNote.rox Movement Order Despatch Note with transaction reference generation

n/a n/a

MsgLogging.rox [Prints Report Debugging data in RPT_MSG table]

n/a n/a

MTSdetails.rox Movement Type Setup Details Static Data

IRMT1 Movement Type Setup

MTSsummary.rox Movement Type Setup Summary Static Data

IRMT1 Movement Type Setup

Operator.rox Operator Setup XROS1 Operator Setup

OperatorGroup.rox Operator Group Setup XROG1 Operator Group Setup

OperatorGroupPermissions.rox Operator Group Permissions Listing XROG2 Operator Group Permissions

Payment_Collection_Run _Streamlined.rox

Streamlined Payment Collection Run FPPC1 Payment Collection Run Listing


Description

Payment_Listing_Streamlined.rox Streamlined Payment Listing FTPL1 Payment Listing

Payment_Run_Streamlined.rox Streamlined Payment Run FPPR1 Payment Run Listing

PaymentReferences.rox Payment Reference Static Data FRPR1 Payment Reference Setup

PaymentRules.rox Payment Rules Static Data FRPP1 Payment Profiles Setup

PaymentTerms.rox Payment Terms Static Data FRPT1 Payment Terms Setup

PL-MC.rox Payment Listing FTPL1 Payment Listing

PL-MC-CV4_5.rox Payment Listing with 4th Currency FTPL1 Payment Listing

PostProv.rox Provisional Posting Listing FPTR3 Provisional Posting Listing

PTSdetails.rox Purchase Type Setup Details Static Data

PRPT1 Purchase Type Setup

PTSsummary.rox Purchase Type Setup Summary Static Data

PRPT1 Purchase Type Setup

PurchaseInvoiceStatus.rox Purchase Invoice Listing PTIL2 Purchase Invoice Status Listing

PurchaseOrderStatus.rox Purchase Order Listing PTOL2 Purchase Order Status Listing

PurchInvoiceCommitment.rox Purchase Invoice Commitment Listing

PTIC1 Purchase Invoice Commitment Listing

PurchOrderCommitment.rox Purchase Order Commitment Listing PTOC1 Purchase Order Commitment Listing

RCVNComplex_ItemCode.rox Received Note by Item PTRN1 Received Note Listing Sorting by Reference

RCVNComplex_Order.rox Received Note by Order PTRN1 Received Note Listing Sorting by Reference

RCVNComplex_ReceiptNotes.rox Received Note by Reference PTRN1 Received Note Listing Sorting by Reference

RCVNSimple.rox Received Note PPRN1 Received Note Document

RDS_REPORT.rox Rule Data Set Details XPRD1 Rule Data Set Details

reconciliation_manager.rox Reconciliation Manager FPRM1 Reconciliation Manager Listing

SAADPbase.rox Statement of Account in Base Currency

FPAD1 Statement of Account in Transaction Currency

SAADPtxn.rox Statement of Account in Transaction Currency

FPAD1 Statement of Account in Transaction Currency

SADBP.rox Daybook Listing FPDL1 Daybook Listing

saGDp.rox Payment Collection Run FPPC1 Payment Collection Run Listing

sagpNDR.rox Payment Collection Run Debit Exception

FPPE1 Payment Run Exception Listing

sagpp.rox Payment Run FPPR1 Payment Run Listing

sagpp-CV4_5.rox Payment Run FPPR1 Payment Run Listing

sagpp-CV4_5-nobase.rox Payment Run FPPR1 Payment Run Listing

SalesBlnktRenwl.rox Sales Contract Renewal Listing STCR1 Sales Contract Renewal Listing

SalesOrderStatusByItem.rox Sales Order Listing by Item STOL2 Sales Order Listing by Item

SalesOrderStatusByReference.rox Sales Order Listing by Reference STOL3 Sales Order Listing by Reference

SALIVRP.rox Ledger Import Validation Listing FPLI1 Ledger Import Validation Listing

SALIVRP-CV4_5.rox Ledger Import Listing with 4th Currency

FPLI1 Ledger Import Validation Listing

SALRP.rox Ledger Revaluation Listing FPLR1 Ledger Revaluation Listing


61


Description

SAPDP_S1.rox Remittance Advice Only for Separate Payments

FPPD1 Cheque and Remittance Advice

SAPDP_S2.rox Cheque Only for Separate Payments FPPD1 Cheque and Remittance Advice

SAPDP_S3.rox Cheque and Remittance Advice for Separate Payments

FPPD5 Cheque and Remittance Advice for Separate Payments

SAPDP_S3_top.rox Cheque and Remittance Advice at Top for Separate Payments

FPPD5 Cheque and Remittance Advice for Separate Payments

SAPDP1.rox Remittance Advice Only FPPD1 Cheque and Remittance Advice

SAPDP1TD.rox Remittance Advice Only FPPD1 Cheque and Remittance Advice

SAPDP2.rox Cheque Only FPPD1 Cheque and Remittance Advice

SAPDP20.rox Cheque Only with Nil and Negative Suppression


SAPDP3.rox Cheque and Remittance Advice FPPD1 Cheque and Remittance Advice

SAPDP3_2REM.rox Cheque and two remittances FPPD3 Cheque and Two Remittance Advice

SAPDP3_top.rox Cheque and Remittance Advice at Top


SAPDP30.rox Cheque and Remittance with Nil and Negative Suppression


SAPDP3-CV4.rox Cheque and Remittance Advice at Top


SAPDP3TD.rox Cheque and Remittance Advice at Top


SAPDP4_TextOutput.rox Payment Details Text Output FPPD2 Payment Details Text Output

SARBB1.rox Rebuild Budget Balances Exception Listing

FPRB1 Rebuild Budget Balances Exception Listing

SATBP.rox Trial Balance FPTB1 Trial Balance

SATMP.rox Transaction Matching Listing FPTM1 Transaction Matching Listing

SATMP-CV4_5.rox Transaction Matching Listing FPTM1 Transaction Matching Listing

SAVPP.rox Payment Voiding Listing FPPV1 Payment Voiding Listing

SecuritySettings.rod Security Settings XRUM1 Security Settings

SecurityUser.rod Security User XRUM2 Security User

SecurityUserGroup.rod Security User Group XRUM3 Security User Group

SerialNumHist.rox Serial Number History OTSH1 Serial Number History

SFCDP.rox Depreciation Calculation Listing APDC1 Asset Depreciation Calculation Listing

SFCDPA.rox Advanced Depreciation Calculation 1 n/a n/a

SFCDPR.rox Reduction Depreciation Calculation 1 n/a n/a

SFDIP.rox Asset Disposal Listing APAD1 Asset Disposal Listing

SObyCustPickList.rox Sales Order Picking List by Customer SPPL1 Sales Order Picking List by Customer

SobyCustTxnPickList.rox Sales Order Picking List by Customer with transaction reference generation

n/a n/a

SObyLocPickingList.rox Sales Order Picking List by Location SPPL2 Sales Order Picking List by Location


Description

SobyLocTxnPickingList.rox Sales Order Picking List by Location with transaction reference generation

n/a n/a

SODespatchNote.rox Despatch Note SPDN1 Sales Order Despatch Note

SOTXNDespatchNote.rox Despatch Note with transaction reference generation

n/a n/a

StatementLayouts.rox Financial Statements Layout Static Data

FRSL1 Financial Statements Layout Setup

StatementRows.rox Financial Statements Rows Static Data

FRSR1 Financial Statements Row Setup

STSdetails.rox Sales Type Setup Details Static Data SRST1 Sales Type Setup

STSsummary.rox Sales Type Setup Summary Static Data

SRST1 Sales Type Setup

SubsidiaryLedgerListing_86.rod Subsidiary Ledger Listing FTSL1 Subsidiary Ledger Listing

Supplier.rox Supplier Static Data XRSS1 Supplier Setup

TableColumns.rox Financial Tables Columns Static Data

FRTC1 Financial Tables Column Setup

TableFormats.rox Financial Tables Formats Static Data FRTF1 Financial Tables Format Setup

TableRows.rox Financial Tables Rows Static Data FRTR1 Financial Tables Row Setup

TaxDetails.rox Tax Details Static Data FRTD1 Tax Details Setup

TaxListing.rox Tax Listing FPTR2 Tax Listing

Trial_Balance_Streamlined.rox Streamlined Trial Balance FPTB1 Trial Balance

TxnList.rox Inventory Transaction Listing ITIT1 Inventory Transaction Listing

UDCostsdetails.rox Item User Defined Cost Details Static Data

ORUD1 Item User Defined Cost Setup

UDCostssummary.rox Item User Defined Cost Summary Static Data

ORUD1 Item User Defined Cost Setup

WarehouesCosting.rox Warehouse Costing ITWC1 Inventory Warehouse Costing

Whsesummary.rox Warehouse Summary Static Data ORWS1 Warehouse Setup

infor sunsystems upgrade guidewebasset.uxceclipse.com.au/wp-content/uploads/2017/...7 about this...

Documents