Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Where to find Mass Synchronization report

With the report /XALM/CC4_MASS_SYNC, it is possible to send multiple tickets to an external system defined in the configuration profile (for configurationsteps see CC4 Create and maintain configuration profile).

The report can be accessed via transaction code /xalm/cc4_mass_sync and can be found in SPRO via SAP Solution Manager → Cross Connecter → SAP Solution Manager to External System → CC4 mass synchronization:

image-20240328-081503.png

Use Case 1: Synchonization without SCOM or PPF-Action

You can easily schedule the report as job in the background, which then can synchronize for example every hour the tickets of a certain transaction type. The configuration of SCOM or PPf-Actions would not be necessary.

Use Case 2: Mass synchronization after down time

Was your external system not reachable for a time and multiple synchronizations have failed, you can re-synchronize those failed tickets.

To do that open the report /xalm/cc4_mass_sync and configure which tickets should be synchronized and start it.

image-20240328-085550.png
  1. your CC4 configuration profile

  2. the actions you want to perform (e.g. in case of re-synchronize U~update and T~transit might be sufficant)

  3. here you can set some fine adjustments (filter for certain transaction numbers or types, and define the period where tickets might have been changed)

  4. If your tickets failed to synchronize during a down time of Jira, you can filter this condition here

  5. enable/disable “test run”

Use Case 3: Synchronization closed tickets/Mass Migration

It is also possible to synchronize old, already closed tickets subsequently to the external tool. This is useful, if you want to document older tickets or need the ticket informations additional in your external tool.

If you want to push a large number of tickets to your external system, it is recommanded to let this report run as a job in the background.

  • No labels