Creating a SAP Transport

SAP uses a three stage development cycle (at least where I work) which requires developers to make changes in the development system and then users to test the changes in the test system before they can be released into production. In order for changes to get from one system to the next a transport must be made. This post will detail the steps required to create a SAP transport.

The first step is opening the transport manager, which is transaction SE09, in the development system. On the selection screen enter the desired user name and click display. Then, you click on the new request button and choose either customizing or workbench. On the next screen we have special format that we use for the short description:

  • aa -- SR for helpdesk service request or CR for a project generated request 
  • nnnnnnnn -- The request number 
  • bb -- the system, LE for logistics execution, MM for material management, etc. 
  • d -- C for customizing or W for workbench 
  • ww -- the calendar week 
  • yy -- the year

Now we have a request number that can be entered after we save a change using SPRO (for customizing) or after we active an ABAP program or SmartForm.

After the change is assigned to the transport number we go back into SE09, click on the customizing or workbench task click the "Release directly" button (or hit F9). This will prompt to document you change. Once documenting is complete it must be saved. Next, click the request and click "Release directly" again. For programming changes a code review will be necessary, otherwise you will be taken directly to the project selection screen. There is a folder for each of the different SAP areas, and underneath those folders are more folders for the type of change, select the appropriate change type.

Now the transport is nearly ready. At our company we use the RealTech transport manager (transaction code /RTC/TM). Once in the transport manager the author name must be filled in, then hitting enter will open the transport workflow monitor. Items show up here every half hour. Once it shows up, highlighting the line and clicking the "Next status" button (down arrow) will move it to the signature queue. For our company we must now send an email to one of the people who are authorized to sign off on the change and they will release it.

The system will then transport the changes.

Comments (newest first)

SAP Program Manager
If you are using Solution Manager and CHARM then I recommend creating transports using CHARM. But nevertheless you can still create transports in STMS.

For regular traditional approach, I recommend that appropriate technical architects and Sr developers review tasks and objects under each transport, group the requests and approve to maintain a better integrity of your RICEF and config objects.
Published: 2009-04-23