Events

Events are triggered directly from the code. Always with the method /PACG/ECM_CL_S_EVENT=>TRIGGER_EVENT. This way it is easy to find all spots where event are triggered. We used to use ‘Events for change document’ (SWEC) but the advantage of doing it directly is that we can verify till certain extant if object is FSM-relevant prior to event’s triggering. The Connector in 4 cases uses also Business Transaction Events (tcode: FIBF) but also here a dedicated function is triggered which eventually calls TRIGGER_EVENT method. Events’ configuration is done by the /PACG/ECM_SETUP tool, it can be then found in transaction SWETYPV. Because Events rely on tRFC for monitoring purposed transaction SM58 can be used.

Use /PACG/ECM_EVTD - Enable/Disable FSM Connector Events to control events:

• It allows for mass maintenance and for manual control over each event individually

• Events by default are active   

• When an entry is removed from the underlying table the corresponding event is considered as inactive

• If IDOC is set as inactive then IDOCS are still created by Connector but they remain in status 30 and are not further processed in the system waiting for manual actions