Create LAT issue

Create LAT issue

Intended audience
Language Tester


Watch the instruction video.

This article explains how a language tester can report an issue.

Editable fields

The dialog to enter an issue has one more of the following fields. Fields may be optional or mandatory, depending on the quality profile that the project manager selected for this language test.


Error category
The error categories depend on the quality framework. An error category may have sub-categories. You can select main and/or sub-categories.  Clicking the field will open the select error category dialog.

The priority indicates how fast an issue must be resolved.

Translation preferential change (not applicable for non-translation issues).
Nice-to-have functional or source text improvement; small linguistic issues like minor spelling or punctuation mistake.
MediumDoes not affect the usage of the functionality, but impacts user experience, e.g. meaning mistake, grammar error.
Causes great difficulty in using functionality or impacts confidence in the product .
Very high
Showstoppers, interruptions of business or loss of data.

Free text.
The project manager can grant the language tester the permission to edit the translation, or to suggest a translation.

Edit translation
Edit the translation. Your changes will be immediately stored in the project.

Suggest translations
Suggest a better translation here.

Hint: use the short-cut icon to copy the current translation, and then do a quick edit.

Read-only fields

Read-only field
Current translation
The translation at the moment that you create this issue.
Note: this translation will be stored with this issue, even if the translation is later changed.

Source text
The source text at the moment that you create this issue.
Note: this source text will be stored with this issue, even if the source is later changed.

Selected string ID
Unique identifier of the selected string.


    • Related Articles

    • Execute live LAT

      This section only applies when you need to review translations for the live application. If you need to review a set of previews, please visit the instructions for a preview-based LAT. This guide describes the steps how to review translations on a ...
    • Execute preview-based LAT

      This section applies to a preview-based LAT, where you need to review translations for pre-defined set of previews. If you need to review the live application, please visit the instructions for a live LAT. This guide describes the steps how to review ...
    • LAT main window

      Each LAT task has a main window with a main menu and action buttons. Intended audience Language Testers SAP users Please refer to the SAP Help Portal. The steps to execute a preview-based review tasks are described in this article. It will bring you ...
    • LAT Status

      An LAT task can have the following states: Open Completed Closed State diagram The states are shown in the following diagram. The Language Tester completes the LAT by pressing a button when he is done. As a result: the LAT is marked as completed, and ...
    • LAT Process step

      The following figure shows the LAT as part of the overall localization process. Development Developers send the complete set of resource files (e.g. json, properties) to be translated to the Project Manager. Translation The Project Manager creates a ...