Maintenance Optimizer Sunset in SAP Solution Manager 7.1
In SAP Solution Manager 7.1, Maintenance Optimizer has retired since January 9, 2017.
SAP Solution Manager’s cloud-based Maintenance Planner is the successor of Maintenance Optimizer. Maintenance Planner enables:
• Easy and efficient planning of all changes in your SAP system landscape
• Offers integrated processes for SAP Fiori apps and SAP S/4HANA
• All critical aspects of landscape maintenance in one tool.
Maintenance Planner has been available for our customers since Q2 2015, with sunset of Maintenance Optimizer, Maintenance Planner becomes default tool for planning all changes in your SAP system landscape. For further information refer Maintenance Planner blog , FAQ and SAP TechEd session replay.
SEA (Scope and Effort Analyzer) will continue to be supported in SAP Solution Manager 7.1 & 7.2.
SEA in SAP Solution Manager 7.1
SEA functionality in SAP Solution Manager 7.1 remains unchanged.
Trigger SEA via work center
Create analysis in SEA
Guided procedure to create analysis continued to be supported, product systems are still needed for SEA.
Maintenance Optimizer will continued to be supported in context of SEA.
Trigger MOPz from SEA
For further information about SEA, please refer SEA How-to-Guide, SEA Wiki , SEA Overview .
To know more about landscape entities in SAP Solution Manager 7.1 & 7.2 , please refer Product-systems and Maintenance Planner , Landscape entities and Maintenance-Planner , Planning Landscape Changes – a Best Practice Guide .
Hello Priti,
did you already try to run a SEA analysis after the MOPZ sunset?
If I do this in my Solution Manager I get a short dump described in note:
"2413262 - Runtime Error OBJECTS_OBJREF_NOT_ASSIGNED_NO in MOPZ transaction".
Regards
Hi Renato,
Thanks for reporting this, we are looking into it.
Best Regards,
Priti
Hi Renato,
Issue has been resolved.
Best Regards,
Priti
Hi Priti
I tried to work with SEA on Solman 7.1 this morning, and with MOPZ sunset impossible to run the analysis.
I encountered the same error discussed in oss note
“2413262 – Runtime Error OBJECTS_OBJREF_NOT_ASSIGNED_NO in MOPZ transaction”.
I opened a SAP incident
Thanks for reporting this, we are looking into it.
Best Regards,
Priti
Issue has been resolved.
Best Regards,
Priti
Hi Priti,
Could you mention for the benefit of other readers what these issue resolutions are? I presume you're resolving them in Customer Incidents, but others may be getting the same dumps, and if it's as simple as "Apply Note xxxxxxx," then we could all save a lot of time by mentioning that here.
Cheers,
Matt
Hello Matt,
Thanks for asking this question, issue is fixed on SAP side of the process, no action is required on customer side.
Best Regards,
Priti
Hi Priti
Bumping into this issue again this morning at customer side. No options on second step in MOPZ.
“2413262 – Runtime Error OBJECTS_OBJREF_NOT_ASSIGNED_NO in MOPZ transaction”.
Can you please look into this on SAP side?
Best regards
Tom
Hi Tom,
Issue is resolved, could you please check at your end.
Best Regards,
Priti