Quote-to-Cash Between SAP Sales Cloud V2 and S/4HANA Public Cloud: Who Owns Which Document?

When a CRM and an ERP carry the same sales process, one question decides whether the integration lasts for years or turns into a permanent construction site: who owns which document? Not which interface you pick or which mapping tool, but in which system a quote is born, where the order is born, and who is allowed to change what. Almost every painful quote-to-cash integration we have been asked to fix had no clear answer to this at the start.

For SAP Sales Cloud V2 and S/4HANA Public Cloud, there is a clean answer. It follows from SAP’s standard integration content if you read it consistently. Here it is, including the spots where projects typically stumble.

TL;DR: Every object has exactly one leading system. Customers, products and prices are led by S/4HANA Public Cloud; the quote is led by Sales Cloud V2; the sales order is created in S/4HANA as a follow-up document and replicated back read-only. Prices are simulated live in S/4HANA instead of being maintained twice. Settle the status level of quotes and a governed list of rejection reasons before the first iFlow is built, and agree who fixes which failed message.

The ownership matrix: one object, one leading system

The ground rule is simple: every object has exactly one leading system. That is where it is created and changed. Everywhere else it is a copy, and copies are read-only.

Object	Leading system	In the other system
Customers (business partners)	S/4HANA Public Cloud	replicated to the CRM
Products	S/4HANA Public Cloud	replicated to the CRM, read-only there
Prices and conditions	S/4HANA Public Cloud	simulated live from the quote, not maintained in the CRM
Quote	Sales Cloud V2	becomes a follow-up sales order in S/4HANA
Sales order	S/4HANA Public Cloud	replicated to the CRM, read-only there

The quote is born in the CRM because that is where sales works: opportunity, contact history and activities in one view. The sales order is born in S/4HANA because that is where availability, credit limit, logistics and billing live. The transition runs as a follow-up document through the standard iFlows of SAP Integration Suite, published on the SAP Business Accelerator Hub as the integration package for sales processes between Sales Cloud V2 and S/4HANA Cloud Public Edition. In the return direction, the order appears in the CRM as a replicated document that sales can see but not change.

This matrix belongs on the project room wall before the first iFlow is deployed. It matters more than any technical design document. For the full technical picture, see the Sales Cloud V2 integration architecture.

Live pricing: one price truth, not two

The most elegant part of this architecture is the part that is not maintained twice: pricing. While the rep enters a line item, the CRM quote is simulated in S/4HANA and the price comes back with conditions, customer-specific prices, scales and discounts. SAP describes the setup in its help on integrating Sales Cloud V2 with S/4HANA Cloud Public Edition for simulation and transfer.

SAP’s master data package can also replicate pricing conditions into the CRM. We use the simulation wherever the connection allows it. As soon as prices are maintained or calculated in two places, you have two price truths, and sooner or later someone quotes with the wrong one. With live pricing there is exactly one place where conditions are maintained, and the quote calculates with the same numbers as the order and the invoice later on: no reconciliation job, no awkward conversation about why quote and invoice differ.

Two pitfalls from real projects

The architecture above is tidy. In our experience, projects did not stumble on the technology but on two functional details nobody had settled before the build.

Pitfall 1: the won/lost status lived on two levels. In one project, the ERP tracked quote status at header level: a quote is won or lost. The CRM tracked the same status per line item, because a customer can order three out of five items. Both are defensible; both at once are poison. The win-rate analytics in the CRM counted line items, the ERP reporting counted headers, and management was shown two figures that were far apart. Define the status level once, identically on both sides, before the first integration piece is built. Changing it afterwards costs many times more.

Pitfall 2: rejection reasons as free text. Why was a quote lost? With a free-text field you get “price”, “too expensive”, “price too high”, “competitor cheaper” and forty more variants of the same reason, and reporting is dead before it starts. Rejection reasons belong in a governed value list, mapped identically on both sides, with an owner who approves new values. One hour of governance in the concept phase saves years of useless analytics.

If your quotes involve configurable products, the same ownership logic applies to the configuration; our post on quoting configurable products with Sales Cloud V2 and AVC shows how, and when SAP CPQ is needed with S/4HANA Public Cloud covers the heavier case.

Monitoring: who fixes what

Replication means asynchronous messages, and asynchronous messages fail from time to time: a customer without a valid VAT number, a blocked product, a mapping value that does not exist on the target side. That is normal. What is not normal is nobody noticing.

Integration Suite message monitoring shows every failed message with payload and error reason. On top of that belongs alerting that reaches a named person instead of gathering dust in a shared inbox. Then settle the responsibility question before go-live: the CRM administrator fixes what originates in the CRM (quote data, missing mandatory fields, CRM-side value mappings); the ERP key user fixes what is rooted in the ERP (master data errors, condition problems, blocked business partners). Without this split, every failed message travels back and forth between two teams before anyone touches it.

The one rule that holds it all together

If you take one sentence from this article, take this one: the same document type must never be editable in two systems. The moment an order can be changed in the CRM and in the ERP, the race of versions begins, and the integration becomes a referee that can only lose. SAP’s standard integration largely enforces the rule itself, because replicated documents are read-only on the other side. Resist every requirement to soften it through an extension; the exception that feels convenient today is the reconciliation workshop of the day after tomorrow.

This is also where finance and sales meet, which is why we plan quote-to-cash with ERP and CRM consultants in the same room; our guide to the best SAP partner for Cloud ERP and CRM in Switzerland explains why that matters, and the integrated S/4HANA Public Cloud and Sales Cloud V2 stack shows the whole picture.

Frequently asked questions

Can orders also be created directly in the CRM?

Technically yes: Sales Cloud V2 has a sales order object, and SAP’s standard content can replicate it to S/4HANA. We still recommend quote in the CRM and order in the ERP, because the order needs availability, credit limit and logistics data from S/4HANA. An order captured in the CRM is at best a pre-entry that is checked again in the ERP, which means one more place to maintain data.

Are quotes replicated back from S/4HANA Public Cloud into the CRM?

Not as Sales Cloud V2 quotes. The standard content can create a follow-up quote in S/4HANA from an opportunity and keeps the reference on the opportunity, but quotes created in the ERP do not become CRM quotes. That is one more reason to let quotes be born in the CRM, so the sales view stays complete.

What about field sales without network coverage?

Live pricing needs a connection to S/4HANA. Offline, field sales can capture items and quantities, and binding pricing runs once the device is back online. For the customer meeting, a guide price on the product master, clearly marked as non-binding, has worked well for us.

What happens when a replication fails?

The message stays in SAP Integration Suite message monitoring with payload and error reason and can be reprocessed after the correction. What decides the outcome is alerting and a responsibility split agreed up front: the CRM administrator for CRM-side causes, the ERP key user for master data and condition errors. Then a failure is a matter of minutes, not weeks.

---

Planning the integration of Sales Cloud V2 and S/4HANA Public Cloud, or does your existing one produce two truths? We will put the ownership matrix on the wall with you. If S/4HANA Public Cloud is still ahead of you, start with the S/4HANA readiness assessment. Talk to our team.