Skip to Content

ChaRM document - submitted to QAS no longer required

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.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 29, 2016 at 02:19 PM

    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



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 29, 2016 at 11:51 AM

    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.



    Add comment
    10|10000 characters needed characters exceeded

    • 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.