WSDL created with Function module does not work in message mapping in CPI. SOAP UI gets it right

[pablomartin]

Hi all,

I have created an enterprise service based on a Function Module,

The interface is pretty simple:

Just importing these two parameters, ZHR_WINTID_FILE is a table type of strings

I_ROUTE TYPE STRING

I_FILE TYPE ZHR_WINTID_FILE

When I pick up the WSDL and use it in SOAP UI I get this request as sample:

Which makes sense and can be used in fact to call the FM,

When I use exactly the same WSDL in CPI, something strange happens:

I get this, like the two parameters get lost and only the item part is there.

I can provide the WSDL if anybody wants to make a test.

For me there is something wrong with the way CPI is interpreting the WSDL but not sure what.

Any help will be much appreciated.

doc-webi-zhr-wintid-file.txt

Regards,

Pablo.

doc-webi-zhr-wintid-file.txt

[pablomartin]

Hi all,

I just tested and if instead of a plain table type of strings I add a table type with a component named line which acts as a string, the WSDL is correct for CPI.

Anyway for me this is a bug in CPI, since SOAP UI is able to "understand" the WSDL correctly.

Regards,

Pablo.

[pablomartin]

Hi Sriprasad,

Finally I decided to go for a single string and later in my FM I will do a split on CR_LF or LF.

I tried to revert the FM to the version that was not working, and now it is behaving properly.

I still have the old WSDL without bindings I am going to attach it so you can check if curious.

Regards,

Pablo.

[Sriprasadsbhat]

Hello Pablo,

Could you please attach WSDL to verify further pls.

Regards,

Sriprasad Shivaram Bhat