Retrofit - creation of target requests

[vervinckt_joyca]

Dear Experts,

We are setting up Retrofit (+ ChaRM) at a customer currently.

But I have a question regarding the "target request" for Retrofit.

So there is a DEV1-QAS1-PRD1 maintenance landscape and a parallel DEV2 and QAS2 project landscape.

TR1 is created in DEV1 in the maintenance landscape. It is released, so now it is possible to perform the retrofit.

When retrofitting, the Retrofit screen asks you to fill in a "target request" from the DEV2 system in the "retrofit request" column.

However this 'target request" on DEV2 needs to exist already beforehand?? Honestly I would have expected Retrofit to create his own new target requests, or at least a button "create transport request" on the retrofit screen...

How, where and when would you then best create this target request on DEV2?

On DEV2 we have the implementation project running. Should we create a separate Normal change document on that project in which we create all of the "target requests" for retrofit? But then they would also be creating TOCs etc towards QAS2 which is not necessary imo? Or should retrofit requests be created directly on the Task List of the implementation project? (but this then complicates the procedure towards the users, most of them normally stay in the Web UI while for the task list they need to go to GUI etc)...

Your advise is very much appreciated,

Thanks,

Joyca

[artemzhegalin · Accepted solution]

Hello, Joyca.

There are several options for retrofit.

1. You can create 1 RfC and 1 subsequent CD in implementation project for retrofit. All your "target requests" in that case will be assigned to one change document. This option is OK if you have 1 implementation project and use IMPORT_ALL strategy;
2. If you are using selective import (not standard IMPORT_ALL) - previous option is not the best one. Downgrade Protection conflicts are not raised for transport requests assigned to the same change document. So in that case you should have separate CD for every "target request";
3. Also there is a challenge when you have multiple implementation projects. You can create special project per each logical component (production system) or use one of your implementation projects (the deal is to decide - which one).

Also you can find some small discussion about retrofit in comments here.

BR,

Artem