cancel
Showing results for 
Search instead for 
Did you mean: 

ChaRM document - submitted to QAS no longer required

jay_johnson4
Explorer
0 Kudos

What is the best way to abandon a change that was captured in a ChaRM document, moved from the development system to quality - transport and task fully released and now the change is no longer required.  There is a twist to this.  The change included an OSS note which is now obsolete per the note browser in the development system.

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jay,

Once the TR released, you could nt decouple until unless you implemented CCTS.

to prevent the unwanted transports (which already moved to Q, but dont want to be moved to PRD) you can set the custom status and drive with Status dependent import,please check

https://wiki.scn.sap.com/wiki/display/SM/Import+strategies%3A+Status+Dependent+import+and+Selective+...

Thanks,

Jansi

Former Member
0 Kudos

Hi Jansi,

We can decouple the released TR from charm CD though CCTS is not implemented.

Below are the tables used to decouple the released transport from Tasklist and I have done it number of times:

/TMWFLOW/TRISAVC

/TMWFLOW/TRORDHC

Regards,

Abhishek

Former Member
0 Kudos

Hi Abhishek,

yes, but not standard charm could do this. with table and custom developement we can do any thing

thanks for the sharing.

Best Regards,

Jansi

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jay,

Do you want to decouple the released TR.Is that your requirement?

I know how to decouple the released transport from ChaRM CD.

Regards,

Abhishek

jay_johnson4
Explorer
0 Kudos

As stated in one of the other replys, the decouple option is not available after releasing the change. 

What we are trying to avoid is:

Change 1 made in development

Change 1 moved to quality

Change 1 found to be flawed and no longer required

Change 2 made in development to back out change 1

Change 2 moved to quality and confirmed (net change is zero)

Change 1 and 2 move to production (net change is zero)

We would like to halt processing of the ChaRM ticket after change 1 was found to be flawed, but there does not seem to be a way to back out the change and complete the charm document without moving both changes through the landscape and into production.