32. How to check Import Prerequisites to install SAP ADD ON or DO SP Updates?

Considering Ariba CIG Add on for example.

Most of the projects use Ariba CIG Add on. It's widely used in both ECC and S/4 HANA Systems.

We have below note for uninstallation.

Note 3243704 - Uninstalling Add-ons 'ARIBA CLOUD INT SAP S/4HANA 1.0', 'ARIBA CLOUD INT SAP ERP 1.0'

However, SAP doesn't release explicit KBA & Release notes (21.04.2026) for Installation. We could see many generic articles/issue fix related ones.

Consider I'm gonna install Ariba add on ARBCI1 10S - SP25 in S/4HANA 2023 FPS00 System.

For S/4HANA, It's ARBCI1 10S, For ECC, It's ARBCI1 100.

In our case, we can manually have prerequisites confirmation via below ways.

1) Check PAM Information - Mandatory

It confirms that Product "ARIBA CLOUD INT SAP S/4HANA 1.0" is compatible for S/4HANA 2023.

2) Check "Import Prerequisites in Package condition" manually for corresponding installation package.

S/4HANA 2023 FPS00 - Have SP00 -> EA-PS 808, Basis 758, S4CORE 108.

Hence, it's fully compatible. 

3) If Stack XML, then we can trust MP generation itself since only compatible packages will be shown.

In 80% cases, SP update packages such as SP1,2,..25 would be valid only. We just need to crosscheck installation prerequisites only.

For example - Checking SP25 prerequisites, It's just have SP24 only.

In simple words, All SP versions (From Lower to Latest) will be supported irrespective of S4CORE releases - S4CORE 100 to 109.

20% case - there might be an additional import prerequisite condition for some SP version due to compatibility nature/support of further versions.

4) Additional - You can just load installation package in SPAM/SAINT as well to crosscheck "Import prerequisites". 

Final note:

PAM check is mandatory for initial check.
Direct checking in Software center is an simple confirmation method. 
Direct checking in Maintenance Planner is an Assurance - in addition to XML generation.

✨Above step helps a lot in most of the cases where there is no release notes available and your project planned to install that add on.

I have done an manual checks for best practice as well as used generated XML in Maintenance planner and run with SUM/SAINT to install the add on. Ensure to update SPAM/SAINT version to latest before any operations to avoid surprises.

Note 3377364 - S/4HANA, on-premise 2023 Compatible SAP Solution extensions

Hope above info helps !

Ever stuck in SUM error due to SPAM/SAINT package archives failures?

Refer below tick.

24. SPAMCHK_INI - SPAM/SAINT Package upload failures & Manual file uploads during SUM

Thanks for visiting !!!

31. How to tackle SAP_ABA is in undefined state error during SUM Run ?

Most of the basis peoples who have played with SUM run will definitely experienced this error once.

Subjected error usually occurs if we didn't reset previous SUM Run properly.

Even I have tried SUM run for practice - deleted directory directly without proper reset and faced subjected error while trying to run SUM once again.

Let's have a quick tips.

While we perform SUM Run, UVERS table status will change FROM "+" - "can be upgraded" status TO "U" - "Upgrade running" status.

✨"+" status usually denotes that Previous upgraded completed successfully and system can be upgraded newly further.

Assume that we decided to Stop SUM update. Then, status will be set back to "+" - if we performed reset properly. If not, it stays with "U" status triggering this "Undefined state" error.

Before SUM Run:

(Sample snap)

During SUM Run:

(Sample snap)

Usual resolution would be below ones.

Step 1) If SUM directory backup taken before deletion, Restore SUM directory using backup. Do an proper reset. SUM reset can be done till it reaches downtime phase.

1.1 -  If you already reached Preprocessing/Execution (before SUM Downtime) phase in previous SUM run, then it's necessary to restore SUM directory and do SUM reset which will deal and delete shadow tables, others whichever created during SUM run. If you don't have backup, Step 2&3 might help but there would be some consequences since SUM was not properly reset despite it's reached Preprocessing/Execution phase (before downtime).

Step 2&3 - Mostly valid for Preparation RoadMap Cases - Extraction, Configuration, Checks.

Step 2) If there is no backup,  Reset the table buffer. It will set back to "+" state.

AL12 - Edit - Reset buffer - Table buffer - enter UVERS - click on Invalidate.

Step 3) If table buffer reset doesn't help, just restart SUM instance. It will clear table buffer caches.

Above steps usually resolve in 99% cases.

1% case, It won't work. I have tried above steps multiple times in one of my scenario but it didn't work. (Not sure what happened)

Since I'm confident that I haven't changed anything w.r.t my system operations/updates, I have manually changed PUTSTATUS to "+". I can able to run SUM newly without any issues.

Caution - You can do it on own risk

In general, Before starting SUM run,

Crosscheck whether SPAM/SAINT status is in green status. You can only do SUM operations if SPAM/SAINT is in GREEN 

Crosscheck whether PUTSTATUS is in "+" or not.

Note 1790486 - SAP_ABA is in an undefined state that is not safe to be upgraded vers36

Additional comments on Step 1.1:

SAP set this as mandatory condition in Note 1790486 till vers34. However, Removed in vers35 and made step 2 & 3 as common resolution.

Vers 34:

Vers 36:

✨However, As I stated in Step 1.1, It's best practice and necessary to restore SUM directory and perform SUM reset if previous SUM run already reached Preprocessing or Execution (before downtime phase)

Ever uploaded older package for SPAM/SAINT update and wondered why you have uploaded?

Refer below tick.

18. Doing SPAM/SAINT Import ? Seeking Older version files ?

Thanks for visiting !!!

30. Maintenance Planner - Solution Manager Java Verification Error case?

This tick is created just to highlight the issue I ran into.

I have faced error related to CA Introscope BCI VIA SM 8 during Solution Manager Java verification.

Note:

CA Introscope BCI VIA SM 8 has been part of the Java stack until SAP Solution Manager 7.2 SPS 11. Component is out of maintenance and there is no successor, it is no longer part of the stack as of SPS 12.

When we are updating or upgrading our Solution Manager to SPS 12 and above, SUM will ask the action for this component. We can feel free to select "Delete" option.

Similar information will be available in Solution Manager 7.2 Master guide (i Note section ) 

My scenario:

I'm having Solution Manager Java 7.2 SPS14 system.

I have generated SysInfoExport XML via SUM and uploaded in Maintenance Planner via "Manual Addition".

Not sure what happened, It ended up with Solution Manager Java SPS00 Initial Stack with Verification error Red - Might be Generated SysINFO file is corrupted one.

However, When I tried to manually verify (without automatic MP feature) to change SPS14, Solution Manager showed the below error.

Required Component "CA - INTROSCOPE BCI VIA SM 8" is missing for the Product Component Solution Manager 7.2

Is Solution Manager 7.2 SPS00 installed?

Above error statement was clear-cut one. Actual error was slightly different (confusable) when I faced.

Maintenance Planner (MP) detects as Solman Java SP00 - Initial Stack only which usually have CA - INTROSCOPE BCI VIA SM 8.

Hence, MP asks whether Solman SP00 installed in the system or not actually since it didn't find "CA - INTROSCOPE BCI VIA SM 8" in installed list.

🌟This error occurrence possibility is higher since it can show in any cases if verification gone wrong and <Solman Java SPS12. There is no SAP KBA exist (20.04.2026) separately stating this error.

Resolution 1:

Enable "Expert Options" in "Personalize" menu and edit the system

We need to disable "Allow Automatic MP feature" in verification if MP picks/shows wrong system by default (Yes/No) - Like I got Solman SP00 installed or not.

Once Automatic MP feature disabled, I have deleted wrong version SP00 and add my required system version SP14.

Save verification - Crosscheck components once.

It's just usual Solution Manager Java SPS14. It worked fine.

Resolution 2:

I have also generated System Info XML with duplicate SID_BACKUP once again since existing file might be corrupted ones despite I have done verification. Just want to be 100% sure.

Newer SysInfoExport XML is fine. Once uploaded, It showed correct system version SPS14.

Note 2287046 - How to Generate the System Info XML and upload in Maintenance Planner - Refer "For Java Stacks" Section

Note 2293050 - SUM: Generating a System Information XML File for SAP System - Maintenance Planner

Hope you like this tick !

Thanks for visiting !!!