Object Lists 

Use

Object lists, which are not language-dependent, contain a subgroup of all objects in the system that can be translated. You set various parameters to determine which objects are included in an object list, in accordance with your translation objectives. The objects that are included in the object list form the basis of language-dependent evaluations to create the global worklist. Therefore, the object lists indirectly determine which source texts can be called up for translation in the worklists.

Object lists are also used to create demonstration objects, and transport proposal pools.

Integration

The global worklist is created for translation when one or more object lists are evaluated.

You need to create a new object list every time new objects or corrections are imported into the system. You can then run a new evaluation to analyze the objects in this object list, or in several object lists, in order to update the global worklist, create new demonstration objects, or prepare a new proposal pool transport.

Features

The object list creation program scans the system for translation-relevant objects. You set parameters to determine the basis for this. You can generate object lists on the basis of specific collections for a particular development, or for the entire system. In ABAP systems, you can also generate object lists on the basis of transport requests, piece lists, and transport objects. Furthermore, object lists can be created in accordance with various criteria.

The domain assignment can be renewed while an object list is being created. This is necessary so that application standards can be created for a valid domain when translation subsequently commences.

Object list according to collections

If you create an object list on the basis of collections, objects are only included in the object list if they belong to the collections you specified. No other objects in the system are taken into account. This method of creating object lists is useful if only some of the objects in the system are translation-relevant, and you are quite sure you know which collections contain these objects. The disadvantage is that the resulting object list could contain more objects than actually need to be translated. Objects in collections that you have not specified for the object list are not offered for translation via the worklists. For example, this is the case if new collections are created during translation and you forget to add them to the object list parameters.

If object lists are created on the basis of collections, you can also determine which object types should be evaluated.

If you want to evaluate the entire system for translation, create an object list for all of the collections in the system.

Object list according to transport requests

If you create an object list on the basis of transport requests, objects are included in the object list if they are imported into the system with the transports you specify, and as of a date that you also specify. You decide which transport types are evaluated, and the status that the transport requests require. You can also make generic entries, such as ABCK* to evaluate all of the transport requests from system ABC. You are advised to use this method if the texts to be translated are not restricted to specific collections. The disadvantage is that more objects than necessary may be translated in the worklists. You must also remember that objects imported into the system via transports other than those used to create the object lists are not included in the object lists.

Object list according to piece list

You can create an object list on the basis of a piece list, which is a subcategory of creating object lists on the basis of transport requests. Objects only appear in translators’ worklists if they have been explicitly specified in the evaluated piece list. All of the objects that are not included in this piece list are ignored. Using this method, you can ensure that only translation-relevant objects can be called up for translation in the worklists. However, you must first create the piece list and then keep it up-to-date during the translation project.

Object list according to transport objects

If you only want to translate a specific transaction or screen, and if you know the transport object(s) of this transaction or screen, you can create an object list specifically for this transaction or screen. Note however that this object list does not contain any table keys (the affected objects are in table E071K.)

An object can be in more than one object list at the same time. However, it can only be in one global worklist or demonstration object at a time.

Activities

Object lists are created in three steps:

...

       1.      The object list is registered with a unique number

       2.      Parameters are maintained for the object list

       3.      The object list is created

For more information on how to create object lists, see Creating Object Lists.