topic Re: WS error - cannot be processed in plugin mode HTTP in Application Development and Automation Discussions

WS error - cannot be processed in plugin mode HTTP

Former Member — Mon, 11 Jan 2016 15:15:30 GMT

Hi all,

I am using a custom RFC, which uses standard RFC 'WS_DELIVERY_UPDATE' to update the delivery. When I run the RFC from SE37, it is executing without any error.

But when it is called through a web service with the same test data, Web service is returning the error "Message E VL 217 cannot be processed in plugin mode HTTP".

Please help me to resolve this.

Thanks and Regards,

Johan

Re: WS error - cannot be processed in plugin mode HTTP

Former Member — Tue, 12 Jan 2016 07:01:09 GMT

no replies yet...

Re: WS error - cannot be processed in plugin mode HTTP

RaymondGiuseppi — Tue, 12 Jan 2016 07:14:28 GMT

When you execute from test mode of SE37 conversion-exit are executed (error message suggest material id) not during actual RFC call. you may be required to execute some INPUT conversion-exit to format data before calling some BAPI... (e.g. CONVERSION_EXIT_MATN1_INPUT or CONVERSION_EXIT_ALPHA_INPUT, check domain MATNR)

Regards,

Raymond

Re: WS error - cannot be processed in plugin mode HTTP

Former Member — Tue, 12 Jan 2016 12:25:11 GMT

Yes that was the issue. Since the error message mentioned 'cannot be processed in plugin mode HTTP', I thought it might be due to some restriction of the RFC to work in HTTP mode.

Added the conversion exit for MATNR and it worked.

Thanks Raymond for the solution.