System exception after a succesful synchronous ABAP Proxy call

[Former Member]

Guys,

I have the following scenario:

1) From an R/3 box I initiate a synchronous ABAP proxy call

2) On XI everything works fine, the http request is sent out (using the http adapter), the response comes back succesfully and it is transfered back to the R/3 box - no error whatsoever

3) On the R/3 box however the EXECUTE_SYNCHRONOUS method throws a system exception BUT the returning (input) parameter holds the response message!

So in the end if I catch this exception (CX_AI_SYSTEM_FAULT) then I could be happy and just ignore the exception, but I don't feel comfortable leaving it this way. Why is the exception and how can I eliminate it?

Any help would be greatly appreciated.

Thanks a lot,

Viktor

[Former Member · Accepted solution]

Why don't you just debug the proxy call? You should be able to see where the error occurs in your system and maybe get some hint or some more detailed message about what was going wrong.

Regards,

Jörg

[Former Member · Accepted solution]

Joel/Jörg,

Thank you for your response, indeed I ended up debugging it and found my error deep down:

Error code: ABAP_PROXY.PARSE_APPLICATION_DATA

Error text: Error handling Response Message; XSLT error: CX_XSLT_DESERIALIZATION_ERROR: XSLT program and source line: /1SAI/XS00000000000000000088: 0000000122; Tree Position: abap.values.1.1.1.6.1.5 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: WINDSOR CT 06095-1712

The data field defined in SAP was too short for the field.

Thanks a lot,

Viktor

[JoelTrinidade]

Hi Viktor,

It does not sound like a problem with your PI system , get someone to debug the RFC and he would be better able to tell you what is wrong.

Regards

joel