BASIS SPAM UPDATE – HIDDEN GLITCH #ATR

[AJAYTR_ATR66]

#ATR(19)

Informative Note:

• Created this blog to share information on Support Package Insights w.r.t System Consistency.
• We will update SAP BASIS Component due to multiple recommendations – Planned upgrades/Hotnews Vulnerability fixes/Add on Prerequisites etc.,.
• We might not focus/crosscheck on other basis component dependencies and overall system consistency during update.
• SUM or SPAM --- BASIS or NW UPDATE – Consistency?

System Consistency:

Case 1) Proper System Consistency – Defines both SAP NW and SAP BASIS component have same versions as below. Other components will also be in same set of versions.

Case 2) At least same release version is required for System Consistency.

Case 3) If there is a requirement on Basis Component Dependencies update (Say SAP_UI) and update done without any checks, then it might not fulfill system consistency. Below snap refers to SAP_UI 752 update done on SAP NW 7.5 SP 9 – BASIS 750.

• If we plan to do BASIS Component update (SAY SP 9 TO SP 10), then prerequisites will fail. From SPAM perspective, it requires 750 SP 10 package only.

• Even if you load SAP_UI 750 package, Update can’t proceed and always show below error since SAP_UI 752 already installed.

How SAP_UI upgraded to 7.5x?

• We can’t directly update SAP_UI from 750 to 752 via SPAM.
• I have uploaded SAP_UI 752 in SPAM and it’s clearly mentioned that it can’t be updated.   [Existing component - SAP_UI 750 SP 5 ]

• From Customer Point of View to do SAP_UI component update alone, there are several ways to update SAP_UI component version.
• https://me.sap.com/notes/2488242 - SAP_UI 7.52 minimal installation requirements

• https://me.sap.com/notes/0002775410 - 2775410 - How to update SAP_UI to a next version on a Netweaver system without Fiori Frontend Server
• https://me.sap.com/notes/2431951 - 2431951 - How to generate a stack file for upgrading SAP_UI or kernel without updating other SAP components

Via Maintenance Planner (MP) – Possible :

• Consider, we have SAP_UI 750 SP 5. [Check done on 27.04.2024]

• You can select current/higher NW version in Maintenance Planner and able to update from SAP_UI 750 to 754 (latest which supports NW 750). I have selected current NW.

• SAP_UI versions till 753 already went to archived state.
• Hence, System will run with SAP_UI 754 and SAP BASIS 750 post update.
• Likewise, Customer might have agreed and upgraded SAP_UI version from 750 to 752 (which was valid maintenance) in earlier scenario.
• Indirectly, it resulted in SPAM BASIS Inconsistency.
• Even if you plan to update directly to latest 750 SP 28 via SPAM, it requires SAP_UI 750 as prerequisites.

Next steps/Recommendation?

If SAP_UI already updated to higher version by mistake:

• One wrong move with SAP_UI seems to affect SAP BASIS Component update via SPAM permanently.
• You need to plan updates via MP only (NW/Major) further.
• For 750 – If you SAP BASIS Version already crossed SP 20, then SAP_UI dependency won’t be shown in SPAM. You can update SAP_UI to Higher Release version(75x) as well as SAP BASIS SPAM update from SP 21 – 28 without any issues since it won’t show UI dependencies. This check will vary for each systems UI and BASIS Component version.

If updates required without SAP_UI:

• Using Upgraded SAP_UI version might be the default method provided by SAP since it’s compatible and older versions gone out of maintenance.
• Above Scenario taken with ERP EHP8 but it might affect all systems (ERP/S/4HANA) since each type of system have SAP_UI core component.
• Make sure whether you need to update SAP_UI or not and plan accordingly. You can deselect and plan NW/Major update without USER INTERFACE Technology if update required. Stack XML file can be generated without any issues since SAP_UI won’t be the mandatory component to select if planned via MP.

• However, you can update to the latest SAP_UI SP version post NW/Major update manually via SPAM. We won’t face any issues since SAP_BASIS and SAP_UI will be in same release version only.

 INFO:

• None of the other cases will have this type of weird scenario. From technical basis end, we can’t update release version itself. Updates to latest SP possible.
• Runs on  -> EHP 7 – SAP BASIS 740, EHP 8 – SAP BASIS 750, S4HANA 2022 – BASIS 757, S4HANA2021 – BASIS 756, etc.,.

                                                           *******PLAN WISELY*******

Thanks for Visiting!

Please do connect and follow my Linked In Profile.

https://www.linkedin.com/in/ajaytr66/

AJAY TR - ATR - SAP BASIS ADMINISTRATOR