Skip to Content
Technical Articles
Author's profile photo Roman Gorbenko

Export and Import tables in SAP from the OS Level with real use case


R3trans is the SAP transport tool is used to transport data between SAP Systems and in the migration use case. R3trans is usually called from other programs (for example tp) and in turn, tp is also usually called from Application Layer (transactions STMS_IMPORT, SPAM, etc)
But sometimes SAP BASIS Administrator must interact with these utilities in specific tasks directly

Real use-case:

For example – your development system contains a lot of “dead” development objects (abandoned internal projects, developers who left the company and did not leave proper documentation, and so on)
The more such objects, the greater the chance that new developments will not work correctly in the QAS and Production systems.
For continuous normal development process, you must refresh the Dev system from the Qas/Prod system (for example via backup/restore homogenous system copy)
This is a very complex task with many pitfalls!
One of them –  Version management
Version management contains only in the Development system so after system copy you may lose this information.
To keep this from happening you must export version management and import them after system copy.
For such a specific task, you can use Export and Import tables in SAP from the OS Level procedure.


In your development system before system copy
Log in via <sid>adm OS-user and execute the following commands
For Linux OS:
R3trans -w /usr/sap/trans/log.txt /usr/sap/trans/export_control
For Windows OS:
R3trans -w <drive>:\usr\sap\trans\log.txt E:\usr\sap\trans\export_control
* export_control file you can download from github, adjust only a file path (String nr.2)
Transport request created on the OS level
In your development system after system copy:
For Linux OS:
R3trans -w /usr/sap/trans/log.txt -i /usr/sap/trans/data/R00000.EWD
For Windows OS:
R3trans -w <drive>:\usr\sap\trans\log.txt -i <drive>:\usr\sap\trans\R00000.EWD
* transport request file name and path you specify in the export_control file from the previous step.
Transport requests contained table content of vrsd, vrsx, etc tables imported in a system from the OS level


SAP BASIS routine task explained.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Mark Wilmowsky
      Mark Wilmowsky

      Dear Roman,

      great blog and I totally agree that there are situations where you have to handle problems directly via R3trans.

      In the case mentioned above would it also be possible, to turn on object versioning during import by setting tp-parameter VERS_AT_IMP, so those informations comes directy from the source system? This would save an additional pre- and post system copy task.


      Author's profile photo SHU FANG
      SHU FANG

      Thank you. This is a good blog.

      I always use this as the backup and recovery of RFC information before system recovery, which is very easy to use.

      This is a good tool