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.

20 Comments
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.

        Regards,

        Gairik

  • 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.

       

      Regards,

      Anuradha

       

       

    • Hi,

       

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

       

      Regards,

      Anuradha Jha

  • 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

  • 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

      Adil

  • 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?

    Regards,
    Thomas