Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This transaction can be accessed with authorization object /PACG/E015.

Info

Starting from

Status
title(S4)PACG 200 SP16 / 300 SP3
, equipment and functional location are handled by separate events.

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 is possible that event can trigger another one 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.