Context
If you have set up the translation environment in transaction
LXE_MASTER, you can put top texts in a
standard worklist. Although the initial time investment is greater than that for
accessing top texts directly in
transaction SE63, or via
the DEMS Objects (Administration) dialog box, or in an on-the-fly worklist, it is
actually a more efficient procedure in the long run, especially if you have a high
number of top texts to process for two or more target languages.
-
Detailed statistics are provided for each target language, which means you have
an overview of the top text workload and can plan and budget the translation
project accordingly.
-
Worklists enable translators to
process top text objects sequentially.
-
Standard worklists make it very difficult for translators to process top texts for
the wrong combination of source and target language by mistake.
Procedure
-
Define object type dems as translation-relevant for
the target languages in the system that will process top texts.
- Create a
new graph for the top texts.
Note
In standard translation graphs, target languages are almost always translated from a single source language. For example, if the collections in graph 001 contain a mixture of objects with original language German and English, and if the collections are translated into Danish from source language
German, the language entries look like this:
|
Target Language
|
Original Language
|
Source Language
|
|
daDK
|
deDE
|
deDE
|
|
daDK
|
enUS
|
deDE
|
If the collections in graph 002 contain a mixture of objects with original language German and English, and if the collections are translated into Danish from source language English, the language entries look like this:
|
Target Language
|
Original Language
|
Source Language
|
|
daDK
|
deDE
|
enUS
|
|
daDK
|
enUS
|
enUS
|
The original language of each top text object is the same as the source
language that was scanned to generate it. So if the collections in graphs 001
and 002 are scanned to generate top texts for target language daDK, translators
need to process:
That means the Danish language entries in the top text graph must look like this:
|
Target Language
|
Original Language
|
Source Language
|
|
daDK
|
deDE
|
deDE
|
|
daDK
|
enUS
|
enUS
|
- In this top text graph,
set the status of every combination of target, original, and source language to
Inactive. This deactivates all language combinations
and ensures that DEMS objects are not accidentally included in any other worklist evaluation.
-
Assign
collection
SAP_TRANSLATION_DEMS to this graph.
- Just before you start an evaluation to put the top text objects in a standard
worklist, set the status of every combination of target, original, and source
language to Active in the top text graph. You do this
by selecting
Select All at the bottom of the Graphs
dialog box and then choosing Status. In the
Activation Status dialog box, choose
Active. Save your changes.
-
Evaluate the special
object lists that were generated automatically by the report that created
the top texts. Each generated object list includes the language direction of the top
text objects that it contains. For example, I_17-09-10
deDE->frFR contains top texts from source language German to
target language French.
Caution
Do not add the top text objects in the generated object lists to any other
worklist in the system that contains translation-relevant objects. We recommend
that you generate a separate top text worklist with its own worklist number
instead.
- After the worklist evaluation has finished, reset the status of every target,
original, and source language combination to Inactive in
the top text graph.
Results
The top text objects are now available in their own standard worklist.
Translation coordinators can display top text statistics in transaction
Translation Statistics
(SLLS). After a translation coordinator has
assigned the collection SAP_TRANSLATION_DEMS to
a translator, he or she can then reserve the top text objects in a standard worklist and process them in
accordance with Processing Top Texts.