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.
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:
In the Transport Management Assignment Block you find the ‘Assign Transport Request’ function:
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.
But lets stay with assign transport request funtionality…
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…
When we have transports available and depending from the user status the ‘Decouple Trahnsport Request’ functionality can be found in the same place.
Again, downgrade protection is active and prompting warnings…we ignore the warnings (which is logged), so I can proceed to show the effect.
The transport request is decoupled.
Note that everything is logged in the text log:
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 http://scn.sap.com/community/it-management/alm/solution-manager/blog/2012/06/29/ui-control-of-charm-specific-ui-objects 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,