Mass synchronization (full sync)

This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps for interface activation, especially on a production system. For more detailed descriptions, navigate to links included in each step.

The so-called full sync is a process of mass transfer of FSM-relevant objects from SAP ECC/S4 to FSM. It’s executed once, after a company is created, the message broker was started with the new company definition and FSM Cloud Connector is already customized to the customer’s needs.

Learn more about full sync https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1831108615.

Configuration Step

Customizing transaction

Specify which message types are relevant for full sync (field “Fullsync rel.”). Review which objects really need to be fully synced.

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952719

Specify which order statuses are relevant for full sync (field “FullSync”)

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135798

Full sync should be done with the “Only users” parameter switched on. This prevents the cloud to create EMPLOYEES first. The idocs in the cloud are processed asynchronously and it might happen that EMPLOYEE will be created before ERPUSER. If something like that happens, the reference could be incorrect.

Optionally generate reserved materials for already existing components and transfer them to FSM.

 

Next chapter:

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.