Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Regarding requests

Former Member
0 Likes
695

What is customizing request and workbench request? when creating new object it will go for workbench request and not for customizing request what is the reason?

5 REPLIES 5
Read only

Former Member
0 Likes
663

Customizing request

Customizing requests contain changes to client-dependent tables.

Workbench request

Workbench requests contain changes to client-independent tables.

Regards.

Read only

uwe_schieferstein
Active Contributor
0 Likes
663

Hello Naveen

See my answer in your duplicate thread [ Regarding requests|;

Regards,

Uwe

Read only

Former Member
0 Likes
663

Hi Naveen,

Workbench Requests

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

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.

Reward if useful.

Thankyou,

Regards.

Read only

Former Member
0 Likes
663

hi,

SE09 is for workbench request

SE10 is for Customizing request

SE09 is the transaction code for workbench organiser.Workbench organiser is the set of utilities for development change management.All Development changes are tracked via Workbench organiser.

SE10 is for Customosing organiser.Customising organiser is the set of tools for customising change management.All customizing changes are tracked via customising organiser.

plz reward points if helpful..

Read only

Former Member
0 Likes
663

Hi Naveen,

You basically have two types of requests:

Workbench

Customizing

Workbench Requests

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.

Changes to cross-client Customizing objects and to Repository objects are recorded in Workbench requests

In workbench request .... it can be programs(repository objects) and cross client data (ie not specific to one client).

Customizing requests

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 client-specific Customizing objects are recorded in Customizing requests.

Customer customized data designed for a specific client is transported to another client using customizing request. Most of the cases these requests are something like changing values in tables (that too client specific).

Differences---

In workflow you will use a workbench request for client independant objects such as BOs, Workflow Templates, Tasks etc. You will most often use a customising request for config such as event linkages etc.

Example for Workbench changes are - Changes in Reports etc..

Example for customizing changes are - Changes in SAP Script or Standard Text creation etc..

Customizing requests contain changes to client-dependent tables.

Workbench requests contain changes to client-independent tables.

When you transport an object in a request, the object’s transport attributes must match the transport attributes of the request (local or transportable).

Almost all repository objects (reports, classes, DDIC objects, etc.) are client-independent. They are transported using a workbench request.

A few repository objects (like forms, R3TR FORM) are client-dependent but transported in workbench requests, too.

reward if useful

thanks and regards

suma sailaja pvn

Edited by: suma sailaja pvn on Jan 11, 2008 6:06 AM