Skip to main content

Process table data using R3trans

With this function you can save and restore any table from the SAP system. Use it to save data in front of a system copy and restore them afterwards (for example the system specific RFC connections) or to copy data from one system / client to another.

In this function the "R3trans" utility of SAP is used. R3trans is available in every SAP system as an essential tool of the transport management system. If you have a transport request containing table data, the data was read from the database and written into transport request file by R3trans, and if you import the transport request into a system, reading the transport request and putting the data into the database of the target system / client will also be done by R3trans. It is suitable for small tables as well as for big tables.

The small "i" button right from the input field for the tables offers a list with the fields of the selected table.

If at least one of the specified tables is client-dependent, the client has to be specified in the input field. Different from other functions you can also enter "*" for specifying all clients.

The available operations with R3trans can be chosen from the list box. Here are some typical scenarios that can be done with this function:

Save some system specific tables in front of a system copy and restore them afterwards

In front of the system copy use "Export" to store the data in a data file. As usually a system copy means that "only" the database will be renewed you can use the server as location for the data file. After the system copy restore the data using "Remove / ClientRemove" (empty the tables) and "Import" (to fill the tables with the saved data).

Save some system specific tables for protecting the operability of your system

There are lots of tables in your SAP system containing system specific data. Your SAP system is the one and only source for this data, and in case this data gets lost it can not be copied from anywhere except from a full system copy from a backup! Think of RFC connections and other settings. In case they get lost (by a stupid mistake or a misdirection of an incorrectly created transport request) you will be in a lot of trouble.

Use the "Export" function and a data file on the application server to have a backup of these system specific data. In case you need it you can use it to restore the data and enable your SAP system again.

Hint: when using the "Import" function, you do not have to specify all tables contained in the data file. You can also specify only a subset. Only the data from the specified tables is then processed.

Copy data from one system / client to another one

Use "Export" to store the data in a data file - here the location on your computer might be suitable in most cases, because usually the source and the target system / client do not use the same file system. If you do an "Export" of big tables and you specify the data file to be stored on your computer, it might be that the data file will be splitted into parts of max. 100 MB. If you use the splitted files for "Import", "Testimport" or "List data file content" later, the splitted files will be uploaded and automatically concatenated to one single file on the application server (it is the same logic as available in the "Download / upload server file" function in category "Miscellaneous".

Use "Remove / ClientRemove" for deleting the data in the target system / client, afterwards do the "Import" to fill the tables again using your data file.

When "Remove / ClientRemove" or "Import" is used this function is highly critical from data consistency point of view. Handle it with care and know exactly what you do, please!

If you specify the data file to be stored on your computer, a file transfer between your computer and the SAP server will be (automatically) done which requires the availability of an SAPGUI and a user with dialog capabilities used in the chosen SAP connection.

In case your dialog user is not authorized for the execution of R3trans think about a step-wise approach:

- use a connection with a system user executing R3trans and specify the data file on the SAP application server.
- use the "Download / upload server file" function in category "Miscellaneous" with a connection using a dialog user for transferring the files between application server and your computer.

The order depends on the R3trans operation (see above). The idea is to split R3trans execution and file transfer by using different users in different connections.

If you use your computer as location of the data file, the function does these steps:

"Export": first the R3trans utility will be executed, then the data file and the log file will be transferred to your computer. After the file transfer the data file and the log file on the application server will be deleted.

"Import", "Testimport", "List data file content": first the data file will be uploaded to the application server. Then R3trans will be executed and afterwards the R3trans log file will be downloaded to your computer. At the end the data file and the log file on the application server will be deleted.

"Remove / ClientRemove": for this operation no data file is necessary. First R3trans will be executed, followed by the file transfer of the R3trans log file to your computer. After the file transfer the log file on the application server will be deleted.

In case you import data of tables containing a logical system name from another system / client: consider that for adjusting logical system names a BDLS run for these tables might be necessary.

This function is also in the command line tool available.

####