SAP Cloud ERP (S/4HANA Public Cloud)

What is SAP S/4HANA Public Cloud?

SAP Cloud ERP (SAP S/4HANA Cloud Public Edition) is SAP’s multi-tenant software-as-a-service ERP for finance, procurement, sales, supply chain and operations. It ships processes based on SAP Best Practices, SAP operates the software and delivers the releases, and the core stays clean: extensions use released key-user and developer extensibility or run side by side on SAP BTP. It is sold as a subscription, usually through GROW with SAP.

S/4HANA Public Cloud is one of three ways to run S/4HANA, next to the Private Edition and on-premise. We assess the available scope items, country requirements and integration needs with you. Product features and licence entitlements depend on your contract and release. This page compares the editions, shows what the ERP covers and where CRM begins, and explains how we deliver it.

We deliver the core.

The consultants in our S/4HANA team have implemented Public Cloud projects before, including SkyCell’s five-month rollout, delivered at Actum Digital Schweiz by the team that now works at Spadoom. Today they implement your ERP and connect it to sales, service and commerce in one programme.

Spadoom implements S/4HANA Public Cloud with its own team. We lead fit-to-standard workshops, configure the agreed processes, migrate data and build the integration with SAP CX. One programme connects the ERP core and the customer-facing systems. Your named project team owns the agreed scope.

Our practice grew from cloud commerce and customer experience into Cloud ERP. The colleagues in our ERP team bring experience in public-cloud architecture, finance, procurement and logistics. Their experience is distinct from the customer projects published below.

That combination is the point for you. CX projects rarely fail inside the CRM; they fail at the ERP seam: the order that will not post, the price the quote cannot resolve, the service case with no material behind it. Spadoom is the only Swiss-headquartered SAP Gold Partner that delivers the ERP core and the complete CX stack with one team, so one party owns each of those seams.

Plan your readiness check

Public Cloud vs Private Cloud vs on-premise: the editions compared

SAP sells S/4HANA in three deployment models, and the names invite confusion. The differences are structural:

	Public Edition	Private Edition	On-premise (incl. ECC)
Tenancy	Multi-tenant SaaS	Single tenant, operated for you	Your data centre or your own cloud
Commercial offering	GROW with SAP	RISE with SAP	Licence plus maintenance
Upgrades	Delivered by SAP on a fixed release cycle	Scheduled by you within SAP’s maintenance windows	Your own upgrade projects
Extensions	Released key-user and developer extensibility, side-by-side on BTP	Classic ABAP possible; clean core recommended	Unrestricted, with upgrade effort to match
Path from ECC	New implementation	System conversion or new implementation	Already there
Licence metric	Subscription, Full User Equivalents (FUE)	Subscription, Full User Equivalents (FUE)	Perpetual licence and maintenance fees
Maintenance horizon	Continuous	Continuous	ECC mainstream maintenance ends 2027 (optional extended maintenance to 2030)

The short version: Public Edition fits companies willing to adopt SAP standard processes, which covers most new implementations in the midsize segment. Private Edition fits companies with deep customisation that still want an SAP-operated system and a conversion path. On-premise ECC needs a decision before 2027, which is why the edition question is on so many Swiss agendas right now.

Standardisation in the Public Edition is a deliberate design choice. It does mean that requirements which once became Z-tables need another home. For many of them that home is SAP BTP, and designing what lives there is part of our work. More on this under clean core below.

What S/4HANA Public Cloud covers natively

The Public Edition is a full ERP. Through preconfigured scope items it covers finance and accounting, order-to-cash (sales orders, deliveries, billing), procure-to-pay, manufacturing, inventory and supply chain, project and professional services, and embedded analytics on live ERP data. The business partner model is the authoritative record for customer and supplier master data. Joule, SAP’s AI assistant, is available in the product; which Joule functions you can use depends on your release and licence (see SAP Business AI).

What the ERP records, it records precisely: a quotation was created, an order was placed, an invoice was issued. Within the ERP, users see order history, open deliveries, billing documents and credit status per customer.

What it deliberately does not try to be is a front-office system. That boundary deserves its own section.

Does S/4HANA Public Cloud include CRM?

Not in the front-office sense, and knowing where the line runs saves expensive assumptions about your landscape.

Native to the ERP: transactional sales documents (inquiries, quotations, contracts), order processing, billing and the ERP-side customer view. Not native: opportunity pipeline, lead capture and qualification, guided selling, sales forecasting and structured visit planning. That is the job of SAP Sales Cloud V2. Omnichannel case management, SLA tracking and agent knowledge live in SAP Service Cloud V2, not in the ERP.

This is a design choice: the ERP handles back-office precision, the CX clouds handle front-office work, and both share the customer master. Companies on S/4HANA Public Cloud without a CX layer often manage their pipeline in spreadsheets next to a very accurate order history. We mapped the boundary line by line in what S/4HANA Public Cloud gives you natively vs what needs Sales and Service Cloud V2.

For you this is where the one-team argument becomes concrete. The CRM project and the ERP project meet at four hand-offs: the quote that must become a sales order, the price the quote needs from the ERP, the service case that needs material and equipment data, and a customer master that must not be owned twice. We deliver S/4HANA Public Cloud and Sales and Service Cloud V2 together, so each hand-off has one owner. If you are mainly looking for CX delivery, our page on SAP CX consulting in Switzerland covers that side.

The integrated stack: S/4HANA Public Cloud with Sales and Service Cloud V2

S/4HANA Public Cloud and Sales Cloud V2 work on the same business partner. When a sales rep opens an account, they see the customer record finance works with, including payment terms, credit status and open invoices. Quotes are built on pricing conditions from the ERP, not on a spreadsheet the rep maintains. A won deal posts as a sales order in S/4HANA; delivery and invoice status flow back into the CX view. A service agent in Service Cloud V2 sees the equipment the customer bought and the orders still in fulfilment.

A third-party CRM can be connected too, but it needs a mapping between two different data models that someone must license, monitor and maintain. We wrote up the comparison, including when another CRM still makes sense, in why Sales Cloud V2 fits an S/4HANA Public Cloud landscape and in S/4HANA Public Cloud with Sales Cloud V2 vs Salesforce.

For the architecture itself (master data flow, the quote-to-order-to-invoice loop, where the logic lives) see the integrated CX and ERP stack guide and the deep dives on the Sales Cloud V2 integration architecture and the Service Cloud V2 integration.

A transformation, delivered in stages

We start with the business process, not a list of products. ERP-first establishes the master data and finance processes, and the CX layer then goes live against clean source data; the cost is that your sales team waits. CX-first can deliver earlier value but may require an interim integration with ECC that is rebuilt when S/4HANA arrives. Parallel delivery needs shared milestones, one integration owner and key-user capacity; without those, two projects compete for the same people. The assessment determines which sequence fits your business.

For the CX layer, our Sales and Service Cloud V2 projects reach go-live in a median of 14 weeks, typically 8 to 16 weeks depending on integrations and countries. The ERP timeline is agreed after the readiness check, once process, data and country scope are understood. The sequencing logic and sync points are described in rolling out S/4HANA Public Cloud and Sales Cloud V2 together. The wider picture, from ECC to a connected ERP and CX landscape, is on our transformation page.

Clean core leaves room for your business

Clean core does not mean “no configuration” or “all custom code must move to BTP”. Public Edition supports configuration, released key-user and developer extensions, and side-by-side extensions on BTP. We choose the supported option for each requirement and include integration and regression testing in the release plan.

For CX integration the practical consequence is simple: the integration layer stays above the line. APIs and events are the contract; mappings and validations live in SAP Integration Suite or in side-by-side apps. If a CX requirement seems to need a modification inside S/4HANA, that is the signal to redesign the flow. We describe the extension pattern in clean core with SAP CAP.

ECC: plan the transition with the right dates

SAP’s mainstream maintenance for the last three enhancement packages of Business Suite 7 ends in 2027. Optional extended maintenance runs to the end of 2030 under SAP’s conditions. That is not an automatic shutdown of ECC. Public Edition requires a new implementation rather than an in-place ECC conversion. We assess data retention and an archive, potentially on AWS, separately: access, legal retention, licences and operating costs must work before the old system is retired.

What the customer references show

intelligentfood demonstrates our Sales & Service Cloud V2 delivery and Cloud ERP integration, including work in parts of MM and SD. The three-month figure relates to the Sales & Service platform. Meier Tobler demonstrates our Integration Suite hub between the online shop and S/4HANA. SkyCell is a Public Cloud reference from Actum Digital Schweiz: a five-month project whose team now works mostly at Spadoom. The SkyCell reference describes the experience of our current team at its previous employer.

Pricing and licensing

S/4HANA Public Cloud is licensed as a subscription. The user metric is Full User Equivalents (FUE): different user types (for example advanced, core and self-service users) count as different fractions of the contracted total. Commercially, the Public Edition usually comes in a GROW with SAP contract, which bundles the ERP subscription with SAP BTP entitlements, SAP Activate and the Best Practices content. The subscription price comes from SAP’s offer for your company; we do not publish figures for it on this page.

What drives your total cost: number and mix of users, countries and legal entities, the scope items you activate, the data migration effort and the integration and extension layer on BTP. The last item is the one most budgets underestimate, and it is where an ERP and CX partner in one team saves coordination effort.

Scope, cost and your first decision

Start with the readiness check: five consulting days, from CHF 12’000, with a fixed price agreed for the assessment scope. You receive findings, a target architecture, priorities and a phased plan with a cost range. Implementation, SAP subscriptions, extensions, migration, travel and ongoing operation are scoped separately. A full ERP programme has no blanket 14-week promise. We agree timing after process, data and country scope are understood.

What good looks like

A well-built S/4HANA Public Cloud and SAP CX landscape means:

• One business partner record: sales, service and finance look at the same customer
• Quotes priced from ERP conditions, not from a rep’s spreadsheet
• Orders that flow from CRM to fulfilment without re-entry
• Releases that land without regression panic, because the core is clean
• An integration layer someone owns, monitors and can explain

Plan your readiness check · Explore the transformation · Discuss your ERP project

SAP

• SAP Cloud ERP
• SAP S/4HANA Cloud Public Edition documentation
• GROW with SAP
• SAP maintenance strategy
• SAP clean-core extensibility