Different discussions on this topic. Lets have a look on all the discussions.

(For Beginners)

Workbench request Workbench request

and Customizing request.

Workbench requests contain changes to client-independent tables. Workbench Request: These are related to the Development tasks. Workbench Request - for all ABAP Dev. Objects. 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 . 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. Workbench request is client independent, automatically reflects into the dev client also. ABAP developer creates the workbench requests for all his development work Workbench request is created for any objects that you develop like cubes, reports DTP transfer rules .update rules..etc. Any settings that are done in SPRO transaction are related to customization and if you need to transport those settings across landscape create a customizing request.

Customizing request.
Customizing Request is Client Dependent and contains configuration settings while work bench is client independent. Customizing requests contain changes to client-dependent tables. Customizing Request is raised by the functional people while doing the configurations/setting in SPRO Configuration Request: These related to the system configuration done by functional team. Customizing Request - For all Customization data. 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. 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 changes to the Customizing settings are possible the changes are recorded when you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System. Customizing Request: It is client dependent, If u develop something in golden client that is not automatically reflect into the dev client. U has to import using SCC1.

Change request.
Change request - Changes done on to already developed objects. Change requests:- Changes to Repository and Customizing objects are recorded in change requests. Purely tech definition: An information source in the Transport Organizer that records and manages all modifications made to Repository objects and Customizing settings during a development project.

When ever you do changes to Repository Objects the WORK BENCH requests are created. When ever you do changes to Customizing Objects (SPRO) the CUSTOMIZING requests are created. This means both these type of requests are subset of CHANGE REQESTS (we can think this as CTS-change and transport syste).

BADI If you want to get notified when a workbench request is created or changed use this BADI.
BADI Interface : : CTS_REQUEST_CHECK. CHECK_BEFORE_CREATION for notifying

Issues
I have created a local change request in my workbench. But I am not able to release it. It is giving error as objects not activated, but the objects are already activated? Sol : In SE09, select your request/task and there is a menu option to check inactive objects. Pls make sure that everything is active here. I want to transport one workbench request from 800 client to 900 client in Development server. Do i need to release the task and request? Sol : 1. Don't think that you have to do that. Go to the target client and run transaction SCC1. 2. Since its a work bench request, (which may contain program, table, data element etc), there is no need to transport it to another client. (in the same box) (since, it will usually contain client independent objects/entries/records) 3. Use 'SCC1' to copy request to another client without releasing. we currently did a client copy. Before this copy, there used to be an automatic workbench request in Develpment that came up and required me to enter a new or existing request.Now, after the client copy, nothing comes up when I change something? Sol: 1. Did the transport got released? Just click on button 'Other USers' & give * in the popup and ENTER. Check for the required trnsport request. 2. Check for client settings in SCC4. I have created a z table (in $TMP)with following details: 1. Delivery class:: L 2. Maintenance allowed 3. Table maintenance generated with FM (in $TMP). Now, it should be a local object and never be transported. But when I creating enteries in that and trying to save it, its asking for a workbench request. If it would have asked a customizing request i would have understood, but my question is why workbench request for entries. Sol : 1. table is one object and entries is one another object. thats why its asking request. Someone created an Report for me in order to develop some new functionalities have to transport it now in the test system but i do not know how i can find the workbench request for it or how i can save it in another workbench request. Sol: 1. See the version management: here u can see all requests of the report, the last one will be the request u're looking for, from SE38 . Utilities->Versions->Version Management. 2. go to utilities->versions->version management. and click on it there u ll find the active request if it is in a local package ,then go to GOTO->Object Directory entry->change the package then u ll be able to generate the request. 3 If you want to add this request into another request goto SE01 and there you will find the icon for adding the objects for your request. 4. go to T-code SE03 and go to find request there give your program name. That will show you request related to program.