33. How to deal with Maintenance Planner Synchronization issues post uninstallation of software component?

There can be various real time scenarios which might ended up in Maintenance Planner Synchronization issues. Here, we can have a quick recap with one of the scenarios which we will have a higher possibility of occurrence.

Usually, we will performing Add on Installations or Uninstallations in SAP System. Most of the Production Projects will be using Solution Manager/Frun for sending system information to SAP Support Portal which then shows correctly in Maintenance Planner with updated information.

Consider an scenario that I have uninstalled ARIBA Add on component from SAP System via SAINT instead of using SAINT with XML/SUM.

Software component was uninstalled. However, Product Component ARIBA Cloud INT information will still exist as it is until we run SUM CISI and remove the same. It's an default behavior that XML is required to remove from the Installed Product component list. Also, Same information will be sent to Solman/Frun LMDB. LMDB might have add on entry as it is OR have Product Add on as it is. These information will be sent to Support Portal/Maintenance Planner.

In the end, Maintenance Planner will have wrong information - Either Verification would be RED due to these Incorrect System Details. Sometimes, It's just exist in Green as well. We need to cautious before generating stack XML and ensure whether all information exists correctly or not.

Note:

Even if you try manual verification and select "Ignore from planning" for that Product Add on, It picks and set deleted component/add on entry once again after few mins since Solman/Frun LMDB sends false/incorrect information to Maintenance Planner. 

In simple words, Add on Software Component and it's Product Component Information should not exist in LMDB.

Note 2449349 - MP: System is missing or system data is outdated/incorrect on Maintenance Planner (MP) vers7

Quick Resolution:

1) If Uninstalled component of Product Add on entry exists, Remove first using SUM CISI

2) Crosscheck SLD - Data Supplier whether correct system information sent to LMDB or not.
     We can also manually correct LMDB information.

3) Once corrected in LMDB, Check periodic LMDB Upload job running fine or not.

     SM:LMDB GENERIC UPLOAD job name - for newer Solman versions

This job will send LMDB - System Data (Replication) to SAP Support Portal which then used in Maintenance Planner (Last Replicated time)

Usually, It will take near 2 hours Max to reflect sometimes. Data will be fetched from LMDB and drops at Postbox of Support Hub/Portal Connectivity. From the Postbox, Support Portal/Hub connectivity will take those data packages every one hour and then reflects the latest system information.

OR

Try once - Selection of "Upload to SAP Support Portal" button manually in LMDB which again triggers job in backend instead of waiting on next scheduled job run iteration.

Now, Maintenance Planner will have correct system components (without Ariba Product)

Another scenario:

If you are not using Solman/Frun, then we can do below steps.

Generate new Sysinfo.xml file via SPAM - Add Manually in Maintenance Planner with duplicate ID say SID_DUPI.

Do an manual verification and remove Uninstalled Product Add on - Generate Stack XML.

Run SUM CISI. Now, System will have correct information.

You can delete original system SID and reupload newly once again by generating new Sysinfo.XML.

In the end, we have our system with correct information.

Hope you like this tick !

Thanks for visiting !!!