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 !!!