Object Types with Multiple R3TR Transport Objects in the Transport Environment

You can translate object types with multiple R3TR transport objects. This topic explains the concept of R3TR transport objects.

If object types have multiple R3TR transport objects in the transport environment, they are divided into subtypes in the translation environment to standardize the references from translation to the R3TR transport objects. This affects the following object types:

Interface texts
Developer interface documentation
Field selections
Function titles, parameters and exceptions
Function groups
Text elements
Screen Painter headers
Screen Painter texts
Tables

The numbers in the object type IDs of such object types indicate the referenced R3TR transport objects as follows:

Function group (FUGR)
Function group with customer include: SAP part (FUGS)
Function group with customer include: customer part (FUGX)
Program (PROG)
Transaction (TRAN)
Context (CNTX)
Logical database (LDBA)
Class (CLAS)

Example Object type RPT1 = text elements for function groups

Object type SRT4 = Screen Painter texts for programs

Furthermore, the client-dependency and delivery class of a table are relevant to table transports. The object type IDs of tables therefore indicate if the table is client-specific or not.

In the case of client-specific tables, the third letter of the object type ID is D
In the case of cross-client tables, the third letter of the object type ID is I
The last letter of the object type ID indicates the delivery class of the table

Example You call up a client-specific system table for translation via the object type ID TADS.

You call up a cross-client Customizing table via the object type ID TAIC.

In practice, it can prove difficult to find out which R3TR transport object applies to a translation object, or which delivery class a table belongs to. Meta object types make it far easier for you to call up such objects directly for translation.