Translators can call up objects to be translated in a worklist. To call up objects in a worklist, they do not need to know the object types or technical names of the objects.
When you call up a worklist, the system first assigns a reservation number for the selected language direction. The objects in a translator's worklist are reserved by this translator, which means no other translators can call up these objects in their worklists for the same language direction. After a worklist has been called up, the objects can be accessed for translation individually with a double-click, or sequentially.
Worklists are the result of an evaluation run, in which the system analyzes the objects to be translated. Depending on how the parameters have been set, worklists and statistics are created or updated for each target language.
On the initial screen of transaction SE63, translators choose to call up an existing worklist again, or to reset an existing reservation and then reserve objects in a new worklist.
The system takes account of the settings entered in the translation environment, such as the target language for which the translator has been defined and his or her collection assignments. Translators can only call up a worklist for the target language for which they have been defined in transaction LXE_MASTER. Furthermore, they can only reserve objects in a worklist if they belong to collections assigned to them for translation.
Worklists are called up dynamically; unlike the translation statistics, the worklist always shows you the current translation status of the objects.
When objects are accessed from the worklist screen, the system opens them in the short text editor or long text editor, depending on the object type. You can create session-bound top texts in your worklist.
You can determine the area from which objects originate, the way in which objects are displayed in the worklist, and how you process objects, by maintaining settings which you access from the initial screen of transaction SE63 by choosing Maintaining Worklist Settings and Transaction SE63.
, and then selecting the Languages and Worklist tab pages. For more information on these settings, refer to the sections about maintaining translation settings in the following documents:When you call up a worklist, you can determine its scope using the following criteria:
Collections
Domains
Object types
Number of objects per object type
Translation status
Related objects
The title bar of the worklist screen contains your user name and the language direction. The functions in the application bar are described in Translating Objects via a Worklist.
Depending on how you have maintained your settings, the objects in your worklist are sorted according to object groups (ABAP texts, F1 Help, etc.) or collections.
First level: root
Irrespective of how the worklist is sorted, the root of the worklist shows you the number of objects in the worklist, the total number of units to be translated, the total number of units per translation status, and the sort parameters. The icon indicates that a figure is a grand total.
Second level: collections
Depending on how you have maintained your settings, the second level contains the descriptions or names of the collections from which you have reserved objects for translation as the title of the nodes.
To the right of each collection, the system displays the number of units to be translated in the collection, and the number of units per translation status. The icon stands for a subtotal.
Third level: object types
The object types are listed under every collection. The shortcut, which consists of 2 to 4 characters, is displayed in front of the description of each object type. The color of the object type node is white if just one object is assigned to it. The color of the object type node is blue if more than one object is assigned to it. The settings enable you to determine whether object types with a single object are expanded by default.
To the right of each object type, the system displays the number of units to be translated for this object type, and the number of units per translation status.
Fourth level: objects to be translated
The objects to be translated are listed in alphabetical order under their respective object type nodes. To the right of each object, the system displays the number of units to be translated in this object, and the number of units per translation status.
Second level: object groups
On the second level, the system lists the object groups that are used to group object types together that logically belong together, for example ABAP texts and F1 Help.
To the right of each object group, the system displays the number of units to be translated in the object group, and the number of units per translation status.
Third level: object types
The object types are listed under every object group.
Fourth level: objects to be translated
The objects to be translated are listed in alphabetical order under their respective object type nodes. To the right of each object, the system displays the number of units to be translated in this object, and the number of units per translation status.
After you call up an object and then return to the worklist screen, and after you execute the Refresh Status or Flag Locally Saved Versions functions, the system displays a date to the right of each object. This date indicates when the status of the object in question was last refreshed.