2016 Jan 11 3:15 PM
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
2016 Jan 12 7:14 AM
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
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.
2016 Jan 12 7:01 AM
2016 Jan 12 7:14 AM
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
2016 Jan 12 12:25 PM
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.
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |