...
Note |
---|
This tool is dedicated only for urgent issues in system performance. When are too many messages during process, that may leads to serious reduce of system speed. This transaction has a huge impact for transfer data from Connector to FSM application. Only authorized users must have access to editing entries inside transaction. |
Info |
---|
This transaction can be accessed with authorization object /PACG/E015. |
Program allows to enable/disable Idoc transfer and event processing for selected outbound FSM objects types. User can decide which events should be turn off or just stop sending Idocs generated by event to the Cloud.
...
Object type - name of specify event. It can be is possible that event can trigger different another one event or generate idocs for few object types.
Event not active - when checkbox is ticked, the event will be turn off. This means event will be triggered and at the after starting of processing the event will be set instantly as processed. In case when checkbox is unmarked, the communication for event is running.
Idoc not active - when checkbox is ticked, then idocs generated by event will be put into queue with status 30. All idocs created by selected events stop sending all related objects to FSM.
The all settings are disable by default. All existing entries in transaction are from /PACG/ECM_CEVT - Event configuration. User can add new record with event. Please pay attention that configuration from transaction is irrelevant for transports. Due to the high impact on the communication between the Connector and the FSM, a dedicated authorization object /PACG/E015 has been created for authorization role /PACG/ECM_ROLE_FSMADMIN.
Info |
---|
Triggering idocs to the Cloud is still possible by sending transactions (manual object sending) even when checkboxes ‘Events are not active’ and ‘IDocs not active’ are enabled. |