Data Languages (ttaad1111m000)

Use this session to define Data Languages.

You can define multiple data languages. You must mark one data language as the Base Language. For details, refer to Multilanguage application data.

A data language consists of an ISO 639-1 language code and, optionally, an ISO 3166-1 country code. See the following examples:

ISO 639-1 language code	ISO 3166-1 country code	Description
de		German
en	GB	English_UNITED KINGDOM
en	US	English_UNITED STATES

Life cycle of a data language

Data Languages have a status which is used to control their life cycle.

1	New data languages have an initial status of "Pending for Addition". You can manually delete such data languages.
2	You must mark one of the data languages, which are pending for addition, as the base language, before you can start the Convert Data Languages to Runtime process.
3	When you convert data languages to runtime, all data languages with the status "Pending for Addition" get the status "Being Added".
4	Once the Convert Data Languages to Runtime process succeeded, the data languages with status "Being Added" get the status "Available".
5	You can mark "Available" data languages for removal. This sets the status to "Pending for Deletion". You can make such data languages available again, as no changes have yet been processed.
6	When you convert data languages to runtime, all data languages with the status "Pending for Deletion" get the status "Being Deleted".
7	Once the Convert Data Languages to Runtime succeeded, the data languages with status "Pending for Deletion" are deleted.

Note

In Infor Enterprise Server versions prior to version 8.4.1, the coding of data languages is based on the ISO 639-2 standard. To use these data languages in Infor Enterprise Server 8.4.1 and higher, they must be migrated to the new ISO 639-1/ISO 3166-1 standard. After a conversion, these data languages have the "Migrated" status. For details, refer to To migrate data languages.

Convert data languages to runtime

You must use the Convert Data Languages to Runtime command to (re)generate the $BSE/lib/data_langs file, which is used by the porting set at runtime. The process stores information, such as package combinations and languages processed, in a log file that you can print through the Display Logfile command.

Important!

Use this command only if you are sure that you do not want to change the base language anymore. See the restrictions listed below. It is recommended to perform the conversion to runtime, after you have registered the multilanguage tables and fields.

Note

The Convert Data Languages to Runtime command dumps the ISO 639-1/ISO 3166-1 data languages in the $BSE/lib/data_langs file, with a ‘_’ character as separator. So, for example, en_US.

Restrictions

You can fully maintain data languages as long as no Convert Data Languages to Runtime has ever been done.
Once the first Convert Data Languages to Runtime has succeeded, you cannot change the base language anymore. However, you can still add data languages, which get the status "Pending for Addition" and mark data languages for deletion, which get the status "Pending for Deletion".
You can only delete a data language, or mark a data language for deletion, if the language is not used in LN. For example, you cannot delete a data language that is used in the Software Languages (ttaad1510m000) session or in the User Data (ttaad2500m000) session.