Easy Unicode Migration (ttcon8110m000)
Use this session to migrate and monitor the Unicode migration process.
The Unicode character set is the international standard for multi-language support by providing a unique code for each character, regardless of the language. Single-byte and multibyte character sets, also called locales, support only a small set of languages. Unicode, on the other hand, takes away this limitation. You can use for example English, Russian, and Chinese within one LN environment.
You can migrate one or more existing LN databases within a single-byte, multibyte or (legacy) Unicode environment into the new Unicode standard.
Depending on the number of companies and the amount of data, the migration can take a considerable amount of processing time.
See the Infor Enterprise Server Unicode Migration Guide
Field Information
- Package Combination
-
Select one or more package combinations.
- Converted to Runtime
-
Ensure all (pending) program domains and table definitions are converted to runtime, and all LN tables are correctly reconfigured. Correct all errors if listed.
- Tools Conversion Script
-
This field will be set to completed, when the command line script for the data conversion of the Tools company 000 is created successfully.
- Company
-
Per company the source locale must be specified which will be used for the interpretation of the data.
- Locale
-
The locales are defaulted if possible. If the user locale defined in the session ‘User Data Template’ (ttams1110m000) of all users linked to the specific company in the session ‘User Data’ (ttaad2500m000) is the same, this locale is used as a default value, else the locale remains blank.
- Mapping
-
If the process "Generate Code Point Mapping Tables“ was successful this field is set to completed, including a timestamp.
- High ASCII
-
If the report
$BSE/log/log.aad4233_<Package combination>_<company>
indicates “No (invalid) high ASCII present”, this field is set to completed by checkmark including a timestamp. - Data Conversion
-
When the conversion of the processed companies is successful, this field is set to ‘Converted’ with a timestamp. In case the conversion failed, this field will be set to 'Failed' with a timestamp, for the companies concerned.