Sales Orders from SAP Sales Cloud V2 to S/4HANA Public Cloud: How the Standard Integration Works

To send a sales order from SAP Sales Cloud V2 to SAP S/4HANA Cloud Public Edition, you use SAP’s standard integration content in SAP Integration Suite. There are two paths. The rep creates a follow-up sales order in S/4HANA from an approved sales quote, or the rep captures a sales order in Sales Cloud V2, simulates it against S/4HANA and transfers it. Either way S/4HANA creates the order, and its number comes back to the CRM.

TL;DR: Path one is the follow-up sales order from the quote. Path two is the CRM sales order with Simulate and Transfer, which in the public edition also needs sales order replication from S/4HANA back to Sales Cloud V2. On the S/4HANA side, simulation and transfer use communication scenario SAP_COM_0109, replication back uses SAP_COM_0287. Nothing works before business partners, products, org data and code lists match on both sides. Once transferred, the order is changed in S/4HANA, not in the CRM.

My colleagues have covered the surroundings: Sofiene Karaja the integration architecture, Marek Budik who owns which document in quote-to-cash, and Radim Trávníček how to test the quote-to-order handoff with CPQ. This post stays with the order itself.

Two paths into S/4HANA

	Follow-up order from the quote	CRM sales order with Simulate and Transfer
Where the rep starts	Approved sales quote in Sales Cloud V2	Sales order in Sales Cloud V2
What S/4HANA receives	A new sales order, created directly	The CRM order, after simulation
What stays in the CRM	A reference with the external ID	The full order, read-only after transfer
Way back	Document flow refresh, retrieval of order details	Sales order replication from S/4HANA
Typical use	Quote-led sales, the ERP owns the order	Reps who capture orders themselves

Path 1: the follow-up sales order from the quote

SAP describes this in Create Follow-Up Sales Orders in External Systems. In the quote’s Sales Orders section the rep chooses Create and selects ERP Sales Order. Another SAP help page calls the same entry External Sales Order, so expect both labels in training material.

Three conditions must hold before the button does anything:

• The pricing status of the quote is calculated successfully.
• The external order request has not started yet.
• The approval status is Approved or Approval Not Applicable.

Before that, Simulate in the side pane returns prices and taxes from S/4HANA without pricing master data in the CRM, and an optional preview fetches the order confirmation PDF.

Once the order exists, the quote shows its number as the external ID with a link into S/4HANA. When the follow-up status reaches Finished, the quote progress is set to Won and the quote status to Completed. In an opened sales order, the document flow refreshes external documents every 20 minutes; the Refresh action updates it immediately.

One detail from the same page: if such a follow-up order is also replicated back into Sales Cloud V2 as a CRM sales order, the document flow diagram does not show the link between that order and the original quote. Decide early whether you need both.

Path 2: the CRM sales order with Simulate and Transfer

The second path starts with a sales order object in Sales Cloud V2. SAP’s page on simulation and transfer explains the two steps: Simulate asks S/4HANA for prices, taxes and checks, Transfer creates the order in S/4HANA. The transfer status runs through Not Started, In Process, Finished and Interrupted. Orders on prospect accounts are Not Relevant, because a prospect has no customer in S/4HANA.

Two settings matter here:

• The order document type needs the maintenance mode Internal & External (see document types). The mode External alone means display-only orders that come from the ERP.
• Simulation can run synchronously or asynchronously. If the rep changes the order after simulating it, Transfer is disabled until the next simulation.

For the public edition, SAP’s page on integration with S/4HANA Cloud Public Edition adds a hard prerequisite: sales order replication from S/4HANA back to Sales Cloud V2 must be set up. That is how the CRM receives the external order ID and every later change made in S/4HANA. Without it, path 2 is a one-way street with no confirmation.

What runs in SAP Integration Suite

The flows come from the package SAP Sales Cloud Version 2 Integration for Sales Processes with SAP S/4HANA Cloud Public Edition on the SAP Business Accelerator Hub, version 1.0.22 on 31 October 2026. The order-relevant iFlows:

iFlow	Path
Simulate Sales Quote in SAP S4HANA Public Cloud	1
Create Follow-Up Sales Order in SAP S4HANA from Sales Quote	1
Retrieve Follow-Up Sales Order Details from SAP S4HANA Cloud	1
Delete Sales Order Reference from SAP S4HANA	1
Simulate Sales Order in SAP S4HANA Public Cloud	2
Replicate Sales Order to SAP S4HANA Public Cloud	2
Replicate Sales Order from SAP S4HANA Public Cloud	2

Two artifacts carry the prefix “Deprecated”: an older follow-up sales order flow and an older quote simulation. According to the package change log, SAP replaced them in May 2026 and the new follow-up flow uses the S/4HANA OData V4 API. Deploy the current flows, not both generations. A June 2026 fix for duplicate order creation required updating and deploying three flows together; read the change log before every package update.

Configure through externalized parameters and the value mapping only: per SAP’s note on package updates, a modified artifact no longer receives updates.

The S/4HANA side: communication arrangements

S/4HANA Cloud Public Edition exposes its APIs only through communication arrangements: a communication scenario, a communication system for the partner, and a communication user. Two scenarios carry the order flows:

• SAP_COM_0109 Sales Order Integration contains the inbound services Sales Order (A2X) and Sales Order Simulate, each as OData V2 and V4. The sales order simulation API requires this scenario.
• SAP_COM_0287 Sales Order Bulk Replication Integration sends orders from S/4HANA to Sales Cloud V2. SAP’s setup page for sales order replication lists the outbound service Sales Order - Replicate (A2A), a replication model whose name must not contain “/SAP/” or “/BDO/”, and an additional communication system with the business system ID of the Sales Cloud V2 system in uppercase letters. That last point is easy to miss.

For the quote follow-up flow, the public SAP pages do not name the arrangement explicitly. Take it from the integration guide for your release instead of guessing.

Master data that must be in place first

An order can only be created for a customer, a product and a sales area that S/4HANA knows. SAP’s guide lists the initial load order: company code, organization structure, material group, material, business partners with relationships, employees. Code lists such as distribution channels, divisions, units of measure, payment terms and Incoterms come before that.

• Business partners. The account in Sales Cloud V2 must be the replicated S/4HANA customer with sales area data, not a lookalike created in the CRM.
• Products. Replicated from S/4HANA with their sales data.
• Organisational data. Sales organisation, distribution channel and division on the order must exist as a sales area for that customer in S/4HANA.
• Pricing. Simulation does not need replicated conditions. If reps need estimated prices before a simulation, SAP offers internal pricing with imported configuration and replicated price master data.
• Employees. Workforce IDs differ between the two systems. SAP maps them through the stable work assignment external ID, so maintain it in S/4HANA before the first order carries a sales rep.

The same page names the scope items that must be active in S/4HANA: 1RO, 6KO, 5LE and 1VP.

Pitfalls we see

SAP’s documentation lists the limits, most of them on the public edition page. These are the ones that surprise project teams:

• No changes after transfer. Header attributes, products, pricing, non-internal parties, notes and attachments cannot be modified in Sales Cloud V2 after integration. Simulation, transfer, approval actions and finish are no longer available. Train reps that changes go to order management in S/4HANA.
• No schedule lines. Schedule lines are not transferred, so a rep cannot request a delivery schedule per item from the CRM.
• Item numbers differ. Item numbers are not transferred, so the line number in an S/4HANA error message may not match the CRM line.
• No delivery or billing status. These are not replicated back.
• Parties. Employee parties must be internal and cannot be used in simulation or transfer.
• Plants. SAP has extended plant handling in the order flows during 2026 (see the package change log). Check the current state against your process before you promise plant-specific orders.
• Quotes from S/4HANA. Sales Cloud V2 does not replicate sales quotes from the public edition. A quote born in the ERP stays in the ERP.

One more, from our own projects: most first test failures in this area trace back to master data, such as an account created in the CRM that was never replicated, not to the iFlow.

Setup checklist

1. Decide the path per sales process: follow-up order from the quote, CRM order with transfer, or both.
2. Check the contract: does it include SAP’s integration setup service? Then SAP sets up the communication and owns the flows (see below).
3. In S/4HANA, confirm the scope items 1RO, 6KO, 5LE and 1VP, and maintain the work assignment external ID for sales employees.
4. In SAP Integration Suite, copy the master data package and the sales process package, configure externalized parameters and security material, maintain the value mappings.
5. In S/4HANA, create the communication systems, users and the arrangements for SAP_COM_0109 and, for path 2, SAP_COM_0287 with its replication model.
6. In Sales Cloud V2, create the communication system and the communication configuration templates “Integrate Sales Quote with SAP S/4HANA” and, for path 2, “Integrate Sales Order with SAP S/4HANA Public Cloud”, with value mappings for party roles and document types.
7. Set the order document type to maintenance mode Internal & External if you use path 2.
8. Run the initial load in SAP’s order: code lists, company code, organisation, material group, material, business partners, employees.
9. Test with one customer and one product end to end: simulate, create, see the external ID, change the order in S/4HANA, see the change in the CRM.
10. Test the failures (unknown product, missing sales area, blocked customer): each must fail visibly with a readable reason.
11. Set up message monitoring in Integration Suite and in Sales Cloud V2 (Settings, Integration, Message Monitoring) and name an owner per error type.

Set up by SAP or by you

If your contract includes SAP’s integration setup service, the guide Set Up and Managed by SAP applies. SAP creates the communication users, systems and arrangements and owns, monitors and manages the integration flows. You still run the initial load and fix business data errors, and you must not alter the communication configuration SAP created. In that scope SAP lists the follow-up sales order from the quote; the follow-up quote from an opportunity is excluded. If you need path 2 or your own logic next to the standard, you run the flows in your own Integration Suite tenant.

What Spadoom does

We set up this integration on the SAP S/4HANA Public Cloud and the Sales Cloud V2 side with one team, including the SAP Integration Suite on SAP BAIP in between. That means choosing the path per process with sales, aligning sales areas and code lists before the first load, running master data replication and migration, configuring both sides, and testing the failure cases before go-live. How this fits into an ERP and CX project from one partner is described on our page on the SAP partner in Switzerland.

Want to walk through your order process? Talk to us.

Frequently asked questions

How does a sales order get from SAP Sales Cloud V2 into S/4HANA Cloud Public Edition?

Through SAP Integration Suite, on one of two standard paths. Either the rep creates a follow-up sales order in S/4HANA directly from an approved sales quote, or the rep captures a sales order in Sales Cloud V2, simulates it against S/4HANA and transfers it. In both cases S/4HANA creates the order and its number comes back to the CRM as the external ID.

Which communication arrangement does S/4HANA Public Cloud need for sales orders?

For simulation and transfer of Sales Cloud V2 sales orders, SAP_COM_0109 (Sales Order Integration), which contains the Sales Order and Sales Order Simulate APIs. For the way back, the replication of sales orders from S/4HANA into Sales Cloud V2, SAP_COM_0287 (Sales Order Bulk Replication Integration). Take the exact setup for your release from SAP’s integration guide.

Can a sales order be changed in Sales Cloud V2 after it was transferred?

Not for S/4HANA Cloud Public Edition. SAP’s documentation lists header attributes, products, pricing, notes and attachments as not modifiable after integration, and simulation, transfer and approval actions are no longer possible. Changes happen in S/4HANA and come back through sales order replication.

Do I need price conditions replicated into Sales Cloud V2?

Not necessarily. Simulation returns prices and taxes from S/4HANA without pricing master data replication. Replicated conditions only help if reps need estimated prices before a simulation is possible.