Hi everyone,

we’ve heard the need for clarify on SAP S/4HANA release strategy, especially how a Feature Pack Stack relates to a Support Pack Stack,…

I will try to give you our SCN readers clarity on that, with a focus on the on premise product only: SAP S/4HANA, on premise edition

What is a Feature Pack Stack and at what cadence are they shipped?

For the product SAP S/4HANA on premise edition, SAP is shipping 1 new key release per year, and 3 successive Feature Pack Stacks (FPS) on a quarterly basis. Then comes the next key release, followed by 3 Feature Pack Stacks, etc.

Technically speaking, an FPS is similar to an SPS, but it may include non-disruptive, non-mandatory features. You will find the detailed definition of an Feature Pack Stack in the release strategy glossary: https://support.sap.com/release-upgrade-maintenance/release-strategy/glossary.html#f

What does this mean concretely for SAP S/4HANA, on premise edition?

Here concretely for the current on-premise product:

  • SAP S/4HANA, on premise edition 1511 (shipped in November 2015)
  • Then SAP S/4HANA, on premise edition 1511 FPS01 (shipped in February 2016)
  • Then SAP S/4HANA, on premise edition 1511 FPS02 (planned in Q2 2016)
  • Then SAP S/4HANA, on premise edition 1511 FPS03 (planned in Q3 2016)

In Q4 2016, SAP S/4HANA, on premise edition 1511 will go into maintenance only mode, and will be supported with SPS (Support Package stacks), according to the maintenance contract.

The numbering of FPS/SPS will be consecutive, i.e. the first SPS after a FPS3 would be consequently SPS4.

At the same time, SAP will ship the next big on premise release, SAP S/4HANA, on premise edition 1610, which will be followed by Feature pack stack on a quarterly basis.

————————————————————————————————————————————–

Important update from October 20 2016:

1. SAP will ship neither an FPS in Q3 2016 as initially announced, nor an SPS. All the planned, non-disruptive, non-mandatory features were shipped with the FPS2.

2. SAP will ship an SPS in Q4 as planned and communicated and shown below

3. SAP will ship as planned a major release, SAP S/4HANA 1610, planned for end of October

————————————————————————————————————————————–

 

RM.PNG

Picture: SAP S/4HANA release management

Need more information?

You will find more details about the maintenance rules strategy here:

https://support.sap.com/release-upgrade-maintenance/release-strategy/release/on-premise/rules.html

Hope this help to clarify the topic, happy to get your feedback!

Thanks, Yannick

Follow me @ypeterschmitt

To report this post you need to login first.

34 Comments

You must be Logged on to comment or reply to a post.

  1. Joachim Rees

    Thank you very much for the clarification, Yannick!

     

    So the re-phrase it in my own words:

     

    For S/4HANA 1511 on premise, we get a new “paket” of software about every quarter;

    The first 3 of those are called “FPS”, the following ones are called “SPS”.

    (but the method of delivery is the same, right?!)

     

    So if “Installed Software” says

    Component / Release / SP-Level

    S4CORE 100 0001

    it means I’m on S/4HANA 1511 FPS 01.

     

    if it says

    S4CORE 100 0003

    it means I’m on S/4HANA 1511 FPS 03.

     

    but if it says

    S4CORE 100 0004

    it means I’m on S/4HANA 1511 SPS 04.

     

    right?

     

     

    And one last question to round everything up:

     

    Eventually I’ll get SAP S/4HANA, on premise edition 1610 – how will that be represented at software component relese-level ?

     

    • S4CORE 101 0000 ?
    • S4CORE 200 0000 ?
    • something else?

     

     

     

    best

    Joachim

    (0) 
    1. Christian Lechner

      Hi Joachim,

       

      from a technical/deployment/delivery point of view SPs and FPs are the same. The only difference is the “promise” that comes with them:

      FP: New functionality + enhanced functionality + patches/bug fixes

      SP: Just patches (new functionality is not even allowed here)

       

      So your assumptions are right.

       

      Concerning the release level – this is something that SAP has to answer 🙂

       

      BR

      Christian

      (0) 
      1. Yannick Peterschmitt Post author

        Hi Christian, hi Joachim,

         

        Christian’s answer is absolutely correct. Technically FPS and SPS are the same, FPS can include minor, non mandatory, non disruptive features. Check our Q1 2016 blog to find examples of features delivered with FPS1.

         

        Regarding the release level: you have properly spelt the logic Joachim. I’ll get confirmation on the # from the production team.

         

        Thanks again for raising the topic.

        Regards, Yannick

        (1) 
    2. Yannick Peterschmitt Post author

      Hi Joachim

       

      … and to answer to your other questions on the #

      S4CORE 100 0004 it means I’m on S/4HANA 1511 SPS 04, this is correct.


      ot the question:

      • S4CORE 101 0000 ?
      • S4CORE 200 0000 ?

      here are both options possible, you will find the final name at shipment of the software.


      Hope this helps, Yannick

      (0) 
  2. Christian Winheller

    Hello Yannick,

     

    thanks for the clarification. I now stumpled over comments in which people spoke of “SR0”, “SR1” … referring to them as SR0 = 1511 FPS01, SR1 = 1511 FPS02 ….

     

    I found the Blog: SP, SPs, SR | SCN in which people tried to explain this.

     

    1. Maybe you’d like to add this (FPS vs SPS vs SR).

     

    2. What I am really missing, ever again, in my past few years in the SAP World, is a clear documentation on all the marketing speech, versioning language and constellations (Suite,ERP Core, Platform,…). There must have been so many steps in the product architectures, portfolios, components, applications, naming, versioning schemes – I believe I am not the only one finding this very hard to get sorted. Isn’t there any central explanation?

     

    Thanks again, Christian

    (0) 
    1. Yannick Peterschmitt Post author

      hi Christian

      thanks for your note and recommendation. On 1: will do.

      On 2: point taken! I’d recommand to focus on 2 things first:

      – the solution explorer: https://solutionexplorer.sap.com/solexp/ui/

      … to understand the business scope of the different solution

      – the Innovation Discovery https://zinnovationdiscovery-supportportal.dispatcher.hana.ondemand.com/#/innovations

      … to found out the recent and planned innovation

      Hope this simplifies a bit the understanding.

      Regards Yannick

      (0) 
  3. Junaid Alam

    Thanks Yannick.

     

    Great information and clarity. Now it is lot clear on future releases of 1511 FPS versions followed by 1610 FPS.

    Is it possible to get future innovations document in 1610. We know EWM will be native to S4HANA, etc.. Same way wanted to get future innovations for SAP TM & Consolidation in 1610?

     

    Regards

    Junaid

    (0) 
    1. Menno van Rooij

      Hi,

      Very good blog !

      I was wondering how you should update to the new patch level, as our Solman 7.1 with the highest SP level is not able to generate a stack file :

      Internal Error: unable to get software components for instance SAP S/4HANA Server of SAP S/4HANA ON-PREMISE 1511-01 (02/2016) FPS


      Is this something that has to be done with Maintenance Planner instead of the Maintenance Optimizer?

       

      Regards,

      Menno

      (0) 
  4. Dirk Umbach

    Hi Yannick,

    one detailed question about software packages inside the FPS / SPS.

    When are the basic software packages like SAP_BASIS, SAP_ABA, SAP_BW updated?

    Are there only with a new edition like 1610 updated, or also with a FPS update?

     

    I am wondering why we got a 1511FPS02 with a SAP_BW 750 SP0001 and not the new SP0003.

     

    Regards, Dirk

    (0) 
  5. Jarlath Hoade

    Hi Yannick,

     

     

     

    Thank you, this is great information.

     

     

    One question if you don’t mind. Has the SAP S/4HANA on premise edition 1610 been confirmed for Q4? I checked SAP Marketplace and the SAP S/4HANA Road Map from July 2016 does not mention it.

     

     

     

    Regards,

    Jarlath

    (0) 
      1. Jarlath Hoade

        Hi Yannick,

        Thanks for the confirmation.

        As we are now in mid-October, has there been a confirmed date for the availability S/4HANA on premise edition 1610?

        Regards,
        Jarlath

        (0) 
  6. João Costa

    Hi Yannick!

    Nice blog! 🙂

    I’m wondering, and would appreciate your input, if  based on the information below from SPAM, can say we are on FPS2.

    Thanks and Best Regards,
    João

    (0) 
    1. Joachim Rees

      Hi João,

      you’re right, you are on S/4HANA, 1511,  FPS02!
      (I can tell by S4CORE 100 0002
      Details:
      S4CORE: S/4HANA
      100: 1511 (101 would beo 1610)
      002: FPS2 (000 would be initial shipments stack, 001 would be FPS01).
      ).

      best
      Joachim

      (1) 
      1. João Costa

        Joachim,

        thank you for your reply and understand the explanation.

        Just saw your post.

        In between my post and yours, and because we were having some trouble because were asked to implement software that should be there, checked the Maintenance Planner (which was wrong), and the Solution Manager, and updated the entire stuff including the Content Repository.

        Asked Maintenance Planner to prepare a solution to update the system to FPS02 and it prepared a package. After applying that package got this:

        (this list is correct, the previous was missing all of these products inspite they were installed..)

        Apart from several ACP, there were some SAR files being the biggest the SAP_UI 750 05 (K-75005INSAPUI.SAR).

        The SAINT analysis report shows that the following components were changed:
        SAP_GWFND
        SAP_UI
        ST-PI
        UIBAS001
        UIMDC001

        After applying this, and updating Maintenance Planner (MP), asked again to MP (to double check) to prepare an update solution to FPS02, this time nothing come out.

        Meaning, how can we be sure about the FPS/SPS level? Is it given by the S4CORE or by other components? Do you know a place, document, that can further clarify this?

        Thank you and Kind Regards,
        Joao

        (0) 
        1. Joachim Rees

          Hi Joao,

          sorry, I don’t know anything about Maintenance Planner and stuff like that (I’m not a Basis-person), so I probaly cant really help you here. 🙁

          All I can say (and that’s a repeat of my last comment) is that it is my undestanding, that you can tell by the S4CORE-Component on which Product/Release and FPS/SPS you are:

          S4CORE 100 0002 -> S/4HANA, 1511,  FPS02!

          best
          Joachim

          (0) 
  7. RAVINDRANATH GOVINDASWAMY

    Hello Team

    Could you please let me know which would be the best practice to use? Either 1511 or 1610
    We are in the initial stage of a POC and looking forward for a Big Time project as well.
    Since now we heard 1503 is ruled over by 1511, and since then before we digest, SAP has introduced and released 1610 last month, could you please advice which would be better to proceed further (either 1511 or 1610)

    We are considering the Finance and Controlling part (E2E) including the Cash management and Consolidation.

    Kindly let us know which would be the best to start up and any links on what is New in 1610 over 1511 so that we can include that as well would be appreciated.

    (0) 
  8. nitesh nagpal

    Hello Yannick – Thanks for the great insight !

     

    Have a query which may not be related to this blog but for the sake of my understanding I would like to ask.

    FP: New functionality + enhanced functionality + patches/bug fixes but as you mentioned that they are non disruptive/minor changes so obviously they are different from EhP’s ? EhP’s as such are not relevant from S/4 HANA perspective but for Business Suite and other non HANA products, correct ?

    Regards,

    Nitesh

    (0) 

Leave a Reply