R3trans log file

BTW, you might get more ideas related to system copies and saving of system specific tables by viewing the components and their related tables in this function module. However, due to license issues the use of the PCA tool requires some prerequesites the program might deny your request. In that case you can try this program which is a modified copy of it, showing all components managed by the PCA tool and their related tables in one big list.

Some of the given tables are client-dependent other than most of the RFC tables , therefore you have to specify a client. Of course you can also specify a specific client. Regarding the RFC tables saving the data for all clients is to be recommended see footnote 1. Depending on the release of your SAP systems maybe not all of them exist in your system. Sc4SAP checks this and indicates missing tables.

Just leave them out. As our purpose in this example is to create a backup of table contents we place the backup file on the application server. Of course you can also use the frontend for storing the data. In that case you have to use an SAP connection using a user with dialog capabilities because of the download of the data file to your computer. Now let's start the export. If we would have used the Frontend as the location it would of the data file this could be done by a mouse click only, but in this case we used the server.

So we use transaction AL11 for viewing the log file. The log file contains the information about the written data:. That's all for the moment. It took only some minutes to create a backup file of the RFC connections - and hopefully we don't need it, but in case the RFC connections would get lost shit happens! The following modes are available:. Normally only change requests with the status A all locked , O open or R released are exported. If the transport succeeds, the change request is released by R3trans.

Some tables are part of complex objects and generally cannot be exported alone. Usually only objects which have not already been imported successfully are imported again. The following options are possible: -c f1 f2 : Copy file f1 to f2 with character set conversion.

Test if SAP database is available. All database changes are rolled back. See below. Write more details to the log file. Some tables are part of complex objects and generally cannot be exported alone.

The following umodes are available during imports : 0 : overtaker, leave the respective task in the buffer, mark it to be imported again 1 or I.

This umode normally only appears in the buffer when umode 0 has been used. J in buffer only : repeat the import of the transport request into the respective client from the beginning. That means for example that client independant objects are not imported again. F in buffer only : buffer entry is at a wrong position. A subsequent implicit addtobuffer will correct that later. This umode normally only appears in the buffer of delivery systems when umode 0 has been used.

N in buffer only no delivery. This flag normally is set by the TMS workflow during their addtobuffer commands.