Collections
Purpose
Collections are used to group objects that logically belong together. When they arrive in the translation system, they are registered in the translation environment. In the ABAP environment, a package is automatically assigned to a collection.
If you want to use worklists to translate, a registered collection must be assigned to a translation graph. You can then include the collection in the evaluation runs for worklists. It can also be included in automatic distribution. If the assignment to a translation graph is missing, the collection is regarded as irrelevant for translation (which means it has been locked.)
To ensure a translator can call up the collection in his or her personal worklists, it must also be assigned to the translator. The collections contain objects that logically belong together, which means you can determine the subject area of the texts translated by a particular translator. In this way, you can take account of your translators’ specialist knowledge when distributing translation work.
You should only ever assign translation-relevant collections to translation graphs. This significantly reduces the runtimes for object list and evaluation runs. The assignment must be effected before productive translation starts, and before the worklists are generated.
If you want to exclude collections from translation, assign them to a lock graph. This enables you to make it clear for all users that a collection should not be translated. It is also advisable to create a graph with collections whose translation-relevance has yet to be determined. In this way, you can include these collections in evaluations and use the statistical values, for example, to estimate the amount of translation that would be required.
Prerequisites
· If you want to assign collections to translation graphs or cancel such assignments, your translator profile must include authorization object COGA with the value 01.
· If collections have already been assigned to you and you want to assign them to other translators for a specific target language, or cancel such assignments, you must be defined as a coordinator for the target language. If you want to assign these collections to translators for any target languages, you must be created as a translator for all languages. In both cases, your translator profile must include authorization object USCO with the value 02.
· If collections have not been assigned to you already and you want to assign them to other translators for a specific target language, or cancel such assignments, you must be defined as a coordinator for the target language. If you want to assign these collections to translators for any target languages, you must be created as a translator for all languages. In both cases, your translator profile must include the authorization objectUSCO with the value 02, and the authorization object COSE with the value 01.
Process Flow
There are a number of functions to help you assign and lock collections.
Activity |
For more information, see: |
Assigning Collections to a Translation Graph |
|
Deleting Collection Assignments to a Translation Graph |
|
Selecting Collections |
|
Selecting Translators for Collection Assignments |
|
Assigning Collections to Translators |
|
Locking Collections for a Specific Target Language, or All Target Languages |
|
Checking Which Collections Have Been Assigned to a Specific Translator |
|
Removing Collections From a Translator’s Collection Assignments |
|
Determining the Translators to Whom a Collection is Assigned |
|
Determining Which Collections are Assigned to More Than One Translator |
|
Copying Collection Assignments Between Systems |
|
Displaying Various Translation Overviews |