Transport Requests in SAP are the ONLY way in which you can record changes and move them across systems. Let’s take a simple example to understand this better. If you just want to quickly create a transport request in SAP, follow this link. If you want to understand a Transport request better, read through.
Copyright © SAP AG
The detailed steps to create this is available at How to Create new Customer Groups in SAP. When trying to save the newly created customer group you get the following window. The fields Request and Short Description might be empty in your case. What does this mean and why is this being shown ?
Copyright © SAP AG
Solution : If you look at the “View Maintenance : Data..” field in the picture above, you can see some database table view V_T151. This is an internal SAP defined view which will contain a bunch of database tables that has been updated by this change. What this essentially means is that, the process of creating the new Customer Group “ZA” has resulted in a new database entry being created in the tables T151 ( The view V_t151 consists of the database tables T151 and T151T as shown below)
Now,the database table T151 contains the new entries ( for the new Customer Account group that you have created )
This example illustrates something very important.
Most Customization requests are mere entries in some Internal SAP Database tables
If some changes to the database is happening, it needs to be recorded. Why ? In order to understand this you would have to understand the concept on SAP Landscape. To simplify things, let’s just say that if you need to move ( “Transport” ) the changes that you have done in a system to another system, ( Instead of recreating them in the new system ), you should let the source system record the changes. A “Transport Request” is SAP’s way of recording changes to the source system and generates a unique number for you so that you can just give that number to your SAP System Administrator ( SAP Basis Consultant ) and ask him to migrate the transport to the new system.
Let me take another example of SAP Product Hierarchy that I have created and saved using the SAP Transport Request Number VANK900319 ( The one right above the highlighted one ). Click on the folder button to the left of the Transport request to view the contents of the change.
It is exactly these entries that are being recorded in the Transport Request.
Now you know the contents of a Transport Request, why transport requests are created, but who transfers these to the Target system ? The Basis Consultant is responsible for this. When we discuss the SAP System Landscape, we will discuss more about this.
Types of Transport Requests
1. Customizing Transport Request
2. Workbench Transport Request
We will discuss these in detail in the class.