Asynchronous Business Object Event not triggering Workflow

Question

Hello everybody,
I created a workflow for processing of inbound messages (IDoc). The workflow is correctly started when an IDoc arrives. Then it prepares some data and runs into a waiting step. After the user processes the messages via a custom transaction, the workflow should proceed and send some additional information to the message origin.
I created a new BO with an event ProcessComplete, which is called in the custom transaction via the following code:
INCLUDE <cntn01>.
DATA lo_zisu TYPE swc_object.
swc_container lo_container.
swc_create_container lo_container.
swc_set_element lo_container 'VAR1' lv_var.
swc_create_object lo_zisu 'ZABC' lv_object_key.
swc_raise_event lo_zisu 'ProcessComplete' lo_container.
But when I call this code, the workflow does not continue. When I use SWEL to manually create an event on this object, the workflow only continues when I set the check box "synchronous call". So in some way, the asychronous calls disappears completely.
Can anyone give me a hint, where to look for these calls? May there be a setting not active on the system for this particular workflow? Other workflows with the same method of event handling work well.
Thanks and regards,
Christoph

Answer 1

Hello,
I debugged deeper into the whole issue. When I call the function module for the event creation directly (not via the macro posted in my initial post), I have the option to control syncronous va. asynchronous processing:
CALL FUNCTION 'SWE_EVENT_CREATE'
  EXPORTING
    objtype              = 'ZISU_MDC'
    objkey               = lv_objkey
    event                = 'ProcessComplete'
    start_recfb_synchron = 'X'
  IMPORTING
    receiver_count       = lv_rcvcnt
    event_id             = lv_evtid
  TABLES
    event_container      = lo_container
  EXCEPTIONS
    objtype_not_found    = 1
    OTHERS               = 2.
The export parameter start_recfb_synchron controls this. In the program flow, the following is the difference between the two ways:
Synchronous:
      CALL FUNCTION im_handler->m_linkage-recfb
           DESTINATION im_handler->m_linkage-rfcdest
           EXPORTING
             sender                   = l_sibf_object_por
             event                    = l_sibf_event
             rectype                  = l_sibf_rectype
             handler                  = l_receiver_por
             exceptions_allowed       = 'X'
             xml_size                 = l_xml_size
             event_container          = lt_xml_container
           IMPORTING
             result                   = l_result
           EXCEPTIONS
             temp_error               = 1
             OTHERS                   = 99.
Asynchronous:
      CALL FUNCTION im_handler->m_linkage-recfb
           IN BACKGROUND TASK
           AS SEPARATE UNIT
           DESTINATION im_handler->m_linkage-rfcdest
           EXPORTING
             sender                   = l_sibf_object_por
             event                    = l_sibf_event
             rectype                  = l_sibf_rectype
             handler                  = l_receiver_por
             exceptions_allowed       = ' '
             xml_size                 = l_xml_size
             event_container          = lt_xml_container
      CALL FUNCTION 'ID_OF_BACKGROUNDTASK'
           IMPORTING
                tid = l_trfc_id.
The first one works fine, the event gets processed, there is an entry in SWEL, the workflow continues. The second way does not work. The second function returns a tRFC ID, but when locking tRFC in the debugger and search for the call via SM58, there is no entry.
In parallel I opened an OSS message, but did not get any (useful) response yet.
Regards,
Christoph