RFC FM with XSTRING input is not supported from CPI.?

[former_member75463]

Hello,

We have an interface SOAP to RFC scenario and RFC FM has input parameter of type XSTRING (base64binary) to accept attachments.

We have implemented interface in CPI with no mapping as FM's WSDL we used to generate SOAP service.

Now when we call SOAP service from SOAP UI, base64 data is treated as java.lang.string and not base64.

In Monitoring we get error : Error in executing RFC Function, cause :.com.sap.conn.jco.ConversionException: (122) JCO_ERROR_CONVERSION: Cannot convert value "VGVzdA==" from type java.lang.string to type XSTRING at field I_ATTACHMENT.

Thanks

[Ryan-Crosby]

Hi Suraj,

You could always use attachments in a proxy interface by directly attaching the content to the message, and then wrapping the RFC inside the proxy stub. As for the data in your example... you would need to convert it to a hexstring before calling the RFC for the system to be able to process it without error.

Regards,

Ryan Crosby