Skip to Content

use of SWE2 transaction in workflow

Oct 09, 2017 at 11:26 AM


avatar image

what is the use of linking Object Type, Event & Receiver Type in SWE2 transaction when events are already linking in standard Tasks?

Is it mandatory to link Object Type, Event & Receiver Type in SWE2?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Susan Keohan
Oct 09, 2017 at 01:39 PM

You would use this functionality to link customer created objects and events. Or to enable SAP-delivered objects and events (some of these get turned on during customizing).

And yes, if you are trying to get a new object type/event pair to trigger Workflow, then you'd need to create a new entry in this transaction.

You can try following through some of these links below for more info.

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Susan

Thanks for you Answer

I have a requirement to create workflow for Inbound failure Idocs and work items should generate for the different Agents/users regions wise.

Agents are determined based on company code & Region which are maintained in Z custom table

To achieve this I have created task by copying standard one and also created custom function module(logic implemented to determine agents based z table data) which can be assigned under Rule

Question: In this case Is it necessary to Link Object Type, Event & Receiver Type in SWE2 transaction?

If yes, why it is required to link if standard task, Object type & event already linking in SWE2


If the object type and event are already linked, and the linkage is activated, then you should not create an additional linkage in SWE2. What happens when you raise your event? Do you see it in the Event Log?