In this topic, we described about the below sections -
Transport request is a collection of information about the configuration changes required to move one source to one or more destinations. Transport request is created for changes in configuration table or program.
Each transport request contains one or more change configurations which are also called as change tasks. Change task is assigned to only one user and is a set of objects that are modified by the specified user.
A transport request can contain multiple tasks which are completed by multiple users. The transport request contains multiple tasks which are saved like files stored in folder of windows.
Task are not self-transportable but part of transport request. Transport request can be released only once all the tasks inside transport request are completed, released or deleted.
The transport request movement from one client to other is done by basis team. Transport request records the information regarding the type of change, the purpose of transport, request category and the target system which is known as Change Requests.
Transaction SE09 is used to transport a Transport Request From one client to other. Change requests are named in a standard format shown below.
- SID – System ID.
- K – Specifies the keyword/alphabet.
- Number – can be anything from a range 900001 to 999999.
These change requests are not modifiable by system administrators.
Transport request Types -
There are four types of requests
- Local request
- Change request
- Transport of copies
- Workbench request
Local Request -
This request resides on same box and can't transportable to other SAP R/3 systems. These kinds of request are of only workbench types.
Change/Customizing Request: -
These requests are generally for system customizing activities done in SPRO. Change task is assigned to only one user and is a set of objects that are modified by the specified user to transport from one system to another system. The change requests are of two types -
- Customizing change request
- Workbench change request
A request for defining/customizing settings.
The customizing change request are of two types.
- Client dependent
- Client independent
Workbench Request -
These requests are for the changes made in the ABAP workbench. The changes are mostly code or custom objects. These requests carrying out development work in the ABAP Workbench. The user can be able to create or modify any object only if the change request opened for the same.
Transport of Copies -
Transport copies uses to copy/move the latest version of the code to the specific system of user choice. It assumes that the specified system is the final destination and no further movements. If the changes required to move to PROD/QAS, then user needs to create another workbench request to proceed.
Creating Transport Request -
Transport Request can be created in two ways:
- Automatic – While creating or modifying objects or customizing settings, the system itself displays the 'Dialog box' for creating a Transport request and once the user proceed with the dialog box the new change request will be created. In this case, the system automatically taken care of the Transport request creation whenever it required.
- Manually – User needs to create the Transport request from the Transport Organizer for the specific requirement.
Now we will discuss about the process of creating workbench request manually.
Step-1: Go to SE01.
Step-2: It navigates to the transport organizer screen. Click on “New” icon to proceed with new request creation.
Step-3: It opens a new dialog box asking for the request type. Select the work bench request and click on right mark to proceed.
Step-4: It opens a new dialog box. Enter the short description, target system and click on save button.
Step-5: Workbench transport request created like below. Click on the transport request number to open “display request” screen.
Step-6: The display request screen has options to process the change request.
Once the changes are completed, release the transport request to process the movement.
Step-7: Place the cursor on Release icon (Truck). Transport Request is automatically added to the appropriate import queues of the systems defined in the TMS.
Check the status on the status bar after release.
Step-8: Releasing and importing a request generates export & import logs.
Who creates/Releases the Transport Request -
The designated person (PM or PL or TL) is responsible for creating the transport request and adding/assigning the project members to the transport request by creating task for each individual added to request.
The designated person (PM or PL or TL) is the owner and will have the full control of all the changes that are recorded in the transport request. The person who created the transport request can release the transport request or the person who got assigned with transport request.
The assigned project members can also release their respective changes if those are completed earlier. But it is always suggestable to release the entire transport request at a time once all the assigned changes are fully completed. Otherwise, it may affect the functionality.
The Import Transport Request -
After the TR released from Source system, changes appear in QAS. The import process should complete manually as the process is not automated.
The files in the transport request are copied to common transport directory at OS level as soon as the transport request released (export). Once the files copied, the entry made in Import Queue/Buffer.
Import Queue is set of transport requests that are having the files available in common directory and ready to be imported into the target system. Import queue is at the SAP Application View. At the OS level, it known as import Buffer.
Step-1: Login to the target system in the client 000.
Step-2: Go to STMS transaction.
Step-3: Click on Import button or Select Overview --> Imports.
Step-4: It shows the list of systems in the current domain, description and a number of requests available in Import Queue and the status.
Step-5: Click on the desired system to get the import queues list.
If the expected queue is not displayed, then refresh the import queue once to get the queue list updated.
If the transport request is not added automatically in the import queue, even though the OS level files existed in the common directory.
We need to add manually to the queue. Click on Extras --> Other Requests --> Add to add manually.
The Import Status -
Each queue in the Import Queue list always shows some standard number icons in the first column represents the type of the queue.
Below are the list of number icons and their meaning.
Each queue in the Import Queue list always shows some standard status icons in the last column represents the status of the queue.
Below are the list of status icons and their meaning.
User can also verify the import history for the already imported transport requests like below.
Click on Goto --> Import History or Ctrl + F7.
Transport logs -
Transport import request performed by the system administrator. After the transport request import performed, administrator must verify the status of import process.
The total process recorded in the forms of logs. There are two types of logs generated as part of import process.
- Action log - displays the actions performed during the process.
- Transport Logs - displays the record of transport logs.
Return Codes -
The status information displayed in the forms of return codes in the generated logs.
0: The transport process was successful.
4: Warning was issued but all objects were transported successfully.
8: A warning was issued and at least one object could not be transported successfully.
12 or higher: A critical error had occurred and the error not caused by the objects in the request.