Caution: in SRM 5.0 - using SWE_EVENT_MAIL

[Susan R. Keohan]

Hello WF-ers,

While debugging in SRM 5.0, WAS 700, to determine if an event is raised...

If you use standard functionality to send an SAPOffice message to your userid when an event is 
created (see attachment), unless your username begins with a letter greater than W (for 'WS'), your 
username will be returned as the first row in table lt_start_receivers after the following calls...

BBP_PDH_WFL_CHECK_BEFORE_START
SWE_BBP_EVENT_SIMULATE

SWB_2_CHECK_FB_START_COND_EVAL
SWB_COND_EVAL

Back in BBP_PDH_WFL_CHECK_BEFORE_START...
   IF sy-subrc <> 0.
* Kein Genehmigung-Workflow gefunden; Systemverwaltung informieren
     MESSAGE s012(bbp_wfl) RAISING no_workflow_found.
*    RETURN.
   ENDIF.

   READ TABLE lt_start_receivers WITH KEY wf_task = 'X'.
   IF sy-subrc <> 0.
* Kein Genehmigung-Workflow gefunden; Systemverwaltung informieren
     MESSAGE s012(bbp_wfl) RAISING no_workflow_found.
*    RETURN.
   ELSE.
     IF sy-tfill > 1.
* Genehmigung-Workflow ist nicht eindeutig; Systemverwaltung informieren
       MESSAGE s013(bbp_wfl) RAISING workflow_not_unique.
*      RETURN.
     ENDIF.
   ENDIF.

   ev_cond_task = lt_start_receivers-rectype.
   gv_wf_start_cond_task = lt_start_receivers-rectype.

At the point where the read table lt_start_receivers is executed, the row with the workflow template 
which should be started is, in my case, the second row.  Therefore, when sy-tfill is evaluated, it 
is equal to 2, which causes the 'workflow_not_unique' to be raised.

A Customer Message has been raised, but I wanted to help any of you prevent needless heartache.
Regards,
Sue
-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu