Alert Prioritizing in ALRTCATDEF

Hi experts,
Is there any way to get the alerts based on for high priority interfaces?
As of now I am getting alerts to all the interfaces when any common errors occurs.
I am in need of grouping the high priority alerts.
We are using solution manager and not CCMS.
Any points welcome.
Ray.

Hey you classify the interfaces according to your priorities and you can perform the configuration for those.
am in need of grouping the high priority alerts.
[LINK|http://www.****************/Tutorials/XI/AlertConfiguration/AC3.htm]
Regards
Pothana

Similar Messages

SolMan alert prioritizing

Hi All,
We have implemented Technical monitoring in our Solution Manager(7.1 SP8) system. We are reciving the mails for the yellow and red alerts.
Is there any way to differentiate the red and yellow alerts for mail alerts(like sending alerts with "high importance" or to different distribution list). As we need to prioritize the alerts, like Red alerts needs to be solved first.
Regards,
Sukanya

Hi Sukanya,
There is no ready made solution available for your scenario, however we may have a workaround. I suggest you customize the email subjects using the procedure mentioned in this blog Customize Email Subject in Solman 7.1 using BADI and then put rules in your mailbox for sorting the emails according to priority in subject line.
Let me know If this works for you.
Regards,
Vivek

Using Standard Container Variables in Email Alerts from BPM

Dear All
While creating alert categories from ALRTCATDEF we have a Long Text Tab where we can use Container Variables like SXMS_MSG_GUID ,SXMS_RULE_NAME, SXMS_ERROR_CAT , SXMS_ERROR_CODE etc create the mail contents. We can also display the message passed by the BPM by using the variable
ALERTDYNAMIC_SHORTTEXT , ALERTDYNAMIC_LONGTEXT .
In my case when I call the alert category from the BPM , the message passed by the BPM is displayed through the ALERTDYNAMIC_LONGTEXT in the alert inbox , but I am not able to utilize the other container variables (like SXMS_MSG_GUID ,SXMS_RULE_NAME, SXMS_ERROR_CAT ) for displaying the messageid ,error category etc. Using these variables for alerts invoked from BPM results in Blank Values for all the container variables.
If the alert is not invoked from BPM these variables are getting populated.
My question is is there a way by which we can utilize these variables for Alerts thrown from BPM.
regards
Nilesh .

hi check the below links for reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
http://rant03.ranffm.de:50000/rwb_mdt/detailsservlet?objectName=name=is.00.rant03,type=XIIntegrationServer&rwb=true&XIDomain=domain.00.rant03&archive=false&selectMessage=%SXMS_MSG_GUID%
note:reward points if solution found helpfull.....
regards
chandrakanth.k

How to receive alert mails when communication channel fails

Hi everybody,
Today there were in the "Communication Channel Monitoring" of the Runtime Workbench some Communication Channels in a "red" status and I would like to know if it is possible to receive per mail any alerts about a failing communication channel?
In SXMB_MONI the error is the following:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=ECPOPR1.corp GROUP=PRODUCCION_SANTANDER R3NAME=PR1 MSSERV=sapmsPR1 PCS=1 ERROR partner not reached (host ECPOPR1.corp, service sapmsPR1) TIME Mon Apr 20 03:25:16 2009 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r_mt.cpp LINE 8688 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 1</SAP:AdditionalText>
Usually, I receive mail alerts when messages failed since I have CCMS configurated but in the CCMS I don´t see any entries for this kind of errors with a Communication Channel...
Thanks in advance,
Regards,
Olivier

Hi!
You can receive Alerts even though you are configured CCBPM. Through Control Step you can throw alerts but only difference between PI7.1 and XI is in 7.1 you can easily create Alert categoy in ESR itself at java stack but in XI you can't create it in Java stack you need to create this ALert category though ALRTCATDEF t code in ABAP Stack even though in 7.1 you created in Java Stack it will be reflecting in ABAP Stack.
Next thing is later you need to Configure ALert Rules in RWB and in ABAP Stack at Alert Category you need to Add your XI SAP ID;s at FIxed Receipients and before adding this Ask your Basis people to link your company mail ID or any mail ID with SAP ID so that you can receive Alerts both in RWB ALert Inbox as well as your Mail Server.
Since the above experts given diff blogs you can easily configure...
I hope u understand the flow....right ?
Regards::
Amar Srinivas Eli

Alert to Error in Receiver determination mapping

Hi everyboy.
Im using a mapping to decide the receiver determination (ReceiverDetermination - http://sap.com/xi/XI/System).
I can´t configure an alert when the mapping fails.
How could I do that????
Thanks a lot

Hi Christian,
As per my understanding you are using extended receiver determination by creating an interface mapping in between your outbound interface and standard receiver interface of SAP BASIS.Do you mean to say that if source data doesnot fulfill the condition to determine any receiver.If so, then I believe in SXMB_MONI we can find the error as unable to determine receiver.Since it belongs to mapping so it will be executed in Integration engine.
create an alert category in ALRTCATDEF
Define Alert Rule in RWB -> Alert Configuration
Select the our own Alert Category
Click to Add Rule and activate the corresponding rule
Regards,
Nutan

XI Alert Categories in CCMS alert monitor

We defined an alert category through ALRTCATDEF and we generate alerts using SALRT_CREATE_LOCAL in the Graphical and Java mapping. We would like these alerts to be visible in CCMS alert monitor in addition to XI alert inbox. We have done config specified in the SAP documentation to get the RWB alerts in CCMS alert monitor, but only the alert categories for which alert rules are defined in RWB are visible, at the moment. IS this because we dont have an alert rule for the alert categories called by SALRT_CREATE_LOCAL,we are not able to see them in CCMS? Is there a way to get around this problem and get these alerts also in the CCMS ?

HI,
See the below links may be helpful..
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1 -- ccms alerts - 1
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 -- ccms alerts -- 2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3 -- ccms alerts --- 3
Regards
Chilla

Types of alerts in PI 7.3

Hi ,
May i know the types of alerts in sap pi 7.3

could anybody give me complete steps for alert framework in ALRTCATDEF and RWB Configuration
pls refer below doc:
Setting-Up Alert Mails:
[Setting-Up Alert |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00e97ba2-85ce-2b10-20bc-bc05cd172154?overridelayout=true]
Message Alerting for SAP NetWeaver PI Advanced Adapter Engine Extended in pi 7.3:
[alerts in pi 7.3|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10d828df-0a5e-2e10-6d9f-83d9034a5301?QuickLink=index&overridelayout=true]

Alert in BPM not triggered anymore

Hello,
I have a strange behavior in my integration process. I defined an alert category in ALRTCATDEF and in my BPM I trigger an alert using that defined category.
This worked fine so far, but after making some non alert-related changes in the process and reactivating it, no more alerts are visible using report RSALERTDISP. Even when rolling back the history to a process version that already worked no more alerts are received.
Checking the workflow log I can see that the alert step is executed successfully "Triggers a process alert in the background" : --> Step completed.
What I have seen however is that in the list with technical details the ALERT_ID in the container is 00000. In earlier tests there was always a value assigned.
Could this be a reason or are there any limitations on the max. number of alerts that can be sent?
Any help is highly appreciated.

This worked fine so far, but after making some non alert-related changes in the process and reactivating it, no more alerts
are visible using report RSALERTDISP. Even when rolling back the history to a process version that already worked no more
alerts are received.
Did you checked the return code of your IP in SXI_CACHE after activating the changes?
Also do a check on the BPM in IR....F7...and see if there are any warning messages.
There is no limit on the number of alerts that can be raised....just that you should have unchecked Suppress Multiple Alerts option in RWB and Alert Rule should be active
Regards,
Abhishek.

Concern: NO ALerts being triggered for SXMB_MONi errors

Hello Experts,
I have configured the SXMB_MONI alert setup in alrtcatdef t-code according to Michal's Blog.
The users configured in SU01 are using the RML mode for communication.
I am able to see the dummy alert triggered from Standard reports like RSALERTTEST in my Alert Inbox (RWB).
But I am unable to see any alert mails (in RWB) for errors being generated in SXMB_MONI.
Kindly help as to what is missing in the alert setup.
Is it anything at the SMTP level or am I missing something in Alert Setup itself?
PS: On checking the "Overview of Send Requests" in SCOT t-code it shows the error "Cannot process message, no route from <login_id> to <SYSID>:<CLNT>:<login_id>.
This error also is shown only for errors triggered from the Report RSALERTTEST and not the actual errors from SXMB_MONI.
Pls Advice,
Thanks in advance,
Elizabeth.

you need to do the configuration of SMTP adress in the mail configuration
go to SCOT transaction and select the SMTP node and select the internet and configure the SMTP host and port details there
and check the option node in use then test the routing
Rajesh

Alert configuration Add Rule Not Working in IE but working in FireFox

I am running into same issue with the Alert configuration Add Rule being disabled in IE. We're on SP 16. I can create the alert classification and alert categories through ALRTCATDEF.
But through IE, when i go into the Runtime workbench->Alert Configuration, though i can see the alert categories i created, i am not able to select any of them. So the Alert rules "Add Rule" and "Change Rule" are always disabled. How did you fix the issue in IE?
There are two posts about this issue.
alert configuration add rule is disabled
creating rule in alert rwb
The second one post says to that this was working in FireFox and not IE. Has anyone run into this with IE and then gotten it to work. We have given all of the necessary roles to the user.
Thanks,
Jay malla
Licensed To Code

Hi Jay Malla,
I am not sure if you might have tried this, but to Add Rule, in your Alert Configuration, you first need to select your Alert Category.
At the bottom , on the left for every ALERT Category, you will find a rectangualr box. When you click on this, your ADD rule button gets enabled.
Regards,
Bhavesh

Getting exception when trying to open Alert Configuration in RW

Hello friends,
I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
Exception:
com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
        at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
        at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
        at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
        at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
        at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out in solving this problem?
Thanks & Regards,
Senthil

From your error, maybe your profile parameter for alert message server is not properly configured:
I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
Liang
=====Post from Aashish Sinha=======
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
· For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
· For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
· The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
· If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
============End of the Post=======================

Send email alerts to multi email addresses

Hi Guys
I have configured my alert on TCode: ALRTCATDEF, SCOT, SU01 and Iu2019me able to get the email alerts but the requirement is to send to other member on the team thought they donu2019t have User Ids in SAP PI. I need to know whether is possible to send an email alerts to those people even if they donu2019t exist in SAP PI they have email address in the same domain
Thanks
Yonela

Hi Yonela,
Request your security/Authorizations team to create userid for those people who need alert mails to be triggered and addtheir users in ALERTCATDEF.
Regards,
Naveen

Problem on configuring Alerts

Hi Gurus,
I'm having some requirement of which alerts need to be configured.
I have created alert category in ALRTCATDEF on ABAP side, and the created one is also reflects in RWB--> Alert configuration.
The problem is when I'm selecting the alert category(created one) it is not reflecting in the selected criteria to move further.
It is not giving me any error of authorization and also I'm not able to create any further action after selecting the created category.
My Question here is what are the roles required to create Alerts.

Hi das
follow these threads
Alert Configuration
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Inbox
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Defining Alert Classifications
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Triggering Alerts
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Setting up alerts
Setting up alerts in RZ20
Alert Management
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04141e8-0f11-2a10-adaa-9d97b062c2df
Alert Notification
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90f449a8-a6db-2910-a386-d2b5999f5751
Custom Alerts in CIC Win Client for CRM 5.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/601db2b2-2839-2a10-0381-8807979f6ff8
Understanding u'r SAP EarlyWatch Alert Report
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4b88cb90-0201-0010-5bb1-a65272a329bf
Thanks
sandeep
if helpful reward points
Edited by: sandeep sharma on May 21, 2008 10:23 AM

Alerts Issue

Hi Team
After configuring the Alert Category in "ALRTCATDEF", and then moving to Runtime Work Bench to define the Alert Rule, the Tabs"Alert Rule" and "Change Rule" are in disabled mode, only "Reset Input Fileds" is in enabled mode. i am unbale to add the "alert rule"
please help me out
thanx in advance

Hi,
To add an alert rule, you will first have to select the Alert category.
In your Alert Configuration page, click on UPDATE TABLE. Then, click on the SQUARE button on the left of your ALERT CATEGORY.
After you select the Alert Category, the ADD RULE button will get anabled.
Check XIRWBUSER Roles are below;
SAP_BC_BASIS_ADMIN
SAP_BC_BASIS_MONITORING
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Also it may be due to browser privacy and security issue.
Go to Privacy in ur browser and set accept all cookies....
Regds,
Pinangshuk.

Alert Category in XI

Hi...
I am doing file to file scenario using BPM. I have created an exception. For that i want to create Alert Category in Xl. Kindly help me out in this by detailed descripition of how to create alert category.

1. Define Alert Category in ALRTCATDEF
2. Define Alert Rules in RWB --> Alert Configuration
And depending on the alert rules , if an error occurs in XI, the alert will be triggered.
Read the Blog by Michal and you will get the picture and then let me know if you need any inputs.
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
The Alerts in SAP XI can be raised for error happening in:
1. Adapter Engine
2. Integration Engine.
1. These Alerts are system generated in case anything happens in either of the component.
For this you need to:
1. Create ALert Category in the Trnasaction ALRTCATDEF
2. Create Alert rules in Runtime Workbench--> ALert Configuration and associating these rules to Alert category.
If you want you can do it without a BPM
and throw an exception in case any of the values is missing:
have a look at this weblog on how to throw exceptions
in a nice way:
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Also just go through Raising Exceptions in SAP XI Mapping and see if it helps you solve the problem.
Also go through these links:
Forwarding Alerts to Alert Management (ALM)
Alert Management
XI: Alerts - Step by step
XI: Alerts - Troubleshooting guide
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f2243d711d1893e0000e8323c4f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/2166e6a91d11d188de0000e8216438/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/05/bb223905b61b0ae10000000a11402f/content.htm
For a Simple case with BPM refer:
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
To send an EMAIL, assign an EMAIL ID to the corresponding user in the transaction SU01 and then set up SCOT and you can send emails when the ALERT is triggered..
Once you have configure Alerts, you will get the Alerts into ALERT INBOX in RWB of the user. To also get the email, the following needs to be done,
1. In SU01 -- Assign the Email ID for the Recipient of the ALERT.
2. In , RWB>ALERT INBOX> PERSONALIZATION--> Time Independent Delivery and Email are selected.
3. Finally, SCOT needs to be set up to send Emails. Check this for the same. You can ask your BASIS team to do this step.
http://help.sap.com/saphelp_nw04/helpdata/en/23/1edf098ea211d2b47300609419ed29/frameset.htm
Also, In ALRTCATDEF, go to SETTINGS--> CONFIGURATION. By default, the option selected is INTERNAL PROCESSING. Select the option SMTP FORWARDING AS XML and give the email id. This will enable you to send an email alert whenever an error occurs in XI.
/people/ginger.gatling/blog/2005/06/16/integrating-alerts-into-uwl--its-no-problem
http://help.sap.com/saphelp_erp2005vp/helpdata/en/92/5e073c8e56f658e10000000a114084/frameset.htm
http://service.sap.com/alert.
I hope it helps.....
pls reward points if solution found helpfull
regards
chandrakanth

Alert Prioritizing in ALRTCATDEF

Similar Messages

Maybe you are looking for