Start of Content Area

Background documentation Global Worklists  Locate the document in its SAP Library structure

A worklist generation run must take place to create a global worklist so that translators can reserve objects for translation in their personal worklists. This facilitates quick, efficient translation. The worklist generation run creates a subgroup of objects that are relevant for your translation objectives. This subgroup is taken from all of the potentially translation-relevant objects in the system. The subgroup of objects is then evaluated for translation.

The global worklist is created in two stages. In the first stage, one or more object lists are created. They contain translation-relevant subgroup(s) of objects and are not language-dependent. There are different ways of creating object lists, and therefore subgroups. You can create object lists for specific collections. In the case of ABAP-based developments, you can also create object lists for transports or transport objects. These object lists form the basis of the global worklist. However, you can also use them for other purposes, such as creating demonstration objects and transporting proposal pools according to object lists.

In the second stage, the object list(s) is/are evaluated for individual target languages. A global worklist can be based on one or more object lists. An evaluation takes place for each defined target language. The translation graphs to which collections are assigned, and the object types defined for translation into a particular target language, determine which objects are included in the global worklist. You can automatically distribute translations, and update the usage counters, during the worklist runs. The translation statistics are also updated. Translators and coordinators can use them to monitor their own progress, or overall progress during the translation project.

You must create global worklists when new, translation-relevant objects are transported to, or created in the translation system. In the case of large translation projects, new translation-relevant objects are continually transported to the translation system. You are therefore advised to create global worklists at regular intervals, such as once a week. In the case of small translation projects, new translation-relevant objects only need translating in the translation system every now and then. You only need to create global worklists when these objects are created in, or transported to the system.

Developers sometimes delete their own developments. In such cases, you must delete the old worklists before generating new ones so that the objects deleted by the developers are removed from the translators’ worklists.

 

End of Content Area