System verification error in Maintenance Planner

Did you ever face the problem of a not matching stack.xml during your important Upgrade project? Then the following article will help you out: This blog describe situation how it can be happening verification erroneous and how to request correction and implementing correction.

Why it is happening

Sometimes the System Data cannot be exactly verified by Maintenance Planner. Usually this happens when the software information is changed manually like installing or updating with SAINT/SPAM in maintenance system. The reason is that manually changed Software components information isn’t stored in tables which contain Product instance and Software Components information: PRDVERS, SWFEATURE and CVERS. Information is collected after Software Component update only with the stack.xml file. It is important to update Software component through the SL-Tool.

How to create CISI file

If a Planner verification error occurs, then you can correct it with the CISI file. Here we describe how to generate CISI file and how we can implement and correct the error.

If a system’s verification status is “ERROR” in Maintenance planner Systems list and a System Detail circle has a verification task in red:

Clicking the “Verify” button shows the correction that can be done:

Or it can be ignored and skipped to configuration. For example, if you delete software component on the system, then You can ignore this step and with SUM (Software Update Management) phase in status “IS_SELECT”, you can select component which can be deleted. However, you need to make sure, that the component can be deleted in the SAP Note: 2011192 — Uninstalling ABAP add-ons.

Then click Confirm.

Go ahead clicking “Next” until you have completed the task. There you can download CISI file and activate changes in the Maintenance Planner.

A CISI file is in the form: MP_CISI_1000570832_2018111_.xml and for implementing the CISI you have to use the SUM tool.

How to implement CISI with SUM

Software component information in contained in tables: PRDVERS, SWFEATURE and CVERS. The more important one is the first of the three tables.

For example, before implementing the CISI file, the table SWFEATURE contains the following entries:

When using SUM, you are working with it exactly in the same way as when upgrading. If SUM is asking to stack file, then you point to the CISI file and it will know what to do:

The CISI implementing phase is quite simple. The SUM will ask system parameters and DDIC password and that’s all. It takes about 20 minutes.

After CISI implementation, the entries are corrected in the table SWFEATURE:

Next you can upload the corrected System data again and head to the Maintenance planner — if you did everything right, the “Verify” status button should now be green:

Used information

https://blogs.sap.com/2017/02/24/sap-solution-manager-special-cases-in-installation-and-upgrade/

https://blogs.sap.com/2018/05/04/verification-in-the-maintenance-planner-part-ii-how-to-examples/

https://help.sap.com/doc/9c9945692df94231b8dc323afe48a58e/latest/en-US/loio6a17e10646f647bc8ace581ebc039b05.pdf

Sap Notes:
2011192 — Uninstalling ABAP add-ons
2523380 — Improvements to Rectify Erroneous Systems in Maintenance Planner