Sharing best practice for conducting an SAP S/4HANA Feature Package or Support Package update on the same S/4HANA release
If your organization has a periodic maintenance cycle to conduct updates to keep up with feature/support packages (FPS/SPS) to maintain stability within your SAP S/4HANA landscape, this blog along with the documentation will help guide you through this process. For S/4HANA upgrades (e.g. Upgrade to higher S/4HANA versions such S/4HANA 1809 to 1909), please refer to another of our S/4HANA RIG colleagues – Quang Vu’s blog RIG SAP S/4HANA 1909 Upgrade Document. For best practices on SAP S/4HANA upgrades to help demystify the How, Why, and best practices, please consider reading this blog Upgrading SAP S/4HANA AnyPremise – How, Why, and Best Practices guide now available! by another S/4HANA RIG colleague – Jocelyn Dart.
Similar to SAP S/4HANA upgrades, update of FPS/SPS also share a slight similarity to doing an upgrade regarding some tools and post activities. In this document we will discuss running the following steps to get you on your way to conducting a successful update of FPS/SPS of an SAP S/4HANA system (e.g. S/4HANA 1909 initial shipment to S/4HANA 1909 FPS02):
- Steps to running a Maintenance Planner transaction to generate and gather the update software for your source system you want to update.
- Leverage Software Update Manager 2.0 to conduct the update with standard downtime minimized approach. For additional information on more advanced approaches to reduce business downtime, please refer to Leveraging Zero Downtime Option of SUM for SAP S/4HANA Support Package Stack updates blog from Jens Fieger, product manager in the Cloud & Lifecycle Management area.
- Conducting post update activities in the areas of:
- Application of additional OSS Notes for the target stack.
- Fiori post update tasks.
- ESH for SAP Fiori tasks.
Link to document: SAP S/4HANA FPS/SPS Update – S/4HANA RIG version
SAP S/4HANA RIG