2012 Aug 03 10:26 AM
Hello,
I am working with a Client Proxy webservice implementation. I'm getting a confusing error message from SAP when trying to view the payloads.
My the logic looks something like this:
CREATE OBJECT my client proxy
lo_payload_protocol ?= my client proxy->get_protocol( if_wsprotocol=>payload ).
CALL METHOD lo_payload_protocol->ANNOUNCE_PAYLOAD_CONSUMPTION( ).
CALL METHOD my client proxy webservice
CALL METHOD lo_payload_protocol->get_sent_request_payload
CALL METHOD lo_payload_protocol->get_sent_response_payload
Now I can see the request payload fine, it works as expected. However when I try to view the response payload, SAP gives me a strange error:
"Payload consumption has not been announced (see note 1118825)"
This seems strange to me as I am announcing the consumption, and it works for the request payload!
Any advice is much appreciated! I'm currently wondering if the reponse from the external webservice provider is not being handled correctly and SAP is just mis-reporting the error.
Stuart.
2012 Aug 10 4:23 PM
I eventually discovered that you get this misleading error message when SAP receives a SOAP response containing data in a namespace that it was not expecting.
So if you are waiting for <ns1:data>..... and SAP instead gets <ns2:data....> you will get this error.
Mystery over.
2012 Aug 03 10:32 AM
did you just post this or had you you done what the message told you to do?
read OSS note 1118825 from SAP market place
2012 Aug 07 12:52 PM
Of course I have read note 1118825.
That is why I am calling ANNOUNCE_PAYLOAD_CONSUMPTION
Hence my lack of understanding of the error message ""Payload consumption has not been announced" when I can see the request payload correctly...
2012 Aug 09 11:23 AM
the problem could be that your provider expects a value in the SOAP Action
header. You can set this on the Operation Specific tab in Ta.
SOAMANAGER editing the logical port's configuration.
In the ICM trace you should see the following error:
Server did not recognize the value of HTTP Header SOAPAction
Let me know it this helps. All the best
2012 Aug 09 12:44 PM
Hello Keith,
Thanks for the advice. Unfortunately I don't think that is the solution for us - we have no errors in the ICM log.
Currently this error is appearing hand-in-hand with an exception when we call the proxy:
GENERAL_ERROR Error during proxy processing (PART UNKNOWN (NULL)
It is as if sometimes SAP is receiving some combination of data which prevents it from storing the response payload. If I can work it out I'll post results here.
On a positive note, over the past few days we have had some response messages come through and we can see the response payload. When this happens, the exception payload works as well, you get text explaining that there is no exception to see.
Thanks,
Stuart.
2012 Aug 10 4:23 PM
I eventually discovered that you get this misleading error message when SAP receives a SOAP response containing data in a namespace that it was not expecting.
So if you are waiting for <ns1:data>..... and SAP instead gets <ns2:data....> you will get this error.
Mystery over.
2023 Aug 15 3:27 PM
Hello,
I am getting the same issue.
Have you been be able to resolve it ?
Kindly please help.
Regards.
2025 Jun 06 3:37 PM
If the proxy is consumer service, you can try used this configuration the service:
Add these fields proxy and port, this data is provided by the basis team.