on 08-26-2013 2:24 PM
Hello experts,
I have a problem with IDocs send from PI to AII and OER. The IDocs are not processed. After restarting them a queue appears. After activating it it is still not working. I have copied the Trace from XML_MONI and hope somebody can give me a hint how to solve this problem. Thank you!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Inbound Proxy
-->
</Trace>
************************************
--> </Trace>
</Trace>
************************************
--> ************************************
--> ************************************
--> </Trace>
************************************
--> ************************************
--> ************************************
--> ************************************
--> ************************************
--> ************************************
--> </Trace>
************************************
--> </SAP:Trace>
Hi,
this is probably situated in the receiver system (as the error states "System Error at Receiver... => ROLLBACK WORK").
Please look at AII or OER system (probably OER system). There's also SXMB_MONI. Please look at error data there. If you can't get it to work, come back with detail error information.
HTH
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jens,
the error data for OER shows following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Inbound Proxy
-->
</SAP:Error>
the error data for AII seems to be the similar error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Inbound Proxy
--> </SAP:Error>
Thank you for your help!
Regards,
Fatih
You might want to check this post (and mabey subsequent posts referred there)
http://scn.sap.com/thread/3167996
Bottom line is: Check "Trace" section in SXMB_MONI in receiver system. There you should be able to get more details about the error causing the exception to be risen.
You might try a search with those error details from "Trace" section. If you are not able to resolve, come back.
Could also be possible that you need do debug the proxy class, but since this is standard code, I don't think that this is actually a bug in the code but some missing / wrong customizing. Debugging however, could lead you to the place where the exception is risen so you might be able to determine the cause. I would resort to debugging however only if error details in "Trace" are not sufficient to resolve the problem.
HTH
Cheers
Jens
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.