Preface – This post is part of the ABAP Beginner series.
Table of Contents
Before we start with Transport Request in SAP, let us discuss basic concepts of coding environements/landscapes in SAP. In SAP ERP, we have three landscapes: Development, Quality and Production.
- Development landscape is where a developer develops his/her codes/programs.
- Quality landscape is where a developer/tester tests his/her codes/programs.
- The production is where users actually use the programs made by developer.
These landscapes give us flexibility to develop, test and run our under-development code before actually giving to the end user. In this way we can find and fix bugs that can actually cause crashes and dumps.
Now, to make a connection between these landscapes and to transfer our code, SAP provides us something known as Transport Request.
What is a Transport Request in SAP?
A transport request is a package where a user can register changes done. It is used in order to transfer data from one installation to the other.
Whenever we do a small or major change that can be an update an SAP user has to create TR.
TR holds change tasks that can be understood by a folder that holds files.
SID: System ID
K: After releasing TR creates a data file and co-file where data file holds database details and co file contains controlling data.
NUMBER : Starting with 900001(randomly generated).
Category of Transport Request
A TR can hold n number of sub request tasks categorized as:
- A task is not released yet.
- One can add more tasks and complete them before TR is finally released.
- Tasks are completed and then it is released by the owner.
- One cannot do changes and send it to the target system.
Types of Transport Request
TR is preferably created in two types, but we will discuss others too.
- TR created as workbench request is cross-client i.e. changes done for one client reflects in the other client.
- It is synonymously said that this type of request is created by technical
- TR created as Customizing request is client specific i.e. changes done for one client won’t reflect the other client.
- A client copy has to be created using T-CODE SCC1.
- Client number can be seen next to this type of request
- It is said that this type of request is created by a functional person