Request are not transported to Production correctly in CHARM

[Former Member]

Dear All,

We have Implementing Change request management(CHARM) for our system landscape. we are trying to transport one request from Quality to Production but all other request that are imported in quality under the Maintenance cycle are also moved to production along with the request that we transported. This is causing unnecessary request to be move to production before testing.

We are following this process:

Create change request->Create Normal correction->Create Trans port request->Release the request->Test transport request->Schedule it in Quality->Complete development->Change the status of maintenance cycle to GO live->Schedule in Production.

Regards,

Pavan.

[r_rajeshkumar · Accepted solution]

Hi,

By creating Urgnt Correction, you will be able to move individual requests.

Regards,

Rajesh Kumar

[Former Member]

Not answered

[RajeevP]

Hi Pavan,

Normal correction does not have a sepearte task list. It uses the one of maintenance cycle. So when you are release one request from quality to prd, you are not doing by selecting a particular request. You perform taht from the task list of maintenance cycle. Hence all the requests associated witht that will get moved to PRD. For a single request, you need to create u'gent correction which have its own task list.

Hope this solves your question. Please revert back if there is any more doubt.

Regards,

Rajeev.

[Former Member]

Hi Pavan,

This is the standard behavior for the 'Normal Corrections'. They work under the philosophy of 'Release Mgt' where all normal corrections move to production together as part of the release.

If you want changes to move independently, you should work with Urgnt Corrections. They have their own tasklist. But please note the urgnts are re-imported with the maintenance cycle when it is moved to go-live phase and imported.

Thanks & Regards,

Kriti Bhalla