cancel
Showing results for 
Search instead for 
Did you mean: 

Error

Former Member
0 Kudos

Hi Friends,

Can anyone help me what is the best way to find the reason of error while working in xi support project?

Thanks & Regards,

Suresh.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

1) Tran SXMB_MONI

2) Runtime Workbench go fot Message Monitoring and End to End Monitoring.

Thanks,

Punit

Answers (5)

Answers (5)

Former Member
0 Kudos

hi suresh kumar,

Try to close the thread if you get suitable answers....hope you got it..

you got ample of answers

DO ENCOURAGE SDNers

Regards

chandrakanth

Former Member
0 Kudos

Reason for error would depend on your scenario.

Most of the errors can be found in

SXMB_MONI,

RWB->Messgae Monitoring->Adapter Engine,

SXMB_MONI_BPE

Additionally you can use the following for Monitoring.

SMQ1, SMQ2 - Queue Monitoring

SM58, IDX5 - For IDocs

SXMB_MONI in the source/target SAP systems - for proxy scenarios.

SXMS_SAMON - For Sync-Async Bridge.

Former Member
0 Kudos

Hi,

1) Tran.Code: SXMB_MONI

2) Runtime Workbench go fot Message Monitoring and End to End Monitoring.

regards,

suresh

Former Member
0 Kudos

Hi Suresh,

If you click on the message in the tcode sxmb_moni and click on display,you can find all the details about the message and the error.

If it is a File to Idoc scenario,you can check if the message is successful on the outbound side as well in sxmb_moni by checking whether it has a checkered flag on the outbound status.

Thanks and Regards,

Induja

Former Member
0 Kudos

hi

use t.code SXMB_MONI...each and every details regarding errors are available there

regards

chandra

Former Member
0 Kudos

Hi,

this not truth.. SXMB_MONI (btw, it is SXI_MONITOR actually) monitors only errors in IE.

Use RWB (Runtime Workbench for complex monitoring) - you will see error from Adapter Engine & Integration Engine as well there. MOnitoring only "SXMB_MONI" will tell you nothing in case of error in communication channel for example..

Peter