Triggering Mass Synchronization
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 https://crossalm2.atlassian.net/wiki/spaces/JXFB/pages/6574244380).
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:
Use Case 1: Synchonization without SOCM 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 and time range. The configuration of SOCM or PPF-Actions would not be necessary. The configuration of the transaction type in the configuration profile is still neccessary.
Use Case 2: Mass re-synchronization after down time
In case your external system was not reachable for a time and multiple synchronizations got failed, you can re-synchronize those failed tickets.
To do that just open the report, chose the tickets to be synchronized and start the resync.
Select your CC4 configuration profile.
Chose the actions you want to perform (e.g. in case of re-synchronize U~update and T~transit might be sufficant).
You can setup some fine adjustments (filter for certain transaction numbers or types, and define the period where tickets might have been changed).
If your tickets failed to synchronize during a down time of Jira, you can filter this condition here.
Enable “test run” first to find out how many transactions got put into scope.
Use Case 3: Synchronization of 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 recommended to let this report run as a job in the background.
Please filter on transaction type and change/creation date. Please perform a test run. Please perform a real run with a small number of transactzions. Please estimate the complete run time.
Please keep in mind that the transaction type must be configured in the configuration profile but the configuration of a SOCM action or PPF is not needed.
Use Case 4: Initial synchronization before using Cross Connector regulary
Let’s assume you want to use the Cross Connector. You configured everything. Everything is working fine. You can use it for transactions created from now.
But what to do with all transactions created yesterday and the day before yesterday?
You can put it out of scope.
Or these tickets will be synchronized as soon as they will be changed/saved by an end-user.
Or you could synchronize it using this report moving your sync starting point some days or weeks or years into the past.