sap maintenance planner что это
SAP PM — Планирование технического обслуживания
Планирование технического обслуживания в SAP PM используется, чтобы избежать поломок оборудования или производственных сбоев. Он используется для представления осмотра, профилактического обслуживания и ремонта, для которого вы заранее планируете время и объем работ. Выполняя эффективное планирование технического обслуживания, вы можете устранить поломки, которые могут привести к опасности для окружающей среды.
Компонент планирования технического обслуживания интегрирован с различными компонентами других модулей и подкомпонентов в Техническом обслуживании завода —
Существуют различные компоненты планирования технического обслуживания, которые интегрируются с другими модулями, такими как планирование качества и управление материалами.
Планирование технического обслуживания используется для описания даты и действий по проверке технических объектов. Это гарантирует, что технические объекты работают с разбивкой и, следовательно, улучшают оптимизацию всех объектов.
Планы обслуживания
План технического обслуживания определяет расписание и список задач, которые должны быть выполнены в рамках Плана технического обслуживания. План обслуживания может быть создан в соответствии с работой организации, например, различные объекты могут обслуживаться в разные даты, а область действия может отличаться в зависимости от типа объекта.
Следующие процедуры могут быть использованы для создания плана профилактического обслуживания —
План одного цикла
План обслуживания на один цикл используется для точного определения одного цикла обслуживания на основе времени или производительности, в котором вы указываете интервал, с которым должен выполняться план обслуживания. Это один из самых простых планов обслуживания, используемых для планирования обслуживания.
пример
Ежегодное обслуживание автомобиля или обслуживание принтера после 1 миллиона копий.
Шаг 1 — Чтобы создать план с одним циклом, перейдите к разделу Логистика → Техническое обслуживание завода → Профилактическое обслуживание → Планирование технического обслуживания → Планы обслуживания → Создать → Единый план цикла или T-код — IP41
Шаг 2 — В следующем окне введите имя плана и категорию плана обслуживания и нажмите «Продолжить».
Шаг 3 — Введите необходимые данные.
Когда вы вводите единицу производительности для цикла, система автоматически выбирает первый счетчик, подходящий для контрольного объекта, в качестве значения по умолчанию.
Вы также можете сохранить параметры планирования, если это необходимо.
Вы можете поддерживать параметры планирования только для плана обслуживания, если вы ввели единицу в раздел Интервал цикла. От устройства система может распознать, является ли план с одним циклом основанным на производительности или основанным на времени, и предоставляет соответствующие параметры планирования.
SAP Maintenance Planner
by sapposts · Published January 14, 2017 · Updated January 28, 2017
SAP Maintenance Planner
What is the SAP Maintenance planner?
SAP Maintenance Planner is the successor version of the SAP maintenance optimizer, it is introduced on July 2015. SAP Maintenance Planner replaces the SAP maintenance optimizer. Since January 9 th 2017 onwards all the customers are advised to use only SAP Maintenance Planner. Now SAP Maintenance Planner is the central tool for new installations and upgrades.
Currently Maintenance Planner is not integrated into SAP One Support Launchpad. To access the Maintenance planner please go to https://apps.support.sap.com/sap/support/mp
SAP Maintenance Planner
SAP Maintenance Planner
Differences and Similarities between SAP Maintenance Planner and Maintenance Optimizer
As mentioned earlier SAP Maintenance Planner is the successor version of the SAP maintenance optimizer to handle the critical tasks like planning the upgrades, new installations, support packages or product dependency checks, and generating stack configuration files etc…
SAP Maintenance Planner also generates stack XML files like maintenance optimizer that can be consumed by SUM tool and SWMP for upgrades and new installations.
Now SAP Maintenance Planner is mandatory to upgrade the systems to SAP EHP 8 for SAP ERP 6.0 based on netweaver release 7.50 or higher.
What has been changed?
SAP Maintenance Planner is embedded in SAP support portal with launchpad interface, we can access the tool from browser via link https://apps.support.sap.com/sap/support/mp
How SAP Maintenance Planner works?
SAP Maintenance Planner use the SLD data which is transferred to SAP support portal via LMDB, this data can be called as customer profile. Maintenance Planner uses this customer profile for all its maintenance related and planning activities.
What actions we really need to switch to Maintenance planner?
Here first you need to know how SAP handles the data for customer landscapes. This is can be classified in three layers.
System Landscape Directory (SLD): SLD server as central information repository for all the technical and business systems. It also gathers the information about SAP clients, application components, and hardware components. Every SAP system must be added to the SLD, this is the first place where landscape data management starts. SLD push the data to SAP PI (Process integration) and SAP Solution Manager. SLD always contains the up-to-date information about the installed systems.
Landscape Management Database (LMDB): Solution manager LMDB is responsible for managing the system landscape information. LMDB receives as much as possible information from SLD automatically and whenever there is a new update or change in the SLD. LMDB collects the data from SLD and its agents and update the customer profile in SAP Portal. Thus LMDS acts as source for entire landscape.
Customer Profile: This data is available at SAP Portal and used by SAP Maintenance Planner for maintenance and planning activities.
Why all the systems are not accessible in SAP Maintenance Planner?
Sometimes we may see as few systems are missing or all the systems are not available in SAP Maintenance Planner, to trouble shoot such cases please perform the below checks.
You can use the reports to push the data RPT_CLEAR_SL_CACHE and AI_LMDB_MIG_OSS_SYNC_CONFIG.
For more information please refer to SAP Maintenance Planner user guide
Maintenance Planner – Frequently Asked Questions
This collection of frequently asked questions provides brief answers to common questions about Maintenance Planner. If you don’t find answer to your questions, please add them as comments.
Accessing Maintenance Planner
How do I access Maintenance Planner?
The Maintenance Planner is a hosted application on SAP Support Portal and can be accessed with an up-to-date browser. To access the tool:
• Login with your SAP credentials (S – user) to get access to landscape data for this user
What are the authorizations required for accessing Maintenance Planner?
You need an S-user for the SAP Service Marketplace (SMP). There is no separation of specific roles in the Maintenance Planner. For more information, refer SAP Note http://service.sap.com/sap/support/notes/1822202
Prerequisites for using Maintenance Planner
What data does Maintenance Planner need?
Why don’t I see my systems in Maintenance Planner?
Perform following steps/checks:
I see outdated data in Maintenance Planner.
Perform following steps:
Maintenance Planner and Related Tools
Which versions of SAP Solution Manager are supported?
Please note that SAP Solution Manager 7.0 / 7.01 status is “In customer-specific maintenance”.
Is SAP Solution Manager LMDB still needed?
Maintenance Planner consumes landscape data available on SAP Support Portal for all maintenance planning activities. “Technical System Editor” of the LMDB is required where system data is automatically registered and supplied to the customer profile in SAP Support Portal.
Landscape Data
Security policies in my organization prevent me from creating RFC connections to OSS. What should I do in this case?
In such a case the technical system information for ABAP systems will be uploaded by generating a system_info.xml file from Support Package Manager (SPAM).Prerequisite: This is supported on SPAM version 59 or latest. Please check and upgrade SPAM version to 59 before you proceed.Perform the following steps:
What should I do if the same system appears multiple times in Maintenance Planner?
First of all, check if the error is caused earlier in the process (in SLD or LMDB):
If the problem is not solved by that, Maintenance Planner offers the functionality to delete irrelevant data. Check the replication date, and based on this, you can decide to delete systems manually.Note that the deletion of the system in LMDB does not suffice, you also have to delete it in MP separately.
What are the most important considerations in case there are multiple productive SAP Solution Manager systems in the landscape?
If you have more than one SAP Solution Manager System, you can choose from which landscape data is to be replicated on Maintenance Planner. In the system maintenance cycle, the Sync button is green if there exists only one SAP Solution Manager and the same is chosen by default. If the Sync button is yellow, it indicates that multiple Solution Managers are available. Perform the steps described in the user guide to select SAP Solution Manager, from which landscape data is to be replicated on Maintenance Planner.
Does Maintenance Planner support value-added resellers?
Yes, Maintenance Planner handles all data available in the LMDB and uploaded to the Customer Profile – please refer to the following blog to learn how to handle landscape data of multiple customers: How-To Handle Landscape Data as a Value-Added Reseller Using LMDB
How can I upload landscape data manually?
To manually upload the landscape data from Solution Manager to the customer profile, you can go to LMDB and click the Upload to SAP Support Portal button. Once this is done, system data will be immediately available on Maintenance Planner.
Do I need to create product systems in LMDB?
Creation of product systems is no longer required for planning maintenance in Maintenance Planner as Maintenance Planner lets you plan maintenance on technical systems. You can create dependencies – between your SAP Business Suite backend systems and Portal front-end systems for example – directly in Maintenance Planner.
Note: However, if you are using SAP Solution Manger 7.1 Scope and Effort Analyzer to estimate the test effort caused by a change or Change Request Management, product systems are still needed. For details, see Product Systems and Maintenance Planner in SAP Solution Manager 7.1
Correcting Landscape Data
How can I proceed with planning if a system is marked erroneous in Maintenance Planner?
An erroneous system is indicated in red in the maintenance cycle. If system is marked erroneous you first have to verify and provide the information required to correct the installed software information/details. Once the Verify button in the maintenance cycle turns green, you can proceed with the planning activities. At the end of the planning, Maintenance planner generates a consolidated stack configuration file which can be used by Software Update Manager to correct the system description and to implement the landscape change.
What is the importance of the CISI xml file?
Once you have verified an erroneous system, a corrective xml is generated. This corrective xml can be used by Software Update Manager (SUM) to correct the information on the system.
Dependency Management
What kind of dependencies are currently handled in Maintenance Planner?
Example: A system track can follow one of the following patterns of logic:
How do I handle dependencies between connected systems where business processes are running across the various systems?
For such dependencies, you can use the Upgrade Dependency Analyzer (UDA) to check the existence of upgrade dependencies between two separately installed SAP systems in your system landscape.
You can access UDA with link http://service.sap.com/uda
What happens to the product systems already available in LMDB?
All existing Product Systems and Technical Systems declared in LMDB are synchronized to Maintenance Planner.
Miscellaneous
I see the planning cycle/screen even after I have just defined my changes and confirmed it. Why?
This is because you can plan multiple changes on Maintenance Planner in a single transaction. This feature is called Iterative Planning.During Iterative planning:
The Stack XML file generated at the end of the planning process contains the metadata of all the planned changes.
Does Maintenance Planner support planning of new system installation?
The Maintenance Planner supports planning of new installations of ABAP & JAVA systems on a chosen stack level. The Maintenance Planner significantly simplifies the process by eliminating the steps of system registration between installations and update the required SPS level and a separate system update planning during installation. To learn more, see Up-To-Date Installation.
The new process supports following product versions for Java systems:
Does Maintenance Planner support planning of new installation of dual stack systems?
The Maintenance Planner does not support planning of new installations of dual stack systems.
Does Maintenance Planner support planning of SAP BW4/HANA System systems?
Maintenance Planner now supports planning of SAP BW/4HANA systems. Maintenance Planner allows you to plan installation of a new SAP BW/4HANA system or a conversion of an existing SAP NetWeaver system to SAP BW/4HANA system.
For converting an existing system to SAP BW/4HANA system following product instances must be present:
Which product instances are required for installation of SAP NetWeaver Process Orchestration system?
In case of a Process Orchestration system choose the following product instances, other required instances will be calculated automatically:
How can I install SAP Fiori Apps with Maintenance Planner?
There are two ways to do this:
Note: This is the recommended process
Switch framework components are not pre-selected in Maintenance Planner. Why?
Check if SAP Note 2186164 is implemented in your SAP Solution Manager system.
How can I add HR Packages in Maintenance Planner?
You can find the option to add HR packages on the screen to Select Stack Dependent and Independent files.
This functionality will be available, f or ABAP systems :
1) On which one or more of the following software components are installed: EA-HR, SAP-HR, HR-CCE.
2) RFC connection is established between the SAP Solution Manager system and the technical system.
How can I request side-effects report?
Maintenance Planner supports generation of side-effects report, using this feature side-effects report can be generated in Maintenance Planner directly.
Alternatively you can request side-effects report with link : http://service.sap.com/side-effects
While planning upgrade to EHP8 FOR SAP ERP 6.0, upgrade export DVD is missing from the download basket?
For planning upgrades to SAP Business Suite 2016 releases e.g. EHP8 FOR SAP ERP 6.0, EHP4 FOR SAP CRM 7.0, upgrade export DVD needs to be downloaded from Service Market Place, Delta files and OS/DB files will get calculated in Maintenance Planner, however the upgrade export DVD needs to be downloaded from Service Market Place.
Which Add-ons are supported by Maintenance Planner?
Maintenance Planner does not support installation or maintenance of Add-ons, if SAP NetWeaver version is below SAP NetWeaver 7.0 EhP2, in the current state of the system. Please refer the SAP Note 1770071 for further details.
Support Related
How do I report problems with Maintenance Planner?
Create an incident on the component BC-UPG-MP.
Assigned Tags
Where exactly is the CISI XML file applied? Since the data reflects what is in the LMDB, i s the corrective xml applied to the solution manager system or to the verified system?
CISI XML is applied to the verified system.
Could you please explain a bit more in detail what to do with the MP_CISI_*.xml file?
Hello, maintenance planner for some reason does not accept passwords containing «!»
Thanks for writing this blog, and making it easy for many.
I have one question, on Maintenance Planner, what is the difference between ‘Saving’ and ‘Activating’ the system details on Verify section.
Activating lets you persists the verification, if you only save, the changes will be applicable only for that transaction.
I have doubt regarding dependency analysis for NW 750 system.
As mentioned in above blog that you can get this information from UDA but unfortunately UDA does not shows any information for NW 750 system. Is there any simplest way to check the dependency between system for NW 750 system.
I have the same doubt. Could anyone help us?
Hello Prem, Hello Monica,
I reached out to UDA experts to help clarify your query, the dependencies for latest releases are depicted in Note 1388258. Unfortunately data for UDA is not yet available.
Hello, i just upgraded EHP8 with NW 7.5 on sandbox, for our assessment, i have to send the side effects for review to our functional team.
Looking at 2309475, gives me a not so good feeling, is there a better way to get the side affects for the Maintenance Transactions. MOPZ was so easy to get all the side effects of SPS or a EHP.
This feature is under development.
Best Regards,
Priti
Looking forward to it, thanks for your feedback!
I think you can update the FAQ above as there’s an update to note 2309475 [1]. MP is now capable of generating the side effect report.
Note to myself:
#2309475 was updated again; functionality still isn’t available.
Option to generate Side effects reports is available in MP.
Thanks for feedback, I’ve already seen the updated note #2309475
It takes time at every step, try to improve the performance of MP as well.
Best Regards,
Priti
Yes I now get this exact message when using google chrome but not IE.
I need the side effects notes for my Maintenance Transaction MP_ _20160830_115151, Can you suggest a better way to get this than the note 2309475
Integration of side effects functionality is under development.
Best Regards,
Priti
We are planning an upgrade of our Solution Manager system and I created a track for our SBX, DEV, and PROD systems. When I use the Plan feature for the track I get the dreaded
«ABAP Queue Check FAILED with SY-SUBRC ‘2’. » error, and can’t resolve it using the various notes I found. I can successfully create stacks for the systems individually, so in that sense we’ve moved on, but the track system seems really useful as presented in ITM213. I hope that can be resolved for our next upgrade.
Best Regards,
Mike Dumas
Thanks for reaching out, we need to take a deeper look at the issue. Could you please raise an incident – component is: BC-UPG-MP. Please provide transaction id and steps to replicate the issue.
Best Regards,
Priti
Now at the end of the year the new SAP-HR packages come available. These have to be maintained in the HR systems of our customers. In MOPZ I was able to select the HR packages manually. In MP I can’t find the option to maintain these HR packages.
In your notes above you describe the option to add the HR packages in another change plan, but that is not what I want to plan. I only want to maintain the current HR packages nothing else.
Hope you can help to solve this issue.
If your requirements is to only apply the HR package you need to select the current SP level in «Define Change» step and proceed to add HR packages.
Best Regards,
Priti
We have got multiple solution managers and lots of system in our landscape. The option suggested above when you have “multiple Solution Managers” seems to suggest that one will need to do it for each and every system in the landscape. I wonder if there’s a setting at the global level to ensure MP is updated only from one solution manager.
At the moment I am considering to disable LANDSCAPE_FETCH job on all other solution managers except for one. Please let me know your thoughts. Thanks.
No response to this question for few months now. I think I should stop asking difficult questions :-p
Is there also a possibility to use the MP for an upgrade from a SAP ERP 6.0 with MSSQL to SAP ERP 8.0 with HANA?
So NOT S4/HANA or BW/HANA, but only to the HANA database.
You can plan for upgrade to SAP ERP 6.0 EHPxx supported on HANA, in Maintenance Planner.
For migration to SAP HANA you would have to use DMO option in SUM.
But i get the error «Error in SAP backend» «No relevant Maintenance Planner transactions found».
I contacted experts on this topic. It looks like you are using SEA and not BPCA. There is no connection between BPCA and maintenance planner in SAP Solution Manager 7.2.
Here are couple of checks:
1) If you are using value help in SEA to get all the maintenance plans for a system. Please make sure that the system name in the maintenance plan and the one entered in SEA are the same.
2) The maintenance plan must also be created for the same customer number as the S-User that is used in the connection from SAP Solution manager to the SAP backbone.
If this does not resolve the issue, please open a ticket on SV-SMG-IMP-SEA.
All of my systems are not displaying in the Maintenance Planner. All data is in-sync between the ERP system, SMSY, LMDB and the SAP Portal. How can I manually get my systems to appear in the MP? I do not have the button in LMDB Upload to SAP Support Portal.
Please check if SAP Note 2002546 is applied in your SAP Solution Manager.
This Note is needed to enable the button in the LMDB.
There is no specific option for Process orchestration system, you need to select Product Instances Manually as described in the link:
and (in SWPM phase-2 (define parameters)
Window will appear again once you click on the image depicting type of system, next to the SID input field.
Can you please raise a ticket.
I would like to use the stack.xml copy functionality which could be accessed via RPT_MOPZ_COPY_STACK_XML report in SolMan 7.1.
Is there a similar tool in Maintenance planner or SolMan 7.2?
This feature is available in Maintenance Planner. Please refer release highlights for more details.
Google chrome now always fails when using landscape planner. I get a message cannot get access to the backend system and times out. Used to work two weeks ago. Then when I go to IE this works but I have no idea where download files goes. I check from browser view downloads and nothing. I search my pc and again nothing. I then go back into google chrome find the transaction and do the download to my pc.
How do I add new business packages while generating stack file using maintenance planner?
We are facing One Issue in maintenance planner. we are trying to generate stack.xml for Solution manager 7.1 for upgrade but our solution manager SP level is not showing correct information. We are on solman 7.1 SP14 but it is showing SP06. please let us know how we can resolve this issue.
OUR current version : solman7.1 SP14.
we have also re-sysnc SLD to LMDB & LMDB to SAP portal but information still not updating in maintenance planner
Even we are facing the same issue in Maintenance planner. We are on Solman 7.1 SP11 but its showing SP10.
Kindly let me know how your issue got resolved?
This is vishnu and I have just installed a fresh version of solman 7.2 sp02 the base version and was having plans to upgrade to sps04. I have installed both the abap and java stacks separately on the same host with different SID’s on oracle 11.2.0.3
I have entered the maintenance planner after pumping the system information from my existing SLD into the maintenance planner and then went on to the creation of the stack file for sps04, but to my surprise there is no option for update support package and instead I get only the option «Install or maintain an addon» and on selecting it there is no option to select the sps04.
Kindly advise on the above. Not only this I tried to plan a new system installation of solution manager 7.2 sps04 through the maintenance planner and on selecting the abap system installation as per your blog, I do not see any option such as SAP solution manager 7.2 and instead I see only two options namely «Install an SAP Netweaver System» and «Install an SAP NW AS ABAP INNOVATION PACKAGE system» and once again there is no such option as solution manager 7.2.
If you could put light on the above two scenarios then I can proceed with the update from sps02 or go on with a fresh installation.
we are planning to upgrade a ERP 6.0 EHP 7 (including add-ons like IDEX,…) to EHP 8 using the Maintenance Planner. We start by chosing Maintain/Install Add-on and proceed clicking the EHP 8 option.
The following screen shows needed components to upgrade to EHP 8 but add-ons seem to remain untouched.
What does this mean? Are these add-ons compatible with EHP 8 or else how can we make sure that they will be upgraded to a supported level? Actually I assumed, MP will do the job for us 