CRM & ERP integration
Move commercial commitments from Salesforce into SAP under control.
Closed opportunities, quotes and account changes become governed SAP sales order, finance and product operations, with status reconciled back to the sales team in one recorded run.
The problem
Why Salesforce + SAP needs a governed process
Orders agreed in Salesforce are often re-entered in SAP by hand. Status, pricing and customer data drift between the two, and nobody can show which decision moved which record.
Responsibility
How the systems divide responsibility
System of engagement
Salesforce
Accounts, contacts, opportunities, quotes and the commercial conversation.
System of record
SAP
Sales orders, invoicing, finance postings, products and procurement.
Capabilities
What Nexus orchestrates
Pre-built action groups used in this pattern. Anything else runs through an API, protocol or database step, or Rules + Code, in the same workflow.
Salesforce
73 ACTIONS
- Opportunities10
- Accounts10
- Contacts10
- CPQ Quote8
- CPQ Approval1
- Reports10
SAP
97 ACTIONS
- Sales Orders14
- Invoice10
- Finance20
- Products10
- Core SAP7
Architecture
One governed run across both systems
How work starts
Salesforce (SOQL polling)
Nexus polls Salesforce with SOQL for new or updated records. SAP steps run as actions inside the same workflow.
When a pre-built action does not cover it
Workflow patterns
What teams run across Salesforce + SAP
01
Closed opportunity to SAP sales order
A closed-won opportunity is validated against account and product data, then a sales order is created in SAP. The order reference returns to Salesforce.
02
CPQ quote approval before order creation
Quotes outside discount policy pause for a named commercial approver before any SAP write is attempted.
03
Invoice status back to the account team
SAP invoice status is read on a schedule and summarised on the Salesforce account so sales can answer customers without asking finance.
04
Product master consistency check
Products referenced in quotes are checked against SAP product records. Mismatches open a review task instead of creating an order.
Direction and ownership
Which way each change moves
Commercial intent flows from Salesforce to SAP. Operational status returns from SAP to Salesforce. Each direction is defined separately, and neither system gives up ownership of its records.
Salesforce SAP
Validated order context from a closed opportunity or approved CPQ quote.
SAP Salesforce
Order, invoice or product status written back to the account or opportunity.
Control
Approvals and exception handling
Human approval
Orders that fail validation, exceed discount policy or reference unknown products wait for a commercial or finance owner. Approved orders proceed automatically; rejected ones return to Salesforce with a reason.
Exceptions
- Missing or malformed fields route to a correction queue with the source record attached.
- SAP write rejections are captured with the full response and retried or escalated by policy.
- Duplicate detection prevents the same opportunity creating two orders.
Security, audit and deployment
Every run leaves a reviewable record
- The Salesforce record and field values that started the run.
- Validation results and the rule version applied.
- The approver, decision and timestamp where approval was required.
- The SAP request, response and resulting document reference.
Credentials for Salesforce and SAP are held in the vault and used only by the steps that need them. Role-based permissions decide who can edit, approve and run the workflow. Nexus runs on premises, in private cloud or air-gapped, so the execution record stays inside your deployment boundary. Governance and audit
Participating connectors
The connectors behind this pattern
Related
Continue from here
- Salesforce to SAP order handoff without replacing either system
A worked order handoff with validation, approval and reconciliation.
- Enterprise automation
Governed processes across the systems you already operate.
- Enterprise integration
Connectors, interfaces and code in one platform.
- Integration explorer
Add more systems to this combination.
FAQ
Salesforce + SAP questions
- Does Nexus replace Salesforce or SAP?
- No. Both remain the systems of record for their own data. Nexus runs the process between them and records each decision.
- Is synchronization bidirectional by default?
- No. Each direction is designed separately, with its own validation, ownership and conflict handling.
- What if an SAP operation is not in the pre-built actions?
- Use SAP RFC, an HTTP or SOAP request, or Rules + Code in the same workflow. Approval and audit apply to those steps too.
Integration review
Discuss this integration
Bring your Salesforce and SAP process. We will map ownership, approval and the steps each system needs.