Skip to Content
Author's profile photo Former Member

How to Manually import transports into SAP without using command line TP

Manually Importing Transports into SAP – A practical how-to for beginners
Sometimes you will receive transport files from external developers who have developed custom solutions for SAP and you will be required to import their transports into your SAP System manually. If you are new to SAP Basis like me then you will find this helpful, if your old-hat though its probably nothing you haven’t seen before.
It used to be done the old school way using the “tp”commands like the following:
D:\usr\sap\ECD> tp.exe addtobuffer K900237.X20 ECD client=100 pf=\\bansapdevap01\sapmnt\trans\bin\TP_DOMAIN_ECD.PFL
However I found that our PFL file just did not seem to be compatible for some reason this command does not work – why I didn’t really spend too much time trying to figure out, instead I figured there must be a better / easier way to do it by now than just command line.
So Instead of doing it through command line I did the following:
     1. Unzipped the transport file sent through by the developer
     2. This gave me two files:
          a. K900237.X20
     3. Naming convention used is R<6 digits>.<source system> and K<6 digits>.<source system>  (The Source system is the developers source system)
               a. K Type Transport = Cofile – Normally only 1 – 3 KB
               b. R Type Transport = Datafile – Normally more than the Colfile
     4. K900237.X20 was a Cofile –  it doesn’t contain much data, it has the attributes of the data file stored in it. Command or change request information files that include information on the transport type, object classes, required import steps, and post-processing exit codes
     5. R900237.X20 was a Datafile – This contains the actual data for the Transport – what changes will be made in your system.
     6. Go to the Development Server and navigated to the following directory: D:\usr\sap\trans
               a. Copy the K Type Transport to Cofile folder located in D:\usr\sap\trans\cofile
               b. Copy the R Type Transport into the data folder located in D:\usr\sap\trans\data
     7. Go into the SAP ECC Dev System and proceed to transaction STMS
     8. Proceed to import queue (F5 then Select Dev System)
     9. Go to the Extras Menu, Select Other Requests then select Add
     10. This will show the following screen, enter your target client (in our case it is 100 as the  golden development system)
     11. Then select the Transport request search button
     12. Search for your transports by entering the * at the start for a wildcard selection and then putting in the  digit code in the transport file – ie *900237      don’t include the .x20 extension, this will likely show up as the transport prefix) and lastly ensure you pump up your number restriction to a number that      will give you the result you are after.


     13. Find your transport number and select it


     14. Then you will end up with a screen like below with your transport request filled out, target client and import queue filled out. You can if you want select import again if you are re-importing this transport.


     15. Click Yes when asked to attach to import queue


     16. Then once it is attached to the import buffers, import the transport then use the forward transport options from the menu system to send the      transport to QA for testing.

Assigned Tags

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

      Hi Mapp,

      Do you have any idea what is the authorization to have in STMS--->Extras Menu---> Other Requests ---->Add? I do not have that.

      Thanks for the help.


      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Angel, Sorry I've only just gotten back to you, was a busy year last year 🙂 I run in Dev with SAP_ALL / SAP_NEW so don't have any authorization issues when dealing with transports et-al


      Author's profile photo Giovanni Leggio
      Giovanni Leggio

      Thanks Tyrone. Great blog on on how to "Import the ABAP transport"

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Cheers mate

      Author's profile photo Mohammed Ezzat
      Mohammed Ezzat

      Dear Sir

      many thanks to you , i follow steps in document , i success in importing the request , but when i open Tcode STMS , and used my way to import them

      ABDK902529 ( from DEV server )

      ABDK902519 ( from QAS server )

      as you in statue it take along time to execute , and still running .

      my to import as the following :



      finally it works now

      Author's profile photo Deidre Logan
      Deidre Logan

      But how do we add a set of transports to the Import buffer without using scripting of the tp addtobuffer command.  STMS only allows you to do a single transport at a time.

      This is very cumbersome when you have more than 5 transports....

      Author's profile photo SAP BASIS

      tp provides an addtobuffer option

      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      Thanks for the blog! We have no Basis person on staff and I just got mystery files R... and K... by email. Because, you know, I'm an ABAPer and this has something to do with ABAP, so somehow I'm supposed to know what to do with those files. But with the blogs like this who needs Basis, he-he. 🙂

      Just a couple of hints for the "shadow Basis" folks:

      - you can use transaction CG3Z to copy the files from your PC to the directories mentioned

      - directories may look different in your system, go to transaction AL11 and look for DIR_TRANS there (or similar) to confirm

      - if you just need to import the transport into current client, instead of STMS transaction use STMS_IMPORT, it will save you a step and take you right to the transport queue.

      Thanks again!

      Author's profile photo Michael Flash
      Michael Flash

      thanks for the blog. I am new and i do know this process. The question I would like to ask though is after you "forward" to QA, is there any way for this manual transport to be added to the production queue?

      If you transported a Dev transport into QA and execute in QA, it will then appear in production. this doesn't happen when you are using manually added transports. Is there any way to make this happen?

      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      You should be able to add those transports manually to QA or PRD queue the usual way (Add Request menu). But the way we handle this is we only put these transports into DEV system. Then we create a transport of copies (TOC) and use only that TOC to move the changes to QAS and PRD. This also covers our internal audit requirement since our transports have to reference the ticket numbers. And it's not unusual that the objects actually need to be modified slightly after the import.

      Have you ever wondered why the transports properly created in DEV magically appear in QA and PRD queue? Look at their Properies tab. Most likely they are assigned to the "Target Group" while these "foreign" transports are probably imported into one client.