Technical Articles
Steps to Setup Instance Synchronization Between Two Successfactors Instances
With this blog post, I aim to visually depict the process to pair two Successfactors instances so that configuration objects/artifacts can be pushed from Source Successfactors Instance to the Target Successfactors Instance using Instance Sync Tool. The steps specified here are as per the latest Successfactors release. Remember that pairing the source instance to a particular target instances is a one-time activity.
You can find more information about Instance Sync tool here or try searching for various other blog posts/KBAs.
Follow below steps to pair source and target instances:
- Go to Provisioning of both Source and Target systems to enable below setting
- Log onto Source and Target Successfactors Instance and create RBP Role via Manage Permission Roles > Create New Role like below
Grant desired Permissions in both source and target systems by hitting Permissions button and navigate to Manage Instance Synchronization section as shown below. The user who will be assigned this role in source system, can push only related configuration/artifacts out of the source system whereas the user who will be assigned this role in target system will only be able to bring related configuration into the target system. So, in order to push an artifact from source instance to target instance, both source and target users should have the relevant permissions in both the instances.
Also, create RBP group to assign above RBP Role to appropriate users in both source and target instances via Manage Permission Groups > Create New Dynamic Group like below
Finally, associate the RBP group to the RBP role created above via Manage Permission Roles
Even if the user is granted permission to Sync at least one configuration object/artifact e.g. Sync Data Model, then the user will get access to all three transactions below which are required to perform Instance Synchronization:
-
- Instance Synchronization Wizard
- Instance Synchronization Monitor
- Manage Sync Packages
- Now, in Source Instance go to Manage Sync Packages, scroll down and click ‘Add New Pair’ (this can be alternatively be done by Instance Synchronization Wizard as well)
In Step 1, populate various details like Data Center, Environment and Company ID of Target system.
In Step 2, we need to enter a Token generated by target system:
So, log into target system and go to ‘Instance Synchronization Wizard’ and click Next:
Click Copy Token button. Remember that the token generated by Target instance will be valid for a specified time period only.
Go to source system and paste the token and click Validate button. Paring process should complete now.
- In the source system, go to ‘Instance Synchronization Wizard’
Click Next after selecting Configuration Copy
Click on link Launch the Instance Synchronization Wizard. Here user will need to select the target instance that is already pared to the source instance. Depending on the user permissions in the source and selected target instance, list of artifacts that can be pushed into target system will appear.
Now run the wizard further to copy configuration from source to target instance. This step can be repeated any number of times to sync configuration objects/artifacts from one system to another.
Obsolete Functionality: In the beginning of the blog post I mentioned that the steps to pair two systems for Instance Sync are as per latest Successfactors release. Prior to current release, the steps 3 could be carried out via Provisioning of source system only but with current release it is no longer possible. Go to Provisioning (source) and click on Instance Synchronization Company Permissions link
System now shows message ‘Please use new mechanism from Instance Sync Wizard page’
That’s it for this blog post. I will soon come up with another blog post where I will explain how to use Instance Sync Wizard to synchronize various artifacts, purpose and usage of each of the three Instance Sync transactions and some tips. So, stay tuned…
This is very helpful. To-the-point and crisp overview of the required steps.
Thanks Aamir
Hi Amit,
Very well written with simple steps to follow, Many thanks.
Govind
Thanks Govind
Well written. Very helpful indeed. Often sync between instances do not work. I hope this helps
Thanks Hussein
excellent
Thanks Jwala
I love step by step blogs. They are always useful.
Nicely done,
Michelle
Thanks Michelle. I am glad that you liked it.
Nice Doc. it will very helpful.. thanks a lot.
Very Informative. Thank you Amit
Very well written with simple steps to follow, thanks Amit
Thanks for your guidance!
is there any risk to sync between two instance? and can i just transport latest additional configuration?
thank Amit
Hi Denny
Regarding risks, I would say you need to be absolutely sure about what you plan to move and understand the fact that whatever you are doing with Instance Sync cannot be undone without manual intervention. To mitigate this risk to an extent, there is Test Sync functionality using which you can simulate if configuration will be synced over or you will run into errors during Actual Sync. Also you can move certain configurations using Instance Sync while some other type of configurations have to be moved manually like workflow, themes, provisioning settings etc. So make sure you plan for those manual sync activities.
Now for your other question that, can you just transport latest additional configuration, I would say it depends on what you are moving. For example prior to rel 1905, if you wanted to move additional values in existing picklist, instance sync didn't work. That was fixed by SAP in rel 1905. Another example, if you want to move changes in Business Rules to target instance, Instance sync will work like a charm.
Hope this helps.
Can we also clone the Foundation and Employee data along with the configuration from one instance to another?
Hi Farhan,
Yes, the Full Copy (Instance Refresh) function is designed to do just that. Also, you can now copy instances with random anonymized data.
KBA: 2827300 - [Provisioning Opt-In Feature] Instance Refresh Tool | Data Anonymization feature (https://launchpad.support.sap.com/#/notes/2827300)
This helps. Many, many thanks