In SAP, there are four primary types of transport requests used for managing changes and moving objects between different systems within a landscape.
Understanding SAP Transport Request Types
SAP Transport Requests are essential for maintaining system integrity and ensuring that development, configuration, and data changes are systematically moved from one environment (e.g., development) to another (e.g., quality assurance, production). These requests categorize the changes being transported, each serving a distinct purpose.
Here's a breakdown of the four types:
Transport Request Type | Description | Typical Use Case |
---|---|---|
Customizing Request | Records changes made to Customizing settings (client-specific configurations). | Moving configurations like new company codes, GL accounts, pricing procedures, or user authorizations. |
Workbench Request | Records changes made to ABAP Workbench objects (development objects). | Transporting custom programs, function modules, reports, dictionary objects (tables, domains, data elements), etc. |
Transport of Copies | Allows you to transport (sub-)objects. | Re-transporting existing objects, or for testing specific object changes without impacting original requests. |
Relocation | Used for moving objects between different original systems or packages. | Changing the original system of an object or transferring objects from a temporary package to a permanent one. |
1. Customizing Requests
Customizing requests are specifically designed to capture changes made to the configuration settings within an SAP system. These changes are typically client-specific, meaning they apply only to a particular client within the system.
- Purpose: To manage and transport modifications related to system configuration and master data settings.
- Examples:
- Defining new organizational structures (e.g., company codes, plants, sales organizations).
- Setting up new number ranges for documents.
- Configuring new workflow rules or approval processes.
- Changes to user roles and authorizations.
2. Workbench Requests
Workbench requests are used to record and transport changes made to development objects within the ABAP Workbench. These objects are typically client-independent, meaning they apply across all clients in a system.
- Purpose: To manage and transport custom developments and modifications to standard SAP objects.
- Examples:
- Creating new ABAP programs, reports, or function modules.
- Modifying existing SAP standard code (using enhancements or modifications).
- Developing new tables, data elements, or structures in the ABAP Dictionary.
- Building new SAP Fiori applications or OData services.
3. Transport of Copies
Transport of Copies (ToC) are special types of requests that allow for the transportation of selected (sub-)objects without impacting their original development request. They are often used for testing purposes or for transporting objects that are part of other, larger transport requests.
- Purpose: To transport specific versions of objects for testing, or to send a subset of changes to another system without releasing the main development request.
- Key Characteristics:
- The objects transported via a ToC do not lose their original source system or package assignment.
- They do not automatically delete from the target system after import.
- Often used to consolidate objects from multiple development tasks into a single transport for integration testing.
4. Relocations
Relocation transport requests are utilized for very specific scenarios involving the movement or re-assignment of objects within the SAP landscape, particularly when changing their original location or ownership.
- Purpose: To handle the physical movement of objects, such as changing their original system or relocating them from one development package to another.
- Scenarios:
- When a development object was mistakenly created in the wrong system and needs to be assigned to its correct original system.
- Moving objects from a temporary local package (
$TMP
) to a standard transportable package.