Skip to Content

Through the Looking Glass: ChaRM: New functionality with SP5: Assign and Decouple Transport Requests

With SAP Solution Manager ST 7.10 Support Package 5 Change Request Management introduces a set of new functionality.

A new feature is to handle transport requests more flexible.

It is now possible to assign not released transports not connected to a change document.

Possible Scenarios:

1.) This is especially useful if a customer starts with ChaRM and wants to put the old transports under change documents to control them with ChaRM and use all the other useful features ChaRM makes possible.

2.) If you are working for example in a project (lots of transport in a normal change 1) and are in the testing phase and you find out you have dependencies to another normal change 2 with lots of transport requests which is planned to go live later because it’s taking longer than expected, you generally have an issue.

If you now find out that the dependent objects are created in one transport of the normal change 2, it’s possible to decouple this transport (we will come to that) and assign it to normal change 1 so the project can be imported in one step into the production system.

So, how to do that and how does it look like:

Here a normal change without transports:

Assign Transport Request.jpg

In the Transport Management Assignment Block you find the ‘Assign Transport Request’ function:

assign Transport - Selection screen 0.jpg

A selection screen is issued wher you can search transport request with different criteria like transport request number, description of the transport, user name, type, etc…

You mark the transport(s) and choose ‘Assign Transport Request’ (at the table top):

As you can see here warnings might be issued, coming from the downgrade protection. If you assign and decide to transport and have downgrade protection active, you will be prompted to check the conflicts. It’s possible to ignore the conflicts, otherwise no import will take place.

assign Transport - Selection screen 2.jpg

But lets stay with assign transport request funtionality…

assign Transport - Selection screen 3.jpg

Now the transport request is assigned. Note the information message.

The second new functionality is the already mentioned ‘Decouple Transport Request’ functionality. It completes the other functionality and comes in nicely if you have done an error with ‘Assign Transport Request’ functionality or want to decouple specific changes contained in transport requests from the change document in specific circumstances. Might be downgrade issues, might be organizational issues, for example two normal changes in a project should be import in one normal change…because organizations have been joined and now working as one project and your change manager wants it in one normal change…there could be lots of possible reasons which the real world creates and now you just have the flexibility to decouple it and then assign it to other changes.

The example here…

Decouple Transport request.jpg

When we have transports available and depending from the user status the ‘Decouple Trahnsport Request’ functionality can be found in the same place.

Decouple Transport request 2.jpg

Again, downgrade protection is active and prompting warnings…we ignore the warnings (which is logged), so I can proceed to show the effect.

Decouple Transport request 3.jpg

The transport request is decoupled.

Note that everything is logged in the text log:

text log.jpg

SAP Standard Process:

With SP5 the functionalities are available in the Normal Change (SMMJ), Defect Correction (SMTM) and Urgent Change (SMHF) in status ‘In development’ and ‘Created’. It is possible to make the functionality available in user status ‘To be tested’ (or your own newly created user status) by using the user status dependent UI object control. See thread to get more information. The technical keys of the UI objects are ‘ASSIGN_TRA’ (Assign Transport Request) and DECOUPLE_TRA (Decouple Transport Request).


As I predict, there will be questions to the authority, we are working right now on a concept for authority to control the UI objects. Will not take long and be introduced for SP 5-6 with a note.

Hope that is useful for you, if you have feedback, get in contact,


You must be Logged on to comment or reply to a post.
  • Hi Michael,

         Thanks for sharing the useful information.As far as I understand the automatic management of transport requests is only available in CHaRM.


         Is it possible to have this  transport of the requests based on the actions for the "Incident Management"?

    Thanks and Regards.

    Piyush R. S.

  • Hi Michael,

    are there any other possibility to block transport already in import queue of PROD system (long time running imports which should be planned in another time slot, change which must not be imported before specific date etc.). I see as possibility to decouple transport from one maintenance project/change and couple it again to another urgent/normal change (it means to another maintenance project -> maintenance cycle). But you mentioned that decouple/couple is possible only in status CREATED, IN DEVELOPMENT a can be accessible in TO BE TESTED. What to do with transports already in import buffer to PRODUCTION (-> in status SUCCESSFULLY TESTED)? Can you help?

    Thanks a lot,


      • Hi Michael,

        I had been following your blogs closely and they are really helpful. In your blog, it is mentioned as " It is possible to make the functionality available in user status 'To be tested' (or your own newly created user status) by using the user status dependent UI object control".

        based on my understanding, we can enable it at other statuses, but these options will work only when the transport request is "Not Released and Changeable". Do you see any option, where in i want to decouple a TR which is released and imported to QA and reassign it to another CD. Is this possible.

        Please help.



        • Dear Imran,

          technically it is not possible to decouple and assign a released transport request with CTS or CTS+.

          Technically it is worked on with cCTS for a future release.

          But there is no official use case, normally transports are decoupled with develpments which are skipped. Assigned transports would be external transports for example.

          If you have a normal change with status 'To be tested' only a ToC is in the QA system but not the original transport is released.

          But imagine a bigger project with several transport requests by team A and see there is one dependent transport (out of others) from another project with a normal changes from team B.

          Because of...

          - misunderstanding,

          - a developer touched an  object he should not

          - organizational changes

          and because of the dependency you decide to put that together, then it could be helpful. I could theoretically construct a situation where organizational changes lead to such a situation.

          Sure, normally, dependent changes should be in one change but if you have different development teams and they do not know of the dependencies (or do not speak to each other, etc.), maybe such situations arise.

          At least you have the flexibility...

          Best regards,


  • Can I restrict this functionality (Assign and decouple TR) to the role of developers alone?

    The Change managers can also act as developers. So how can we allow only the developers, and not the change managers, to assign and decouple the TR ?

  • Hi Michael,

    in case I want to assign several TRs to the NC document, is it possible to control the sequence of the transports ? What I saw is that the TRs are sequenced automatically in the Transport Management section in a crescent TR number sequence and then imported in this sequence into the next system. Is there a way to have the sequence not in a crescent TR number sequence and would this be kept when we release the TRs through the change of status of the NC.

    Best regards,


    • Hi Dislich,

      the sequence of transports is defined by the time of their export. This defines the import sequence. The release of transport is done with the list of transports with their number ascending. But as far as we know there is no issue as all transports are released in one step and are as well imported together.

      Hope that helps,

      best regards,