From Package to Production: S/4HANA Public Cloud and Sales Cloud V2

To connect SAP S/4HANA Public Cloud and SAP Sales Cloud V2 through SAP Integration Suite, you copy two standard packages from the SAP Business Accelerator Hub into your tenant, configure and deploy them, load code lists and master data in a fixed order, and only then switch on quotes and orders. Custom logic goes into separate iFlows, never into SAP’s.

TL;DR: Two standard packages cover master data (version 1.0.48) and sales processes (version 1.0.20) as of 7 October 2026. Configure, do not modify: a modified or renamed artifact stops receiving SAP updates. Load org data and code lists first, then products, then business partners, then transactions. Test one record and one quote end to end, plus three failure cases. In operation, every error type needs a named owner.

My colleague Sofiene Karaja has explained the integration architecture, and Marek Budik the quote-to-cash ownership model. This post covers operations, from package to production. If SAP BAIP (formerly BTP) is new to you, start with Lea Marijanovic’s introduction to SAP BAIP and the first steps with a trial account.

Two ways to run it: SAP-managed or customer-managed

The SAP Sales Cloud V2 product page lists two integration guides for S/4HANA Cloud Public Edition. The first is the integration guide “Set Up and Managed by SAP”. It applies only if your contract includes SAP’s integration setup services.

In that option, SAP creates the communication users, systems and arrangements in S/4HANA, configures the integration flows in SAP Cloud Integration, sets up default value mappings in Sales Cloud V2 and handles certificate renewals. SAP owns, monitors and manages the integration flows.

After the handover you configure Sales Cloud V2, add value mappings beyond the defaults, run the initial load, set up single sign-on and resolve business data errors in both applications. You must not alter the communication configuration SAP created.

The second guide, “SAP Sales Cloud and SAP Service Cloud Version 2 Integration with SAP S/4HANA Cloud Public Edition”, covers the customer-managed route. It sits on SAP’s support site and needs an SAP login, so I describe that route below from the packages and the Cloud Integration documentation. It applies when your contract does not include SAP’s setup service, or when you need logic beyond the standard scope, because SAP-owned flows leave no room for your own.

What the standard content contains

Both packages are on the SAP Business Accelerator Hub, maintained by SAP, with support component CEC-CRM-INT. Versions as of 7 October 2026:

Package	Version	Content
Master Data with SAP S/4HANA Cloud Public Edition (Sales and Service Cloud V2)	1.0.48	46 iFlows, 1 value mapping, 1 script collection
Sales Processes with SAP S/4HANA Cloud Public Edition (Sales Cloud V2)	1.0.20	12 iFlows, 1 value mapping

Grouped, the master data package covers:

• Business partners in both directions, plus business partner relationships in both directions, each with its own confirmation iFlow back to the sender.
• Products: product, product type, product group, and a confirmation for product replication.
• Pricing: pricing conditions, customer price list type, price specification customer group, cash discount terms, and a lookup to retrieve price customization.
• Org data: company code, sales organization, sales area, sales office, sales group, distribution channel, division, plant.
• Code lists: order, delivery and invoicing blocking reasons, incoterms classification, delivery priority, customer group, ABC classification, industrial sector, legal form, region codes, unit of measure, VIP reason, department, functional title, billing cycle.
• Service objects and more: equipment, functional locations, currency exchange rates, employees, and a lookup for product stock details.

The sales process package covers follow-up quotes in S/4HANA from an opportunity, quote and sales order simulation, follow-up sales orders from a quote, sales order replication to and from S/4HANA, retrieval of follow-up quote and order details, and deletion of quote and order references.

Three artifacts carry the prefix “Deprecated”: the old region code flow, an older follow-up sales order flow and an older quote simulation. Deploy the current twin, not both.

Activation order and configuration

On the customer-managed route, the sequence in your tenant looks like this:

1. Copy both packages from the Discover area into your design workspace. The technical package name is set at this point and cannot be changed later.
2. Configure externalized parameters of each iFlow (addresses, credential names). Use externalized parameters rather than editing the flow itself.
3. Deploy security material: credentials and certificates the parameters refer to.
4. Maintain the value mappings in both packages for your codes.
5. Set up communication on both sides: communication user, system and arrangements in S/4HANA, and communication system with inbound and outbound services in Sales Cloud V2. Take the exact communication scenario names from SAP’s set-up guide for your release.

Then the load. SAP’s guide lists the initial load order as company code, organization structure, product group, product, business partners and relationships, employees. Code lists come before all of that. Quotes and orders come last, once a test customer and a test product exist on both sides.

Two prerequisites from SAP’s guide: an authorization group for data extraction views is needed before code lists replicate (SAP Knowledge Base Article 3525713), and workforce IDs differ between the two systems, so they need a mapping via the work assignment external ID.

Standard vs custom: where your logic goes

SAP’s documentation on updates for SAP’s integration packages is unambiguous. A modified artifact no longer receives updates, and neither does a renamed one. Configured externalized parameters survive a package update. SAP recommends to only configure the standard content.

Situation	Approach	Cost at the next package update
Different endpoints, credentials, code values	Configure parameters and value mappings	None, settings are kept
Extra field or extra mapping rule	Separate custom iFlow, called from the standard flow where it offers an exit	Low, standard flow keeps updating
Standard flow cannot do what you need	Copy the standard iFlow, modify the copy, document the delta	High: you merge every SAP fix by hand
New scenario SAP does not cover	Separate custom iFlow in its own package	None for the standard content

SAP’s guideline keep modifications separate from prepackaged content describes the pattern: custom flows deployed on the same tenant, called through customer exits and the ProcessDirect adapter. Our conventions: a customer prefix on every custom package and iFlow, a new version number with every transport, a short delta note in the package documents.

Testing: one record, one quote, three failures

Test against the test tenants, with one record you can follow through every hop.

#	Test	Expected result
1	Change one business partner in S/4HANA	Account updated in Sales Cloud V2, confirmation message completed
2	Opportunity, quote with live simulation, follow-up sales order	Price from S/4HANA on the quote, order number visible in Sales Cloud V2
3	Code value without value mapping	Message in error with a readable reason, nothing half-written
4	Quote with a product unknown in S/4HANA	Simulation or follow-up fails visibly, the rep sees why
5	Send the same change twice	No duplicate record on the target side; document the actual behaviour

Note who triggered each test and where you saw the result: your first operations manual.

Monitoring in operation

Failed messages show up in three places. In Cloud Integration, Monitor Message Processing lists every run with its status. In Sales Cloud V2, Settings, Integration, Message Monitoring shows inbound and outbound messages as Successful, Error or Pending, with payload and error details. S/4HANA has its own message monitoring.

SAP Cloud ALM Integration & Exception Monitoring brings this into one place for the components it supports: message monitoring, tracking by business attributes such as an order number, and alerts on failed messages that land in an Alert Inbox where you assign a processor. Its Business Object page shows the status of master data replication.

Rhythm	Check	Owner
Daily	Open alerts in Cloud ALM, messages in Error in Cloud Integration	Integration owner
Daily	Business data errors in Sales Cloud V2 and S/4HANA	Key user of the source system
Weekly	Messages stuck in Pending, recurring errors by iFlow	Integration owner
Weekly	“Update Available” labels in the design workspace, certificate expiry dates	Integration owner
Per package update	Rerun tests 1 to 5 before transport to production	Integration owner with key users

Reprocessing follows ownership: fix the data at the source, then trigger the change again. Resending without a fix only fails twice.

More on S/4HANA Public Cloud, SAP BAIP and the Service Cloud V2 integration. Want to go through your own landscape? Talk to us.

Frequently asked questions

Do I have to run the integration in my own SAP Integration Suite tenant?

Not always. If your contract includes SAP’s integration setup service, SAP configures the integration flows and owns, monitors and manages them. Otherwise you copy SAP’s standard packages into your own Integration Suite tenant and run them yourself.

In which order should I load the data?

SAP’s guide lists the initial load in this order: company code, organization structure, product group, product, business partners with their relationships, and employees. Code lists come first, transactional flows such as quotes and orders only after the master data is complete.

Can I change a standard iFlow from SAP’s package?

Technically yes, both packages allow editing. But SAP’s documentation is clear: once an artifact is modified or renamed, it no longer receives updates. Configure where you can, and put your own logic in separate custom iFlows next to the standard ones.

Who fixes a failed message in operation?

Technical errors (connection, certificate, deployment) belong to the integration owner. Business data errors (missing mapping, blocked customer, unknown product) belong to the key user of the source system. Even in the SAP-managed option, SAP’s guide leaves business data errors with the customer.