Show TOC

Procedure documentationLanguage Settings in SAP POS

 

Most of the features and capabilities that support multiple languages in the SAP POS applications are applied when the applications are installed. However you can make changes to the original series of available languages by adding a new language, or changing the main language of the store. To do so, you need to make changes to various settings in the system. To maintain language consistency across the entire system landscape, you may also need to configure settings in other areas that impact the POS system such as the operating system on the machine on which it is installed.

The following procedures outline the types of configurations and settings you need to make, along with steps you need to perform to ensure that multiple language support is fully implemented in your SAP POS product suite.

Procedure

To ensure complete implementation of multiple languages for the store:

  1. Determine the main language of the store.

  2. 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.

  3. In the operating system settings for the POS machine, 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: Start of the navigation path Control Panel Next navigation step Regional and Language Options. End of the navigation path

  4. 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, refer to the installation guide.

  5. In the Start of the navigation path Terminal Next navigation step Xpress Languages End of the navigation path screen of the Configurator application, define all the languages required at the store.

    Note Note

    The main language of the store must be the first language in the list.

    End of the note.
  6. In the Configurator application, create all the base parameter files you need for the store. 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

    When you create definitions for any of the parameter files shown above, you can also create translations for the descriptions of the definitions. These are downloaded to the POS along with the parameter file information. These fields appear in a different color in the Configurator application.

    Note Note

    If you do not make a translation for a descriptive field, the convert process uses text in the language of the store

    End of the note.
  7. Define the store language in each of the required *.ini parameter files. For more information on the *.ini files for each application, see Set the Store Main Language.

  8. Use the Configurator application to download the parameter files with the translated fields to the POS Server base parm directory. The base parm directory is located at C:\program files\SAP\Retail Systems\Xpress Server\parm. When the POS Server processes these files, it creates subdirectories for each language defined under the base parm directory.

    Note Note

    The multi language convert process creates parm files as well as some parm subdirectories.

    End of the note.
  9. Stop and start all applications.

  10. Create 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 Xpress Server.

  11. 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 or the Store Manager applications, or through direct input into the Transaction Employee file (empxtxn.asc.)

  12. Create the POS literal files for each required language. Literal files contain the field and text labels and messages that are displayed at the POS. For information on how to do this, see Create Translation Export Files for SAP POS. 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

  13. If you need to translate the system into a language that was not provided when it was installed, you can use the DB Export/Import utility (txtxlt.exe) to create files to submit to translation for the Configurator, POS/Store Manager, Electronic Journal Viewer databases:

    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 of the Import command line:

    TXTXLT –I DUTCH –f ALL –d BACKOFFMS –u user –p password – t IMPORT –c 1 –s c:\translation

    Note Note

    For detailed information on how to use the DB Export/Import utility (txtxlt.exe), see Using the DB Export/Import Database Utility.

    End of the note.
  14. If you need to translate the POS system files into a language that was not provided when the 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 Note

    For more information about the use of the mkascii.exe utility, see About MKASCII.EXE.

    End of the note.