Workbench request released

Hi,
I accidentally released a workbench request for Asset Accounting in R/3. I have tried numorously to delete the request even in R/3. I now have an error when I try to change a query. Is there any way that a request can be deleted/changed after it is released?
Regards,
Adri

Hi Adri,
I'm not sure how can we back the changes from the target system. (it depends on version management and high complex issues)
And I sugget you to release a corrective request for the previous released request.
To capture, follow the process as you did before.
Create a new request in SE09.
To this request, assign the package associated to your query in BEx transport in Transport Connection (RSA1)
Hope this Helps! Assign pts if its useful!
Regards
GSK

Similar Messages

Customizing request & Workbench request

Dear all,
What is the differance between Customizing Request & workbench request?

Hi,
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.
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.
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 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.
Regards,
Satish

New Requests created are in 'Local Workbench Request' in R3 Development

Hello ,
I am going to transport data sources from R3 Dev to R3 Quality.
I have successfully transported the package (which is created in SE80 ) and Application componenet hierarchy and all active version data source RSA6 to R3 Quality .
I have also checked that the package , application transport hierarchy and data sources in R3 Quality.
Now when I tried to create new requests for LBWE data sources ( maintain extract structure , generate data source) , I am getting a message Create Customizing Request , So I created Customizing Request and then I am getting message to create Local Workbench request. If I create local workbench request then it can not be imported to R3 Quality.
Client R3 is open SCC4 settings are 'Automatic Recording of Changes ' and 'Changes to repository and cross client customizing are allowed'.
I am not getting why the system is not asking me to created 'Workbench Request'.
Thanks and Regards ,
Amol Kulkarni

Hello Viren ,
Local Transport Request are not transportable even if we release them.
I have resolved the issue in the below way ,
I went to SE21 and entered the package name as 'YBW' and then clicked on change .
Then Click on properties tab and then select Transport layer as SAP and save.
Go to SE80 and select package and in dictonary Objects drill down view ...right click on any selected view name ...go to other function and click on Write Transport Entry...mention request from Own Request tab which was earlier as Local Workbench Request.
Then go to SE10 and double click on request and go to properties tab ...there select Target Group as
R3 Quality Server name and save it.
Transport the package to R3 Quality.
Henceforth whichever request u create will be of type 'Workbench Request'.
go to SE10 and cross check that your request is now Workbench Request,
Regards ,
Amol K.

Single workbench request for CONSUMER PROXY in crm 7.0.

Hi all ,
I have a problem related to "consumer proxy" in sap crm 7.0 release. In our system , we have several proxies (existing) for consuming inter system web services (WSDL's) which were generated from SE80 , client proxies, wizard.
As we know , at the very first time of creation , the workbench request holds both the structure , class and object of the proxy ,but if afterwards , the proxy is regenarated for changed structure in WSDL , then that workbench request only holds the regeneration request , doesnt hold the base structure.
In our case , in those old proxies , there are so many requests .in some of it , many cross object requests are there , so we are facing problems to transport these proxies to a blank client(newly created).
So my question is
IS THERE ANY WAY TO CREATE ONLY ONE WORKBENCH REQUEST (MIGHT BE FROM SE80) FOR THOSE EXISTING PROXIES , THAT THEY HOLD THE STRUCTURE AND THE CHANGED STRUCTURE ALSO FOR INDIVIDUAL.
THANKS IN ADVANCE.
ARNAB MUKHERJEE
INTEGRATION DEVELOPER.

Hi,
Refer the following to get the understanding the Equipment download to CRM.
You define the default settings for replicating equipment in the IMG activity: Customer Relationship
Management -> Master Data -> Installed Base -> Replication of Equipment from SAP R/3 Customer
Service -> Define Default Settings for the Equipment Replication.
For more information about the integration of different systems, see the SAP Library under mySAP
Customer Relationship Management -> Architecture and Technology -> Business Integration -> CRM
Middleware.
The Business Add-In : Business Add-In: Equipment Upload (CRM_EQUI_LOAD) can be used to
flexibly enhance the data transfer and validation in SAP CRM. The Add-In offers comprehensive options
for influencing the mapping between equipment and individual objects
Also refer to the following notes:
1. Note 627279 - Serial number & configuration download
2. Note 637173 - Equipment download/delta synchronization
Hope it helps.
Regards,
Rajiv

Question to local workbench request

Hi,
I have question to local workbench request. If this kind of request is released, is it stored also in the local transport folder (/usr/sap/trans...) in the file system? Or where I can find it?
Thanks for your answers.

Hello Andreas,
A local workbench TR or for that matter any local Transport Request is one which has no target group/target system assigned to it and hence even after releasing it the changes stored in it don't get moved to other systems.
A local TR when released does not get stored in /usr/sap/trans folder as data and co-files for local TRs don't get created.
A released local TR can be viewed in SE01 transaction in SAP.
Please let us know what is your exact requirement with local workbench TR? May be we will be able to help you out with that.
PS award points if you found this answer useful.
Regards.
Ruchit.

How to transfer local workbench request to production server

Hi,
All my workbench requests are saved under local change request node instead of being in the production system node. How to release and transport these requests to the production server.
Kindly help.
Regards,
Sriram

Hi Sriram,
In SE01 check whether u have given value for target system or not.
Target system is ur production system .Check whether u have specified it in SE01 for ur transport request.
If u have not specified target system for ur Transport request it will be shown in Local Workbench request
Regards,
lakshman.
Edited by: Lakshman N on Aug 4, 2009 9:31 AM

Workbench request goes to aother

When I am creating New request . It is going to new Workbench Earlier It was going Local Change Request but Now It is doing to PRD Production system.
Now I am unable to release Request that are in Local Change Request.
Workbench            Workbench request
    Local Change Requests
        Modifiable
    -> PRD Production System
        Modifiable
Customizing          Customizing request
How I activate Local Change Request

Hi,
Your Workbench request in DEV is getting into PRD as customizing request, this was next to impossible.
Workbench: client independent request(usually these technical changes)
Customizing: these are client dependent(these are usually changes developed by functional ppl)
You cannot release local change request, since these request are local to tht system/client and non-transportable. Probably you can try to re-save them and system will ask new request number while saving and you can save it in transportable change request.
You can still create a new request from se01 and then add the objects of your local change request into the newly created request and save and release the request to transport.
But still certain changes are non-transportable and they will be saved as local change request and even if you transport them nothing is going to affect in target system.
For this reason we openup the client to make manual changes.
Please frame your question properly so that we can clarify your doubt.
Regards,
Raju.
Edited by: Sita Rr Uppalapati on Mar 10, 2009 11:41 AM

How intelligent is the Workbench Request?

Hi,
I created an ABAP program and the Workbench Request was created too. I want to know before Releasing the Request if I go and modify the ABAP program may be after Few Days will that modification get added to the existing Request which was created at the time ABAP program creation?
Thanks,
Kishan

YA.. Until u release the request once created for a report(or any object) all the changes will reside in that request only. If u delete the existing request explicitly then a new request should be created again.
If ur doubt is cleared pl close the thread.
Regards,
Pradhiba

Transporting workbench request

I want to transport one workbench request from 200 client to 210 client in Development server.Do i need to release the task and request? please suggest me.
Points will be rewarded.
Vinay

Hello,
You have to just copy the TA in by T-code SCC1.
scc1->select source client->on the transport request field click F4 -> under request/task click multiple selection-> add ur request to (single vals)list ->F8 (copy)->now under select request/task u can see only one value->F8 (execute)->check including request subtask.->click on start immediately (F5).
regards,
Naimesh

Transportable workbench request

Hi,
What is the 'prompt for transportable workbench request' that I get when I'm activating an info object characteristic? What is the significance? I can still activate the info object by cancelling the prompt. would it create any trouble in the future?

Hi Sameer,
Transports are used to move your development to the higher systems and prompts come up when you are making changes to an already transported object. This is so that you do not need to remember to collect that object in a transport...the system takes care of maintaining the integrity. When the prompt comes up you should assign a request and then make sure that this is released and imported into the higher systems.
Hope this helps...

Workbench request & Customizing Request

Hi ABAP Experts,
What is Work bench request and customizing request ? what is the differences ?
Thanks and Regards,
Vijaya

HI,
Customizing Request:
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 SAP System.
Workbench Request:
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.
Changes to Customizing settings are recorded in Customizing requests.
Workbench requests record changes made to ABAP Workbench objects.
It shows the 2LIS_11_VAITM is already in a particular request......you can do changes and in it if you delete the request or it might be locked in the request with someone's other ids....you can verify with them.....
You can see good details on this thread:
Re: customising and workbench request
Hope this helps...
PLS:AWARD POINTS IF USEFUL
SRI
Hope this helps

Difference between customizing request and workbench request?

Hi ,
What is the difference between customizing request and workbench request?
please reply.........

HI,
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.
pl reward if it helps.
Thanks
Sadhu Kishore

Customizing request and Workbench request

Can some one clarify me the difference elaborately
Thanks
Krishna

Hi Krishna
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).
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).
Hope it helps
regards
Srinivas

Find workbench request for existing report

Hi
Someone created an Report for me in order to develop some new functionalities.i 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.
thanks

Hi Seba ,
You can find the workbench request for the report by displaying the report and following this path in the menubar.
Utilities > version > version management.
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.
Regards,
Anuj

STRANGE!!! Script in a Workbench Request.

Hi All,
Generally i am told:
1. All Client Dependent objects (Table Entries) ask for customizing request.
2. All Client Independent objects (Cross-Client table entries) ask for Workbench Request.
The SAP Script which is a client dependent object, but when i was saving my script it asked for a Workbench Request.
Could any one please let me know why this happens.
Thanks & Regards,
Goutham.

You have mentioned the answer inthe question itself. Customising requests are for Client dependent Table Entries. Since Script is not a table entry but a R/3 object it will be saved in the Workbench Request.
Regards,
Anish Thomas

Workbench request released

Similar Messages

Maybe you are looking for