Move changes from C4C DEV to PROD

[mark_grantg1]

Good day Experts!

The current C4C environment already has a solution that was transported to PROD a year ago, this was for a Sales implementation.

We just scoped an entire new Service solution. I completed and tested the solution in QA and ready to move to PROD.

Was I was supposed to create a change project before I started scoping the new Service project changes? If the answer is yes, am I still able to move these changes from QA to PROD now that I have scoped all the changes already?

Thanks in advance

[Juliuspereira]

Hi Mark,

The answer is Yes. While you can make changes directly in Test, its just easier to make them in a change project as that is the only way to move changes to production in a proper fashion. Otherwise you will have to make all the changes manually in production and that's scary as you might miss something or inadvertently make a mistake.

When you make changes directly in a Dev/ Test tenant and then create a change project in production and copy it down to dev/ test, perform the action 'Update project from production' which is found under the actions menu after you click on the name of the change project. as a best practice you should always do this when you copy down any change project irrespective of whether you have made changes directly in dev/ test. This is to safe guard the changes just in case someone else has done some changes that you might not be aware of.

When you perform this action, if there are differences in the solution between dev/ test and prod, the system will give you a popup stating that there are inconsistencies and you will have the option to choose which changes you want to go with - Dev or Prod. Once you do that, all the changes based on the option you chose, will be added to the change project. Since Dev has most of your new changes, you could choose to retain your dev changes. This will not overwrite anything that is already existing in production. But will mainly assist with syncing the most recent changes in the change project, which you could then be merged with production.

What I'm not sure about is whether this 'update project from production' action also applies to scoping changes or whether it only applies to activity list configuration changes/ fine tuning activities.

You might want to create an incident with SAP C4C support for that. SAP C4C support will generally shoot this down stating that its consulting in nature. However its worth a try as you might get lucky if your ticket is picked by some support person who really wants to help 😉

Alternately, you should reach out to your Account Executive or CEE (Client Engagement Executive) and ask them to arrange a call with an expert from SAP to confirm if the above will work for you.

Hope this helps Mark. When all is said and done, if you don't mind please share the approach taken and/ or how you ended up resolving this, because one way or the other, I'm sure you will.

Good luck.

Julius

[mark_grantg1 · Accepted solution]

Hi Julius

Thanks for your prompt response and apologies for my delayed one.

The approach I followed was the following:

1. I created the change project in PROD. Upon creating the change project in PROD I had the QA/DEV scoping open and made sure that I did a like for like on the scoping in PROD.

2. I took screenshots of all my scoping in QA and MOST importantly of all my config I maintained under the Activity list. This was a life saver! THIS IS THE MOST IMPORTANT STEP.

3. Copied the change project from PROD to QA. I experienced an error around Technical inconsistencies. Which in short was complaining about a certain Z document type that seems like it was deleted, because it existed only in QA but not in PROD. So with the copy from PROD this Z Document Type was basically deleted. I fixed this error by going and manually deleting all of the transactions created against this document type in QA

4. Restarted the upgrade in QA that basically synced the two environments successfully now.

5. Went through all of the scoping in QA comparing it with my screenshots I took of the earlier scoping in QA before the copy. It seemed like all of the scoping copied over 100%.

6. The copy from PROD to QA overwrote all of the config in the QA Activity List that I performed earlier. I had to re-do the config. Luckily the screenshots of the Activities I took ensured that I get the config done in no time, exactly the way it was before the copy from PROD to QA.

7. Last step was then to Merge the changes back to PROD.

Thanks again for your response julius.pereira25!

[Juliuspereira · Accepted solution]

That's awesome Mark. Thank you for sharing!