SAP CRM / CS Supports

Symptom
Below are few of the problems faced when using webservice tool:
1. Generation of a web Service after transport fails with the error message in the trace file under transaction smwt with the below error message’System setting does not allow changes to be made to object’.
2. Generation of a web Service after transport fails with the error message in the trace file under transaction smwt with the below error message’Activation cannot be performed in this client:’.
3. In transaction WSCONFIG, when you try to release the webservice, you are not allowed to release the webservice.
Other terms
WS_DESIGN_TOOL CRMOST_TRANS
Reason and Prerequisites
1. To check for the failure in the generation of the webservice, we first need to check the status of the generation:
–> To check whether the generation during afterimport was successful, check the Outbound Queue in ‘Display Outbound RFC Queues’( transaction SMQ1). The queue name is webservice name and it will be created in client 000. In case if the status of the queue indicates ‘SYSFAIL’, it indicates that the webservice generation failed with above mentioned errors.
Now, to check the reason for the failure of the webservice generation.
In CRM 600 and CRM 700:
Set the trace levels to ‘Detail level 2′ for ‘GENERATION’ Environment in transaction ‘SMWTAD’ or via button ‘Maintain trace levels’ in transaction SMWT.
In CRM 701:
Use transaction CRMOST_LOG to display the generation logs.
Solution
1. In transaction se03, navigate to ‘Set System Change Option’.
a. Here, under ‘Namespace/Name Range’, make sure to set the namespace with prefix ‘/CRMOST/’ to ‘Modifable’. Also, make sure to set the namespaces for ‘Customer Name Range’ and ‘General SAP Name Range’ to modifiable.
b. Under Software Components, make sure to set the component ‘Local Developments (No Automatic Transport)’ (Technical Name – LOCAL) to modifiable.
Note: Once the above changes are done, select the outbound queue for the webservice and proceed with ‘Execute the LUW’. In case of any errors, the outbound queue will show the status SYSFAIL with appropiate error message. In case if there is no error, there will not be any queue for the webservice.
If the outbound queue got lost (because it was deleted in the meantime), you can redo the afterimport generation using the function module ‘CRMOST_AFTERIMPORT_REDO_GEN’.
Note: However, the transport procedure will not release the webservice for usage in a specific client. To create the runtime for the webservice, release the webservice using the transaction WSCONFIG.

2. In transaction scc4(Client Maintenance), Under ‘Cross-client Object changes’ section, select either ‘No Changes to Cross-client customizing Objects’ or ‘Changes Allowed to Repository or Cross-Client Customizing.’
Note: Once the above changes are done, Select the outbound queue for the webservice and proceed with ‘Execute the LUW’.
3. In transaction SCC4, Under ‘Changes and Transports for Client-Specific Objects’ section, select either ‘Changes Without Automatic Recording’ or ‘Automatic Recording of Changes’.
Note: Now, you can use WSCONFIG transaction again to release the webservice.