Deserialization failed

[Former Member]

Hi all,

I am currently opening an interface to other application, which should be able to create purchase order. I use BAPI_PO_CREATE1 and BAPI_TRANSACTION_COMMIT and open it via virtual interface to web service. In the virtual interface creation, i found that there's a bug, that if you select a BAPI to be opened by virtual interface, the virtual interface would opens a BAPI directly below the selected BAPI on the list.

I was able to get around that by selecting BAPI_PO_CREATE and BAPI_TRANSACTION_ROLLBACK in VI creation, which in turn it were BAPI_PO_CREATE1 and BAPI_TRANSACTION_COMMIT that are opened by the created VI.

After i test the services, i found deserialization error. I never encounter this error with previous WS function call. Is it has relation with the bug?

Below is WSDL, SOAP Message, and SOAP Response from the function call:

[Former Member]

Anyone has any experience with this problem? i have go through the forum and find that the deserialisation failed question by other user does not have any answer yet.

[Former Member]

Hi Silvia,

It could be that you are not passing the manadatory fields or the input values you are passing are not in the right format. (check the desired formats in the WSDL for fields like date, timestamp etc...)

Just check.

my 2 cents,

Antony

[Former Member]

Hi,

I have the same problem and getting around the related posts on "Deserialization Failed" . I have created WS from BAPI and test with WSnavigator.

this got solved with the correct input data format.. for example, date format is YYYY-MM-DD but I tried with other format and the response this error.

regards,

[Former Member]

Well, I can not post the WSDL, SOAP Request and SOAP response because 15000 character ceiling. I also have checked SAP Notes 830340 and found that my case are not caused by problems in that notes.

Your help would be greatly appreciated.