How to Handle RC 8/RC 12/ RC 16 TR's in CHARM?

[former_member210909]

Hi Experts,

We are coming across a scenario, where in there are TR's which are imported with RC 8/RC 12/ RC 16. To overcome this issue user create one more Bug Fix TR and fix the same. But in ChaRM user is not able to proceed as it blocks the user at Sucessfully Tested status. ChaRM in Backend tries to re-import those TR's with error.

Could you please suggest us how we can handle this issue in ChaRM.

Thanks,

Rakesh Bhor

[Former Member · Accepted solution]

Hi Rakesh,

As Shailesh mentioned its not a good practice to reuse the same CD for BUG fix. However, in particularly the mentioned case, in SCMA you can click 'Correct import(repair flag)'. It will give you the list of transports that went in error for all (*) users in QAS or PRD systems. Then you can select the transports one by one and click 'error corrected' button.

After this you can try again to change the status of CD to 'Successfully Tested'.

Regards,

Anjali.

[Former Member]

Hi Rakesh,

Reusing the same CD to create a new TR to fix the existing issue during import is not a feasible approach. What we have done is that once the Return code is an erroneous one like 8 or 12 etc we check the logs and inform the concerned team with the details, and they have to create a new CD and if the change is urgent send it to Production as an emergency. Or if its a crucial go-live sometimes Basis team is notified and they manually reimport the TR into production to check if there was an issue while import. But yeah ChaRM is designed that way to prevent repetitive imports through same CD into production.

Shailesh

[former_member210909]

Hi Shailesh,

Thanks for your reply, But there are few more questions which i need to get cleared?

What will happen to that Original CD, which has the TR with errors. Will that need to be moved to Production?

Rakesh

[Former Member]

Once the CD has been imported with an error RC, we remove it from the production import queue and do not reimport it, we do note down the detailed error message for the failure and convey it to the developer team, then only the fix that is send in as an emergency is imported to production.

Shailesh

[Former Member]

We also have many times like the above errors, every day we have a custom prog which triggers the emails to TR creator if there are any errors , so that basis team do not need to monitor all transports with errors.

Jignesh