on 11-12-2012 10:49 AM
In one mapping there is a lot of RFC-Lookup, in which I forgot to add exception handle.
For Alerting I set up an alerting category like this:
And Long text as below:
The following process has error:
&PROCESSNAME&
Error text:
&SXMS_ERROR_CODE&
&SXMS_ERROR_CODE2&
Futher information you get in SXI_MONITOR.
Normally I got alerts always from PIRWBUSER, which is created in SM59 CentralMonitoringServer-XIAlerts.
But yesterday I got an alert from PIP-RFC@customername.com I know this is because of RFC Exception.
I just wondering, where this alert comes from? How to configure it?
Regards
Rene
After research i got the following information:
1. In the R/3 System there is a RFC-Destination: sapPIP in SM59 with type 3. The user is PIP_RFC, which is created in PIP.
2. in the R/3 System in transaction SALRT1: RFC-Destination Alert Server, the destination is sapPIP.
3. In SCIF the service: Default_host -> sap -> bc -> bsp -> sap -> alert inbox is activated.
Therefore I think, this is something like forwarding Alert to ALM.
It should work like this:
The RFC-Lookup has exception in the R/3 System and triggerts an alert. CCMS sends this alert to PI ALM?
If I got further information, I will tell u.
Regards
Rene
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dong,
Check in alert configuration(fixed recipients) to find out which user id is configured there. Based on that user name Check in SU01 to find out the mail id .
Thanks,
Satish.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check the user id to which the above email id has been assoicated to ...
based on that probably you can find out which user /where the above alert has got triggered..
HTH
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.