Skip to Content

When you work with ChaRM in Solution Manager 7.1, the first thing you do if you follow the Configuration Guide is copy the standard transaction types to Z transaction types. You copy the standard Request for Change (SMCR) and the standard Change Documents such as Urgent Change (SMHF), Normal Change (SMMJ), Admin Change (SMAD) and General Change (SMCG). After the copy, when you go to the Web Client and try to create a new Change Request Management document, you see a pop-up to select the standard or the new custom Transaction type that you just created (Figure 1 shows the example of Request for Change pop-up). It may be a problem to keep both options available for the user, as he can select the wrong one, even if you explain, train, write procedures showing the correct transaction types to be used. In order to avoid such errors and confusion, you need to configure the Web Client to show only the customer transaction types. I will show you how to do it. It is very easy.

popup rfc.jpg

Fig 1: Pop-up to select the Request for Change transaction type.

I assume you created your own Business Role as a copy of standard SOLMANPRO. I recommend you to always create your own copies to avoid losing the reference and having your configuration replaced by the standard during an upgrade to a new Support Package. So I guess you have at least one new Business Role. You can have as many as necessary depending of the different activities for different group of users, or user roles. For that Business Role I suppose you created also a new Navigation Bar Profile, so that you can configure the navigation bar the way you want. In this article I show the changes I’ve done in a copy of the navigation bar profile named ZSOLMANPRO, assigned to a copy of the standard Business Role named ZSOLMANPRO.

I will configure the Create menu (Figure 2) of my navigation bar profile to directly call the Z Request for Change, without showing the pop-up for selection of transaction type. This menu is a Direct Link Group. As this Business Role will only be used for ChaRM, not for Incident Management, I have changed it to show only the Create Direct Links that I need.

menu create.jpg

Figure 2: Example of a Create Menu (Direct Link Group assigned to Navigation Bar Profile)

So, to configure the Direct Link Group you go to IMG Customer Relationship Management in transaction SPRO. Open the IMG menu UI Framework. Open Technical Role definition->Define Navigation Bar Profile. (See Figure 3)

menu uiframework.jpg

Figure 3: IMG menu for UI definitions

To display the current configuration of the Create menu assigned to the navigation bar profile, click on Define Navigation Bar Profile and select the navigation bar profile you are working with. I will select ZSOLMANPRO.

Then click on Assign Direct Link Groups to Navigation Bar Profile to see the Direct Links currently in use. The Direct Link Group related to the Create menu is SM-CREATE. (Figure 4)

assign direct link.jpg

Figure 4: Direct Link Groups assigned to Navigation Bar Profile

In the same screen, go to Define Link Groups to see the details of Direct Link Group SM-CREATE. (Figure 5)

Select the Group ID SM-CREATE and click on Assign Links to Direct Link Group. You will see the list of logical links related to the Create menu. The one corresponding to Request for Change is SM-CR-DC. (Figure 6)

direct link 1.jpg

Figure 5: Define Direct Link Groups

assign link to direct link group.jpg

Figure 6: Assign Logical Link to Direct Link Group

Now go to Define Logical Links (the first option in the Dialog Structure) and search for SM-CR-DC.  In the details, enter in Field “Parameter” the transaction type of your Request for Change, ZMCR in my example. In Field “Paramater Class” keep the value CL_CRM_UIU_BT_PARAM_CREATE (Figure 7). Save.

/wp-content/uploads/2012/07/logicallink_sm_cr_123698.jpg

Figure 7: Define Logical Links

After that, the Direct Link for Request for Change of the Create menu will open a new document directly, without asking you to select the transaction type in a pop-up.

To report this post you need to login first.

17 Comments

You must be Logged on to comment or reply to a post.

  1. Hailton Almeida

    I’ve met you some years ago here in São Paulo at Asug. It was a lecture presented by Renan Guedes regarding Implementation tools, remember that?

    I have always seen your contributions on SDN and I find it very interesting how accurate you are.

    Congrats!

    (0) 
    1. Raquel Pereira da Cunha Post author

      Hi Hailton,

      yes, I remember you and our chat that day 🙂

      Thank you for your kind comment.

      By the way, we have ASUG Conference next Aug 14th, I will be there.

      Cheers,

      Raquel

      (0) 
  2. Ryan Lee

    Hi Raquel,

    If my organization has 2 Z transaction types for Normal Corrections due to business reasons, can this configuration support that?

    Ryan

    (0) 
  3. Julius Zbuska

    Hi Raquel,

    Is it possible to enable only one transaction for selection via dno_cust04 and CHANGE_REQUEST_NEW? I entered ZMCR, however I still get SMCR and ZMCR when creating new RfC. Thx

    Regards,

    Julius

    (0) 
      1. Julius Zbuska

        In Web UI, exactly as your first picture in the blog. I expected that SMCR gets removed from this pop up once I put ZMCR in dno_cust04 for CHANGE_REQUEST_NEW. Or did I get it wrong?

        (0) 
  4. Khalil SERRHINI

    Hi

    very nice blog. You could have same result also by declaring standard Transaction Type as ‘inactive’ in SPRO in ‘Definition of Transaction Types’

    Thanks for contribution

    Khalil

    (0) 
  5. Prasanth O

    Is it possible to customize this pop-up? We have multiple transaction types and want to make this pop-up available to our functional team. Currently the description in the pop-up box is not the correct one.

    (0) 
      1. TM Mohamed

        hi Raquel ,

        i face an issue in ChaRM configuration, maybe due to missing step, in crm_ui  RFC is ZMCR but the following documents such as SMMJ , SMHF are created in standard not Zxxx , is it missing copy routine or defining the Z types ?

        thanks

        TM

        (0) 
  6. Ben Mullaly

    Thanks Raquel

      Your method worked well with the SMCR with its own logical link of SM-CR-DC.  I was able to put in ZMCR as a parameter and the pop-up in the web UI was gone and defaulted correctly to ZMCR.

    The question I have is with other Change Documents (SMMJ, SMAD, SMHF, SMCG) and if this technique would work since it appears they all fall under one logical link SM-CD-DC.  If there is only one logical link then you can only have it default to one doc type in the parameter which would not work in this case.

    There was another approach documented in this thread by Khalil Serrhini that noted you could get the same effect if you made the doc type inactive in the Definition of Transaction Types.  Here you can go into each S* doc type that you have Z* doc type counterpart and make the S* doc type inactive.  That appears to work as well.  Is there any other hidden dangers in making the S* doc types inactive here as long as you have a Z* namespace for the document already saved?

    Thanks,

    Ben Mullaly

    (0) 
  7. Tze-Hup Tan

    Hi Raquel,

    Thanks for the details step by step configuration. Do you have any idea on how to configure SAP GUI (SOLMAN_WORKCENTER) so that it can redirect us to ZMCR only?

    I encounter the same screen (fig 1) when I click on New Request for Change in the solman work center.

    SAP_WorkCenter.PNG

    Thanks

    Best Regards

    Remy

    (0) 
  8. Winston San Martin

    Hi everyone!

    I having the same problem, however, it has happend from de solman_workcenter when I try to create a request from Job Schedule Escenario.

    May some one help me to solve the issue, please?

    Wins

    (0) 
  9. Viswanathan Subramanian

    Dear Raquel,

     

    I tried this approach on Solution Manager 7.2 after the upgrade from 7.1 and its not working.

    Request you to share if there is any different procedure that needs to be followed in case of solution manager 7.2

    Best Regards,

    Viswanathan Subramanian

     

     

     

    (0) 

Leave a Reply