cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC Monitoring Procedures for error

Former Member
0 Kudos

Hi ,

Can anyone provide me the link or document for IDOC Monitoring for error?

Accepted Solutions (1)

Accepted Solutions (1)

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

Check this on How to do Monitoring on IDX5(IDOC-Xml )

Check this on how to Monitor Sending Idoc Fails through XI

http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm

Troubleshooting File-to-IDOC Scenario in XI

Answers (4)

Answers (4)

Former Member
0 Kudos

Hey,

R3 side.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

SAP r3

sm59(status check)(no message)

WE02(status check)

WE05(status check)

BD87(status check)

WE42 process code

WE47 status info.

XI Side.

IDx5(Idoc check)

SU53(authorization check)

IDX2

Transaction: IDX2

There are a couple of situation where IDX2 can be useful on the XI system.

1. When we want to test connection between the XI and SAP backend system.

you can also refer to these links will surely help.

http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm

Note:-940313

.

regards,

Milan

Former Member
0 Kudos

Hi

First you need to check the RFC destination is configured properly or not.

You can use the Tr.Codes WE02 or WE05 in R/3 System whether IDocs are reached or not.

You can check the Idocs in XI by using the IDX5 tr.code.

You can use the SM58 tr code in XI system , is there any error while sending the IDoc to the R/3 System.

Regards

Goli Sridhar

SudhirT
Active Contributor
0 Kudos

Hi,

Best way is to use IDX5 and SXMB_MONI if some problem occurs at R3 end go for we02/we05 and also sometimes you can check in SM58, smq1,smq2 if in moni you get green signal.

Thanks!

prateek
Active Contributor
0 Kudos

At R3, use we02/we05 transactions

At XI, use idx5 or sxmb_moni transactions.

Regards,

Prateek