Hi Holger,
I don't there's anything wrong with your web service because you're using a standard SAP BAPI.
The problem is more than likely data related & is the exception handling of the BAPI needs a lot of work, a lot of the times it doesn't cater for web service communication. I'll explain. I've had similar painful experiences. Sometimes if you send through a web servie request & something is slightly wrong with the input data, the provider/ backend is configured to pop-up a window. Web service communication naturally can't handle this.
The only way around this is to do some debugging in the standard BAPI when the web service request comes in until the error is triggered & try & work out what it's expecting you to do different.
The other option would be, by process of elimination, to completely remove all optional tags tags from the SoapUI request so that there isn't any funnies there. Also, maybe clean up all unused data elements attributes. Sometimes when you populate an optional data element, some of the attributes of that element are mandatory & you might not be populating those, that could trigger this error. Just send through the absolute minimum data in the request, no additional elements / tags / attributes.
Lastly, it may help but there's no guarantee, setup an ICF trace in TCode SICF for the user that you're using in SoapUI & see if that yields any helpful results.
Best Regards, Trevor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.