Translating Logical Objects

Logical objects consist of table entries that are grouped together for transport and translation purposes. For example, one large table can be divided into multiple logical objects that can be transported and translated separately. They can even belong to different collections and domains.

Logical objects can consist of short texts, long texts, or a mixture of both.

There are two object types for logical objects:

• TLGS: Lockable Logical Objects (Short Texts)

• TLGD: Additional Documentation on Logical Objects

There is also a meta object type for logical object short texts:

• TLOG: Lockable Logical Object (Meta)

For more information, see Accessing Objects via Meta Object Types.

The table below contains examples of types of logical objects and their purpose.

You can translate logical objects in the same way as all other objects in transaction SE63.

• Via a worklist.

  For more information, see Translating Objects via a Worklist.

• By calling up an individual logical object directly in transaction SE63.

  • The easiest way to call up logical object short texts directly for translation is via meta object type TLOG: Lockable Logical Object (Meta). Using the input help function for the Object Type field, you can select the type of logical object that you want to translate, such as ABAP query user group, personalization object, SAP Smart Form, or logical object area. You can then use the input help function for the Object Name field to select from a complete list of logical objects of the specified type. For more information, see Accessing Objects via Meta Object Types.
  • You call up logical object long texts directly for translation via object type TLGD ABAP Documentation: Additional Documentation on Logical Objects. For more information, see Accessing Objects via Object Type IDs.