Skip to Content
Product Information

SAP S/4HANA Cloud, Single Tenant Edition (STE)

SAP S/4HANA Single tenant Edition (STE) is one of the cloud offerings from SAP and another flavour of S/4HANA solutions among SAP S/4HANA Cloud, SAP S/4HANA in HANA Enterprise Cloud (HEC)  and SAP S/4HANA On-Premise.

This flavour of S/4HANA was being offered as “S/4HANA Cloud, Private Edition” which was recently changed to “SAP S/4HANA Cloud, Single Tenant Edition” (STE). This was in perspective of having customers to discover and consume the solutions that best suited their business needs.

As the name of this offering suggests, the application is provisioned to a single-customer in a dedicated landscape , offering the full scope of S/4HANA. However the total cost of Ownership (TCO), the speed of innovation and time-to-value cannot be achieved as much as in  SAP S/4HANA Cloud which is why customers considering Cloud ERP must first discover and verify the capabilities of SAP S/4HANA Cloud. If the standard best practises and functional scope does not meet all of the customers need, S/4HANA Cloud, STE could be an ideal substitute solution in the customer’s journey to move to cloud.

Some unique features of SAP S/4HANA Cloud, Single Tenant Edition :

  1. Configurable and customisable process upto a certain extent for Finance, HR, Procurement, Sales and many other LoBs.
  2. S/4HANA STE Supports all the industries, even the ones which are not supported by S/4HANA Cloud.
  3. 2 upgrades in 3 years contract period, which is completely up to the customer to choose the upgrade window (subjected to change in 2019 offering) in contrast to the SAP S/4HANA Cloud where upgrades are rolled out every quarter.
  4. Not only SAP managed SAP HEC, but customers can choose to run their systems on AWS, GCP, Microsoft Azure thus giving them the options to choose from 100+ Data Centers across globe.
  5. Concept of Flexible License System.
  6. Dedicated System Landscape on Cloud Infrastructure.
  7. Integration with Public Cloud Systems and OnPrem System are fully supported.
  8. Enterprise support included with one license package without having to worry about managed services or landscape definition including the global AMS services being provided proactively.

Implementation Approach:

The implementation of SAP S/4HANA Cloud, STE should follow the Five Golden Rules (cloud standards) in order to make the transition to the public cloud easier.

Details in the link: Five Golden Rules

To aid Five Golden-rules implementation methodology,  there is a standardised implementation approach which can be achieved by SAP Activate for SAP S/4HANA Cloud, Single Tenant Edition.

Details in the link  : SAP Activate for SAP S/4HANA Cloud, Single Tenant Edition


For customers who adhere to the given guidance SAP offers a smooth transition from SAP S/4HANA Cloud, STE to S/4HANA Cloud as soon as the fully required business and technical scope will be available.

To simplify the move, use available implementation flexibility wisely – only where absolutely required.


The Main Implementation tools to ease the deployment of S/4HANA Single Tenant Edition are :

SAP Roadmap Viewer

— Browse implementation guidance for your digital transformation.

— Access SAP Activate methodology assets and accelerators.
— Browse SAP Best Practices content
— Power your project with ready-to-run processes
— Understand and document SAP Best Practices  configuration guides and activate or adjust the configuration in your solution.
— Use  Project Guidance by importing project template based on SAP Activate



The main worry for the customer to move the existing ERP to the cloud is not just about :How do I move and what benefits do I get from Cloud ERP, but its about “How do I unpick the customization mess that has been created over the last decade or so and what value I’am going to get forward”.

To address this challenge, SAP has started the bridge which is SAP S/4HANA STE which enables the customers to feel the cloud and simultaneously get the business value, ultimately preparing the customer to move to S/4HANA public cloud in future.

As the business environment continues to change, holding and managing all IT assets in-house are near to reaching the limit in current era, and the cloud services that fulfills the necessary resources and needs of the business have become the mainstream.

You must be Logged on to comment or reply to a post.
    • If you are referring “That option” to SAP S/4HANA Cloud in your question then yes, the SAP S/4HANA Cloud is still termed as “Public Cloud” and sometimes “S/4 HANA Cloud, Multi Tenant Edition”.

  • Hi !

    About 'Not only SAP managed SAP HEC' : is it possible to run it on IBM Cloud

    Does the SAP Managed services  (SAP technical administration) has to be performed by SAP , or can it be done by a managed services provider ?

  • What would be the difference with S/4 HANA Cloud , STE and SAP S/4HANA in HEC ?

    is it that it cost less with some restrictions on STE version ?

    does this also have backend access like SAPGUI access ?



    • Nafran,

      The main difference between S/4 STE and S/4 in HEC is that you cannot perform code modification in S/4 STE. You have standard set of open API’s to be used and extensibility options are restricted when compared to S/4 in HEC.

      Implementation in HEC is as good as on-premise implementation where customer has all the freedom to modify the code and adjust the system as per his/her business needs.

      Every offering of S/4 HANA has some cost difference.

      And yes, STE also has the same connection  methods like any other S/4 HANA.


      • Hi Anuradha,

        Just to explain and understand a bit more on Nafran's query, customers and partners don't get SAP GUI access for S/4HANA Cloud (S4C), Multi-Tenant. I believe, in S4C Single-Tenant will have the SAP GUI access even though I understand that modifications are not allowed. Having GUI access, customers and partners can access SE38 and create custom ABAP reports (May not be recommended as ODATA with Fiori etc are recommended approach ). Please confirm my understanding about accessing SAP tcodes via SAP GUI. Many thanks.



  • Anuradha,


    You mentioned that with STE,we will have access to SAP GUI.Does this mean we can create copy of standard SAP programs? My reference here is to the include program RGGBS000 SAP has provided for user exits in FI substitutions. For customer exits,we create a Z version of RGGBS000 and add the user exit definition there.

    • Hi Sreekanth,


      You can create the Z version of this program but any modifications to the programs will not be preserved after the upgrade.






    • Hi,


      No, 3rd party add-ons are not allowed in STE. All the add-ons and some extensions are prepackaged in STE.



      Anuradha Jha

      • Hi Anuradha,

        Have a few questions on Add-ons.


        Is GRC suite prepackaged in STE? If no, can we add this as an Add-on in STE?

        Do we need any cloud connectors or Cloud Identity Access Governance to connect SAP GRC with S4H Cloud STE?

        Please clarify.


      • Hello!

        Is there any technical explanation as to why classic Z developments are generally allowed (as long as they don't change standard objects) and 3rd party addons are not allowed, even if they don't change any standard object?


        On a previous question related to TOC transports you answered that "Based on the content present in those transports, the application decides if we can allow that in STE or not."
        Why isn't this same check applied to 3rd party addons?


        Thank you

  • Hi Anuradha,

    is it possible to move a transport of copies into HEC STE to bring custom code and or configuration over from an S/4HANA on premise version given the content does not violate the enhancement concept of STE?

    Thank you,

    Mario Karrenbrock

    • Hi Mario,


      Based on the content present in those transports, the application decides if we can allow that in STE or not.




  • You mentioned AMS is included with S/4 STE. Does it mean systems integrator is not required for  implementation and post production support?

    Thank you

    • Hi Dan

      The way the STE Commercial Model works is it includes Build of Infra from a Basis perspective and then Support (AMS) for Basis only Services. The same SAP HEC R&R model is use with some slight tweaks.

      Where the SI comes is in supporting the client from a Functional perspective.

      Hope this helps


    • Hi Dan,


      As Adil explained, it's upto you to decide if the scope defined by SAP HEC fulfills your purpose from functional perspective or not.  From technical perspective, everything is being handled by SAP HEC.




  • Hi Anuradha,

    thanks for these most valuable insights. May I ask some further questions.

    1) Am I right that the implementation methodology for STE (initial implementation as well as further extensions) envisages system copies/refreshes from PRD to QAS for testing purposes - like in traditional on-premises environments.

    2) If yes, will SAP provide system copies as managed services?

    3) If yes, are these services covered by the service level agreement?

    4) If not, where to find pricing information?


    • Hi Thomas,


      1. Initial implementation is always a new implementation of STE. Further after implementation, if system copy is required for testing purpose from PRD to QAS, this can be done.


      2. Yes, System copy is part of managed service. (Please refer Hana Enterprise Cloud Roles and responsibilities for more information on this)


      3. Yes, they are covered under SLA.


      4. For pricing information, please contact your SAP Account Manager.




  • Hi Anuradha,

    Can existing SAP ECC customers upgrade to S/4HANA STE? Or customers only have the option of  "New Implementation" if they go for S/4HANA STE?



    • Hi Vincent,


      With STE it's always a new implementation, however you can migrate the data using migration  cockpit.



      Anuradha Jha

  • Dear Anuradha !


    Thanks for the detailed post. I am a functional consultant . If I were to understand

    apart  from S4 HANA on premise, we have S4 HANA Public Cloud ( Multi tenant ) which comes with standard best practices ( as of now Professional services /Manufacturing) with basic ERP standard. Here through extensibility options some leverage is given to customers to have their changes for eg.Forms / custom validations / Addl.custom fields which does not affect the system upgrade.

    S4 HANA -Single tenant is a private cloud with On premise functionality with more relaxed norms for config changes /modifications ,unlike public cloud but still restricted ,warranting usage of extensibility.

    S4 HEC is equivalent to ON Premise and no restrictions of config.changes or custom codes etc and you can use the extensibility options .

  • With regard to functionality, is more functionality available in STE vs MTE?  I would think so, but I can't seem to find anything that details what is in STE that is not in MTE?

    Thank you

    • Hi,

      Marianne Zoricak STE and MTE are based on same codeline but have different functional scopes. MTE has a specific scope (there are currently less industry solutions in MTE than STE for example, but MTE has a specific industry which is not in STE), while STE has pretty much the same scope as SAP S/4HANA On Premise, since it is exactly the same product.

      I hope that it helps, let me know if you need more informaiton.

      Best regards




  • Hi Anuradha,

    thanks a lot for the detailed blog.

    I have a couple of questions to clarify my understanding:

    1. I understand that STE like HEC allows full access to SAP GUI, isn't it?
    2. I also guess it should be possible to use/import third party products and/or own development transports as long as they don't modify any SAP standard objects and use no implicit enhancements of SAP standard objects (in order to guarantee smooth updates/upgrades). Am I right?
    3. Also, I understand that customer developments or third party products aren't limited to white listed APIs and in principle ABAP developments can make use of full ABAP language using arbitrary S/4 backend functionality - even if that isn't recommended.
    4. Is it possible to use implicit enhancements of objects that aren't part of S/4 standard (i.e. own developments or third party)?
    5. What are the options to access a file system (both local FS and in cloud) and how can files securely be transferred to/from cloud FS?

    Thank you and best regards,

    • Hi Martin,


      Please find my answers.

      1. Yes, GUI is also given in STE just like any other S/4 HANA On-premise.
      2. No 3rd Party products are allowed as on today and outside transports are allowed on approval basis.
      3. Only whitelisted API's are allowed for now. Can you please explain what do you mean by "Arbitrary S/4 Backend functionality"
      4. Enhancements that aren't part of standard S/4 is not allowed in STE.
      5. We have a separate service called "SFTP" which the customer will have to subscribe to.



      • Hi Anuradha

        Can you please provide more details on the SFTP service? How can we use SFTP protocol in our integrations with S/4HANA STE (Extended edition)?


        Nishant Kathuria


    • Hi Mario.


      Not possible to have it in production environment. However client copy can be done in non-prod environment.




  • Hi Anurahda,

    My focus of this questions is around Testing and Testing Automation within the Single Tenant Edition.

    In looking thru the Roadmap, SAP Best Practices, it appears that for Single Tenant Edition is more like the S/4HANA On-premise than S/4HANA Multi-Tenant Edition as it relates to testing and testing automation.   The automated testing functionality in Public Cloud is not there in the Private Cloud edition.   Is this observation correct?     If Yes, does this give the customer the option to utilize the Automated testing tool of their choice (for example HP-QC, Worksoft, etc).

    Best Regards,


  • Hi Anurahda,


    In addition to Fiori web interface, what other interface/environment user/basis/IT can access to a STE system ?

    • I know customer can access STE via SAP GUI , right ?
    • Can customer access HANA db through hana studio ?
    • Can customr access OS environment on AS ABAP or HANA DB ?
    • How the STE exchange data with customer’s in-house systems (such as mail system , printer, other database/web service)?

    Ohter questions:

    • The traditional 3 system landscape (DEV/QAS/PRD) still apply to STE deployment ?
    • Need to pay for DEV and QAS system (separate from PRD) ?
    • Can customer do client copy on a STE system ?
    • Do we need BASIS ?


    • Hi,


      Yes, the customer can access STE via GUI.

      Yes, he can access DB via HANA studio but with limited functionalities.

      No, OS access is restricted.

      Exchange of data is possible via standard SAP communication mechanism.


      STE is also being offered with 2 tier landscape.

      Depends on your licence and FUE usgae.

      Yes, they can perform client copy but there are restrictions on the size of the client. Less than 500 GB, the customer can perform themselves via self services.

      HEC offers all the Basis related services. However for detailed Roles and Responsibilities of SAP, please refer to HEC R&R.






  • Hi Anuradha,

    I have read the "Guidance for Extensibility in SAP S/4 HANA Cloud, single tenant edition" document.

    So in the STE we cannot use implicit enhancements in the beginning or end of FMs, subroutines, classes etc.

    What about all those explicit enhancement spots and enhancement sections?
    Can we add code there?
    Can we replace the code in the enhancement sections?


  • Hi Anuradha,

    Single Tenant has HR payroll..?

    Is this support Brown field implementation?

    Where can i find the documentation or Tool to compare SAP ERP vs STE?




    • Hello Mohamed,

      Mohamed Kaleel : SAP S/4HANA Cloud STE has the same technical scope as SAP S/4HANA OP. So if you have documents to compare SAP ERP with SAP S/4HANA OP, you have it for STE.

      Regarding implementation (transition paths) It supports Greenfield or Selective data Transition , but not the traditional conversion scenario.

      Best regards


  • Hi Anuradha,

    I have read the “Guidance for Extensibility in SAP S/4 HANA Cloud, single tenant edition” document. It says it's possible to replicate STE tables to HANA in the SAP Cloud Platform and create developments there.

    My question is: Can we use SLT to replicate tables from the STE environment to a local, on-premise Hana instance?



    Sergio Oliveira

    • Hi Oliveira,


      Yes, you can have SLT (either you can host your SLT server with HEC (HANA Enterprise Cloud) or have it at your on-premise ) to replicate tables from STE environment to your on-premise Instance.



      Anuradha Jha

      • Hello Anuradha


        I have a similar question to Sergio Oliveira about using SLT to copy data tables out of STE on HEC.  Would it be allowed to use SLT to copy HANA tables to a non-HANA database (e.g.  SQL Server) either on premise or in the cloud?  In particular for our requirement these would be largely data dictionary tables like DD02L, DD03T.....


        Thanks in anticipation of your response.


        Nick Porter

  • Hi Anuradha,


    If S/4 Hana Cloud, STE is a cloud version of S/4 , does it mean it will have Fiori applications available for 1908 ? or will it have apps released for 1909.


    Regards, Navin

    • Hello,

      Navin Mittal . SAP S/4HANA CLoud, STE is a Cloud product ( packaged hardware+software+services, available as a subscription..) but the underlying edition is an SAP S/4HANA (on-premise). So it follows the same release cycle as the on-premise. so the answer is that if you start an STE contract today, you would get an 1909 system and as such the 1909 SAP Fiori apps.  And the next release would be the 2020 (sap labs preview/no commitment)

      Best regards


  • Hello, Anuradha,

    Thank you very much for the introduction of STE.

    I want to confirm that can I use the PS(project system) in STE?


    Looking forward your reply.

    Best regards


  • Hi Anuradha,


    Thanks for this blog and really useful information.

    I have just completed a MTE Public cloud  S4 Hana 1911.


    I am now on a new Project S4 Hana STE 1809. I do understand that this is similar to the OP version and non source Abap customization can be done unlike Public C|loud MTE.


    We did the implementation as per SAP Best Practices for Public cloud and followed the road map viewer very closely.


    I do understand for the Road Map viewer under SAP Activate methodology  we need to use the following link:


    My Questions:

    1. i am confused which Best practices explorer  i need to follow, there are so many. Should i use the OP or the Public cloud one (i used in my earlier project for Public cloud 1911).
    2. Do you feel we need to choose 1911 version (at present the client has gone for  STE 1809 ) and then do the implementation.

    Pls advise?





  • Hi Anuradha,

    May you please help us with side by side comparison between STE and HEC or OP ? I am unable to find any such document online there are a lot of documents available for STE vs MTE but couldn't find anything between STE vs HEC or on-premise.



  • Hi Anuradha,


    Can you please help in some of below clarifications on STE?

    Does S/4 cloud STE(extended addition) support proxy for integration? Can we connect to SAP PI/PO using proxy based integration as STE is more similar to on-premise S/4 or we have to leverage API's, SOA services only?

    Do we have to use DRF replication and output management through fiori for master data distributions through IDOCs or we can create partner profile through WE20 and traditional RFC destinations/ports to push data to middleware systems?

    Is restriction mentioned this note on IDOCs usage - for S/4 cloud is applicable to STE as well ? If Yes, What is recommended approach for master data distribution - material, customers, etc. on STE based on change pointers?