cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error While Publishing V4 version service with RAP

19,763

Hi,

When I try to Publish the V4 service, I am getting the below error, Please suggest

Accepted Solutions (0)

Answers (3)

Answers (3)

Andre_Fischer
Product and Topic Expert
Product and Topic Expert

You have to use the transaction /iwfnd/v4_admin to pubish the service, rather than using the ADT tools for that.

3101976 - Publishing OData V4 service is throwing error: Publishing of XXXXXXXXXX in Customizing cli...

  1. Create a RAP BO including a V4 service binding using ADT
  2. Activate the Service Binding (this will create a service group) (but do not use the button "publish locally)
  3. Use transaction /n/iwfnd/v4_admin to publish the service group

In step 3 you have to provide a customizing request when “Changes and Transports for Client specific options” are using the option “Automatic recording of changes”.

shavneet12
Participant

Hello Andre ,

Why is it so ?, is it because of some constraints , or this is a bug as of now ?

Thanks and Regards ,

Shavneet Singh

former_member721373
Participant
0 Likes

Hi Andre Fischer,

Even in tcode /n/iwfnd/v4_admin, I am having the same error as 'No change allowed on this client' while publishing the V4 Odata, Kindly could you please help here?

NicholasB
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Mohd,

In case you are still facing this issue, the client you are trying to publish in seems protected against such changes. Are you sure you are trying this in a system client set up for development and/or customizing?

ajaygupta
Participant

Same as Andre's answer but with images
Step 1) Create a service Binding using V4

Step 2) After activating the service binding, log on to SAP and run TCODE /n/iwfnd/v4_admin to publish the service groupp.

qiujiaoyao
Explorer
0 Likes
I am in an SAP public cloud environment , hot to use transaction /IWFND/MAINT_SERVICE and activate
Andre_Fischer
Product and Topic Expert
Product and Topic Expert

it is because of some constraints on the ADT tooling side.

Former Member

My understanding: If it is on the ADT tooling side it has nothing to do with the backend system ?
Then will these constraints be lifted any time soon ?