SAP S/4HANA Cloud, public edition

What is SAP S/4HANA Public Cloud?

SAP S/4HANA Cloud, public edition is SAP’s multi-tenant SaaS ERP. It ships SAP Best Practices processes out of the box, runs on an SAP-managed release cadence — two major releases a year, with continuous feature delivery in between — and enforces clean core: custom logic lives on SAP BTP, not inside the ERP. It is sold as a subscription, typically through GROW with SAP.

It is one of three ways to run S/4HANA — alongside the private edition (single-tenant, more customisation room) and on-premise. This page compares the three, maps what the public edition covers natively and what it doesn’t, and explains where Spadoom fits. To be clear from the start: we are the SAP CX and integration partner in these landscapes — Sales Cloud V2, Service Cloud V2, commerce, and the BTP integration layer — across Switzerland, Germany, Austria, and Italy. We do not lead full ERP rollouts, and we’ll tell you exactly how that split works in practice.

Case study — SAP CX on S/4HANA Public Cloud at intelligentfood

intelligentfood (Swiss FMCG, home of El Tony Mate) runs S/4HANA Public Cloud as its ERP. We delivered the customer-facing half: a fully integrated Sales & Service Cloud V2 platform, live in three months, bridged to the public-cloud ERP via SAP Integration Suite — including the configuration work on the ERP side to make the end-to-end process run without a media break. Custom BTP apps put visit planning on the field team’s phones. Read the full intelligentfood story.

Two more from the same playbook: at Miltenyi Biotec (German biotech) we orchestrated the integration of five SAP clouds — Commerce, Marketing, Customer Data Cloud, Service Cloud V2, and the S/4HANA system — into one landscape (full story). At Meier Tobler (Swiss building technology) our central SAP Integration Suite hub processes over a million messages a month, keeping shop, logistics, and S/4HANA in real-time sync (full story).

What Spadoom delivers

Spadoom is SAP CX-first. We deliver Sales Cloud V2, Service Cloud V2, Commerce, Marketing, CDP, CIAM, Loyalty, CPQ, and FSM as our core lanes. Around those lanes, S/4HANA Public Cloud is the ERP backbone our customers increasingly land on, and we are deliberately fluent in how it works.

What that means in practice: we advise on the integration architecture between S/4HANA Public Cloud and SAP CX, design the data flows that need to move both ways, and build the BTP-side extensions that keep custom logic out of the ERP. We do not lead full S/4HANA Public Cloud rollouts on our own. For that work we partner with specialised S/4HANA implementation firms and coordinate from day one of the rollout.

If your organisation is moving onto S/4HANA Public Cloud and you also need a connected SAP CX layer — sales, service, commerce, marketing — that is the conversation to have with us. We bring the CX delivery and the integration architecture; the ERP partner brings the public-cloud rollout discipline.

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, not cosmetic:

The short version: public edition fits organisations willing to adopt SAP standard processes — most greenfield rollouts and mid-market companies land here, and it is the strictest clean-core environment SAP offers. Private edition fits organisations with deep customisation that still want SAP-managed infrastructure and a brownfield path. On-premise ECC is running out of road: mainstream maintenance ends in 2027, which is why the public edition question is on so many DACH agendas right now.

One honest caveat: the public edition’s standardisation is a feature, not a limitation — but it does mean requirements that would once have become Z-tables now need a different home. That home is SAP BTP, and designing what lives there is exactly the work Spadoom does. More on that under clean core below.

What S/4HANA Public Cloud covers natively

The public edition is a full ERP, not a starter kit. Out of the box — via pre-configured SAP Best Practices 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 built in for navigation, analytics questions, and a growing set of transactional tasks.

What it records, it records well: a quotation was created, an order was placed, an invoice was issued — accurate, auditable, ERP-grade. Within the ERP UI, users get a customer 360 of order history, open deliveries, billing documents, and credit status.

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

Does S/4HANA Public Cloud include CRM?

Not in the front-office sense — and knowing where the line runs saves you from expensive landscape assumptions.

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 scoring, guided selling, commercial forecasting, structured visit planning — that is SAP Sales Cloud V2 territory. Likewise omnichannel case management, SLA tracking, and agent knowledge bases live in SAP Service Cloud V2, not in the ERP.

This is not a product gap; it is the design. ERP handles back-office precision, the CX clouds handle front-office productivity, and the two share one data model. In practice, companies on S/4HANA Public Cloud without a CX layer end up managing their pipeline in spreadsheets next to a very accurate order history. We mapped the full capability boundary — including a line-by-line decision table — in what S/4HANA Public Cloud gives you natively vs what needs Sales/Service Cloud V2.

The integrated stack: S/4HANA Public Cloud + Sales & Service Cloud V2

This is Spadoom’s actual lane — and the reason to pair the public edition with SAP CX rather than a bolt-on CRM.

S/4HANA Public Cloud and Sales Cloud V2 share the Business Partner master. When a sales rep opens an account, they see the same customer record finance works with — payment terms, credit status, open invoices included. Quotes are built on live pricing conditions from the ERP, not on a spreadsheet the rep maintains. A closed deal posts as a confirmed sales order in S/4HANA; delivery and invoice status flow back into the CX 360° view. A service agent in Service Cloud V2 sees the equipment the customer bought and the orders still in fulfilment. Joule works across the stack: one assistant that can answer about pipeline and payment history in the same conversation.

Every CRM that is not Sales Cloud V2 needs a middleware layer to do this — a mapping between two different data models that must be licensed, monitored, and maintained forever. We wrote up the honest comparison, including when a third-party CRM still makes sense, in why Sales Cloud V2 is the right CRM for an S/4HANA Public Cloud landscape and in the head-to-head S/4HANA Public Cloud + Sales Cloud V2 vs Salesforce page.

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

What clean core actually means in practice

Clean core is not a slogan. In a public-cloud ERP it is enforced architecture.

No Z-tables in the ERP. No user-exits. No enhancements bolted onto standard objects. Every customisation a previous generation of consultants would have written into the ERP itself moves to BTP as a side-by-side extension. Releases land without a regression suite the size of a small product organisation. That discipline is worth having: Gartner found 75% of ERP implementations get derailed, and custom code inside the core is a key contributor — we covered the numbers and the CAP extension pattern in clean core with SAP CAP.

For CX integration design, the practical implication is straightforward: the integration layer must stay above the line. APIs and events are the contract; transformations and validations live in Integration Suite and SAP Build. If a CX-driven requirement seems to need a change inside S/4HANA, that is the signal to redesign — not the signal to open a Z-table conversation. Custom logic does not go inside Sales Cloud V2 either, frankly — that platform has its own plug-in architecture for the same reason.

Sequencing the ERP and CX rollouts

Should the ERP or the CRM go first? We get this question weekly, and there is no universal answer — only trade-offs.

ERP-first is the safer default: S/4HANA Public Cloud establishes the Business Partner master and pricing model, then the CX layer goes live against clean source data. The cost is that your sales team waits. CX-first gets a modern CRM to the field this quarter, but you build one integration against the old ERP and rebuild it when S/4HANA arrives. Parallel delivery compresses the calendar and demands a shared programme manager plus one accountable integration owner — without those, two projects fight over the same key users.

The realistic numbers: 6–9 months for a greenfield SME ERP rollout, 10–16 weeks for the CX layer (our median: 14 weeks), and 9–15 months end to end for a sequential combined programme. The full sequencing logic, sync points, and the pitfalls we’ve seen more than once are in rolling out S/4HANA Public Cloud and Sales Cloud V2 together.

Working with implementation partners

We are deliberate about scope. The CX layer is Spadoom’s lane and we own it end to end. The ERP layer in a full S/4HANA Public Cloud rollout is delivered by a partner who does that work for a living. We coordinate with that partner from the start of the programme on three things: integration architecture between ERP and CX, data migration alignment so customer and product master flow cleanly, and the clean-core boundary so neither side carries customisation it should not.

The pattern works because the lanes are clear. Customers who try to make one firm own everything either get a CX layer that is an afterthought, or an ERP rollout that is a CX afterthought. We have seen both. The version that works has each partner owning their lane and the integration designed jointly from week one.

Pricing and licensing

SAP does not publish list prices for S/4HANA Cloud, public edition. Licensing is a subscription sized in Full User Equivalents (FUE) — a weighting metric where different user types (advanced, core, self-service) consume different fractions of the contracted total. Commercially, the public edition usually arrives inside a GROW with SAP contract, which bundles the ERP subscription with SAP BTP entitlements, SAP Activate, and the Best Practices content.

What actually drives your total cost: user count and mix, number of countries and legal entities, the scope items you activate, data migration effort, and — the part most budgets underestimate — the integration and extension layer on BTP. That last part is where we work. Spadoom scopes the SAP CX and integration side at fixed prices, so at least half of your programme budget is known before signing. The ERP subscription itself is quoted by SAP or your ERP implementation partner; we’ll happily sit on your side of the table when that conversation happens.

What good looks like

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

• One Business Partner record — sales, service, and finance look at the same customer
• Quotes priced from live 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 actually owns, monitors, and can explain

If you are scoping a programme that pairs S/4HANA Public Cloud with SAP CX and want to talk through how the handoff between ERP partner and CX partner works in practice, that is the conversation we are set up for. Discuss your project — no pitch deck, just a conversation.