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

[anujha]

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.

SAP Best Practices Explorer

-- Browse SAP Best Practices content

-- Power your project with ready-to-run processes

Solution Manager 7.2

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

[sap_cdg]

Hi Anuradha,

Does the third party RFC's calls are allowed in STE environment?

Thanks

[former_member632785]

Hi Anuradha,

Thank you for the information. What should be the parameters for SAP GUI1. System ID, 2. Instance Number, 3. Application Server in the case of S4 HANA Cloud STE?

 

We are new to S4 HANA Cloud and would like to use SAP GUI also.

 

Is there any documentation available on this?

 

All help in this will be highly appreciated.

 

Kind Regards,

Savio Michael 

 

 

 

[former_member611236]

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:

https://go.support.sap.com/roadmapviewer/#/group/BE47098A-617A-43EF-A27E-DFD801D70483/roadmapOvervie...

 

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?

 

Regards,

 

Randal

[sergio_oliveira5]

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

[Guiza]

Hi,

Regarding integrations with Ariba, Does it have any concern? CIG connector can be used, right?

 

Thanks in advance,

Guilherme

[former_member677277]

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.

Regards,

Vikash

[Silwood]

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

[former_member249644]

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 - https://launchpad.support.sap.com/#/notes/2653671 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?

 

Thanks,
Ankit

[former_member305187]

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

Thanks

Nishant Kathuria

 

[vadrevu_kk]

Dear Anuradha,

 

Any update on Automated testing tools for STE?

 

Thanks,

Kiran Vadrevu

 

[Former Member]

Is it still valid? I mean S/4 public not available on IBM Cloud ?

[former_member191777]

Hi Anuradha,

 

Thank you for detailed explanation. Regarding testing functionality how about Tricentis with STE will it support.

Regards

Vyomakesh Bharadwaj Racherla

[ahmadnawazcheema]

Hi,

In the text above it says:

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

2 upgrades in 3 years contract period,

The image says: "Bi-Yearly" which means "Twice every year".

I am confused. please can you add clarity and confirm which is accurate for STE?

i.e the text mentioned 2 upgrades in 3 years OR the one of image i.e. Bi-Yearly (that's twice every year)?

Thanks,

Ahmad.