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 , (e.g. object assignments are set up, address determination sources are configured and any other configuration which affects what and how is sent to FSM are set up).Usually performed on production environments, not so often on test companies. It transfers master data objects, such as customers and materials, technical objects such as order types or person reservation types, as well as users or already existing service orders.
...
Another way to perform full sync is execution of the FSM Cloud Connector program /PACG/ECM_FULLSYNC_S - Fullsync simulate.
What is the opportunity/problem the request will address?
Improve efficiency of processing large number of idocs
What is the expected benefit?
Performance improvement.
What are FSM Cloud Connector customizing options that I should consider before performing the full sync?
Specify which message types are relevant for full sync (field “Fullsync rel.”). Review which objects really need to be fully synced. | /PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration |
Specify which order statuses are relevant for full sync (field “FullSync”) | |
Optionally generate reserved materials for already existing components and transfer them to FSM. Reserved materials are not generated automatically with full sync, therefore execution of a dedicated report in addition is necessary. | |
Optionally enable parallel upload flow of the SAP FSM Transporter component to improve full sync performance. | Company setting ‘TransporterSettings.MaxParallelUploadBatches’. Learn more:Initial-/full-sync performance improvement - parallel communication with SAP FSM |
Full sync
...
/ manual mass data transfer’s performance
Full sync’s/manual mass data transfer’s performance can be enhanced by using the program /PACG/ECM_IDOC_30_DIRECT_SEND. Idocs for master data are collected into packages and then sent to FSM. The program requires changes in idoc processing (transaction WE20):
...
Generated idocs should remain in status 30 and then they can be processed by the mentioned program. Input parameters are requiredIdocs will be collected into packages. The report provides better efficiency of processing large number of idocs than the regular full sync process.
...
Further information
Input parameters are required.
The program requires changes in idoc processing (transaction WE20):
...
Do not to send more than 100-200 items in a package, since it could cause overload of webservices.