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 that you create

You must create a new object list whenever new objects or corrections are imported into 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.

Alternatively, if your development is small, you can use the object list as the basis for calling up a worklist of the objects directly in transaction SE63.

Features

The object list creation program scans the system for the objects that match the parameters you define (for example, all objects in a specific collection (package in the development environment), all objects in 3 specific transport requests, and so on).

It is possible to 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 at the end of this section for a variety of scenarios from real life 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 those collections. You need to ensure that you include all translation-relevant collections when you define the parameters for the object list. If the collections you define 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 also need to define the object types to be included in the worklist.

    Example

    You could create an object list for all objects in object groups A5 and A6 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 transport requests in question. You therefore need to 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, date range, and/or source system. Creating specific 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 on objects delivered by SAP (for example, while performing Customizing).

    Example

    You could create an object list for all objects in Customizing requests from system ABCK* created in the last 6 months.

  • Object list according to 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 for them by simply listing them in the Transport Objects section of the object list definition.

    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

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

It is also possible to renew the domain assignment during the object list creation run.

Activities

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

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

You can also create a new object list that contains only 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 all Customizing performed since January 1, 2007. 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 objects and move objects that are not translation-relevant to packages that you do not intend to include in the object list creation.

  2. Make sure that all the Customizing that you want to translate is actually available in released transport requests of the type Customizing.

  3. Create an object list as follows

    • For the collections (packages) you want to translate, by selecting the required collections and object types in the Global section of the object list parameters screen.

    • In addition, make the following entry under Transports in the ABAP System section of the object list parameters screen.

    Table 1:

    ABCK*

    		 W R 01.01.2007 00:00:00 31.12.9999 00:00:00