What S/4HANA Public Cloud Gives You Natively vs What Needs Sales/Service Cloud V2

Does S/4HANA Public Cloud include CRM? It is one of the questions we hear most often from DACH companies evaluating their SAP landscape.

TL;DR: S/4HANA Public Cloud covers the transactional side of selling and servicing (orders, quotations, contracts, billing, service orders and contracts) but it is not a front-office CRM. Pipeline, leads, forecasting and field sales activity need Sales Cloud V2; multi-channel case handling with SLA timers and an agent workspace needs SAP Service Cloud V2. The two layers connect through SAP Integration Suite, with S/4HANA staying the master for customers, products, prices and orders.

This post maps the boundary so you can decide what you actually need.

Does S/4HANA Public Cloud include CRM?

S/4HANA Public Cloud is an ERP system. Its sales capabilities are built to process transactions, not to manage sales activity. That distinction gets blurred in vendor conversations, and it causes problems when companies build their landscape assumptions around it.

In the customer-facing layer, S/4HANA records what happened: a quotation was created, a customer placed an order, an invoice was issued. These records are accurate, auditable and ERP-grade.

What it does not do is help your sales team see what is likely to happen next. There is no opportunity pipeline, no lead management, no deal stage tracking and no guided selling. Those tools live in Sales Cloud V2.

The same logic holds on the service side. S/4HANA Public Cloud handles back-office service: service orders, service contracts, returns and repairs. It does not route inbound customer contacts from phone, email and chat into cases, and it does not give agents one workspace across those channels. That is Service Cloud V2’s job.

This is not a product gap but the original design: the ERP handles back-office precision, the CX cloud handles front-office productivity. Trouble starts when companies assume one system does the work of both.

What S/4HANA Public Cloud covers natively

S/4HANA Public Cloud ships with SAP-standard sales, order and service management. SAP documents the standard scope in the S/4HANA Cloud Public Edition documentation. No extra products are needed for the following:

Order to cash. Sales orders, delivery processing, goods issue and billing are in the core, integrated with logistics and finance.

Sales documents. Inquiries, quotations and contracts are supported natively. Pricing conditions and customer-specific prices live in S/4HANA and flow into the Sales Cloud V2 quote once you add the CX layer.

Business Partner. The authoritative record for customer and supplier data. When you integrate Sales Cloud V2, the Business Partner is replicated outward and S/4HANA stays the source of truth.

ERP view of the customer. Within S/4HANA, users can see an account’s order history, open deliveries, billing documents and credit status. That is a view of what happened in the back office, not a pipeline view: it tells you what was sold, not what is in progress.

Back-office service. Service orders, service contracts, returns and credit memos run through standard ERP processes. That is different from multi-channel case management, which requires Service Cloud V2.

In practice, DACH companies on S/4HANA Public Cloud without the CX layer manage sales activity in spreadsheets, shared inboxes or bolt-on tools. The ERP gives them accurate order data and nothing on the pipeline.

What needs Sales Cloud V2

Sales Cloud V2 is the front-office layer: everything that happens before an order exists in S/4HANA, and everything that helps salespeople get there. The Sales Cloud V2 documentation describes the full scope.

Pipeline and opportunity management. Lead capture, opportunity stages, weighted pipeline and deal reviews. When a customer shows interest, that activity lives in Sales Cloud V2 until it becomes a quotation or order.

The lead-to-order flow. In the integrated stack, leads arrive in Sales Cloud V2, progress through opportunities, produce quotations with prices from S/4HANA and become orders that go to S/4HANA for fulfilment, using SAP’s standard integration content for Sales Cloud V2 and S/4HANA Cloud Public Edition.

AI-assisted selling on pipeline data. Joule is available across SAP’s cloud applications, including S/4HANA. The seller-facing AI (flagging deals at risk, suggesting next steps, drafting follow-ups from call notes) works on opportunity and activity data, which only exists once Sales Cloud V2 is in place.

Field sales activity. Call logs, meeting notes, visit planning and calendar integration. S/4HANA has little to offer here.

Commercial forecasting. Revenue forecasts rolled up by territory and product line, adjusted by managers, are a Sales Cloud V2 function. Planning in S/4HANA serves supply chain and finance, not the sales forecast.

For how the two connect technically, see our integrated stack guide and the quote-to-cash walkthrough.

What needs Service Cloud V2

Service Cloud V2 covers the customer contact side of service; the Service Cloud V2 documentation lists its capabilities.

Multi-channel case handling. Phone, email, chat and web forms arrive in one queue with a single agent view. S/4HANA executes service orders; it does not turn multi-channel contacts into cases.

SLA timers and escalation on cases. Response and resolution targets on each case, with escalation when a target is at risk. Service contracts in S/4HANA can carry service commitments, but the case-level timer and routing sit in Service Cloud V2.

Knowledge for agents. A structured knowledge base with suggested articles, so agents do not search across disconnected systems.

Field service. For companies that dispatch technicians, Service Cloud V2 and S/4HANA connect with SAP Field Service Management for scheduling, parts and work orders. Our post on SAP FSM with S/4HANA Public Cloud covers that setup, and the Service Cloud V2 and S/4HANA integration guide covers the case-to-resolution flow.

For a head-to-head against a single-vendor CRM suite, see our S/4HANA Public Cloud + Sales Cloud V2 vs Salesforce comparison.

A capability decision table

“Native” means available in the S/4HANA Public Cloud standard. “Needs Sales Cloud V2” or “Needs Service Cloud V2” means a separately licensed product is required.

Capability	S/4HANA Public Cloud (native)	Needs Sales Cloud V2	Needs Service Cloud V2
Sales order creation and processing	✓	-	-
Inquiries, quotations and contracts	✓	-	-
Billing and invoice management	✓	-	-
Business Partner (customer master)	✓	-	-
ERP customer view (orders, billing, credit)	✓	-	-
Service orders, service contracts, returns	✓	-	-
Opportunity pipeline management	-	✓	-
Lead capture and lead management	-	✓	-
Sales activity logging (calls, visits, tasks)	-	✓	-
Commercial forecasting	-	✓	-
AI-assisted selling on pipeline data	-	✓	-
Quoting in the CRM with S/4HANA pricing	-	✓	-
Order handoff from the CRM to S/4HANA	-	✓	-
Multi-channel case management (phone, email, chat)	-	-	✓
Case SLA timers and escalation routing	-	-	✓
Agent knowledge base and article suggestions	-	-	✓
Case-driven field service with SAP FSM	-	-	✓

What the table does not show: S/4HANA Public Cloud and the CX products share data through SAP Integration Suite, so the boundary is a handoff, not a wall. Prices from S/4HANA appear in the Sales Cloud V2 quote, and orders created in Sales Cloud go to S/4HANA for fulfilment.

Do you need the CX layer at all?

The real question is not whether S/4HANA can do it; in the front-office sense it usually cannot. The question is whether your sales or service volume justifies a dedicated front-office system. For most DACH mid-market companies with a structured sales team, or a service desk handling a steady flow of cases, it does.

We deliver both layers with one team. At intelligentfood, Spadoom delivered Sales Cloud V2, the integration with Cloud ERP and work in parts of MM and SD. Our guide to the best SAP partner for Cloud ERP and CRM in Switzerland explains why one owner for the boundary matters. To size the right scope for your situation, the five-day S/4HANA readiness assessment produces scope, sequence and a cost range across ERP and CX, as the first step of an ERP and CX transformation. Or talk to us.