Importing/Exporting Development Objects

Whether you want to transport your abap developmnents from one system to another, make backups or share code, you have several options to choose from:

  1. Code download and upload via ABAP Editor
  2. SAP Transport Requests with full import/export capabilities in cofile and data format.
  3. SAPLink – an open source project (not provided or supported by SAP) with partial import/export capabilities in XML format.

Each of the above methods has its pros and cons:

  • use code download/upload if you have just one file/report to export/import. it doesn’t require any special usage rights or settings configurations. but you can’t export multiple files at the same time or database data with this method.
  • use SAP transport requests if you have the required usage rights. exporting from a newer version system to a lower version one can lead to errors as the low version system may not be able to support the exported files.
  • use SAPLink if you want more control on how to group exporting objects. this way, a lower version system can partially import objects from a newer version system without generating errors. at the moment SAPLink does not support all development objects.

A. Code download and upload
From the ABAP Editor, choose Utilities -> More Utilities -> Upload/Download. Upload acts as an import, download acts as an export. It doesn’t get more simpler than this but you’re restricted to one file at a time, only code and no dictionary data saving.

B. SAP Transport Requests
You need to have authorization to transaction STMS and be able to run a STMS import activity.
a) when creating a new abap development object you’re prompted to select a package and if it’s not a local object, you’re prompted to select a transport request or create a new one. via this transport request you can import/export your projects.
b) under SE80 (Object Navigor) select “Transport Organizer” -> select the request you’re interested in, right click “Release”. you will have to release the sub requests shown in the display tree before releasing the main request.
Note: This step may throw the following error: “ ended with error code 0208”.
Check if everything is running as it should by STMS -> Imports -> Import Queue -> Check -> Transport Tool. It will check tp Interface, Transport Profile, RFC Destination and tp Call. You should see a green arrow if everything is working fine. If not, check the following:

  • under the transport directory, usually something like C:\usr\sap\trans, make sure bin/DOMAIN.CFG and bin/TP_DOMAIN_NSP.PFL exist. if they don’t, run STMS (Transport Management System) -> Overview -> Systems -> Select the NSP System ->  Extras -> Distribute and Activate Configuration -> Distribute Configuration to All Systems
  • if this throws an error as well, run STMS -> Overview -> SAP System -> Change. Under Communication tab make sure target host is valid and under Transport Tool tab make sure transdir is correct.

c) request has been released, you can now see it exported under two files located under /usr/sap/trans/cofiles/K<trans_number>.XXX and /usr/sap/trans/data/R<trans_number>.XXX . Cofiles contain TRQ (transport request) metadata while the data files contain the actual TRQ content.
d) to import a TRQ, copy the exported cofile and data file to the corresponding /usr/sap/trans/cofiles/ and /usr/sap/trans/data/ directories of the system you want to import the files into
e) run STMS -> Overview -> Imports -> double click the system you’re interested in -> Extras -> Other Requests -> Add -> Enter request number -> Attach to import que. Queue -> Start Import -> Immediate.

C. SapLink
Download the latest version from Instalation wiki pages describe the process in details. Basically you create a new program and copy/paste saplink abap installer code. This will create the saplink program ZSAPLINK. Running this will allow you to import/export single (slinkees) or multiple objects (nuggets).

By default, SAPLink does not support a lot of ABAP object structures but you can install SAPLink plugins also available from their homepage to handle abaps like DDic, BSP, WebDynpro and so on.

One thought on “Importing/Exporting Development Objects”

Leave a Reply

Your email address will not be published. Required fields are marked *