Inbound ABAP proxy failing with type CX_SY_ZERODIVIDE occurred

[Former Member]

Hi Experts,

I am looking for your help, we have an interface from File-Proxy, the ABAP inbound proxy fails as given below in ECC (with Manual Restart Possible) with error message below, however, there is no error in PI. This error happens only when we have nultiple invoices in XML Payload, but when we have a single invoice in the XML Payload it goes through and posts in ECC successfully. Also I debugged the ABAP Proxy and there is no issues with data and the strange thing is it will post when we manually restart the failed message. Also it throws CX_SY_ZERODIVIDE exception where in the Proxy there is no calculation and also in the XML Payload we do not get any data with operator '/'. 

[Former Member]

Hi Misha,

I'm getting the same error. Please guide me how did you solve this issue.

Thanks

Sathish

[vadimklimov]

Please check tx. ST22 in the receiver system (proxy provider) and check respective ABAP runtime errors corresponding to the indicated issue. From there, you can retrieve more details on the context of the exception (e.g. user and transaction context, source code extract where the exception occurred). If possible, please provide this kind of information so that further analysis can be conducted more precisely.

Regards,

Vadim

[Former Member]

Thanks Vadim for your reply. I had already checked ST22 and there is no dump as well in ECC system. The strange thing is it works for single record in XML Payload but not for multiple records in XML Payload, it fails in ECC side. But when I do manual restart it posts directly. So if there is short dump then it should not post on manual restart in SXMB_MONI.

[former_member181962]

Does it create any short dumps (in ST22?)

[Former Member]

Hi Ravi,

No it does not create any short dump in ST22 and I also debugged proxy using SPROXY for any data issues and it does not have any data issues as it posts them successfully. However, when the intefrace is executed for multiple records (more than 1) then it fails in ECC side with (Manual restart possible). It goes through fine in PI and inbound ABAP proxy fails in ECC side.

The SXMB_MONI Trace and error messages are already provided in my original post.

[Former Member]

Please check the maximum data type length assigned to each XMl field of ABAP proxy and the corresponding value received in XML.

I had the same situation and Amount can be only upto 10 digit and 3 decimal. But value received was more 11 digit. and XML processing failed.

[Former Member]

Hi Rajesh,

I did check the all field XML and data in XML Payload are within the length values. My question is if length is the issue then will it post on manual restart, it still give the same error in SXMB_MONI right?

[MichalKrawczyk]

Hi,

have a look at my blog on how to catch and reprocess proxies

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/20/michals-pi-tips-how-to-recordtest...

the thing might be related to the fact that you're using different user in proxy call and in restart procedure - can you compare both users - su01 - defaults section - maybe there is something different there

Regards,

Michal Krawczyk

[Former Member]

Thanks Michal for your prompt reply. I don't seem to understand if it has to do with user authorization, because it works fine when the XML Payload has only 1 invoice. If it had to do with authorization then it should not have worked for single invoice. The issue is this happens when it is multiple invoices in Payload. They are also correctly provided and no data issues, because when I process with manual restart it works fine.

We also performed system trace and it does not point to the exact issue, it starts showing the class messagings that starts to generate.

However, I will try to check the proxy interface by activating the recording for interface user id as you have suggested and keep you posted.