on 10-07-2010 8:28 AM
Hi,
I want to include payload specific information in my alert mails. I am looking forward to this approach, to help my customer, directly understand the alert mail by pin pointing a few payload specific primary fields.
I have gone through a few blogs, forum threads and SAP help documents and all say that this is not directly possible in ALRTCATDEF.
Please suggest how i can achieve this without using BPM.
Warm Regards,
Anshul
Hi Anshul -
I don't see a way to do this without BPM. You could use the standard container variables in your alert message in case of a communication error. If you require payload specific information, you will have to create a custom report to create the alerts and schedule it in backgroud.
Regards,
TK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
To include the payload specific information in the alert, you might need to trigger the alert from your mapping. you can handle this situation in the mapping and trigger an alert from UDF with all of your required information. Please check the below blog, it uses the SALERT_CREATE RFC call from UDF and no BPM is required!!
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
regards,
francis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Francis,
I have gone through this blog already.
To give you a jest of my scenario:
Itu2019s like ECC to PI to SQL synchronous communication. Now if there is a communication error between PI and SQL or there is an error on SQL then how can i use this UDF-RFC combination to raise alerts with payload specific information?
Would appreciate if you can give your inputs on this.
Warm Regards,
Anshul
Hi Anshul,
Well, I think in this case you would need a small custom ABAP report.First you will get the message id and interface details from the normal XI alert configured with alert rule and alert categories for the messages fails in the receiver side PI SQL communication.
This will be there in the SALRT table. second step use this message id to get the payload using the function module SXMB_READ_MESSAGE_VERSION_RAW. Then use the function module SALERT_CREATE to create your custom alert with this.Not sure if we have a better approach though.
regards,
francis
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.