Skip to Content
Author's profile photo Daniel Lippmann

Executing server-side processes

Be aware that you should only do things which won’t harm system!

Maybe you know the problem – you have to execute something at OS level and don’t have access. Basis team isn’t accessible and it’s urgent…

With a few tricks, you can help yourself.

Example 1: Manual import of transport requests

Starting situation: You have to import a transport request and don’t have proper rights in target system, but are allowed to call transaction SM69.

First, you need to find out where the transport profile is located – usually in /usr/sap/trans/bin. AL11 or RZ10 might help.

Next step is to check if there is a command in SM69 defined, if not, create one:



After that, you may run it. First add your transport to buffer:


The syntax is (write in field Additional parameters):

tp pf=<transport profile> addtobuffer <transport request> <SID> client=<target client>

After that, you can import it:


Just change “addtobuffer” to “import” – you may even add unconditional modes with the U flag, refer to tp Options – Software Logistics – SAP Library

Example 2: Exporting table contents

Starting situation: You need to export complete table contents with R3trans in order to import everything in a target system. First of all, you need to define your export file. Create a new file with thetext editor of your choice (mind to use proper line ending):

file = '/tmp/export.txt'
delete from <table>
select * from <table>

The delete statement is not executed when you export the table, only at import. Uploading this file can be done with transaction CG3Z:


After upload, just call R3trans using SM69 with these parameters:

R3trans -w /tmp/output.txt /tmp/export/controlfile.txt

When the export is done, you can use CG3Y to download the file. Upload it and import it in the target system with:

R3trans -w /tmp/output2.txt -i /tmp/export.txt

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.