cancel
Showing results for 
Search instead for 
Did you mean: 

Web service ping failed (RC=405)" error in S4H

0 Kudos

Hi Experts,

We are integrating S4H system with SAP CC (Convergent Charging). In the process we have created the Logical Ports for the SAP CC server in SOAMANGER in S4H. But after configuring we are receiving the following error when we ping the Port "Web service ping failed (RC=405). Service Ping ERROR: Method Not Allowed"

When tried testing the WSDL for which we created the Logical Port in SOAP UI, we are receiving the error as "The security token could not be authenticated or authorized</faultstring"

We are trying to integrate both Updater and Dispatcher Servers of SAP CC in the form of

http[s]://<UPDATER_HOST>:<UPDATER_WS_PORT>/rating?wsdl

We have validated that the credentials we are using is correct.

Request for some thoughts on this.

//Thanks

Tapas Tarun

Accepted Solutions (1)

Accepted Solutions (1)

In SoapUI you need to fill soapenv:Header. There you can put user and Password:

User and password can be created in CoreTool. It should be webservice account. Not end-user. Otherwise password will expire.

In BRIM integrated scenario the same user id/password needs to be used in SOAMANAGER in CRM and ERP for logical ports to CC webservices. There are 2 SAP documents describing it.


By the way: Ping might be blocked in some companies.

0 Kudos

Thanks Rafal !!

Your suggestions did work for us, was assigned to a different project for few months, back to the CoreTool now. We are able to get a response back from the CC server when passing the request from SOAP UI. We have used the same credentials in SOAMANGER Logical Port creation but are receiving the security error in message verification as seen in below screenshot.

Does CoreTool have some certificates, which needs to be imported in STRUST of S4 ? Request for your views.

// Thanks

Tarun

Answers (1)

Answers (1)

former_member428395
Active Participant

Dear Tapas Tarun

First, please check the SAP note 2428165 - web service requests rejected

Then, can you check that the authentication data that you are using are valid ? If the user that you have set in your request is valid, kindly check if this user is associated to at least one catalog in SAP CC. To check this you can open the core tool and open this specific user.

If it is not working after these 2 steps, create an incident on the SAP Support Portal

Best regards,

Eric Fremont