cancel
Showing results for 
Search instead for 
Did you mean: 

Error reason in moni as ABAP report.

Former Member
0 Kudos

Hi,

Can We get error/exception message which we see in trace of moni as a Abap report.

Like when a message is failed,in the report it should state the message guid and reason for the error Like com.sap*********** Cannot produce target element CID********...

I cant go ahead with the alerts coz the user wants an ABAP report only for the error files.

I Searched through SDN and found some blogs where in i can get reports for no.of processed files per day or no.of error files per day etc.. But i havent find suitable blog/thread for the above requirement.

Any Help would be appreciated.

Thanks,

Kiran

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Kiran,

XI message is actually stored in different tables,

SXMSPMAST, SXMSPMAST2 XML Message master Table, contains runtime information on XML messages processed by XI; in this table you can find all the information that is visible in SXMB_MONI.

Please also check these links.

/people/gourav.khare2/blog/2007/12/12/interesting-abap-tables-in-xi-150-part-i

http://wiki.sdn.sap.com/wiki/display/XI/Useful%20ABAP%20tables%20in%20SAP%20XI

http://wiki.sdn.sap.com/wiki/display/XI/XI+Tables

SXMSPMAST2 (SXMSPMAST): This table contains runtime information on XML messages processed by XI; in this table you can find all the information that is visible in SXMB_MONI. Master table for runtime information on XML messages.

SXMSPERRO2: this table contains entries of error messages (only exception is NO_RECEIVER_STOP which is also mentioned in this table.) Store information on error messages in XI.

use the above tables to generate a report according to ur needs .

Just chk this blog for help :-

https://wiki.sdn.sap.com/wiki/display/Snippets/PIMonitoringFunctionality-FetchingDatafromSXMB_MONIStandardTables-PartII

Regards,

Rohit

Former Member
0 Kudos

You can create a custom "SXMB_MONI" and relalize your requirements. There are some enhancement spots available in the existing programs, making it easier to customize.

Basically its "RSXMB_SELECT_MESSAGES" program to handle the monitring messages.

Refer the following links:

http://wiki.sdn.sap.com/wiki/display/Snippets/FindthePIMessagewithNF-eAccess+Key

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b050ff4f-84c3-2b10-3d99-8f9c44f57...

Hope it helps.

Former Member
0 Kudos

Hi Puneeth,

Thanks for the reply.. I Saw this blog but can this be able to get the error message from the trace. This is where i am stuck with.

Former Member
0 Kudos

Kiran,

As I said you have to write a custom program there you can display all the fields you want to.

Also, if you need to display some custom exceptions/errors/information then you have to catch those excpetion and then using the messge class (SE80); throw the relevant errors in SXMB_MONI and then the same will be available in the report.

A code something like below can be used to throw the expcetion in case of proxies:

RAISE EXCEPTION TYPE zpicx_fmt_nir

EXPORTING

standard = ls_fault.

Edited by: Puneet Singhal on Apr 25, 2011 2:27 PM