You mainly have 2 types of requests:-
1. Workbench Request.
2. Customizing Request.
Depending on the type of work these requests will be allocated, for example if you create an object in your abap development workbench(Se80), then it gets stored under workbench, if you save any customizing Changes(SPRO), those requests will be stored in customizing requests.
<b>P.S. Mark usefull answers</b>
Change requests are managed by the Transport Organizer. Changes to Repository and Customizing objects are recorded in change requests.
So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Request Types and Task Types
When you transport an object in a request, the objects transport attributes must match the transport attributes of the request (local or transportable).
Different object types have different transport attributes:
Repository objects and cross-client Customizing objects
Each Repository object has an object directory entry. This object directory entry contains the package to which the object is assigned. In turn, the package is assigned to a transport layer.
If a consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a transportable change request.
If no consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a local change request.
If the change request is transportable, the target of the request must be the same as the consolidation target of the object.
If the current system is the original system of the object, the object will be assigned to a task of the type correction.
If the current system is not the original system of the object, the object will be assigned to a task of the type repair.
Client-specific Customizing objects
Client-specific Customizing objects are recorded in tasks that belong to Customizing requests.
If a consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a transportable Customizing request.
The system uses the consolidation route of the standard transport layer to determine the transport target of the Customizing request. However, you can change this target.
If no consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a Customizing request without transport target.
SAP Help Link...
Thanks and Regards,
Bharat Kumar Reddy.V
Changes to Customizing settings are recorded in Customizing requests.
When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.
The client settings determine whether
o changes to the Customizing settings are possible
o the changes are recorded
When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.
Workbench requests record changes made to ABAP Workbench objects.
There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)
The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.
Transport of Copies
Transports of copies allow you to transport (sub-)objects in an object list into any other SAP System you want.
In contrast to Workbench or Customizing requests there is no automatic delivery into other systems for transport of copies.
There are three types of relocations:
o Relocations without package change
o Relocations with package change
o Relocations of complete packages<b></b><b></b>