Mapping Alerts in BPM

Question

Hi,
  I am working on a scenario where in i need to raise alerts to business end users from mapping errors. The mapping errors occurs due to missing data in Idoc segments. I have tried using the control step in exception branch and posting a call to the Alert Category defined in ALRTCATDEF in the ABAP stack.
In the alert category, i have defined the container variables and used the following configurations in the long text -
Message ID : &SXMS_MSG_GUID&
Sender Service : &SXMS_FROM_SERVICE&
Sender Interface : &SXMS_FROM_INTERFACE&
Sender NameSpace : &SXMS_FROM_NAMESPACE&
Receiver Service : &SXMS_TO_SERVICE&
Receiver Interface : &SXMS_TO_INTERFACE&
Receiver Namespace : &SXMS_TO_NAMESPACE&
Adapter Error : &SXMS_TO_ADAPTER_ERRTXT&
Error Category : &SXMS_ERROR_CAT&
Error Code : &SXMS_ERROR_CODE&
However on mapping error, i get the alert message in the inbox with all the above fields blank. Even i am not getting the possible subsequent activities in the alert mail.
The client requires the details to be filled in case of mapping errors.
For your information, the above information is well filled in case of any adapter error or Network issues (ICM failure etc..).
I doubt that the data is unable to be filled in due to mapping being executed on the Java stack.
Please suggest.
Thanks,
Amit

Answer 1

Hi Amit,
   I faced the same issue in one of my projects.
You canot get dynamic messages(Using container variables) with the long text option in your alert category.
You can do the following.
1) In the Exception branch, have a transformation step with source message as the source message in your actual mapping and target message as an abstartct interface(Name it as Alert_Variables(NOt mandataory to name it the same way) ) with one node and one child (of type string).
2) Have a mapping between your source message and your target Alert_Variables.
3) Write a UDF to get the concatenated text with all the variables you need and map to the target field.
//write your code here
String constant;
java.util.Map map;
map = container.getTransformationParameters();
constant = "Message GUID:"+(String) map.get(StreamTransformationConstants.MESSAGE_ID)+"\n"
+"Sender Party:"+(String) map.get(StreamTransformationConstants.SENDER_PARTY)+"\n"
+"Sender Service:"+(String) map.get(StreamTransformationConstants.SENDER_SERVICE)+"\n"
+"Sender Namespace:"+(String) map.get(StreamTransformationConstants.SENDER_NAMESPACE)+"\n"
+"Sender Interface:"+(String) map.get(StreamTransformationConstants.INTERFACE)+"\n"
+"\n"
+"Receiver Party:"+(String) map.get(StreamTransformationConstants.RECEIVER_PARTY)+"\n"
+"Receiver Service:"+(String) map.get(StreamTransformationConstants.RECEIVER_SERVICE)+"\n"
+"Receiver Namespace:"+(String) map.get(StreamTransformationConstants.RECEIVER_NAMESPACE)+"\n"
+"Receiver Interface:"+(String) map.get(StreamTransformationConstants.RECEIVER_NAME)+"\n"
+"\n";
return constant;
4) After the transformation step in your exception branch, you can have a container step to assign the value of the target node's child element(That was returned by the transformation step).
5) Have the control step to raise the alert category. The alert text should include only the container variable that holds the concatenated value of all the information.
6) Check the Dynamic text checkbox in your ALert category defined in your abap stack.
Regards,
Ravi Kanth Talagana