SAP and Salesforce, with a defined boundary
SAP holds the operational truth. Salesforce holds the commercial relationship. SAP Salesforce integration is less about moving data than about deciding, object by object, which system is allowed to be right.
SAP estates are rarely simple and the integration should not pretend otherwise. SAP and Salesforce can be integrated through a number of proven approaches, depending on the existing technology landscape, the integration requirements and the level of complexity. The MuleSoft SAP-certified connectors are one strong option, particularly where a managed integration layer and a wider API strategy are required, though they are not the only route. Direct APIs, SAP integration services and other middleware platforms can also be used where appropriate.
Whichever approach is selected, the key is to establish clear ownership of data, with a defined master system for each object, and to design the integration around the business processes it serves rather than simply moving data between platforms.
What syncs between SAP and Salesforce
The master data and transactional objects that matter to a sales team.
- Customer master, so both systems mean the same company.
- Products and material master, so quotes reference things that exist.
- Pricing and conditions, so quoted prices are prices SAP will honour.
- Inventory and availability, so nobody promises stock that is not there.
- Sales orders, created in SAP from a closed Salesforce opportunity.
- Invoices and payment status, surfaced against the Salesforce account.
MuleSoft provides SAP-certified S/4HANA connectors for both OData and SOAP, with IDoc and BAPI over RFC available for older estates. Both bulk and real-time patterns are supported.
Which way the data flows between SAP and Salesforce
Predominantly one-way per object with a named master. Two-way is possible but rarely the right answer here.
⇆ Two way→ Out of Salesforce← Into Salesforce
Trying to make every object two-way is the commonest cause of failed SAP integrations. Where ownership is clear, one-way is simpler, faster and far easier to support.
What a SAP integration gives you
Sales stops guessing and operations stops rekeying.
- Quotes that hold. Live pricing and availability rather than a spreadsheet from last quarter.
- Orders without rekeying. The closed opportunity becomes the SAP order, with the transcription errors removed.
- Credit and payment visible to sales before the next conversation.
- Fulfilment status on the record, so account managers answer their own questions.
- One customer master rather than two definitions of the same company.
How we connect SAP to Salesforce
The question to settle before you build the SAP integration
Which system is allowed to create a customer?
In most SAP estates the customer master is governed carefully, with approval steps and data standards attached. Salesforce, by design, lets a rep create an account in seconds.
Those two positions have to be reconciled explicitly. The usual answer is that Salesforce creates prospects freely and SAP creates the customer master when the relationship becomes real, with a defined promotion step between the two.
Without that step you either block sales from working or fill the SAP customer master with speculative records. The integration gets blamed for both.
The prospect that became a customer master problem
A rep creates an account in Salesforce in fifteen seconds. In SAP, a customer master carries tax treatment, credit terms, payment conditions and an approval chain. Sync them naively and finance inherits a list of speculative prospects.
This is the defining question of an SAP integration and it is a governance question, not a technical one. The pattern that works is that Salesforce creates prospects freely, SAP creates the customer master when the relationship becomes real, and a defined promotion step sits between the two with the fields finance needs captured before it fires.
Get that right and the rest follows. Products, pricing and stock flow into Salesforce so quotes reference things that exist at prices SAP will honour. Closed-won creates the sales order without a transcription step. Invoice and payment status returns to the account.
The tooling is mature and certified: MuleSoft’s S/4HANA OData and SOAP connectors are both certified by the SAP Integration and Certification Center, with IDoc and BAPI over RFC available for older estates.
The commonest cause of a failed SAP integration is trying to make every object two-way. Where ownership is obvious, one-way is simpler, faster and dramatically easier to support.
Connect SAP to Salesforce
Mature, certified tooling. The work here is governance rather than plumbing.
Whatever you run alongside it, if it has an API it can be connected, so get in touch and we will tell you what is realistic.
SAP Salesforce integration: frequently asked questions
Most commonly through MuleSoft, whose S/4HANA OData and SOAP connectors are both certified by the SAP Integration and Certification Center. Older estates can be reached through IDoc or BAPI over RFC. Bulk and real-time patterns are both supported. Which you use depends on the object.
Usually only for the customer master, and even then with a defined master and a promotion step. Products, pricing, inventory and invoices normally flow one way from SAP into Salesforce, and sales orders flow the other way. Trying to make everything two-way is the commonest cause of failure.
Yes. Older estates are typically reached through IDoc or BAPI over RFC rather than OData. It is more work than a modern S/4HANA connection but it is well established, and we will tell you honestly which category you are in.
Usually SAP for the customer master, with Salesforce free to create prospects and a defined step that promotes a prospect into an SAP customer. This keeps SAP data governance intact without preventing sales from working at speed.
It varies more than any other integration we do, because SAP estates vary so much. We scope it against an agreed specification and quote a fixed price before any build starts, so you approve the cost up front.