TRANSPORT REQUEST IN SAP

Transport Request in SAP

Transport Request act as carrier of the configuration settings from one system to another system or one client to another client under the same landscape. Ex: Development to Quality

Each TR contains tasks, we can create no. of task in one TR.

Basically, we make any single configurations changes it means one TR is generated.

Task is given to each user ID. We can assign no of task to one user ID.

Changes made by different user ID will be saved in different customizing task but saved in same TR.

The request is named in standard format <SID> <K> <Number> </Number>

  • SID=System ID
  • K=Keyword or alphabet
  • Number= range starting with 900001

    • Each task contains individual configuration. Task will contain next no. of TR, under the Task we can see the full configuration settings done in system. T-Code used is SE09.



    Types Of Transport Request

    There are two types of Transport Request:

    1. Customizing Request
    2. Workbench Request

    Customizing Request: The configuration settings which are valid or applicable to only the client where we do the configuration. Functional consultant performs customizing request. For Ex: Creation of plant, Mat Type, Stg Loc in SPRO. This changes should be moved from client to client in same landscape.

    Workbench Request: The configuration changes which affect the other clients under the workbench transport request. Technical consultant performs workbench request. If you do any changes in a client it will also see in another client of same landscape. You don’t need to move TR from one client to another client in workbench request. Ex: Maximum changes related to ABAP such as new BADI and BAPI program, when you make changes in PO layout.




    There are two status of Transport Request:

    1. Modifiable
    2. Released

    We can create Transport Request manually also. T-Code SE09.
    Go-to create new option>> It will ask which request you want to create whether Customizing or Workbench.
    Select any one and Click on execute button.


    Give short description, Project and you can also add User-ID in the tasks who can save their configuration changes in same TR.

    For Example: If we create a new storage location in 800 clients and created new TR. But now we will not be able to see that storage location in 812 clients.

    So, in this case we need to transport the new storage location configuration to 812 client for this we don’t have to release the TR because we are working in same landscape (Development Landscape).

    For this scenario we need to logon in 812 clients and go- to T-Code: SCC1


    In the screen put Source client =800 and select Including Request Subtasks tick the check box.
    Now click on Start Immediately. It will ask copy client specific data from 800 to 812 client.
    Say, Yes and the program run successfully. Now you can check the changes(Configurations) in 812 client.

    *SCC1 is performed in destination client.

    Now in Workbench Request, if you have done any workbench related configurations in 800 client you don’t have to move the TR in 812 client of same landscape because it will be automatically get reflected in 800 client.
    But when you want to move the configuration in another landscape (server) such as Quality server. From Development to Quality we need to …

    • We need to release the Transport Request, but while releasing you must first release the customized task which is just below the TR and then the main workbench request number. Without releasing the customized task, we cannot directly release the main TR.
    • T-Code used is SE09


    Now, you can see the Transport Request in Released column.
    After this go to T- Code STMS [SAP Transport Management System] select the Transport Request and click on the vehicle symbol to move to the another landscape. It is performed in destination system.

    Types Of Testing

    There are basically 3 types of testing:
    1. Unit Testing
    2. System Integration Testing
    3. User Acceptance Testing

    UT will be performed in Development Landscape and SIT and UAT will be performed in Quality Landscape.

    Reversing of Transport Request:
    We can reverse the TR once released in specific client from released to modifiable status.
    You can use this function if you have to make any changes in the released TR. There is a standard reverse program to execute the reversal function.

    Reversing of Transport Request:
    1. E070
    2. E071

    You can execute E070 T-code in SE16N and we get the information about the TR whether it is released or not.
    Also we can see the type of TR and which user has created it.
    So, by this method the above content will help you to understand the overview of Transport Request in SAP.
    I hope you find the above post is helpful, do share your thoughts and feedback me on email: basavaraj.gulgutti@walsystems.com .



    Author

    Basavaraj S Gulgutti
    SAP IBP Consultant, Baranwal Consultancy and Services (BCS), Pune, Maharashtra, India

    Go to top

    Sidebar Menu