Dear followers

My name is Mateus Pedroso from MOPZ/LMDB/Solman Configuration team and I’ll start to write some posts about these topics. I would like to start writing about MOPZ framework 3.0.

MOPZ Framework 3.0 is the standard for Solution Manager 7.1 SP12, but you can apply note 1940845 to enable MOPZ 3.0 in Solution Manager 7.1 SP05-SP11. Note 1940845 must be always implemented in the latest version and this note fix some bugs in mopz 3.0, so it’s very important to ensure that the latest version of note 1940845 is implemented even in Solman 7.1 SP12. The following points changed in MOPZ 3.0.

– UI and performance.

– Integration of the Maintenance Optimizer with the Landscape Planner.

– Add-on installation procedure.

You can check more details about MOPZ 3.0 in the pdf attached in note 1940845.

One of the most important improvements is the Add-on installation. Here’s a screenshot showing that now you can apply add-ons in step 2.

/wp-content/uploads/2014/11/mopzaddon_596741.png

Now it’s easier to apply add-ons.

/wp-content/uploads/2014/11/mopzaddon1_596742.png

In the next posts, I’ll explain some LMDB/SLD topics related with MOPZ and how to fix some well known issues.

To report this post you need to login first.

9 Comments

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

  1. Vladimir Kogan

    Hi

    Nice blog, but from my experience with new MOPZ 3 I think there are 2 issues to improve.

    1) The add-ons that we have to make decision for them are in green background. Once I decided , I think the checkbox should remain. In case of large numbers of installed add-ons it’s hard to distinguish which of them are selected and which not.

    SNAG-0586.png

    I have selected one but it is still not marked as selected.

    SNAG-0587.png

    2) I can select for the same add-on several times and it will appear several times in selected add-ons list.

    SNAG-0588.png

    3) It take a lot of time for every add-on selection,. In previous version of MOPZ all add-ons were already preselected….

    I have SP12 with latest versions of this note implemented.

    Regards

    Vladimir Kogan

    (0) 
    1. Mateus Pedroso Post author

      Hi Vladimir

      This is the info provided by Dev. Support team.

      Development is planning to enhance the text displayed in add-on selection screen to make it more transparent.


      Some points must be checked

      • User doesn’t have to select anything in add-on selection screen if he/she doesn’t want to install something new. The installed add-ons are automatically brought to the lowest compatible version during the main calculation.
      • The selected add-on remains in the list unchecked because user still has the possibility to select additional instances or higher stacks of this add-on.
      • User can select one add-on multiple times if he/she likes to select the instances one by one. There even could be cases where he/she has to do it in that way because of add-on dependencies.
      • The selected add-on instances and stack are verified on SAP backend and instantly the add-on list is refreshed, that’s why it takes more time than MOpz 2.0.
      (0) 
      1. Achmad Dimyati

        Hi Mateus,

        I am in SOLMAN 7.1 SP12 and has implemented note 1940845 MOpz: enhancement to support new backend services and 2042460 Saving MOpz transaction works improperly.

        So the MOPZ 3.0 is the default.

        Just want to confirm regarding upgrade from EHP6 to EHP7.

        As you have mentioned above, no need to choose any add-on as the backend will calculate automatically for the current ones. Are those will be marked with green color in Add-Ons selection?

        The reason I ask because EHP upgrade from 6 to 7 will replace HR Renewal 1.0. Should I choose HR Renewal 2.0 in the Add-ons selection or if already green, it will be included automatically?

        Also do you have any advise regarding how-to choose Friori related components in Add-ons selection. I am quite lost here.

        Thanks a lot,

        Best Regards,

        Achmad

        (0) 
        1. Mateus Pedroso Post author

          Hello Achmad

          As you have mentioned above, no need to choose any add-on as the backend will calculate automatically for the current ones. Are those will be marked with green color in Add-Ons selection?

          => Correct

          The reason I ask because EHP upgrade from 6 to 7 will replace HR Renewal 1.0. Should I choose HR Renewal 2.0 in the Add-ons selection or if already green, it will be included automatically?

          => Usually mopz will show all possible options. HR Renewal 1.0 can be installed just in EHP6, for this reason mopz will automatically mark option HR Renewal 2.0 that is compatible with EHP7.

          Also do you have any advise regarding how-to choose Friori related components in Add-ons selection.

          => Fiori has lots of versions and applications,

          1) Define what fiori applications you’ll need. There are lots of Fiori apps.

          2) Check if you have a license for them with the contract department or your enterprise advisor.

          3) Check technical prerequisite, usually Fiori applications are compatible with EHP7/Netweaver 7.4, probably this point will not generate problems to apply the add-on.

          (0) 
  2. Achmad Dimyati

    Hi Mateus,

    Thanks a lot for you reply. I have another error now when using MOPZ. It’s working properly before but now it gives this error: An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause

    I have looked SAP Note, and the only similar is  2085394  – MOPZ transaction CX_SY_REF_IS_INITIAL exception             but we don’t have HANA database.

    Do you have any idea why this happening? I have submitted OSS message to SAP.

    Thanks a lot,

    Best Regards,

    Achmad

    (0) 
    1. Mateus Pedroso Post author

      Hello Achmad

      Could you create an incident with SAP and ask to put the incident in my name ? I’ll check this issue for you checking the issue directly in system. Maybe it’s a case to improve the KBA to cover another reason for this message error.    

      (0) 
      1. Achmad Dimyati

        Hi Mateus,

        The problem isn’t happening anymore after I run again solman_setup and managed system configuration. I am not sure which step has fixed that.

        Regarding MOPZ 3. 0, I am currently struggling with Add-On selection for Friori. The issue isn’t choosing which items but the effort to choose the friori add-on itself. It’s really slow and cumbersome. Every click, I need to wait for the proses in the SAP backend. And there are a lot add-on available.

        Perhaps the developer team of MOPZ 3.0 can do something to improve the choosing processes for Add-on especially for Friori.

        Thanks a lot,

        Best Regards,

        Achmad

        (0) 
  3. Joshua Lacroix

    I’m SOLMAN 7.1 SP10 and running MOPZ to grab the latest SP’s for PI and I get hit with this screen that stops be dead in my tracks. Now I must implement this note and latest version. Why would SAP do that!? I should still be able to continue to get my patches!

    #frustrated

    (0) 

Leave a Reply