Show TOC

Object ListsLocate this document in the navigation structure

Use

An object list should contain exactly those objects that you want to translate. When you create an object list, you define parameters to ensure that only the objects relevant for translation are included in the object list.

After you have created an object list, you can use it for the following purposes:

Integration

Creating an object list is the first step towards creating worklists and statistics for each of your required target languages. The next step is evaluating the object list.

You must create a new object list whenever new objects or corrections become available in the system - ideally once a week while development is ongoing. You can then run a new evaluation to analyze the objects in this object list and update the worklists and statistics.

Alternatively, if your development is small, you can use the object list as the basis for creating an on-the-fly worklist of the objects directly in transaction SE63.

Features

The object list report scans the system for the objects that match the parameters you define. For example, you could create an object list that contains all objects in a specific collection (which is known as an ABAP package in the development environment), or all objects in 3 specific transport requests.

You can create object lists according to the following criteria. You can also create an object list according to several of these criteria at the same time. See the examples for a variety of possible scenarios and how to create the correct kind of object list to cope with them.

  • According to collections and object types

    If you create an object list according to one or more collections, the object list only contains objects belonging to these collections. You need to ensure that you include all translation-relevant collections when you define the parameters for the object list. If the collections that you specify also contain objects that are not relevant for translation, this results in unnecessary translation. In that case, you would save time and money by placing the relevant objects in a transport request and creating an object list according to the transport request instead. As well as specifying the collections for the object list, you must also specify the object types.

    Example

    You could create an object list for all objects in object groups A5 User Interface Texts and A6 Table Entries that belong to all collections whose names begin with the string ZFIN.

  • According to one or more transport requests

    If you create an object list according to one or more transport requests, the object list only contains objects that are contained in the specified transport requests. You must therefore ensure that you include all translation-relevant objects in the transport requests that you use as the basis for the object list. If the transport requests also contain objects that are not relevant for translation, this results in unnecessary translation. You can also make a generic entry to create an object list that contains all objects available in all transport requests of a specific type, status, date range, and/or source system. Creating transport requests as the basis for the object list is a great way of ensuring that you have complete control of the objects that you translate. It is also the best way to ensure that you translate any modifications that you have made to objects delivered by SAP .

    Example

    You could create an object list for all objects in released Workbench requests created in the last 6 months from system ABC.

  • According to one or more transport objects

    If you have only a handful of objects that you want to translate and you know exactly how they are referred to in terms of the transport system, you can create an object list by specifying the transport objects.

    Example

    You could create an object list for the following transport objects:

    R3TR PROG ZFIN0001
    R3TR DTEL ZFIN_ORDER
    R3TR DTEL ZFIN_OTYPE
    R3TR MSAG ZFIN

  • According to one or more local lists

    If you have created local lists that are too large to be translated in an on-the-fly worklist, you can use them to create an object list. You then evaluate the object list to put the translation objects into a standard worklist instead.

    Example

    You could create a large local list using a .csv file, use the local list to create an object list, and then use the object list to put the objects in a worklist.

It is possible for an object to be available in multiple object lists at the same time.

It is also possible to refresh the domains when the object list is created.

Activities

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

For more information on how to create object lists periodically, such as once a week, see Scheduling Evaluations.

It is possible to merge several object lists. For more information, see Merging Object Lists.

You can also create a new object list that contains just a selection of objects from an existing object list. For more information, see Editing Object Lists.

Example

You want to translate a selection of packages that you created yourself, as well as the contents of all released Workbench requests from system ABC since January 1, 2014. We recommend that you proceed as follows:

  1. Ensure that the packages that you want to translate only contain objects that really are relevant for translation. If possible, delete any obsolete or test objects and move objects that are not translation-relevant to packages that you do not intend to include in the object list.

  2. Create an object list as follows

    • For the collections (packages) you want to translate, by specifying the required collections and object types in the Evaluate Collections group box.

    • In addition, make the following entry in the Evaluate Transports group box.

    ABCK*

    		 K R 01.01.2014 00:00:00 31.12.9999 00:00:00