How To Run F1-SYNCRQ Without Processing Pending Sync Requests Generated For OU Analytics? (Doc ID 2085252.1)

Last updated on MARCH 14, 2025

Applies to:

Goal

When running the "Create Sync Req" to generate the files for the OUA Initial load, F1-SYNCRQ will continuously process the relevant data. This is causing delays on F1-SYNRQ used for regular operations in MWM/ORS. How can a customer rollback so that the F1-SYNCRQ does not include the records for the initial OUA load?

The goal is to run F1-SYNCRQ but not process the pending sync requests generated for MWM Analytics. For example, if there is one F1-SYNCRQ, which covers all tasks and includes MWM Analytics, and the initial Load jobs for MWM Analytics are initiated, the same F1-SYNCRQ will pickup these tasks automatically and continuously.  It cannot be excluded from F1-SYNCRQ. Is it possible to cancel the initial load jobs so that F1-SYNCH will not pick these records anymore? When the initial Load jobs are run in MWM, the F1-SYNCRQ slowed down the system to the extent that it needed to be rolled back. However, once you run the initial job the F1-SYNCRQ will pickup the load changes from that point onward.
 

Solution