Skip to Content

S/4HANA Extensibility – The new White Paper

Extensibility for S/4HANA is a topic intensively discussed in recent blogs and interviews, see for example the interview by Bernd Leukert ( , in German) and the discussion under the following blog post( and the following posts by Bjoern Goerke). It is heavily debated which extensibility capabilities are available for S/4HANA. A comprehensive view on S/4HANA Extensibility can be now found in a white paper that SAP published in 2015 and updated recently: (new: link to the new version as of September 2018)

Of course, I recommend reading the paper, but as an appetizer, I want to rephrase some of the central points of the paper under the question “What changes”?

What are the changes for the on premise version?

Short answer: Nothing. You can use all extension techniques that you know from the Business Suite. Longer answer: you can use the techniques designed for the cloud and SAP recommends doing so. I will come to this point later, but let us discuss the cloud story first.

What are the changes if you decide to move to the cloud version?

First of all – to avoid confusion – let us recall Bjoern Goerkes answer in the aforementioned discussion: “SAP does not want all customers to be in the Cloud. It’s the market that’s tilting towards Cloud over on-premise in more and more application areas. It’s customers who want to be there with parts of their solutions. Not all customers. And not with all their solutions. But significantly many. That’s why SAP offers choice to customers to the possible extent.” ( )

Now let us come back to the question:

A) SAP offers two flavors of extensibility in the cloud, which are complementary and can be combined:

  1. Side-by-side extensibility is the capability to extend the applications by new functionality implemented on HCP – in Java and server-side JavaScript are the current development languages. Developers are the target group; the current tool set is SAP Web IDE (for frontend & backend JavaScript, and HANA development) and Eclipse (Java). What is about ABAP in HCP? Bjoern answered: “From a purely technical perspective, one could of course imagine to put an ABAP stack “into” Hana Cloud Platform (HCP) — it’s all just turing-complete software ; ). But it wouldn’t comply with the cloud operations and lifecycle principles and requirements that HCP as a PaaS requires.” ( )
  2. In-app extensibility is the capability of extending the existing S/4 HANA applications which are implemented to the vast majority in ABAP (backend) and JavaScript (Fiori frontend) inside the ABAP stack. The target group is the business expert in the company or from a consulting partner (aka key user, thus also called key user extensibility), the tool set consists of web-based apps for end-to-end creation of extensions, for example custom fields, custom logic, etc. See: The Key User Extensibility Tools of S/4 HANA

B) The lifecycle management requirements dominate the extension process

In the cloud version, SAP defines the tact for software updates. For example, SAP ships a major update every quarter, regular fixes every two weeks and urgent fixes asap (just to give some example timelines from existing cloud products). For extensions, this means:

  1. Extensibility artifacts must never block an SAP software update.
  2. Extensibility artifacts must continue to work after an SAP software update without manual work; in other words: SAP software updates do not depend on the reaction by the customer.

All extensibility capabilities in the cloud must fulfill these requirements. This means, for example, that modifications to SAP objects are forbidden.

C) As a consequence of point B, extensibility artifacts use released, stable SAP extension points and APIs only. This has to be enforced by checks on customer side. On SAP side, checks must prevent incompatible changes to objects that are marked as extensible and have been delivered once. A deprecation mechanism must be available.

Points B and C are valid for side-by-side and for in-app extensibility.  In the on premise world, typically the extensibility requirements have clear priority – lifecycle management has to follow. In the cloud model, the relationship is just the opposite. Lifecycle requirements comes first, it dictates the limits of extensibility. (Side note: the SAP HEC offering does not follow this cloud paradigm, but the S/4 HANA cloud does.)

Only a limited set of extensibility use cases and APIs are supported for the first S/4HANA cloud version. However, there will be a high demand from customers for additional extensibility use cases. The existing extensibility concept of S/4HANA proposes that a SAP shared service center may fulfill additional requirements as long as they are not available in the standard extensibility tools.

What changes for the on premise version (cont.)?

As mentioned, SAP recommends that you use the techniques designed for the cloud also on premise (see for example Bernd Leukerts answer in the aforementioned interview). Why? Going forward in this direction, on premise customers can benefit from the tools that are designed for the cloud to reduce their TCO. Why now? The migration to S/4HANA means that you anyway have to touch your code (see the article featuring Rudolf Hois for a comprehensive overview). So it is a good time to change to state-of-the-art extensibility techniques in this project!

You must be Logged on to comment or reply to a post.
  • Thanks Thomas, great blog. Regarding the use of  'released, stable SAP extension points and APIs only'...

    I'm certainly in favour of doing that, but as a caveat there are still many business objects in the suite which don't have a fully-functional API available. Similarly, there isn't always adequate provision of extension points. In one SAP module on my current project, the product team had intentionally decided not to provide any BAdIs on the grounds that customers can use implicit enhancements instead. But of course implicit enhancements are not guaranteed to continue working after an update to the standard code that they enhance.

    • Hi Roger,

      thanks for the comment. The white paper defines a roadmap and it is quite clear that the change cannot be done from one day to th other. But we should push into this direction. Let me clearly point out the difference between on premise and cloud. In the on premise solution, you can move to the "lifecycle-decoupled extensibility" step-by-step as SAP changes the API and enhancement options and reduce the TCO for updates gradually. In the cloud version, there is only the black and white decision.

      Best regards,



  • Hi Thomas,

    Thanks for sharing the great white paper re: S/4HANA Extensibility and your clarifications of the central points of the paper.

    So do you know when SAP would have the list of BAdIs and APIs that are available for  S/4HANA Extensibility?

    • Hi Angie,

      there will be not one date for a list. SAP will release APIs in waves per cloud shipment. The cloud shipments will be quarterly (1511, ...). The white listed APIs will be also available in the on premise shipment subsequently. In parallel there shall be a request process so that customers/partners can request the release of API for particular customer projects even in a faster tact.

      Best regards,



  • is there already some documentation available how to execute the extension in detail? (e.g. key-user-extensions, managed extensions). is it required to perform actions in the old SAP GUI?

    • Hi Emanuel,

      for key user extensibility the first features are available in S/4 HANA version 1506. Please find the user assistance here (you can open this from the S/4 HANA version 1506 Fiori UI):

      Managed extensibility is not yet available in 1506, so there is no detailed documentation yet.

      Best regards,


      • Hello Thomas

        thanks for your quick answer! However, we are running the 1503 on-premise edition and there are no customizing-apps available. Is this feature alread available in the on-premise-edition as well and do we have to download some more apps or will we have to wait until 1511 release?

        Thanks & Regards Emanuel

        • Hi Emanuel,

          1506 cloud edition was the first release for key user extensibility features. In the on premise edition, it will be available for 1511 for the first time.

          Best regards,



          • Hi Thomas,

            might be a simple question, anyhow:
            I had a look at 30 day on premise trial on CAL / AWS. Works pretty smooth.

            I also had a look at 14-day trial for S/4HANA cloud edition 1506. Well - that trial is a little bit "incomplete". Quite often links from one Fiori-App to another do not work and you get messages like "navigation not supported".

            Is there a good way for us to test-drive 1506 edition?

            That 14-day trial does not seem to be the full S/4HANA "cloud enterprise edition" including these extensibility features (cannot check again myself, my 14-day trial is over).

            SAP S/4HANA, cloud edition trial page

            thx & kr, Clemens

          • Hi Clemens,

            I think it would be a good idea to give this feedback directly on the trial page 😉

            So the colleagues have a chance to improve the trial offering. For extensibility: unfortunately the key user extensibility apps are not in the trial scope. We are working on this for the next release.

            Best regards, Thomas

    • Hi Pramod,

      for SAP S/4HANA, on-premise version, you can also use XSA on premise. But as far as I know, there is no special focus on this scenario (as far as I know).

      Best regards,




  • Hi Thomas,

    is there an update of the document planned? In just two month the current version will be two years old. In the meantime i.e. the S/4HANA Cloud SDK was released.

    Best regards