
The aim of processing top texts is to create as many system standards with quality status A as possible for source texts that only need one translation which fits all possible contexts.
Another aim is to avoid creating such proposals for ambiguous source texts that need more than one translation, depending on the context.
This ensures that "easy" source texts, which can be translated automatically, are translated by automatic distribution. It also ensures that ambiguous source texts, which need actual translator attention, are translated correctly during manual translation and in accordance with the context of the object in which they occur.
Before processing top texts, we recommend that you do as much research as possible about the subject area to be translated. Discuss and define as much terminology as you can, so that you can create as many proposals as possible with confidence while processing top texts.
Read the documentation on the proposal pool and automatic distribution carefully, so that you are aware of the consequences of distributing an unsuitable translation, and the work involved to correct it.
You need to know the technical names of the top text objects you want to process. If you have a number of top text objects and more than one translator available to process the top texts for your target language, decide on the objects that each translator will process. It can also be useful for all translators to sit around one PC to discuss and decide how to deal with each source text in the top text objects. This ensures that everyone translates using consistent terminology and style when manual translation starts, because all translators discussed these issues during top text processing.
To process top texts, you need to be able to create proposals with quality status A, to ensure maximum distribution potential. Your translator profile must therefore contain authorization PPQ1 (Assign Quality Status) with value 04 (Level 4).
There are three different ways of calling up top texts for processing:
Directly in SE63
This is the simplest and quickest way to access a top text object for processing. You can only call up one object at a time, and you cannot see how many lines you have processed in each object, until you call the object up. To translate top texts using the direct method, see Processing Top Texts Ad Hoc .
Using an on-the-fly worklist
Calling up top text objects using an on-the-fly worklist means that you enjoy all the benefits that the worklist screen offers, such as sequential processing and the fact that the processing status of each line of each top text object is displayed in the worklist screen. To be able to use this option, you user requires authorization object S_ADMI_FCD with value TRNR . To translate top texts using the on-the-fly worklist method, see Processing Top Texts Ad Hoc .
Using a standard worklist
Calling up top texts using a standard worklist means that you enjoy all the benefits that the worklist screen offers, such as sequential processing and the fact that the processing status of each line of each top text object is displayed in the worklist screen. To be able to use this option, you user requires authorization object ?????. To translate top texts using the standard worklist method, see Processing Top Texts in Standard Worklists .