Evaluations

During an evaluation run, the system analyzes one or more object lists and determines the translation status of the objects in the object list(s) for each target language. Depending on how the parameters have been set, worklists and statistics are created or updated for each target language. After the evaluation has finished, you can refer to the statistics to see the translation volume and monitor the progress of a translation project. Translators can call up a worklist, which enables them to translate the objects quickly and efficiently.

Evaluation runs can be created and started in transaction LXE_MASTER on the Evaluations tab page. The object lists created in transaction LXE_MASTER are the basis of the evaluation. Depending on the parameters, the system determines the translation status, and creates statistics and worklists. The objects in the object list(s) are analyzed for each target language. The analysis takes account of the settings in the translation environment , such as which object types are translated into which target languages, the distribution parameters , and the assignment of collections to translation graphs .

• Your translator profile contains the authorization object WRKL with the value 01 .

• The translation environment has been set up .

• At least one object list has been created .

• You need to assign the collections that are relevant for translation to a translation graph with status active.

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

• To receive an e-mail notification when an evaluation is complete, the mail service must be configured in transaction SCOT and your user name must be entered in table LXE_MAIL in transaction SE16 .

You can set the following parameters when you create evaluation runs:

• Worklist Number

  If you are translating more than one project in the same system, worklist numbers enable you to keep these projects separate.

  Translators for project X call up objects using worklist number 1 and for project Y translators call up objects using worklist 2. You can also view the statistics for each project using the worklist number. Note that an object can only be in one worklist at any one time. For example, if a specific object is included in both the object list used in the evaluation to create worklist 1 and the object list used in the evaluation to create worklist 2, only the last worklist to be created contains the object.

• Activate Automatic Distribution

  For automatic distribution to take place, you need to set this parameter when you run an evaluation.

• Create Preliminary Statistics

  If you set this parameter, the system refreshes the statistics immediately before it starts the evaluation run.

• Create Statistics

  If you set this parameter, the system refreshes the statistics immediately after all jobs for the evaluation run have finished

• Delete Existing Worklist

  If developers have deleted objects since the last evaluation run, you need to set this parameter to remove these deleted objects from the worklists and statistics. The system deletes the contents of the current worklists for this worklist number and rebuilds them according to the objects available in the object list(s) that are the basis for this evaluation

• No Status Calculation

  If you select this checkbox, no real status calculation is performed, instead the system looks in the existing worklist for objects (in the relevant target language). If found, the status is copied over. If not, the status is set to New with 1 line. We recommend that you do not select this checkbox.

• Send E-Mail On Completion

  Select this checkbox to receive an e-mail when an evaluation run has finished. In order for this function to work, the mail service must be set up in transaction SCOT and your user must be maintained in the list of recipients in transaction SE16.

• Object Lists

  Here you select the object list(s) whose objects are to be evaluated during the evaluation run

• Object Types

  Here you select the object types to be evaluated. You can valuate all or just some of the object types in the object list. The object types defined in the translation environment for each target language, however, take priority here. For example, if you create an evaluation for French and select all object types to be evaluated here, the evaluation for French only evaluates the object types defined for French in the translation environment.

• Graphs

  Here you can select the translation graphs to be evaluated. Only the graphs that are active for each target language in the translation environment are taken into account during the evaluation. For example, if you create an evaluation for French and select all graphs to be evaluated here, the evaluation for French only evaluates the objects in collections that belong to graphs that are active for French in the translation environment.

• Target Languages

  You can create evaluations for all, or just some of the target languages defined in the translation environment.

For information on how to schedule evaluation runs, see Creating Evaluations .

You can monitor the progress of the current evaluation run in transaction LXE_MASTER.