Unicode
All text data in SunSystems version 6.2.0 is now stored as Unicode. This enables mixed languages to be used in one Business Unit Group, one Business Unit, or even in a single field. It avoids issues with code page conversions when copying data between Business Units and Business Unit Groups. Previously unsupported languages such as Hindi, and unsupported characters such as the Azerbaijani schwa ‘ə’ are now supported. The full length of a text field can now be used for all languages,

Caution: The database collation must still be binary. Also Business Unit codes and Operator Ids can only contain upper case non-accented alphabetic ASCII or numeric characters.

Changes to the Domain Database
In SunSystems version 6.2.0, 101 tables have moved to the Domain Database, including most of the tables for the Filters, Forms, Dictionary, Hierarchies, Languages, Standard Text, and User Labels. Where these tables were previously auditable, this is no longer the case.

The benefit of this change is to simplify the implementation and maintenance of systems with multiple Business Unit groups.

Business Unit Administration
With the introduction of the Business Unit Administration (BUA) console in this release, SunSystems contains greatly enhanced data integrity checking as part of the BUA functionality. This requires some additional maintenance tasks, especially immediately after upgrade. This is to help ensure that data integrity is maintained.

English/European Languages Data Migration
Users wishing to migrate data from SunSystems version 4 to version 6.2.0 must follow the instructions in the Infor SunSystems Guide to Migrating Data From SunSystems 4.

Ledger Setup
In SunSystems version 6.2.0, a new parameter, called Transaction Date Substitution, has been added to Ledger Setup (LES) >> Options, to limit the automatic substitution of Transaction Dates by Ledger Import.

Settings are:

• Allow on All (default) – any valid transaction dates will be substituted.

• Allow Order Fulfilment Only – any Order Fulfilment invalid transaction dates will be substituted, and all other invalid transaction dates will be rejected.

• Disallow – any invalid transaction dates will be rejected rather than substituted.

Changes to Balancing by Fourth Currency

In SunSystems version 6.2.0, Account Allocation/On Line Allocation, Ledger Entry, and Ledger Import are enhanced with functionality to enforce balancing by a common Value 4 Currency Code, (when Value 4 is defined as Variable, and with Automatic Balancing set).

So depending on the setup of the Business Unit, when the Value 4 Currency Code is common throughout the set of transactions in question, balancing is applied by Value 4 along with balancing by the other Currency Values, .

Using Extended Analysis and Enterprise Data Management

If you are using extended analysis and want to use the Enterprise Data Management (EDM) to enable business units to share key reference data, you should be aware of some limitations in using these features in combination.

Extended analysis data that you create, amend, or delete is not shared via EDM automatically. Only changes to the parent analysis record trigger the enterprise data management functionality.

If you are linking analysis to reference data, you must ensure that this exists in common between business units sharing an EDM relationship. This is best controlled if that data has the same pattern of publication and subscription as the analysis it is linked to.

If EDM integration is deployed across multiple domains, you must ensure that Additional Code Lists are maintained throughout these domains. These are held at domain level and cannot be shared automatically at this time.

You can define standard extension fields on Analysis Dimensions that are ‘linked’ to an Analysis table. However, if a published analysis dimension is processed by a subscriber Business Unit with the ‘linked’ flag unselected, then the standard extension fields and corresponding values in analysis codes will not be retained.

If you do not want to share extended analysis data you can suppress this when using EDM. The analysis extension fields will still be published, but they will be bypassed when the Subscriber Business Unit consumes the BOD:

1 Define a transformation in Transfer Desk, where each of the extension fields in the payload is set to ‘Undefined’.

2 Assign the transformations to the subscriber Business Unit, using ELS-Enterprise Data Subscription Configuration.

Indic Numerals for Arabic-speaking Users of SunSystems Web

Arabic-speaking users who wish to use Indic numerals can use this facility in version 6.2.0 of SunSystems Web by using Firefox or Internet Explorer 8. Versions 9 or later of Internet Explorer do not currently support Indic numerals.

This limitation does not affect right-to-left display, Arabic translations, or support for the Hijri calendar.