Preparation

Start the Easy Unicode Migration (ttcon8110m000) session.

During the startup of this session a question is displayed asking to confirm the initialization of the migration data. Click Yes.

The initialization includes:

Defaulting the high ASCII support parameters
Generating the database connection string
Initializing the package combinations/companies which must be processed with the related processing steps and status fields.

Select Actions > Unicode Migration Parameters.

The Unicode Migration Parameters (ttcon8100m000) session contains all configuration data for the migration process. Validate the (defaulted) data and change if required.

High ASCII support

The storage of high ASCII characters in single byte fields can cause problems because a code point can have different meanings in different locales.

For example:

ISO8859-1 locale (Latin-1) decimal code point 233 interprets the character 'Latin Small Letter E with Acute' (é). ISO8859-7 locale (Latin/Greek) interprets the same code point as a 'Greek Small Letter Iota' (ι) character.

Because of this ambiguous encoding we do not recommend to use high ASCII characters in single-byte fields. However it is not forbidden.

If table data contains high ASCII and you cannot clean up this data, you must enable the support for high ASCII. Select the Infor locale in which the high ASCII characters must all be valid.
Database connection string

The connection string specifies how to connect the source database.

Besides a conversion of the data within the same database (in-place conversion) also the movement of the data from one database to another is supported.

The connection string is already generated during the initialize of the migration data but can be changed manually. Click Generate to initialize the connection string again.

See Source and Target Database Configuration and Database connection strings.

Link Locale to Companies

All users within an LN environment must have the same locale, in fact the only configuration supported but not enforced by the software. You can define a different locale for each user through the User Data Template (ttams1110m000) session. A configuration can exist where each company has its own locale, or even have multiple locales used within a single company. Although not supported, the Unicode migration takes these configuration possibilities into account. Therefore per company the source locale must be specified which will be used for the interpretation of the data.

Note: During the initialization of the migration data the locales are defaulted when possible. If the user locale defined in the User Data Template (ttams1110m000) session of all users linked to the specific company in the User Data (ttaad2500m000) session is the same, this locale is used as a default value. Else the locale remains blank.

Select Actions > Unicode Generate Code Point Mapping Files

A question is displayed asking to confirm to generate the code point mapping file. To continue this action. Click Yes.

After the process is successfully finished, a message is displayed. Click OK. Within the Easy Unicode Migration (ttcon8110m000) session the Mapping field is set to completed by checkmark and timestamp.

Based on the high ASCII settings and the linked company source locales a so called code point mapping table must be created. This is a plain ASCII file which maps each code point, a unique numeric identifier for each character, in the database to its Unicode equivalent. For each unique locale linked to a company a code point mapping table is required. The mapping files are used during the actual data conversion.

Note: In the Easy Unicode Migration (ttcon8110m000) session, code point mapping file(s) can also be generated for the linked locales of marked companies.

Mapping files are stored in this folder: <BSE_TMP>/uni/maps

Select Actions > Check High ASCII

A question is displayed asking to select the companies of, ALL package combinations or the SELECTED package combination. This is the actual displayed package combination in the Easy Unicode Migration (ttcon8110m000) session to be checked for high ASCII validation. If the process finishes a report is displayed with the validation results. If the report indicates No (invalid) high ASCII present, within the session Easy Unicode Migration (ttcon8110m000) the High ASCII field is set to completed by checkmark and timestamp.

Run a validation of present high ASCII characters. Based on the selected support high ASCII settings present or invalid, remove or change high ASCII characters when not valid according to the selected high ASCII locale. In case high ASCII characters are present in the Tools company 0 data, use the Remove High ASCII Characters (ttcor0008m000) session for an initial cleanup. Correct the application data manually.

Note: When invalid high ASCII characters cannot be corrected set the related status indicator manually to completed. The migration process will then continue. This approach is not recommended. The not corrected or invalid characters are displayed as question marks.

In the Easy Unicode Migration (ttcon8110m000) session the high ASCII validation can also be checked for marked companies only.

High ASCIIi related (result) files are stored in this folder: <BSE_TMP>/uni/data

Actions > Generate Tools Conversion Script Files

A question is displayed asking to confirm to generate a command line script for the data conversion of the Tools company 0. To continue this action, click Yes. If the process finishes successfully , click OK. Within the "Easy Unicode Migration" (ttcon8110m000) session the Tools Conversion Script field (present in the view of the company 0 migration data) is set to completed by checkmark. To ensure a smooth migration the conversion of the Tools company 0 data is not run within the Easy Unicode Migration (ttcon8110m000) session. It runs outside LN from the command line by a script. The generated script is stored in this directory: <BSE_TMP>\uni\tools

Note: Do not run the script yet. First convert the (BSE) environment to Unicode. The Tools conversion script is stored in this folder: <BSE_TMP>/uni/tools