Show TOC

Creating Worklists and StatisticsLocate this document in the navigation structure

Definition

After setting up the translation environment in transaction LXE_MASTER, the next step is to evaluate the objects that you want to translate. This results in the following:

  • Detailed statistics for each target language, which enable the following activities:

    • You now have an idea of the translation workload so you can plan and budget the translation project.

    • You can use the statistics as the basis of assigning collections to translators so that you can guarantee that each translator is assigned an equal amount of lines to translate.

    • After you have assigned collections to translators, each translator can call up their personal statistics to monitor their own workload.

  • Worklists which enable translators to fetch and translate the objects requiring translation that belong to the collections assigned to them.

  • If you have satisfied all the prerequisites for automatic distribution, then the evaluation also automatically translates any new and/or modified lines using the contents of the proposal pool, thus reducing the manual translation workload.

Integration

Before you can create worklists and statistics, you need to perform the following activities:

Define the languages into which you want to translate

For more information, see Defining Target Languages.

Create translation graphs

This defines the source language for each target language.

You can also use graphs to define which collections are relevant for translation for each target language, if some collections need to be translated into more target languages than other collections.

For more information, see Defining Translation Graphs.

Define the client(s) in which you want to translate

For more information, see Defining Translation Clients.

Define the object types that each target language is to translate

For more information, see Defining Object Types for Translation.

Assign collections to graphs

Only objects belonging to collections in a graph that is active for the target language in question will arrive in the worklists and statistics for that target language.

For more information, see Assigning Collections to a Translation Graph.

Decide on what objects you want to translate

You need to define the objects that you want to translate.

For information on the options available to you, see the section Features in Object Lists.

If you create Customizing entries in a language that is not the original language of the table to which they belong, and if you want to translate these entries via a worklist, then you must first override the original language of Customizing tables for translation.

Activities

Creating worklists and statistics consists of two steps in transaction LXE_MASTER:

  • Creating an object list

    An object list should contain exactly those objects that you want to translate. When you create an object list, you define parameters to ensure that exactly those objects relevant for translation are included in the object list. If development is ongoing, and objects are still being created in/transported to the translation system, you need to create a new object list at regular intervals (ideally once a week until the development deadline).

    For more information, see Creating Object Lists.

  • Creating an evaluation

    After you have created an object list, an evaluation analyzes each object and calculates the translation status of each line in each object for each target language. The result of the evaluation is worklists and statistics. If development is ongoing, and objects are still being created in/transported to the translation system, you need to create a new evaluation at regular intervals (ideally once a week until the development deadline). This adds new and modified objects to the worklists and updates the statistics. For more information, see Creating Evaluations.

Alternatively, you can use report RS_LXE_EVALUATION_SCHEDULE to create an object list and evaluation via a single interface, and to schedule an object list and evaluation to be created periodically, such as once a week.

Result

After an evaluation has run statistics and worklists are now available for the target languages you defined in transaction LXE_MASTER.

After creating your first evaluation in a system, the next steps would be as follows:

Step

For more information, see

If the translation volume is over 1,000 lines for each target language, we recommend that you create top texts for the object in the worklist for each target language.

Creating Top Texts

Create the translators who will process the top texts with a suitable translator profile so that they can assign quality status A to the proposals that they create.

Maintaining Translators

Translators then process the top texts and try to create as many high-quality proposals for easy source texts as possible.

While top text processing is in progress, make sure that all collections relevant for translation are assigned to a translation graph with status D and that distribution parameters are defined for each object type for each target language.

After translators have processed the top text objects, you can run a second evaluation with automatic distribution to reduce the manual workload.

Creating Evaluations

Now manual translation can start. You now need to assign collections to translators. Use the statistics to help you ensure that each translator gets a similar amount of lines to translate.

After you have assigned all relevant collections, translators can now call up the objects requiring translation using worklists.

Calling Up a Worklist

While development is ongoing, you need to create a new object list and evaluate it at regular intervals (ideally once a week).
Constraints

The translation tools cannot decide what you need to translate. You are 100% responsible for ensuring that all translation-relevant objects arrive in the worklists and statistics, by making sure of the following:

  • The object list contains all objects relevant for translation and is updated and evaluated at regular intervals while objects are still being created/modified/transported to the translation system.

  • All collections that contain objects relevant for translation are assigned to translation graphs.