As you know, BOR Events are called for a lot of operations on a SAP environment all day long…And they CAN be linked to a Workflow ID, so that the WF is started when the event happens. But if you need an event to be triggered again, so a Workflow can be restarted (for test purposes as an example), you don’t need to create the scenario again or edit the previous one, you can use the SWUE transaction.
Let’s use the Purchase Requisition item release strategy as an example:
First you need to discover the BOR related to the scenario (check out SWO2 transaction), for PR item the BOR is BUS2009, and the event called when a release code is ready to be processed is RELEASESTEPCREATED. For you to discover IF the BOR/Event is indeed linked to a Workflow, you can search in SWE2 transaction. This transaction lists all the BOR/Classes & Events and receiver types linkage (Active or not), in another words it “tells” you if there is any active WF for a particular scenario.
For BUS2009/RELEASESTEPCREATED, we have the WS00000038 Workflow ID (the standard one) active.
So now that we’ve covered the theory, let’s get to it! Go to SWUE transaction, and place the BOR and Event:
First thing, now that you have placed the BOR and Event, you need to place the Keys to the specific scenario… Select the Object Key button and place the PR and Item, for the example above is:
Now you’re almost ready, but first you can see if your event will trigger any Workflows by selecting the Event Receiver Button. For our example, as we saw in the SWE2 transaction, the WF WS00000038 will be called.
One important step is to see if there is any Event Parameters… For the BUS2009 RELEASESTEPCREATED, the Release Code is the required parameter. So for our example, the C1 code is the one required, place it like this:
Now you’re all set! Execute the Create Event button.
Now in SWI1 (or SWIA if you have ADM privilegies) you’ll see your newest Workflow created:
So now you can place SWUE transaction in your favorite ones, for every time you need to test and re-test a Workflow for any specific scenario.