Transporting alert rules

Hi All,
We could transport alert rules from DEV to QA using report SXMSALERT_CONFIGTRANS
These alert rules are configured with sender and receiver component(Business System)
After transport, alert rules on QA are referring to DEV business systems.
Do we need to manually change them or is there any way they get automatically changed to corresponding QA systems?
Any thoughts?
Thank You,
Mugdha Kulkarni

Hi,
I think no need of doing any changes manually in the QA to refer to QA business systems. It will automatically point to the QA systems after tranporting.
Contact your Basis team on this.
Regards,
Prasanna.

Similar Messages

Transported Alert rule not visible in RWB - Alert Configuration

Hi ,
I have Transported Alert rule Using Below mentioned blog ..
Know How to Transport Only the Required Alert Rules !!!
I have followed the following Procedure
1. Go to Transaction SE16 Data browser.
2. Give the table name as SXMSALERTRULES and hit F7. Then Execute (F8).
3. Copy the ALERTHASHVAL field value of the entries that needs to be transported.
4. Go to transaction SE10 and Create a Workbench Request.
5. Select the Task under Workbench Request and Go to Menu Request/Task -> Change Type and select Development/Correction.
6. Double click the task and go to edit mode.
7. Enter Program ID: R3TR, Object: TABU, Objects Name: SXMSALERTRULES, press Enter and click on Functions.
8. Paste the ALERTHASHVAL field value copied in Step-3 and Save.
Now I can see the transported entries in SXMSALERTRULES table . But when I check RWB- Alert Configurations .. There is no new entry for above transported rule ...
Please tell me what is missing or where am i wrong ...

Yes, My problem is Resolved ....
Solution : -
After Transport All Alert Rules, - >
I created Manual entry for any one of the alert rule from Alert Configuration. ->
Then automatically all other transported rule came into visible state ....
So now i can see all my transported rule in Alert Config...
I dont Know , How does it happaned .. But it worked for me ... All rules got visible to me only after creating a manual entry for amy one of the alert rule ...
Hope it helps someone else ...
Guys thanks for all your comments ...
Regards
PS

Alert Rules Transport

Hi Friends,
I would like to transport all my alert rules configured for my scenario at RTW of QUALITY system to PRODUCTION system. for that i found 2 options.
1. Manually enter the alert rules in RTW
2. run the report "SXMSALERT_CONFIGTRANS".
in option2: i run the report and transport request created. it shows message as "transport enrty written. alert no: ABC1234".
So now my doubt is: will this report transport all teh alert rules configured in RTW to PROD? my requirement is i need to transport only my scenario related alert rules....(out of 200 alert rules in RTW, only 10are related to my scenario and i need to transfer only those 10).
Best Regards,SARAN

Hi SARAN,
Transport Alert Categories
Go to ALRTCATDEF (In DEV) --> Transport (In TOOLBAR) --> Current Alert Category --> Create a Customizing Request and note down your request number
Go to SE09 (In DEV) --> Check customizing request and Modifiable --> Choose Display Button --> Go to your Request number --> and release the sub node and then release the request.
Go to STMS (In QA) --> Import --> Import your request
Transport Alert Rules
Create a workbench transport request manually with transaction SE09. Delete the corresponding unclassified task of that request. Double click on the transport request and click on button 'edit <-> change'. For Program ID enter R3TR, for Object Type enter TABU and for Object Name enter SXMSALERTRULES.
Now click on the button with the key symbol (located under 'Function'). Click on 'Insert row' and enter * for table key. Save the request, release it and import it in the target system.
SAP Note 1110295
/people/santhosh.kumarv/blog/2011/02/03/know-how-to-transport-only-the-required-alert-rules

Tranport alert rules

Can we transport alert rules from Development to QA system in XI ? If so then how
Thanks,
Jay

Hi,
the report SXMSALERT_CONFIGTRANS doesn't work because
it generates a transport request where all table entries
of the current logon client are selected.However, the table SXMSALERTRULES doesn't have a client key filed so no entries are selected and the transport request is empty. Here is what I did:
Create a workbench transport request manually with transaction SE09. Delete the corresponding unclassified task of that request. Doubleclick on the transport request and click on edit <--> change. For Program ID enter R3TR, for Object Type enter TABU and for Object
Name enter SXMSALERTRULES
Now click on the button with the key symbol (located under 'Function'). Click on 'insert row' and enter * for table key. Save the request, release it and import it in the target system. You should see your alert rules now.
I hope this helps,
Thomas

Alert rules not displaying correctly in the RWB after transporting to QA

Hi Experts,
After transporting the alert rules from DEV to QA, the rules are not correctly displayed in the RWB in QA e.g. a star (*) is displayed in all the fields instead of the filter values which I have entered such as the "Sender Party"; "Sender Interface" etc. I am also not able to manually change the values in the RWB in QA anymore because the values are greyed out.
Strangely enough, the rules are correctly displayed inside the SXMSALERTRULES table in QA.
Do you perhaps know how to solve this issue so that the rules are also correclty displayed in the RWB after transporting?
Thanks and regards
Brendon

Having the same problem and looking for fix...

Transport of Alert Rules across the XI landscape

Hi,
We have created around 30 alert rules in our XI development environment (in the runtime workbench) and we would like to replicate the same across all the subsequent XI environments in our landscape. We want to avoid creating the alert rules manually in each XI system.
Is there any way to transport the same ?
I appreciate your reply.

Hi,
Q7: How can I transport my Alert Categories and my Alert Rules to a different system?
A7: The Basis Alert Framework provides a menu Transport in the transaction ALRTCATDEF which allows you to create a transport request for the Alert Categories. However this works only if you have created the Alert Categories in the customizing client (c.f. the documentation of the Basis Alert Framework). For the Alert Rules you may create a transport request by runnning the report SXMSALERT_CONFIGTRANS.
SAP Note 913858
regards,
Hai

Transport alert category and alert rule

Hi,
We are using SAP BASIS 700 (NW2004S SP9). We have created alert category and alert rule in development system. We now want to transport this alert category and alert rule to test system. I have referred to sapnote 913858 but its valid till SAP BASIS 640 and we are using SAP BASIS 700.
Does anybody know how to resolve this issue?
Regards,
Mateen.

Thank you all you 3 wonderful people, your replies did helped and I am definitely going to reward you with the points..Now I am getting alerts in my alert inbox. Can you also help me with some info on alerts?
1) What exactly happens when I check and uncheck "Suppress Multiple Alerts of this rule" checkbox while creating alert rule? I have read some documentations for it in sap help website and also in some of the forums but its still very confusing to me. Can you please give me an exact picture of it?
2) I am unable to get alert emails in my lotus notes. I compared my profile setup in XIJ and XIT using TCode SU01 and found that the PARAMETERS tab had some discrepancies. Can you please confirm if this can be the reason?
Best Regards,
Mateen.

BAM getting random timeouts calling BPEL web service as alert rule

I have a BAM alert rule set up to call a BPEL process (web service call basically). This is part of our custom error notification and escalation solution.
In production I randomly see timeouts in the BAM event engine logs where the web service call has timed out. On the BPEL side these processes never show as being invoked, nor are they in manual recovery.
This only happens at random times, although usually in "clumps" lasting a few minutes. The rest of the time this has been fairly reliable.
Any help from the BAM experts would be appreciated. I would open an SR on this, but I have found support to literally take days/weeks to get back to me on BAM issues -- and this particular issue does not seem to be reliably reproduceable.
Here is the event engine log message:
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] ERROR - EventEngine Action exception: EEInstEv218067 EEInstAct218066 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] ERROR - EventEngine Action exception: EEInstEv218066 EEInstAct218065 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)

I should note that both BPEL and BAM are at version 10.1.3.1

Error while defining alert rule.

Hi ,
I am working with Alert framework and it is triggering the mail when ever message is failing at IE or AE level.
I have defined the following container variable of ABAP data type
SXMS_FROM_SERVICE                  SXI_FROM_SERVICE
SXMS_FROM_NAMESPACE          SXI_FROM_ACTION_NS
SXMS_FROM_INTERFACE          SXI_FROM_ACTION
SXMS_TO_SERVICE               SXI_TO_SERVICE
SXMS_TO_NAMESPACE                  SXI_TO_ACTION_NS
SXMS_TO_INTERFACE                   SXI_TO_ACTION.
and my long text is defined as
Sender service = &SXMS_FROM_SERVICE&
Sender namespace = &SXMS_FROM_NAMESPACE&
Sender interface = &SXMS_FROM_INTERFACE&
Receiver service = &SXMS_TO_SERVICE&
Receiver namespace = &SXMS_TO_NAMESPACE&
Receiver interface = &SXMS_TO_INTERFACE&
Now I am defining 2 alert rule one for IE and one for AE by using above alert categories.
now My Question
1. When I am putting * for sender Interface and giving receiver Interface detail it is working fine for AE errors.but it is not working when i am giving sender Interface description and putting * for receiver interface description.
I have checked several time that i am giving correct entry for sender Interface detail.
2.my long text giving the wrong Information.
when i have defined my sender interface detail and giving * for receiver interface at my alert rule ,it is copying the sender interface name and namespace name to the receiver interface and namespace name .
EX-
Sender service = ECC1
Sender namespace = testInterface
Sender interface =urn:test.com
Receiver service = 3party1
Receiver namespace = testInterface
Receiver interface = urn:test.com
and reverse is happening when I am giving * for sender detail and entry for receiver detail.
I think these container variable get filled at run time and it has to give correct detail in long text.
please help in knowing why this is happening.
regards,
Navneet

Hi..
please try this....Goto KSR2_VBP.
THere are two strategies.. 01 and 02.
01 for manual creation of settlement rules
02 for auto creation..
first check whether 01 and 02 are in your plant.
Sales and distrib....basic functions......auto gen. of settlement rules.......
here you ll find two activities.
(1)maintaining the settlement strategies and
(2)activating one among them.
If you activate 02, your problem will be solved..
Also check this..
http://help.sap.com/erp2005_ehp_03/helpdata/EN/a9/ab777d414111d182b10000e829fbfe/frameset.htm
The settlement profile is to be defined for thee particular Order Type to generate automatically.
Define Production Order Type in OPJH
Under Cost controlling check the settlement profile .
If not create the same in OPJH.
Settlement Profile: Create settlement profile - SPRO > Controlling > Product Cost Controlling > Product cost by Order > Period End Closing > Settlement > Create Settlement Profile
Enter Settlement profile from OPJH or Choose one for production order
and configure Settlement profile. Indicators
with wishes
karthick.

Transporting Update Rules

Hi,
I am transporting update rules for a Cube.
The InfoSource has been generated from a DSO and created update rules to the above said Cube.
In the transports I am getting the below error.
Start of the after-import method RS_UPDR_AFTER_IMPORT for object type(s) UPDR (Activation Mode)
Update rules 46H2HBH6BRHP9R29L0XREHQP3 read in version M
Update rules 46HK9D48LBRIH89ZBZVTZERTZ read in version M
Error when activating update rule 46H2HBH6BRHP9R29L0XREHQP3
Activation of the update rules for ZICUBE01 8ZDSO1
IC=ZICUBE01 IS=8ZDSO1 error when checking the update rules
Error when activating update rule 46HK9D48LBRIH89ZBZVTZERTZ
Activation of the update rules for ZICUBE04 8ZDSO04
IC=ZICUBE04 IS=8ZDSO04 error when checking the update rules
The InfoCube(It is already there in Q apd P) has been locked in a different user transport as he added a field to it and not yet transported.
Is this the problem?
Thans in advance..
Message was edited by:
        Indira SR

Hi indira,
make neccessary changes to the request if u created earlier i.e u can delete the original request or change the discrption to "Dont delete" and release it, if u unable to delete each task in that particular request.
Second step is activate all the infosources and cubes and Update rules.
Then create transport request individually i.e One for IS and One IC and another for Update rules..It would be easier to trace in case of any error.
Release the requests 4m DEV, and important thing is import these requests in Q or P in hierachiel manner i.e
1. IS
2. IC
and the Update rules request.

Error when transporting transfer rules

Hi, i got an error when i transport transfer rules. i got the following errors in various transfer rules:
Mapping between data source 0CUSTOMER_ATTR and source system EMP300 is inconsistent
AND
Reference to transfer structure 0CUSTOMER_ATTR_BB not available. No activation possible.
I tried to activate the data sources and transport them several times, but i got the same errors. Checking manually i can see the data sources active in my source system, in development and productive instances.
Thanks in advance.
Diego Lombardini

Hello Diego
Do you choose the correct Transfer Structure in DEV?
I mean the one that is assigned to EMP300.
Are you saying that your PROD have the following:
0customer_text_BA
And that your DEV only have the following:
0customer_text_BB
If the answer to the above questions is YES;
Find out if some one has assigned ATTR to 0CUSTOMER directly in PROD or somebody has changed 0CUSTOMER_ATTR in DEV without transporting it to PROD.
I think that one way to resolve this problem is to use the option "overwrite origanls" in STMS.
Use it with caution and do not mass transport when you use this option.
Good luck
/FZA
Message was edited by: Fariborz Zangoui
Message was edited by: Fariborz Zangoui

Problem while transporting transfer rules in BW 3.5

Hi All,
I have a problem while transporting transfer rules in BW 3.5.
I have just checked the box for conversion to Transfer structure / Transfer rules of an infoobject and tried to transport it to quality. I got this below error message:
The selections T ZBW_ZBILLRATP_TEXT_BA specify more than one DataSource
Diagnosis
You need to select an individual DataSource based on the selection conditions
InfoSource =
Source System =
Object Version = T
Transfer Structure = ZBW_ZBILLRATP_TEXT_BA
although the select event is not unique.
Procedure
Check the objects to which the selection applies.
Reference to transfer structure ZBW_ZBILLRATP_TEXT_BA not available. No activation possible.
Message no. RSAR436
Diagnosis
Transfer structure ZBW_ZBILLRATP_TEXT_BA should be transported into this system.
However, no DataSource mapping refers to this transfer structure.
System response
The transfer structure was not activated or deleted.
Procedure
Ensure that DataSource mapping, with a reference to the transfer structure ZBW_ZBILLRATP_TEXT_BA is on the same transport request. Use the transport connection to create a consistent request.
Can any one provide me details of how to overcome this issue. I tried transporting all related objects.
Regards
Lakshmi

Hi Lakshmi,
Befor Transporting the Transfer rules, make sure that you are transporting the Active Versions of your Datasource & DataTarget between which your transfer rules exist.
Also make sure that the Transfer rules are active before it is transported.
Hope it helps!
Regards,
Pavan

Alert Rule Configuration in SAP PI 7.3

Hello,
I am using PI 7.3. It's java stack only. I am using component based alert configuration.
AlertConsumerJob is running. But for a particular scenario, no alert is generated, although the message status is "System error". We are getting the below error for this scenario.
com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of PI_Technical team.
This alert generation is working fine for others scenarios. Means, we are able to get alert mail for other scenarios.
Please advise.
Thanks & Regards,
Moumita

Hi Moumitha,
Please find below links may be its Helps you
Alert Rule is not sending Alert Emails PI7.3
Alert Configuration in PI 7.31
Regards,
Rajendar K

Alert rule not working! Please help!

Hi All,
   I have a Async XI scenario IDOC ---> XI -
> JMS
   In order to receive alerts if JMS adapter or server is down, I have configured alert rule in runtime workbench. The associated alert category is setup correctly with fixed recipients.
   Following are the settings in my alert rule.
   1. Conditions: Connected to message - Not Relevant
       Sender component: I have given my IDOC source system.
       Receiver component : I have given by JMS target system.
       Remaining all values: *
   2. Where did the error occur? : No Restriction
   Now for testing purpose if I give a junk server name in JMS communication channel and send the IDOC from source system, then I found that the corresponding XI message is showing as successfully processed. AT the same time in communication channel monitoring in runtime workbench I get an error:
Error creating JMS connection. JMS provider gave error message as Failed to connect to the server
But I don't receive any alert. Why? Is there anything wrong with the alert rule?
Why is the message in XI showing successfully processed even though there is an error in adapter?
Is this the normal behavior of any Async communication?
Please help! I am struggling with this issue for a long time.
I will be grateful if somebody can help me.
Thanks & Regards
Gopal
Edited by: GOPAL BALIGA on Mar 23, 2009 9:31 AM

Dear Gopal,
you have a couple of questions...
1. Even thought the receiver communica channel is in error , why is the moni showing successfully processed?
Ans...This is not an unusual behavior... what is happening is as your mapping is correct the message is passing through the IE properly but when the adapter engine ( JMS receiver channel ) tries to coomunicate with the receiver JMS system it is giving error ..as u have given some wrong server details
2. Alert e-mail not received
chk whether the alert catergory u created is attached to your alert rule..
you can do this in the alert configuration tab in the RWB
Also you need to activate your alert rule ..this again can be done in alert config tab..there is a chkbox of "rule activation".
Givind points is another way to say thanks
Edited by: Tarang Shah on Mar 23, 2009 9:46 AM

Alert Rule - not working. Wild Card character issue

Hi All,
I have a requirement where I need to trigger alerts for mapping failures
of all the interfaces whose namespace is urn:abc.com:odna* or urn:abc.com.odna*. (in the first instance, there is dot before odna and int he second instance, a colon before odna )
So to suit both the cases, I gave urn:abc.comodna in the Alert Rule.
It worked before. But now its not working.
Then when i changed it to urn:abc.com:odna* it works again. i really dont understand how it worked before and why it fails now.
What is the reason for the unpredicatable behaviour of WildCard Character based Alert Rules?
Should Wild Card Characters be avoided completely?

Hey
Just create two separate alert rules for the same alert category
one for urn:abc.com:odna* and another for urn:abc.com.odna*.
but before that please make sure that "Suppress multiple alerts of this rule" box is unchecked.
Also please check SAP Note 913858
Thanx
Aamir
Edited by: Aamir Suhail on May 20, 2009 9:16 AM

Transporting alert rules

Similar Messages

Maybe you are looking for