Change Project – Merge and Sync with Production
This blog series is designed to help in understanding the concept and usage of change projects in business configuration. The idea of this series is to explain the features of the change projects, and some do’s and dont’s while working on it. This blog series will contain following articles:
- Introduction – Concept and Usage
- Change Project Types – Remote or Local
- Change Project – Merge and Sync with Production
- Change Project Life Cycle
- Change Project FAQ Page
In this blog, we would concentrate on the “Sync and Merge” process.
What is the Merge of Change Project?
Merge of a Change Project is copying the configuration data (Scoping and Fine Tuning) from the Change Project to the Productive project. This can be done by executing the activity “Merge Changes to Production”. Before merge, all the activities of the Change Project have been completed.
What are “Recurring Activities” in the Activity list? Why do I have to perform it again after the Merge in the Production Tenant?
Even though all the activities are closed in the Change Project, activities marked as “Recurring” are reopened after the merge. These activities have to be performed again after merge.
Can I still work on the Change Project in the Test Tenant after it has been merged?
No, once the Change Project is merged in the Test Tenant, further activities on the Change Project has to be done in the Production Tenant.
What is the purpose of the activity “Activate Solution Capabilities”?
If there are any new processes scoped in the Change Project, the activity “Activate Solution Capabilities” is added to the activity list automatically. The processes are not activated in the Production Tenant automatically on merge. It is activated only after this activity is performed.
The reason for the 2 step process is that any data set up (like Master Data) required for the new process can be provided in the Production Tenant before activating the process.
Does performing the activity “Activate Solution Capabilities” have any impact before merge of Change Project?
No, this activity has to be completed to trigger the merge of the change project. However, there is no impact on the Test (Remote Change Project) or Production Tenant (Local Change Project) before merge. This activity is reopened after the merge.
Can I do data migration in a Local Change Project before merge?
No, data migration can be performed only after the merge of the Change Project in the Production Tenant.
Can I use Change Project to test data migration before performing it on Production Tenant?
Yes, you can use the Remote Change Project to test the data migration on the Test Tenant. The same can be repeated in Production Tenant after the merge of the Change Project.
Can I perform the “Recurring Activities” in the Local Change Project?
No, you cannot perform “Recurring Activities” in the Local Change Project as the Productive Runtime cannot be accessed by the Change Project.
Do I need a Change Project to perform data migration after Go Live?
Yes, after Go Live, data migration can only be performed via a Change Project.
Can I get the latest Productive Settings to the Change Project?
Yes, at any point in the Change Project life cycle, you can sync the Change Project with the Productive settings by performing the action “Update Project from Production”.
What if the changes in the Change Project conflicts with the existing Productive Project? How can this be resolved?
If there are conflicts between the Change Project and the Productive Project, a conflict resolution UI opens up. This shows the current conflicting Project and Productive setting and the user can choose to stay with the Productive setting or change to the Project setting.
This UI is available both during merge and updating the project (sync).
Recommendation for Change Project
- Make sure both the Production and the Test tenants are at the same level with respect to Add On solutions (including Patch solutions)
- Close all the activities in the Change Project
- Update the Change Project from Production (Sync)
- Resolve the conflicts (if any)
- Simulate Merge
- Merge the Change Project
- Perform Data migration/Recurring activities
- Activate the solution capabilities.
- Close the Change Project
With this we come to the end of the third blog in the blog series. The fourth blog would concentrate on the Life cycle of the Change Project.