Learn about customization request and Transport request in SAP.

1. You just started your SAP Training and you are trying to do your first customization request in
the system, the system will prompt you with a Customization Request as shown below.
How do you get past this screen? What is a Customizing Request? Simply put, a customization
request is SAP‟s way of saying
You are modifying the SAP system. Please specify the number to record it under.
You can create your own Customizing Request number or choose from an existing Customizing
Request Number. Since you just started off, create your own Customization request by clicking
on the “new‟ button.
A new window
opens up where you can provide a description of the change. Give a human-readable „short-
description‟ so that you/somebody else can read it later and identify the actual change and click
on the save button in the bottom.

2. A unique „Change Request‟ or „Customizing Request‟ will be created by SAP as shown below.
Click on OK button (Green check mark)
This will record
the change you have done in the customizing request and your change is saved.
What is SAP Transport Request
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 want to understand a
Transport request better, read through.
Scenario: You have created a new Customer Group called ZA – Agency Customer by going
through the following menu path in SPRO -> SAP Reference IMG
Copyright © SAP AG
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?

3. 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)
Copyright © SAP AG
Now, the database table T151 contains the new entries (for the new Customer Account group
that you have created)

4. Copyright © SAP AG
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‟s say, the new Transport Request we have created is VANK900323 which is a unique
number created by the SAP system.

5. These Transport Requests are a log of the database changes done due to some customizing (in
this case, creation of a new customer group) and can be viewed in SE01

6. Click on Display to view all the Transport Requests you have created. The newly created
Transport request VANK900323 has been highlighted below in red.
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

7. on the folder button to the left of the Transport request to view the contents of the change.
As you can see, the view affected in this customization is V_T179 (which is tables T179 and
T179T) and the database contents that have been changed are new entries being created as
follows.
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.

8. There are 3 types of Transport requests:
K type:
The transport K type implements transports of DE objects from the integration system into the
consolidation system. When you create a transport request using the workbench organizer, it
always uses this transport type by default meaning that all the transportable change requests
stored in the workbench organizer are allocate this transport type. For this transport type, the
objects are transported to the consolidated systems without changing the object‟s system owner
which means that the transported objects in the consolidated system become repair objects and
no corrections are allowed for the imported objects.
C type:
With this transport type the objects change the system owner after they are transported which
means that the source system of the object loses its ownership after the object is transported. So
the target system in which the objects are transported becomes the original system. In other
words objects are transported as original objects. So they can be corrected or modified in the
target system too. That means that change authorization is also transported. In SAP terms,
objects that are transported with C types are checked out of a system and checked into another
system.
T type:
This transport type is useful when you have to copy object between two systems in a group ie
when a system(other than consolidation system) receives a copy of objects, the corresponding
transport takes place with transport type T. Object including the object of transport type T do not
change their system owner