Show TOC

Language ComparisonLocate this document in the navigation structure


Previous sections have described how to generate queries as well as how to create InfoSets and user groups. These operations involve dealing with a number of different text elements. For example, you have to specify descriptions for a field group when setting up an InfoSet. The system proposes descriptions for fields, but you can modify these if you wish. When you define a query, you must specify a title and you can also enter notes as well as your own headers for the different sublists and selection texts. You enter all these text elements in your own language, i.e. the logon language.

If, however, another user logs on in a different language and wants to use the queries and InfoSets you have defined, all the text elements should preferably be displayed in that language.

  • SAP Query provides a language comparison for this reason. The language comparison allows you to enter all relevant texts in one or more languages for a query or InfoSet. You can then use that query or InfoSet in various logon languages.

  • SAP Query notes the language variants that exist for each text and checks that the individual variants match. If two language variants reveal differences, the system also notes which of the two variants contains changes and indicates which variant has the most up-to-date text.

The language comparison facility is not intended to be used constantly. A language comparison should first take place when the query or InfoSet is stable, meaning that no more essential changes are expected You can of course still carry out changes at any time. If you change texts that have already been adjusted, you must adjust them again. SAP Query provides utilities to help you analyze these texts.

You perform language comparison with the component Language Comparison:

  • The following sections explain which texts you compare individually. It is important that non-specific references exist. To be able to edit a query in different languages, you must first perform a language comparison for the relevant InfoSet, since many InfoSet texts are either used as an aid when creating the query or are copied directly to the query.

This section contains the following subsections: