SAP Transports: difference between R3TR and LIMU

Development objects in SAP world are being moved within the SAP systems via so called SAP transports. SAP system records all changes made (ABAP workbench or customizing changes) in the system in transport requests. Particular object that is being transported is uniquely identified via below combination of keys within the transport. There can be many objects included in one transport.

 

Program ID (PGMID, 4 char)

Object Type (TROBJTYPE, 4 char)

Object Name (SOBJ_NAME, 10 char)

 

Program ID - identifies the type of the transport entry. It has following values:

R3TR - Name for Repository objects and Customizing objects, so called Full/Group Object

LIMU - Subobject of Repository/Development objects

LANG - Language specific part of object, e.g. some selection text of the ABAP program that are maintained there. This can include different language versions of such a text elements.

CORR - Comment (Automatic)

* - Comment Line

Object Type – Type of particular objects, e.g. PROG for Program, CLAS for ABAP Objects Class, ADSO for DataStore Object, HCPR for SAP HANA Composite Provider etc.

Object Name – particular object technical name itself

 

A difference between R3TR and LIMU is that the R3TR stores an information about the whole object (let it be an ABAP class). Whereas the LIMU stores an information about subjects e.g. a method of the ABAP class. Best practice from my point of view is to always transport object in full. Means instead of just taking a piece of sub object to take whole object. Of course as you are the only developer that is working on the whole object.