Creating Top Texts for a Worklist 
If you create top texts for a worklist, the job is language-specific which means you must schedule a separate job for one target language at a time. The system scans the source texts in worklists for the target language in question. It then creates top text objects that contain the source texts matching your selection criteria. The source texts are sorted according to how frequently they occur in the objects in the worklist.
Translators process these top text objects, and should create status A proposals for as many unambiguous source texts as possible. You can then run automatic distribution to distribute these proposals and reduce the manual translation workload.
Anyone whose system user has been created as a translation administrator can generate DEMS objects. In other words, the following roles have been assigned to the system user:
SAP_TRANSLATOR
SAP_TRANSLCOORD
SAP_TRANSLSUPERCOORD
SAP_TRANSLENV_ADM
To create top texts, you need the translator profile XX Super User for all target languages for which you want to create top texts.
A worklist must be available for each target language for which you want to create top texts. This means you must create an object list that contains the objects relevant for translation, and evaluate it for all target languages, before you create top texts. For more information, see Creating an Evaluation Run.
Call transaction LXE_MASTER.
Choose .
Make the following entries in the Generate Top Texts According to Worklist screen:
Source language of texts in top text objects |
In the Source Language field, enter the language in which the source texts should appear in the top text objects. For example, if you are creating top texts for a target language that translates from source language German, enter deDE in this field. |
Target language of texts in top text objects |
In the Target Language field, enter the language in which the target texts should appear in the top text objects. For example, if you are creating top texts for a source language that translates into target language English, enter enUS in this field. |
Status of proposals |
Here you can filter the source texts that the top texts contain according to whether proposals already exist for the source text. For example:
|
Status of texts to be scanned |
You can also restrict the source texts contained in the top texts according to the translation status of the lines in which the source texts occur in the worklist you are scanning. For example:
|
Worklist number |
Choose F4 on the Worklist field and, in the dialog box that appears, select the worklist that is to be the basis for the top texts. |
Target language in worklist |
In the Target Language in Worklist field, enter the same target language as already specified above. This field is mandatory and defines the target language of the objects in the worklist that is to be scanned for top texts. |
Source language in worklist |
In the Source Language in Worklist field, enter the same source language as already specified above. This defines the source language of the objects in the worklist that is to be scanned for top texts. |
Status of objects in worklist |
To improve system performance, we recommend that you enter the value N in the Translation Status in WL field, so that only objects with at least 1 new line are included in the scan to create top texts. This ensures that objects that are already 100% translated are not included in the scan, which speeds up the job. |
Name of top texts |
Enter a text string in the Object Name field that will help you recognize the top texts when you call them up in transaction SE63. |
Description of top texts |
You can enter a description of up to 40 characters in the Description field to document how you created the top texts, for example. |
Frequency of source texts |
Enter the minimum repetition level of the source texts in the Minimum Frequency field. For example, if you only want the top texts to contain source texts that occur three times or more in the worklist for this target language, enter 3 in this field. |
Split top text objects according to domain |
If the worklist contains objects from collections belonging to different domains, we recommend that you create your top texts according to domain. If you do not select the Ignore Application checkbox, the system creates domain-specific top texts. For example, the system creates separate top text objects for the source texts in objects from Basis (domain BC) that match your selection criteria, and so on. This allows translators to create application standards for the domain in question; in cases where it is not possible to create a system standard for the source text, but an application standard for domain BC is perfectly possible. |
Split top text objects according to object type |
If you have already decided to split the top texts according to domain, we recommend that you leave the Ignore Object Type checkbox selected; otherwise the system will create a large number of top text objects where the same source texts occur repeatedly. However, you may want to split the top texts according to object type to see the object type in which the source texts occur. If so, leave the Ignore Object Type checkbox blank and select the Ignore Application checkbox instead. |
Include similar texts |
If you do not select the Ignore Similar Texts checkbox, then the system scans for similar texts and groups them together in the top text objects (for example, Create Document, Create document, Create Document 2). This enables you to create consistent translations in the proposal pool. The similar texts listed in the top texts do not necessarily match the other criteria you defined for top text creation. For example, the top texts could contain similar texts for which proposals already exist, even though your top text creation criteria specified otherwise. If you select the Ignore Similar Texts checkbox, no scan for similar texts takes place. |
Generate object list |
If you select the Generate Object List checkbox, the system creates an object list that contains top texts created in the run. This enables you to create worklists for the top texts by evaluating this object list. To do this, you first need to create a graph for collection SAP_TRANSLATION_DEMS and then activate it for the target languages that will translate the top texts. However, you are not obliged to create worklists for top texts. For other ways of accessing the top texts for processing, see Processing Top Texts. |
Choose
(Execute).
Repeat for the next target language for which you want to create top texts.
As long as source texts matching your selection criteria exist in the objects in the worklist, the system creates top text objects containing the appropriate source texts, sorted according to how frequently they appear in the objects in the worklist.
The spool displays the names of the top texts created by this job. The names of the top texts are structured as follows:
<Source language><TOP><Name you defined when you scheduled top text creation><Target language><Domain, if split according to domain><Sequential number>
So we can learn the following from the object name deDE-TOP__C-INITIAL_FR-frFR-R-BC 0002
It contains German (deDE) source texts
It was given the name INITIAL_FR when the top text job was scheduled
It contains source texts extracted from objects belonging to the Basis (BC) domain
It is the second top text object created by this job (0002)
Each top text object contains 50 texts for processing.
You can now trigger the processing of top texts.