Product Release Strategy Webcast Notes – All About Feature Packages
This was an SAP webcast given last week. Unfortunately the link to the slides is now broken on the SAP Support portal so the link is now removed.
Figure 1: Source: SAP
Figure 1 shows SAP had major shipments every 1-2 years
Market wants more continuous innovation
SAP will have feature packages with new functionality to the customer
The customer chooses which features to implement
Figure 2: Source: SAP
Feature package phase, normal correction and changes, see new functionality which is bundled in feature packages which use the support package technology
There are no new tools required to handle
There is no additional charge for feature packs
Features are optional
Focus is “on time to market”
Figure 3: Source: SAP
Latest SP should be implemented
Figure 4: Source: SAP
Figure 4 shows the different types of packages with respect to impact to platform, kernel changes
Support packages contain corrections and legal changes
- – Aligned with maintenance phases
- – Corrections for SP’s are delivered as in the past via notes
- – There is no kernel or platform update required if you implement SP
- – SUM and SP manager are used to implement
- – If compare SP with FP –
Maintenance is similar
Underlying release
Corrections are provided via notes
Intend to keep platform and kernel stable
Feature Packages bundle changes and corrections – incremental fast cycle innovations which are “non-disruptive”
Enhancement packages stick to underlying release / product version
Release packages provide new functionality, architecture changes are possible
- Has its own maintenance strategy
Figure 5: Source: SAP
Question: How are feature packs different from today’s enhancement packs, which, to be honest, aren’t easily “consumed”
Answer: Yes, Feature Packages are indeed different from Enhancement Packages. Feature Packages are based on the Support Package Technology and are much smaller than Enhancement Packages. The current slide will provide insight to the differences.
Zero downtime – update landscape with no downtime
Feature package phase lasts 2 years; max 2 years after RTC
No big bang approach
Feature package phase starts with a new release
Here is a direct link to a description of the Feature Packages: https://support.sap.com/release-upgrade-maintenance/release-strategy/release/on-premise/maintenance-phases.html
You can also find a definition of “Feature Packages” using the following link: https://support.sap.com/release-upgrade-maintenance/release-strategy/glossary.html#f
Hi, Tammy the ppt's link is broken, could you check for me? I am interested in this subject, if you prefer to send for email, my email is alex.maarin@gmail.com.
Hi Alex - unfortunately I don't have the link any more and now it appears to be broken on the SAP Support portal.
If I find it I will update the blog.
Please note you are not include your e-mail address on SCN except in the profile per the SCN rules of engagement.
Ok, Tammy,
I will wait the blog's update. Thanks for you attention.
Hi Tammy,
Thanks for a nice blog. The information is really helpful even more than two year after you published this blog. I have couple of questions and it would be really helpful if you could help me with the answers 🙂
I assume that with every S/4 yearly release SAP with supply three Feature Packs; FPS01, FPS02, FPS03 and then SPS04, SPS05 onwards as per the Maintenance Strategy Rules (https://support.sap.com/release-upgrade-maintenance/release-strategy/release/on-premise/rules.html).
I understand that SAP controls/decides if there will be three feature packs required after the yearly release or not and same is the case for service packs. Also the conversion path shall be made available by SAP before we can try an upgrade from one version to other (Example SAP S/4 HANA 1511 to 1610 etc.).
Question 1 - Once I am live with S/4 HANA 1610 FPS01, Can I apply the SPS packs released later even when I do not apply subsequent feature packs? Example: I choose to directly apply SPS04?
Question 2 - What if we decide to upgrade at alater point from SAP S/4 HANA 1610 FPS01 to FPS02, Do you think that this will need an effort equivalent to system conversion in terms of testing the existing solution? or that can be just considered as technical upgrade with no functional effort?
Question 3 - In Picture 3 of your blog, For the purpose of my question, I assume that last bar is 1511, above that 1610 and the top most bar is 1709 - What does the alternate path show here? Does it show that If I apply SPS04 of 1511, I will be having same functionalities of 1610 FPS01?
Question 4 - Customers are always confused if they should move to S/4 now or wait for the next release to see what new functionalities SAP will offer. So, Should we assume that once the first SPS is released for the respective product version (example 1511), the product is stable?
Thanks!
Amit Singh
Hi Amit - thank you for reading
First this blog is 3 years old; I am not sure if/how they apply to S/4HANA; perhaps ask these as questions at answers.sap.com under the HANA tags? Â I am not sure how SAP has changed this since 2014.