Implementing multiple languages 
Most features and capabilities which support multiple languages in your SAP POS applications are applied when the applications are installed. However to make any changes to the original series of available languages, such as adding a new language, or to change the main language of the store, you will need to change some settings in various areas of your system. In addition, to maintain language consistency across your system landscape, you may also need to configure settings in other areas of your POS such as its operating system. The following procedures outline the types of configurations and settings you need to check or make, along with steps you need to perform to ensure that multiple language support is fully implemented in your SAP POS product suite.
To ensure complete implementation of multiple languages for your store:
Determine the main language of the store.
When installing the required database application (Microsoft SQL or Sybase), at the language prompt, set the language of the store as the default language for the database.
In the operating system settings for the POS pc, set the regional and language settings to match the country, language and keyboard settings required at the store. These are located at the following path: .
When installing the SAP POS applications, set the language of the store in each required component. If the language of the store is not one of the languages provided, select English. If required, install default demo parameters for the initial setup only. For more information about installing the SAP POS application suite, see the Install Guide.
In the screen of the Configurator application, define all the languages you would like to make available at your store. For more information, see the relevant section in the Configurator User Guide.
Note
The main language of the store must be the first language in the list.
In the Configurator application, create all the base store parameter files you will need at the POS. Use the language of the store in any text fields as required. The following is a list of the parameter files you can create:
Tender
Non-Merchandise
Standard Menus
Custom Menus
Profile Prompts
User-Defined Transactions
Returns
Choice Lists
Taxes
Discounts
Manager Codes
As you create parameter file definitions in any of the parameter files shown above, you can also enter text translations for any descriptive fields that the cashier will see. These are downloaded to the POS along with the parameter file information. These fields appear in a different color in the Configurator application. For more information, see the Configurator User Guide.
Note
If a translation is not provided, the convert process uses the text from the language of the store
Define the store language in each of the required *.ini parameter files. For more information on the *.ini files for each application, see “Where the store language is set” on page 553.
Use the Configurator application to download the parameter files containing the translated fields to the POS Servers base parm directory. For more information, see the Configurator User Guide . The base parm directory is located at C:\program files\SAP\Retail Systems\Xpress Server\parm. As the POS Server processes these files, it will create sub-directories for each language defined under the base parm directory.
Note
The multi-language convert process will create parms as well as some parm sub-directories.
Stop and restart all applications.
Create all the product files for the store such as the PLU/SKU (plutxn.asc) and Promotion (promotxn.asc) files according to established methods (For example, using third-party or other store back-end applications.) Ensure that any text fields in these files are set to the language of the store. Download these files to the base parm directory in the POS Xpress Server.
Create store employee records. For each employee, ensure that their alternate language preference is set. This can be done through Employee Maintenance screens in the Configurator and Store Manager applications, or through direct input into the Transaction Employee file (empxtxn.asc.). For more information, see the Configurator and Store Manager User Guides for information on the Employee Maintenance windows
Create the POS literal files for each of the required languages. Literal files contain the field and text labels and messages which are displayed at the POS. For information on how to do this, see “How to create translation files for the POS application” on page 561. At installation, default parameters are provided for the following languages:
Language |
Literal file name |
|---|---|
English |
Literal.lit |
German |
German.lit |
French |
French.lit |
Spanish |
Spanish.lit |
If you need to translate your system into a language that was not provided when your system was installed, you can use the DB Export/Import utility (txtxlt.exe) to create files to submit to translation for the databases of each of the following applications:
Configurator, POS/Store Manager, Electronic Journal Viewer. To create the export files, do the following: The DB Export/Import utility is located in the \Program Files\Common Files\SAP Shared\Retail Systems directory and is launched by running txtxlt.exe. Begin by running txtxlt.exe.
Submit the output text files for translation.
When the translated text files are returned, run txtxlt.exe again to import the translated text to the database.
If the product suite is being distributed through disk images, the translations can be added to the master image using this utility. If the software is being installed directly at the store, a command line version of the utility can be used to load the translations at the store:
Example
Example of the Import command line:
TXTXLT –I DUTCH –f ALL –d BACKOFFMS –u user –p password – t IMPORT –c 1 –s c:\translation
Note
For detailed information on how to use the DB Export/Import utility (txtxlt.exe), see “Using the DB Export/Import Database utility” on page 563.
If you need to translate your POS system files into a language that was not provided when your system was installed, you can use the mkascii.exe utility to create a text file (LITDEF.TXT) to submit to translation. (When the translated files are returned, you can use mklit.exe to apply them back into the application.)
Note
For more information about the use of the mkascii.exe utility, see “How to create translation files for the POS application” on page 561.