I am sending Po's from R/3 to SUS via XI. In the SUS monitor the messages are in the status Application Error but when I restart the message the messages are processed successfully.
My proxy is working fine without any problem. But the message is getting strucked in the SUS moni. It is also being processed successfully once i restart the message. I think there is some problem with the queues.
Your issue might be related to transient errors like for e.g. material number being locked while posting the data. Hence, a retry works fine. Either check the program what is causing this transient error if it happens for all the messages else if it happens only for isolated cases, you can run the program RSXMB_RESTART_MESSAGES in background which will automatically retry posting the message.
We are doing initial replication of vendors from mm system to sus system through XI. We have already restarted the messages but we are getting the same problem.
Can you please guide me how to go about this problem.
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no clue of ABAP. Please let me know what to do for this.
As I told you earlier, your implementation logic needs to handle the exception CX_BBPX1_STD_MESSAGE_FAULT which is not done. Hence the error. You can ask an ABAPer's help to fix this.
Can you please let me know what you have done to rectify this problem. Even i am getting the same error message when i replicate the vendors from mm system to SUS ssytems. XML message error message is showing in SUS system as below in SXMB_MONI t-code.
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
Due to wrong configurations of business systems (ECC and SUS) in SLD, the messages will error out. Check your business systems and its logical systems are correctly defined in the SLD. For more error log, check in your trace column in the moni.
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:101 -Vendor with e-mail address not found; process monitor Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:101 -Vendor with e-mail address not found; process monitor Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:101 -Vendor with e-mail address not found; process monitor Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
This is wat actually u have to fix...:-)
Note: In our case....in Fault_text it was throwing error as wrong business systems after correcting it in SLD,messages went fine in SUS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.