cancel
Showing results for 
Search instead for 
Did you mean: 

ERP->HCI Quality of Service settings

andreea_mutascu
Explorer
0 Kudos

Dear experts,

We have configured an Integration scenario ERP->HCI->S/4HANA cloud edition, where data is exported from ERP through an asynchronous Consumer Proxy pointing to the HCI endpoint.

The ERP logical port configuration - Messaging settings:

The HCI adapter settings:

But when we call the data transfer, the following error message appears in HCI: Inbound processing in endpoint at XXX failed with message "Fault: Inconsistent QualityOfService set in URL parameters".

I couldn't find any settings for the QaS in ERP side, as it should be ExactlyOnce by default in plain SOAP with Message ID, but I'm not sure what QaS in HCI expecting in this case.

Many thanks in advance for your input!

Best regards,

Andreea Mutascu

former_member637863
Participant
0 Kudos

Hi

what setting you did in soamanager for soap 1.x for asynchronous scenario?

I am getting same error

Thanks

Harsha

Accepted Solutions (1)

Accepted Solutions (1)

engswee
Active Contributor
0 Kudos

Hi Andreea

I have not tried the SAP RM message protocol on the SOAP adapter in HCI. I've checked the HCI's online documentation and there isn't anything there on QOS URL parameters. However, there is a Wiki listed there, which talks about it in the "Interoperability with 3rd parth products" - you can maybe try adding &QualityOfService=ExactlyOnce to the URL configuration in the logical port.

Another option would be to try using normal SOAP 1.x protocol instead on both sides. I know definitely that SOAP 1.x works fine in HCI's adapter.

Regards

Eng Swee

andreea_mutascu
Explorer
0 Kudos

Hi Eng Swee,

Thanks a lot for all your valuable answers!

I couldn't make the interface work on the SAP RM protocol, but indeed changing the protocol to SOAP 1.x worked.

Best regards,

Andreea

engswee
Active Contributor
0 Kudos

Glad to hear that it worked with SOAP 1.x. Please close this thread if you have no further queries regarding this issue.

Answers (0)