SAP S/4HANA Cloud and On-Premise Deployment Options

[Amin-Hoque]

Last updated: Jan 26 2024 (Updated links)

This blog targets SAP solution architects and explains the different deployment options for SAP S/4HANA. I have used the latest terminology. It covers cloud, on-premise and hosted deployment options. Here are the options discussed:

1. SAP S/4HANA Cloud, public edition: This is SaaS public cloud.

2. SAP S/4HANA Cloud, private edition

3. SAP S/4HANA On-Premise managed by SAP (HEC)

4. SAP S/4HANA On-Premise: On-Premise or managed by cloud provider Hyperscalers

Deployment options 1 and 2 are the most commonly positioned options for new SAP customers.  Option 2 is available through a RISE with SAP contract.  Option 1 is available through a GROW with SAP contract.

I cover the following aspects of each option: infrastructure, license, how upgrades are managed, scope (functional, country and industry), configuration, extensibility (how solution can be extended beyond configuration) and implementation (possible approaches). All options can be implemented by the customer, SAP or a partner.

I also cover which roadmap of the SAP Activate implementation methodology is relevant, what SAP Best Practices are used and what tools are relevant. See my other blog for an overview of SAP Best Practices and the SAP Enterprise Management Layer.

 

1. SAP S/4HANA Cloud, public edition 

Commonly used by net new customers that want the full public cloud approach with regular upgrades that include new configuration and new software. This is a SaaS public cloud offering. Also used for subsidiaries alongside SAP on-premise implementations.

• Infrastructure: public cloud shared with other customers and hosted and operated by SAP only

• License: subscription for Software as a Service (SaaS) available as RISE with SAP or for new customers in the mid market through GROW with SAP.

• Upgrades: managed by SAP. fixed and mandatory (configuration and software). The upgrade of configuration is unique to the public cloud edition. SAP and customer do automated and manual regression tests.

• Scope: core ERP (subset of full ERP), specific industries and 59 countries.

• Extensibility: key user (in-app) extensibility, developer extensibility and extensions through SAP Business Technology Platform Extension Suite (side-by-side extensibility) with whitelisted APIs.

• Configuration: use SAP Central Business Configuration and Self Service Configuration User Interfaces (SSCUIs) based on fit-to-standard workshops in the Explore phase

• Implementation: greenfield only (new implementation)

• SAP Activate roadmap: SAP Activate Methodology for SAP S/4HANA Cloud

• SAP Best Practices: scope is selected from these cloud-specific Best Practices.  https://me.sap.com/processnavigator/SolS/EARL_SolS-013/2402?region=DE

• Partner content: partners can add configuration manually.

• Use SAP Cloud ALM for Application Landscape Management.

Unlike all the other deployment options, the user interface is purely Fiori and configuration is done using SAP Central Business Configuration and not through the IMG.

 

2. SAP S/4HANA Cloud, private edition 

Has advantages of the cloud with the scope and flexibility of the on-premise solution. Existing SAP ECC customers can move to private cloud using a system conversion and retain their configuration and extensions. Has standardized infrastructure processes, services and SLAs.

• Infrastructure: dedicated landscape on cloud infrastructure operated by SAP and running at a Hyperscaler e.g. Microsoft Azure, AWS, Google Cloud)

• License: subscription for software but not SaaS (available as RISE with SAP).

• Upgrades: available like on-premise but you chose your own speed but must stay in mainstream support. The customer must manage the upgrade process. SAP does specific technical  aspects of the upgrade only.

• Scope: on-premise S/4HANA functional scope. 64 countries, 39, languages and 25 industries. Some third-party add-on limitations.

• Extensibility: key user (in-app) extensibility, developer extensibility and extensions through SAP Business Technology Platform Extension Suite (side-by-side extensibility). Classic ABAP extensibility is still available but modifications are not recommended.

• Configuration: use the IMG based on fit-to-standard workshops in the Explore phase.

• Implementation: greenfield (new implementation), system conversion or selective data transition

• SAP Activate roadmap: SAP Activate Methodology for SAP S/4HANA Cloud private edition

• SAP Best Practices: SAP Best Practices are available. Enterprise Management Layer is available for a production system  Note: the on-premise Best Practices are used.  https://me.sap.com/processnavigator/SolS/EARL_SolS-055/2023?region=DE

• Partner content: partners templates allowed.

• Customers use SAP Solution Manager and/or Cloud ALM to manage their project design.

Also see this blog on the 5 golden rules to adopt some of the lessons learnt from public cloud. https://blogs.sap.com/2018/07/28/the-5-golden-rules-for-implementing-sap-s4hana-cloud-single-tenant-...

 

3. SAP S/4HANA On-Premise managed by SAP (HEC)

An on-premise solution with individual and private hardware and infrastructure hosted by SAP or a hyperscaler. Infrastructure management is delegated to SAP with flexible service offerings. This can be used for combinations of solutions that are not available in SAP S/4HANA cloud, private edition.

• Infrastructure: customer specific landscape on SAP HANA Enterprise Cloud (HEC) in SAP data centre or at a hyperscaler

• License: infrastructure subscription

• Upgrades: you choose your own speed of adoption of software upgrades. Customer is responsible for managing the upgrade.

• Scope: full S/4HANA functional, country and industry scope and partner add-ons

• Extensibility: customization, modification, and extensibility possible as with ERP

• Configuration: use the full IMG based on a fit-to-standard approach in the Explore phase

• Implementation: new implementation, system conversions or selective data transition

• SAP Activate roadmap: Transition to SAP S/4HANA

• SAP Best Practices: all SAP Best Practices are available. https://me.sap.com/processnavigator/SolS/EARL_SolS-055/2023?region=DE

• Partner content: partner templates allowed.

• Customers use SAP Solution Manager to manage their project design. Most customers use SAP Best Practices activated using SAP Solution Builder or set up by SAP through the "Enterprise Management Layer" service.

 

4. SAP S/4HANA On Premise: On-Premise or managed by cloud providers Hyperscaler

Classic on-premise SAP S/4HANA managed by the customer in their own data centre or managed by a third party.

• Infrastructure: customer data centre or hosted by hyperscaler (e.g. e.g. Microsoft Azure, AWS, Google Cloud)

• License: perpetual or Bring Your own License

• Upgrades: you choose your own speed of adoption of software upgrades. Customer is responsible for managing the upgrade..

• Scope: full S/4HANA functional, country and industry scope and partner add-ons

• Extensibility: customization, modification, and extensibility possible as with ERP

• Configuration: use the full IMG based on a fit-to-standard approach in the Explore phase

• Implementation: new implementation, system conversions or selective data transition

• SAP Activate roadmap: Transition to SAP S/4HANA

• SAP Best Practices: all SAP Best Practices are available. https://me.sap.com/processnavigator/SolS/EARL_SolS-055/2023?region=DE

• Partner content: partner templates allowed.

• Customers may use SAP Solution Manager to manage their project design. Most customers use SAP Best Practices activated using SAP Solution Builder or set up by SAP through the "Enterprise Management Layer" service.

 

Which Deployment Option is Right?

The SAP Activate roadmap has 3 approaches to implement SAP S/4HANA:

1. New implementation (also known as greenfield)
2. System conversion (also known as brownfield)
3. Selective data transition.

New implementation: for new customers or existing customers that want to reset and start again with a clean system.

System conversion involves converting your existing ERP system into SAP S/4HANA by migrating the database, applying software updates and doing a data conversion from the old data model to the new S/4HANA data model. The system must be converted to S/4HANA in one go meaning a single big bang go-live.

In the “selective data transition” approach, configuration and custom code from your old ERP system are used in the new SAP S/4HANA instance. For example, this can be done with a "shell copy" of the old system that leaves all master and transaction data behind and is followed by a system conversion to S/4HANA.

What will influence your choice of deployment option? Organizations that are completely new to SAP will do a new "greenfield" implementation and can choose any option 1 to 4. What about if you are currently running the on-premise ERP ECC and want to move to S/4HANA?

• The route selected by 50% of customers is a "system conversion" where your existing system is converted to S/4HANA. This means option 2, 3 or 4.

• If you want to start again on a new page and do a "new implementation", you can choose any deployment option. Note: option 1 may not cover all the processes and scope in an existing SAP ERP ECC solution.

• The "selective data transition" approach allows you to take some of your existing solution into a new S/4HANA instance. Option 2, 3 or 4 can be used.  Around 5% of customers choose this approach.

See me related blog on moving to S/4HANA from ERP: https://blogs.sap.com/2019/10/30/how-to-move-to-sap-s4hana/.  This blog may also be helpful:https://blogs.sap.com/2020/05/11/sap-s-4hana-deployment-on-hyperscalers/

When using the Transition to SAP S/4HANA SAP Activate roadmap, you can select the approach e.g. system conversion in the search tags. 

Note: there is an option called SAP S/4HANA Cloud, extended edition but this is no longer available for customers buying SAP S/4HANA now. This was an earlier variation on SAP S/4HANA Cloud, private edition.

I hope you found this blog informative.

Amin Hoque
Enterprise Architect at SAP Services UK

[former_member415440]

Amin, I like the article but one thing concerns me presently in the area of Data Privacy.

1809 Cloud Edition has 1J7 Best Practice describing the implementation of ILM-full or partial to support data privacy such as GDPR.

However, 1809 Single Tenant Edition does not. Is this a documentation error or do we have an issue with full support for Data Privacy on Single Tenant?

 

J1809

[Amin-Hoque]

Hello David

This is really out of my area of expertise, so I cannot provide a 100% answer.

However, single tenant edition is like any other on-premise solution and can be managed to meet data privacy legislation in the same way as other SAP deployments.

Cloud S/4HANA is the special case where a customer has less control and flexibility that in the other deployments. That is why Best Practice scope item 1J7 is provided to show how data privacy is met.

Kind regards

Amin Hoque

[Amin-Hoque]

Hello David

See my comment below

Amin Hoque.

[steven_wck]

Thank you Amin for this excellent overview.

I am slightly confused between Option 2 - S/4 HANA Cloud - Single Tenant and Option 4 - S/4 HANA On-Prem particularly if I am going to deploy it on public cloud infrastructure like AWS/Azure.

Am I right to say that both are pretty much the same, but Option 2 is managed by SAP whilst Option 4 allows me to choose who to manage it (be it my own IT or outsource to a 3rd party AMS vendor)?

 

Thank you

 

[Amin-Hoque]

Hello Steven

That is partially correct.

Only SAP offers S/4HANA Cloud Single Tenant.  This is Software As a Service. The SAP Best Practices are always used.  SAP hosts and looks after things like the operating system, SAP software and upgrades.

Partners like Azure, AWS and Google offer IAAS (Infrastructure As A Service). You might not use SAP Best Practices. They look after networking, storage, servers and virtualization.  The customer looks after the operating system up including upgrades.

Cheers

Amin

[former_member647423]

Hello Amin,

Thank you for this really helpful article. I have a couple of questions.

Can we perform a landscape transformation for SAP S/4 HANA Cloud Single Tenant Edition? And further, where will this be hosted (public cloud providers/SAP Cloud Platform)?

For a transformation from SAP ECC 6.0 in Cloud to SAP S/4 HANA, what deployment model would be most suitable and feasible?

Thank you!

[Amin-Hoque]

Hello Simran

 

"Landscape Transformation" is now called "Selective Data Transition".

You can move to SAP S/4HANA Cloud Single Tenant Edition with Selective Data Transition or a New Implementation.  You cannot do a system conversion.

SAP S/4HANA Cloud Single Tenant Edition can be hosted by SAP or Hyperscalers.

If you want to go to S/4HANA Cloud (previously called Multi Tenant Edition) the only option is a New Implementation.

Kind regards

Amin Hoque

[sreekanth1410]

Amin

For the S4 HANA cloud STE,do we have the SAP GUI available for custom code development and modifications?

[Amin-Hoque]

SAP GUI is currently available in the S/4HANA Cloud extended edition (previously called STE).  There are long term plans to limit access to SE80 and move to purely browser based access.

[nicolasfrerejean]

Hello Amin,

Can local (in-country) cloud providers provide the infrastructure services for options #2 and #4? If so, what are the requirements to be certified and provide these services?

Regards

 

[Amin-Hoque]

Hello Nicolas

Currently the cloud providers are Microsoft Azure, Google Cloud, AWS or Alibaba Cloud.

Other potential partners should contact SAP.  See https://www.sap.com/uk/partner/become.html

Regards

Amin Hoque.

[former_member662622]

Hi Amin

Really nice and helpful article. I have a couple of queries:

1. Is it possible to have SAP S/4HANA Cloud extended edition (EX) on infrastructure provided by cloud hyperscalers like AWS, AZURE? In your article you have written it is possible. However as far as I have read, this is a SAAS provided only by SAP? Please confirm.

2. Is it possible to have SAP S/4HANA Private Cloud managed by SAP (HEC) infrastructure provided by other hyperscalers like AWS, AZURE?

 

Thanks

Akhilesh

[Amin-Hoque]

Hello Akhilesh

1. Yes, SAP S/4HANA Cloud extended edition is available with infrastructure provided by MS Azure or AWS.  It remains a SAAS offering with SAP.  SAP partner with the hyperscaler.  See standard slide below.
2. No, the private cloud is only available with SAP (HEC) infrastructure.

Kind regards

Amin Hoque.

[kamal264]

Thanks Amin for nice and informative blog.

I have few queries and will be great if you can help -

1. Do we get SAP Data Services as free with STE.

2. Is there any difference in Migration cockpit approach in different deployed solutions like on premise or STE.

3. How can I check which version or S4 hana deployment we are using.

Regards,

Kamal

 

[FlavioMolina1]

Amin is coorect the afirmation that deployment option 3 (SAP S/4HANA Private Cloud managed by SAP (HEC)) has same functionalities that deployment option 4 (SAP S/4HANA On-Premise).

BR

Molina

[john_pawski]

Amin,  The S/4 MTE(ES) edition is only hosted and managed by SAP and there is not much in the area of customization, correct?

[Amin-Hoque]

Hello John

Yes, S/4 Essential edition is only hosted by SAP.

There is configuration through SSCUIs in Essential Edition but no access to the full IMG which has 1000s of configuration activities. Release 2002 has 1633 SSCUIs. For configuration approach see this page of the roadmap viewer. https://go.support.sap.com/roadmapviewer/#/group//roadmap/IMPS4HANACLDENMGMT/node/001999B7BD851ED68D...

See the PDF called Using Configure Your Solution and SSCUIs.pdf (SAP Customer)

Cheers

Amin

[Amin-Hoque]

Hi Kamal

With Essential Edition, you use the SAP Data Migration Cockpit on its own. See this presentation in the SAP Learning Hub:

https://jam2.sapjam.com/groups/5gwxDPWQPRtOvMO8Xnd32Q/documents/rYDXIPTtHeckofh5x51Erq/slide_viewer

With the other deployment approaches, you can also choose to use SAP Data Services for Extract Transform Load (ETL) e.g. Analysis, Extract, Clean, Validate, Load and Reconcile.

See the new openSAP course: https://open.sap.com/courses/s4h16

I do not know whether Data Services is included in extended edition. Contact your IT team to find out what deployment you are using.

Kind regards

Amin Hoque.

[ralfcaelen1991]

Dear Amin,

Thank you for this great overview of the different options.

Is there also a functional difference between the two cloud editions?

1. SAP S/4HANA Cloud essentials edition (ES): previously called Multi-Tenant Edition.


2. SAP S/4HANA Cloud extended edition (EX): previously called Single-Tenant Edition.

[Amin-Hoque]

Hello Caelen

Yes.  Currently, Extended Edition offers nearly all of the scope of regular SAP S/4HANA on-premise. Nearly all the configuration is available.

Essentials Edition offers a reduced set of the on-premise functionality, transactions, industries, countries and languages.  It is a simplified version of ERP.  The configuration is also reduced meaning that there is less flexibility than in on-premise.

Cheers

Amin

 

[former_member667807]

Hi Amin,

This is insightful and brings clarity.

Also, does SAP MTE ( now ES) support multi-country instances e.g 1instance for US business & other for APAC/China?

How mature is the SAP MTE product for China in terms of local compliance (Data regulations, tax & Payment gateway integrations)?

[Amin-Hoque]

Hello Mustafa

Yes. SAP ES can have many countries all running in one instance. The solution for China draws on the same codeline (product) as the on-premise solution.  There are many features for country localisations. It would be best for you to look at the scope items for China in BPX at this link: https://rapid.sap.com/bp/#/BP_CLD_ENTPR/S4CLD/2005/CN/20

I do not know whether there are specific on-premise features for China that are not in S/4HANA Cloud Essentials Edition.

Regards

Amin Hoque

[federico_pagliaro]

Thanks Amin for this very interesting overview.

Regarding S/4 HANA cloud STE (or EX), assuming to use the ABAP restricted functionality and all new syntax rules.

It is possible to create ABAP custom development into the system or we need to assume that only side-by-side and extension-in-app are possible? Shortly, can I create a custom report with, for example, user parameters and an ALV output and run this from SAPGUI?

Thanks in advance and regards

Federico

[manjudv]

• Single Tenant Edition (STE) is hosted by SAP, does it means that we are hosting in HEC?


• Is there any difference between Hosted by SAP and Hosted by HEC?

[Amin-Hoque]

Hello Federico

Always refer to this SAP note: https://launchpad.support.sap.com/#/notes/2920697.  It is called "Extensibility Guide for SAP S/4HANA Cloud, extended edition".  Things can change from time to time.

I found this in the SAP Activate roadmap: https://go.support.sap.com/roadmapviewer/#/group//roadmap/5368adff269741c9/node/901B0E6D3F501ED8A2DE...

Cheers

Amin

[michael_piesche]

manju7dv, EX and HEC are not the same. One is the Cloud version, the other is the On-Premise version. That is a huge difference. 

[manjudv]

In this Webinar, they said EX is hosted by HEC. https://gateway.on24.com/wcc/gateway/elitesapenterprisesupport/1904844/  My doubt is

• What's the difference between HEC and Private Cloud?


• Where we can deploy EX? Is it just by HEC?


• In about comment Amin Hoque said, EX can be hosted by SAP? Does it mean we are hosted by HEC?

[michael_piesche]

• SAP HEC (HANA Enterprise Cloud) is a managed, private cloud hosting service for SAP HANA. And in the context of the given deployment options it can be used to host the S/4 HANA on-premise version. HEC is a infrastructure-as-a-service.


• Private Cloud means, that you dont share the cloud environment that is hosted by someone else and somewhere else, (someone other than you and somewhere else than your infrastructure)


• If you opt for HEC, the infrastructure as a service, which is managed by SAP, you can either have the S/4 HANA on premise version running on it or the S/4 HANA Cloud Extended Version (EX). Thats how I understand it.

[manjudv]

Thank you. i got it now

[former_member667807]

Very nicely explained and a timely article!

[danielussarz]

Hello Amin,

With reference to option 2., what do you mean by "There is a minimum number of users." Does it mean that the EX edition intended for small/midsize companies. Cou you pls comment on this, why, how many users, limitations etc.

Thanks, Daniel

[Amin-Hoque]

Hi Daniel

This means Essentials Edition is not available to small organizations.  It is for mid size and large only.  The minimum number of users changes from time to time.

Regards

Amin

[former_member249644]

Hi Amin,

 

Thanks for explaining the deployment options.

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

[Amin-Hoque]

Hello Ankit

I am sorry but your question goes beyond my knowledge of Extended Edition features. I suggest you try posting a questions into the community described here:

https://blogs.sap.com/2020/05/20/welcome-to-the-sap-s-4hana-cloud-extended-edition-customer-communit...

Cheers

Amin

[thomas_hofmann]

Hello Armin,

First of all thank you for your very concise and informative overview.

I can tell you from my discussions with customers as a former SAP colleague there is still a lot of confusion and misleading information out in the market.

In your response to Steven Wong's comment last November you mentioned that S/4HANA Single Tenant (now Extended Edition) is only offered by SAP. However, in your current version you mention that also hyperscalers can manage this option. Am I missing something here or has this changed with the renaming?

Thank you for helping to clarify this.

Best regards,
Thomas

 

[former_member728829]

Amin, thank you for the blog. It provided great information. Couple of aspects I am not clear about is related Infrastructure and Extensibility.

S/4HANA Cloud Private Edition : You blog says ' Infrastructure: dedicated landscape on cloud Infrastructure operated by SAP and running at a Hyperscaler e.g. Microsoft Azure, AWS, Google Cloud). But your reply to one of the questions says 'No, the private cloud is only available with SAP (HEC) infrastructure'. So, I am not a bit confused here. Can S/4HANA Cloud Private Edition be hosted only on SAP HEC or can be hosted on both HEC as well as Hyperscalers?

Extensibility in case of S/4HANA Cloud Essentials Edition: I read in another blog that in-app extensibility can be done without impacting other tenants. Is it correct?

Thank you.

Regards,

Kiran

[Amin-Hoque]

Hello

The new SAP S/4HANA Cloud private edition can be hosted by a Hyperscaler.  Private Edition is new in 2021.  The previous question was before it launched in 2020.

Yes...  in-app extensibility can be done in S/4HANA Cloud (essential edition) without impacting any other tenants.

Amin

[Amin-Hoque]

This has now changed with the launch of S/4HANA Cloud private edition in 2021.

[former_member728829]

Thanks a lot, Amin. So, can I conclude as follows:

 

Thank you.

Regards,

Kiran Maddineni

[WRoeckelein]

Thank you amin.hoque for keeping this blog up-to-date!

As announced on TechEd there are plans to offer an "embedded steampunk" in some of the S/4HANA Cloud Variants. Could you add information on where this is to be expected?

 

Regards,

Wolfgang

[Amin-Hoque]

Hello Wolfgang

This is planned for SAP S/4HANA Cloud (public version previously called Essentials).  There is no firm release date.  Initially, it would be for new customers only.

Amin Hoque

[former_member729916]

Dear Amin,

I'd like to set the same settings in on-premise, what I could do in the 'Manage my solutions' application in case of cloud, e.g. function or type for "Teams and Responsibilities" application. How could I do in on-premise system? Could you help me, what is the same point in SPRO?

Thank you,

Bence

[Amin-Hoque]

Hello

Note: some SSCUIs do not have an equivalent IMG activity in SPRO.

Go to this SAP Activate page:

https://go.support.sap.com/roadmapviewer/#/group//roadmap/IMPS4HANACLDENMGMT/node/001999B7BD851ED68D...

Open the Excel:

Expert Configuration and SSCUI Reference.xlsm (SAP Customer)

Find your SSCUI.  The column Activity ID has the technical name of the IMG activity.   You can try searching on this in SPRO.  If that does not work:

To find the transaction code for the IMG activity use SE16 on table CUS_IMGACH with the Activity ID.

Kind regards

Amin

Cheers

Amin

 

[former_member748164]

Hi Experts,

I am seeing SAP ERP PCE also (in HEC Agreement Site). Looks like starting this year ERP PCE is also possible. If I am not wrong this is old BS (ECC) as/in PCE offering? Can somebody comment on this? I still don't get it why SAP has come up with this offering?

Suggest/Validate below deployment table as well:

S4 Deployments

[AdilZafar]

Hi Mukul

SAP ERP on RISE with SAP is offered as an interim step to PCE which is based on S/4HANA. SAP ERP on HANA along with all SAP products being moved to RISE will need to be on ASE or HANA DB.

Thanks

Adil

[Amin-Hoque]

Hello

SAP S/4HANA Cloud Private Edition (previously referred to as PCE) is new in 2021. It is the S/4 on-premise software solution stack offered in a private cloud (managed by hyperscalers).  Key point is that existing ERP customers can move to it using a System Conversion. This was no possible in previous cloud editions. It is available under a RISE subscription contract.

Kind regards

Amin Hoque.

[janwillemhofstee]

Dear Amin,

Thank you for this wonderful overview of the different options.

Is there by any chance also an outline of the functionalities the different options offers, or at least where they deviate from each other? I understand that the Essentials Edition offers a reduced set compared to the on-prem version, but I would like to understand what functionality is currently not supported by S/4HANA Cloud (essentials edition) compared to e.g. the on-prem version.

Many thanks for your feedback.

 

Cheers, Jan Willem

[Amin-Hoque]

Hello Jan Willem

SAP S/4HANA Cloud (previously Essentials Edition) is the only option with less solution functionality.

For detail, I would suggest you compare the Feature Scope Descriptions of S/4HANA Cloud with S/4HANA.  These are in the help.sap.com.  This also includes country availability.  Contents page give a summary.

https://help.sap.com/doc/7c9e0bbbd1664c2581b2038a1c7ae4b3/2105.500/en-US/FSD_CE2105.pdf

https://help.sap.com/doc/e2048712f0ab45e791e6d15ba5e20c68/2020/en-US/FSD_OP2020_latest.pdf

Kind regards

Amin Hoque

[former_member359828]

Hello Amin,

You mention that with S/4HANA Cloud EX only greenfield is possible. Other sources state that also System Conversion and Selective Data Transition is possible with EX.
I would like to know if an existing S/4HANA system can be migrated to S/4HANA Cloud EX?

Thanks and kind regards

Julia

[Amin-Hoque]

Hello Julia

My understanding is that SAP S/4HANA Cloud private edition must be used to do System Conversion and Selective Data Transition.  This is option 3 in the blog.  It is similar to the old Extended Edition (option 2) but SAP does not own subsequent upgrades. This would be the normal approach.

Kind regards

Amin Hoque.