How To Fix TR731 - System objects cannot be transported directly (e.g. T100, TRDIR, TFDIR..)

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 731

• Message text: System objects cannot be transported directly (e.g. T100, TRDIR, TFDIR..)

What causes this issue?

System table entries cannot be transported in the same way as regular
table entries.

System Response

The function was canceled.

How to fix this error?

Do not use transport object R3TR TABU for the entries in the following
tables. Use the transport objects below instead:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

ACLPERMIS: R3TR PINF (package interface)
CTS_HOT_PACKAGE, CTS_HOT_OBJECT:,,R3TR HOTA (Hana object transport -
full object)
CVERS: R3TR VERS (version number)
D010*: R3TR PROG (programs)
D02*, DYNP*: LIMU DYNP (dynpros)
D3*, EUDB, RSMPTEXTS: LIMU CUAD (interfaces)
DD01*, DD07*: R3TR DOMA (domains)
DD02*, DD03*, DD05S, DD08*, DD09L: R3TR TABL (tables)
DD40L, DD40T, DD42S: R3TR TTYP (table types)
DD04*: R3TR DTEL (data elements)
DD06*, DD16S: R3TR SQLT (SQL table)
DD12*, DD17S: LIMU INDX (table index)
DD2*: R3TR MCOB (matchcode objects)
or R3TR MCID (matchcode ID)
or R3TR VIEW (view)
or R3TR ENQU (enqueue object)
DDTYPET: R3TR TYPE (type group)
DEVL, DEVLT: R3TR DEVC (package)
DIAPAR: R3TR DIAL (dialog module)
DOKHL, DOKIL, DOKTL: LIMU DOCU (documentation)
DSYST, DSYSX: R3TR DSYS (hypertext objects)
E07*: LIMU COMM (piece list)
EUIMPORT: LIMU CUAD (interfaces)
FUNCT, RODIR: R3TR FUGR (function group)
IFOBJ*, INTF*: R3TR PINF (package interface)
LDB*: R3TR LDBA (logical databases)
OBJ*: R3TR TOBJ (specification of a
transport object)
O2APPL*, O2NAV*, O2PAG*: R3TR WAPA (BSP application)
REPO*: R3TR PROG (programs)
RSDSQ*: R3TR DSEL (selection view)
SEO*: R3TR CLAS (classes)
R3TR INTF (interface)
SOTR_LINK: R3TR SOTS, SOTR (OTR concepts of a
package)
SOTR_*U: R3TR SOTS (OTR concepts of a
package)
SOTR_*: R3TR SOTR (OTR concepts of a
package)
SPROX*: R3TR CLAS (classes)
or R3TR INTF (interface)
or R3TR DTEL (data elements)
or R3TR TABL (tables)
or R3TR TTYP (table types)
STX*: R3TR FORM (SAPscript form)
or R3TR STYL (SAPscript style)
or R3TR TEXT (SAPscript text)
SVERS*: R3TR VERS (version number)
SYSTABSTMT: R3TR DDDD (change to the nametab
structure)
T100*: R3TR MSAG (messages)
TADIR: LIMU ADIR (object directory entry)
TAPPL: R3TR APPL (application class)
TCDCOUPLES: R3TR TRAN (transactions)
TDCT: R3TR DIAL (dialog module)
TDEVC, TDEVCT: R3TR DEVC (package)
TFAW*: LIMU FSEL (field selection)
or R3TR PROG (programs)
TFDIR, ENLFDIR, FUPARAREF, TFTIT: R3TR FUGR (function group)
TITLE: R3TR PROG (programs)
TLDB, TLDBT: R3TR LDBA (logical database)
TLIB*: R3TR FUGR (function group)
TPARA*: R3TR PARA (parameter IDs)
TRDIR: R3TR PROG (programs)
TSPIN, TSPTB: R3TR TABL (tables)
TSL1*: R3TR SYAG (syslog messages)
TSTC*: R3TR TRAN (transactions)
VARI*: LIMU VARI (variants)
WDY_*: R3TR WDYN (Web Dynpro)
All other system tables are either in ABAP Dictionary or are used as
internal tables of the SAP system. They are not transportable.
The object name is a mandatory field and cannot begin with a comment
(*).
Do not use a name for LIMU COMM transport objects that is structured
like request/task numbers in Transport Organizer (sysKnnnnnn).
<ZH>Note</>
Direct transport of these table entries is only allowed for special
tools, such as the client copy program.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR731 - System objects cannot be transported directly (e.g. T100, TRDIR, TFDIR..) ?

  The SAP error message TR731 indicates that you are attempting to transport system objects directly, which is not allowed in SAP. System objects include tables and other elements that are part of the SAP system's core functionality, such as T100 (text elements), TRDIR (transport directory), and TFDIR (function module directory). These objects are managed by the system and should not be included in transport requests.
  Cause:
  The error occurs when you try to include system objects in a transport request. This can happen if:
  
  You are trying to transport standard SAP objects that are not meant to be transported.
  You have mistakenly included system tables or other system-related objects in your transport request.
  
  Solution:
  To resolve this issue, you should:
  
  Review the Transport Request: Check the contents of the transport request that is causing the error. Remove any system objects that should not be included.
  Use Custom Objects: Ensure that you are only transporting custom developments or configurations that are meant to be moved between systems.
  Check Transport Layer: Make sure that the transport layer is correctly set up and that you are using the appropriate transport request type (e.g., customizing, workbench).
  Use Transport Organizer: Utilize the Transport Organizer (SE09 or SE10) to manage your transport requests and ensure that only valid objects are included.
  
  Related Information:
  
  Transport Management System (TMS): Familiarize yourself with the TMS, which manages the transport of objects between SAP systems.
  Transport Request Types: Understand the different types of transport requests (Workbench requests for development objects and Customizing requests for configuration changes).
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to transport issues.
  Documentation: Refer to SAP documentation for best practices on managing transports and understanding which objects can be transported.
  
  By following these steps, you should be able to resolve the TR731 error and successfully manage your transport requests in SAP.