Skip to Content
Author's profile photo Thomas Schneider
Thomas Schneider
Posted on September 14, 2018 1 minute read

SAP S/4HANA Extensibility – Major Update of the White Paper

Follow RSS feed
3 Likes 4,141 Views 11 Comments

The new SAP S/4HANA Extensibility white paper is now available. It was re-written and replaces the old one. The link to the white paper is still the same, so if you have linked or bookmarked it, you do not have to change the link:

SAP S/4HANA® and SAP S/4HANA Cloud Extensibility for Customers and Partners
http://go.sap.com/documents/2015/07/2ad59b27-347c-0010-82c7-eda71af511fa.html

I do not want to re-phrase the content here, but some points I want to mentioned. The paper is not just a minor update of the previous version, it is re-written to a large degree, I just want to mention some points here:

  • positioning of the SAP Cloud Platform software development kit (SDK) and the SAP S/4HANA Cloud SDK
    positioning of the SAP Cloud Platform ABAP Environment
  • A new chapter “Extensibility Scenarios – When To Use Which Option” was added, which includes a detailed list of criteria.
  • A new chapter “Your Way to the Cloud from an On-Premise Environment with SAP S/4HANA” was added, which depicts the way from SAP ERP to SAP S/4HANA Cloud.

So, it is definitely worth reading.

Im addition, I want to mention a second document that was recently published.

Guidance for Extensibility in SAP S/4 HANA Cloud, Single tenant edition
https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_019%20Guidance%20for%20Extensibility%20in%20SAP%20S4HANA%20Cloud%20STE.pdf

This document provides a very detailed list of guidelines for extensions techniques, which can be used in a SAP S/4 HANA Cloud, Single tenant edition. But I think this document is also useful for developers of SAP S/4 HANA (on premise) as a guidance for choosing the right extensions techniques.

Assigned tags

Related Blog Posts

    Related Questions

      11 Comments
      You must be Logged on to comment or reply to a post.
      • Author's profile photo Thomas Schneider
        Joachim Rees

        Thanks a lot, Thomas!

        For me this come just a t the right time, as I have to look into S/4HANA Extensibility soon – good thing I can do this using the newest whitepaper now!

        A small peace of feedback (which I might have given in the past already, not entirely sure about it) and wish for improvement:

        When using the download link (at the bottom of the page), the filename is kind of cryptic: 2ad59b27-347c-0010-82c7-eda71af511fa.pdf

        It would be nice if it could be something more telling, like “S4HANA Extensibility Whitepaper 09_2018 Update.pdf” instead!

        best
        Joachim

      • Author's profile photo Thomas Schneider
        Satinder Singh

        So Thomas, does this mean that “Managed Extensibility” has been removed to the roadmap now ? And if yes, any alternative is provided for partner add-ons or that option is now excluded from the future roadmap ?

         

        • Author's profile photo Thomas Schneider
          Thomas Schneider Post author

          “Managed Extensibility” has been removed already in the previous (2016) version of the whte paper. For partners, refer to Chapter 4. Unfortunately, as stated in the document, a fixed road map for the feature mentioned therein is not yet available.

      • Author's profile photo Thomas Schneider
        Joachim Rees

        As I’m going through it, here’s another piece of feedback:

         

        5.1.1.2. Recommendations

        In general, if multiple options are available for your enhancement use case, choose the following,

        shown in order of preference, for new implementations:

        • New BAdIs for SAP S/4HANA
        • Explicit enhancement options, user or system exits, or application-specific enhancement frameworks

        • Explicit enhancement options

        • Modifications of SAP code

        • Clone and adoption of SAP code

         

        I guess the 2nd occurrence of “Explicit enhancement options” is meant to say “implicit enhancement options” instead, right?! (Otherwise, why wouldn’t they be mentioned at all?)

         

        best

        Joachim