Translating Logical Objects 

Use

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:

·        Lockable logical objects (short texts) with the object type shortcut TLGS

·        Long texts for logical objects with the object type shortcut TLGD

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

Logical Object Type	Purpose
BMFR	Texts in the application hierarchy
CUS0, CUS1, CUS2	Texts in IMG structures. See Translating IMG Structures.
VCLS	View cluster texts
PDWS	Workflow templates

Procedure

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

·        Via a personal worklist. See Translating Objects via a Personal Worklist.

·        By calling up an individual logical object directly in transaction SE63. See Translating Objects Directly.

The technical name of a logical object consists of the technical ID of the logical object type, the actual object name, a variable number of blank characters, and the table in which the logical object is defined. Example:

§         CUS0SIMG_CFMENUOCNGBCG3         04

§         CUS10ALE_HRDST_FSD         02.

It is difficult to estimate the number of blank characters, so you are advised to enter the object type and object name and then start an F4 search using a placeholder. For example, CUS0SIMG_CFMENUOCNGBCG3*. You can then double-click the object you require from the dialog box that appears, and access it in the short text editor by choosing Edit.