How to attach event to custome workflow object ?

Question

Hi Guys,
Could someone help me on how to raise event while creating custom workflow object.We can attach event to object in transaction swe2 . I would like to know how to create that event. Could some send sample custom workflow object with events.
Many thanks in advance.
Cheers,
Garrick.

Answer 1

Here's an example  using Business object BUS2080  Service notification
I delegated ZBUS2080 to BUS2080 (service notification).  Added 2 Events REASSIGNED and MODIFIED.
Use transaction SWO1 for manipulating business objects.
The User performs an action on a service notification  (IW52) say PUT IN SERVICE AGAIN.
When the user puts the service notification in service again the event triggered will start a (user defined) workflow which makes a call to a method in the business object ZBUS2080 which launches a batch job.
This batch job creates our user event REASSIGNED which in turn calls a new workflow to be executed.
This workflow performs the action I want -- in this case to re-assign the service notification to a new person, send an email and escalate the deadlines
Code samples are shown below.
So here's how it works.
First you need to set up some entries with table SWE2. I've assumed you've already defined the events to the Business object(s) you want to use.
In SWE2 define entries for BUS2080 (or ZBUS2080) For Events INPROCESSAGAIN and (our event) REASSIGNED.
IN SWE2 define the receiver call as a FUNCTION MODULE
For the receiver function modules  for the SAP event (INPROCESSAGAIN) define the receiver module as SWW_WI_CREATE_VIA_EVENT
For the event REASSIGNED define the receiver module as SWW_WI_CREATE_VIA_EVENT_IBF.
I have no idea whatwhat the difference is between the two but the process works when it's done like this.
Ensure the linkage Activated box is clicked in both cases.
Put your workflow numbers in the RECEIVER TYPE in SWE2 table.
In the first workflow when the user puts the service notification in service ensure your workflow starts a batch job which raises another event
Note : You need to instantiate the object (I.e supply the key) to trigger the event correctly. The key is obtained from the WF and will be in the container anyway.
You can do this by adding this type of function module into the method of the business object you want to execute during the first workflow. The code here creates a batch job which submits the EVENT creating program.
function z_create_event_for_cs.
""Local interface:
*"  IMPORTING
*"     REFERENCE(OBJECT_KEY) LIKE  SWOTOBJID-OBJKEY
*"     REFERENCE(W_REASON) LIKE  HRPXXXX-DUMMY
*"     REFERENCE(W_ESCLEVEL) LIKE  HRPXXXX-DUMMY
Create Batch job to run ZZREASSIGNCS
which creates event REASSIGNED in Customer query workflow.
data: jobnr like tbtcjob-jobcount,
      jobname like tbtcjob-jobname,
      pgmname  like sy-repid,
      w_key like viqmel-qmnum,
      w_code type c,
      w_num  type c.
      w_num = w_esclevel.
      jobname = 'CREATEEVENT'.
    pgmname = 'ZZREASSIGNCS'.
call function 'JOB_OPEN'
  exporting
    jobname                = jobname
importing
   jobcount               =  jobnr
CHANGING
  RET                    =
  exceptions
   cant_create_job        = 1
   invalid_job_data       = 2
   jobname_missing        = 3
   others                 = 4
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
  input =  object_key
  importing
  output = w_key.
w_code = w_reason.
if w_code = ' '.
w_code = 'Z'.
endif.
submit zzreassigncs
with p_key = w_key
  with p_escl = w_code
  with p_escnum = w_num
  via job jobname number jobnr
  and return.
call function 'JOB_CLOSE'
  exporting
     jobcount                          = jobnr
     jobname                           = jobname
   strtimmed                         = 'X'
  exceptions
    cant_start_immediate              = 1
   invalid_startdate                 = 2
   jobname_missing                   = 3
   job_close_failed                  = 4
   job_nosteps                       = 5
   job_notex                         = 6
   lock_failed                       = 7
   invalid_target                    = 8
   others                            = 9
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endfunction.
For the actual program which creates the event  use something like this
program zzreassigncs.
This program creates an event REASSIGN
This triggers a "clone" of the initial customer query workflow
which is now marked as completed.
The deadline and escalation level from the original workflow
should be passed to the new workflow via the event container
Program is submitted from the original workflow
Ensure transaction SWE2 has the event REASSIGN for bus object BUS2080
defined or the WF won't start even if the event is raised correctly
As this program is run as a background / batch task
you need to obtain the relevant notification number and pass it
as a parameter.
When run from the WF the you can get the notification number obtained
from the workflow / task  container.
include <cntn01>.   "For WF macros.
parameters: p_key like swotobjid-objkey,  "Service notification number
            p_escl type c,
            p_escnum type c.
constants: c_event    like swetypecou-event   value 'REASSIGNED',
           c_attrib   like swotra-attribute   value 'USRSTATUS',
           c_object   like swetypecou-objtype value 'BUS2080'.
data:     w_object like swotobjid,
          w_stat     like  tj30t-txt04.
data: rc like sy-subrc.
data: begin of event_cont occurs 0.
      include structure swr_cont.
data: end of event_cont.
data: begin of return.
  include structure swotreturn.
data end of return.
if running from WF rather than a batch job
swc_container container.
swc_get_element container  'Znumber' p_key.
w_object-objkey = p_key.
w_object-objtype = 'BUS2080'.
call function 'SWO_PROPERTY_GET'
exporting
    object                = w_object
    attribute             = c_attrib
  changing
    value                 =  return.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
w_stat = return(4).
event_cont-element = 'Status'.
event_cont-value = w_stat.
append  event_cont.
event_cont-element = 'Escalated'.
event_cont-value = p_escl.
append event_cont.
event_cont-element = 'Escalation'.
event_cont-value = p_escnum.
append event_cont.
Note WAPI calls only valid from rel 6.1 using Webflow engine
(part of standard WF since rel 6.1)
CALL FUNCTION 'SAP_WAPI_CREATE_EVENT'
  EXPORTING
    OBJECT_TYPE           =   w_object-objtype
    OBJECT_KEY            =   w_object-objkey
    EVENT                 =   'REASSIGNED'
  IMPORTING
   RETURN_CODE           =  rc
  EVENT_ID              =
TABLES
   INPUT_CONTAINER       =  event_cont.
if rc <> 0.   "Houston ---We have a problem !! '
  write: text-002 color col_negative.
  exit.
endif.
even though no database / table is updated here by the event
we still need the commit work to initiate the event correctly
commit work.
You CAN use Objects (OO ABAP) but if you are fairly new to this sort of stuff just stick with standard BOR (Business objects) to parctice on until you've got the hang of the process.
It's actually a lot simpler than most people realize --which is why WF consultants get paid decently !!!!.
Cheers
Jimbo