Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Error during proxy processing (PART UNKNOWN (NULL))

Former Member

‎2015 Jul 20 3:43 AM

0 Likes
6,524

Hi,

I created a service consumer through the wizard, based on a WSDL. Proxy object is generated, all structures and methods are found. Then, I add a logical port through SOAMANAGER - all fine, it pings and the connection works.

I populate the input structure, call my method and get an error: Error during proxy processing (PART UNKNOWN (NULL)). This is a very useless error message to me.

So, I active all manners of tracing, so I can see what's going on calling and retrieving data. I can see that

  • My proxy is called correctly.
  • The payload sent TO the webservice looks correct
  • The payload received FROM the webservice looks correct. I know it's correct, because it's identical to the XML I recieve when I call the WSDL through other means.

  • The transformation is empty.

Nothing about this service has been customized: it's generated straight up through the wizard. I have already deleted and recreated it but no results.

Anyone got any advice on what to do?

Preview file
30 KB
Preview file
11 KB

Hi Jorg.

This issue seems to be caused the Encoding style in WSDL service definition as discussed in this thread:

http://scn.sap.com/thread/1961146

" Also check type of WSDL style usually this error occurs if you are using RPC/Encoded style WSDL, modify wsdl for Document/Literal style (as RPC style WSDL not supported by ABAP proxy), see this discussion here: Cleint Proxy error

Refer to note:  1358647  "

Please give it a look and let us know if it works for you or you applied a different solution.

Regards,

Dairo

Reply
1 REPLY 1
Read only

dairolozano
Contributor

‎2015 Nov 24 9:05 PM

0 Likes
3,159

Hi Jorg.

This issue seems to be caused the Encoding style in WSDL service definition as discussed in this thread:

http://scn.sap.com/thread/1961146

" Also check type of WSDL style usually this error occurs if you are using RPC/Encoded style WSDL, modify wsdl for Document/Literal style (as RPC style WSDL not supported by ABAP proxy), see this discussion here: Cleint Proxy error

Refer to note:  1358647  "

Please give it a look and let us know if it works for you or you applied a different solution.

Regards,

Dairo