Controlling recipients when creating alerts via FM SALRT_CREATE_API

Question

Hi all,
I have successfully managed to make a badi implementation which based on certain checks triggers and alert via FM SALRT_CREATE_API. I have a problem though limiting the users that receive the alert.
I want to control recipients via the import table called IT_RECIPIENTS. But I have a problem if any users are assigned as fixed recipients to the alert category used because then they always get alerts of this category whether or not they are part of IT_RECIPIENTS. In other words if a user has an entry in table salrtcatus for the alert category I am triggering via the FM then he/she gets all alerts of this category which does not make sense in my scenario.
I realize that a solution would be to make sure that no values exist in table salrtcatus. However, I would like to be able to use this table so that users can manually select per activity category if they at all are interested in receiving alerts of a particular category. And as far as I can see the table salrtcatus is the only place to store such information. The table can be maintained by each user if they go to theie worklist in the navigation bar and then click on "Personalize alerts". Then they can choose to sunscribe/unsubscribe to each alert category. How do I ensure that the subscriptions made here do not result in the users getting all alerts of a subscribed category but just the ones where they are purposely selected via import table IT_RECIPIENTS?
I hope you understand my problem
Br,
Anders

Answer 1

You can do it like this (it works for me):
1. in spro for actions define for your alert one additional parameter. In my example I trigger alerts via method call and I trigger method ZTRIGGER_ALERT (modification of standard TRIGGER_ALERT method in class CL_ACTION_EXECUTE).
So I defined new parameter, for example RECEPIENT for which I specified ABAP dict. data type CHAR4. Under Initial value you then specify the key for recepients group. For example RESP for employee responsible.
2. Then you have to do the following coding in ZTRIGGER_ALERT method. Below you have the sample for sending alert only to person belonging to employee responsible function. So in this way you can define as many recipient groups as you like.
data: recipient(4) type c.
READ TABLE lt_container INTO ls_container
       WITH KEY element = 'RECIPIENT'.
IF sy-subrc EQ 0.
    recipient = ls_container-value.
    clear ls_partner.
    refresh lt_recipients.
*determination of new recipient of alert
    loop at lt_partner into ls_partner.
*for RESPONSIBLE
      if ls_partner-partner_fct eq '00000014' and
        recipient eq 'RESP'.
        CALL FUNCTION 'CRM_CENTRALPERSON_GET'
          EXPORTING
            IV_BU_PARTNER_GUID        = ls_partner-bp_partner_guid
          IMPORTING
            EV_USERNAME               = ev_username
          EXCEPTIONS
            NO_CENTRAL_PERSON         = 1
            NO_BUSINESS_PARTNER       = 2
            NO_ID                     = 3
            OTHERS                    = 4.
        IF sy-subrc = 0.
         clear LS_RECIPIENTS.
         LS_RECIPIENTS-uname = ev_username.
         INSERT ls_recipients INTO TABLE lt_recipients.
        ENDIF.
      endif.