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
Showing results for 
Search instead for 
Did you mean: 
Read only

WS error - cannot be processed in plugin mode HTTP

Former Member
0 Likes
16,316

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

1 ACCEPTED SOLUTION
Read only

RaymondGiuseppi
Active Contributor
3,819

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

3 REPLIES 3
Read only

Former Member
0 Likes
3,819

no replies yet...

Read only

RaymondGiuseppi
Active Contributor
3,820

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

Read only

0 Likes
3,819

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.