Call Inbound Proxy Error

[Former Member]

There are unprocessed XML messages in the ERP which found to have error (Call Inbound Proxy Error). Here's the XML message from the XML Message Monitoring (SXMB_MONI):

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"

xmlns:SAP="http://schemas.xmlsoap.org/soap/envelope"

SOAP:mustUnderstand="">

<SAP:Category>XIProxy</SAP:Category>

<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>

<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>

<SAP:P2>ZCL_GOODS_ISSUE_NON_SERIALIZED</SAP:P2>

<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>

<SAP:P4/>

<SAP:AdditionalText/>

<SAP:ApplicationFaultMessage namespace=""/>

<SAP:Stack>Error during proxy processing An exception with the type

CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared

in a RAISING clause The database returned a value containing an

error</SAP:Stack>

</SAP:Retry>M</SAP:Retry>

</SAP:Error>

Additional details:

No queue stuck found (SMQ1 and SMQ2) both in ERP and XI systems.

In XI system, no XML messages error/s found thus the error lies only in ERP.

Upon restarting the XML message containing an error in ERP, the payload has been suceesfully processed.

What's the cause of such error? How to eliminate such instance of having that error?

Edited by: SAP y'all on Aug 14, 2008 5:13 AM

[Former Member]

Sorry to bother you, we are having the same issue and was wondering if you ever figured out your issue. If you did, could you please share with me.

Thanks

david

[Former Member]

HI,

This is the error on ERP side....this normally occurs due to the Work process load on SAP database.

Plesae can you also check with the table space of the tables used in inbound proxy code.

It also based on volume of testing you are doing..

One option would be to try catching the exception in the Proxy itself.

http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm

Thanks

swarup

Edited by: Swarup Sawant on Aug 14, 2008 5:18 AM

[Former Member]

Actually, such errors only found after few months of its GoLive. Yea the XML messages unprocessed due to error is in ERP prod. Seems like there's inconsistencies now.

Why is it pointing to the ZCL_GOODS_ISSUE_NON_SERIALIZED which is a proxy generated class? If it normally occurs due to the work process load on SAP database, what should be done? How to eliminate such instance of having that error?

P.S., Swarup, there's a catch of the exception every after a proxy call

Edited by: SAP y'all on Aug 14, 2008 5:44 AM