ERP & Finance · 97 pre-built actions
SAP integration with Nexus
Automate around SAP without forcing change inside it. SAP holds the operational record, and most processes that touch it start somewhere else. Nexus reaches SAP through a prebuilt action or the SAP RFC node, inside one governed run with approval and audit.
Pre-built actions
What you can automate
97 pre-built SAP actions, grouped by what they work on.
97
PRE-BUILT ACTIONS
- 01Reading an invoice from SAP is available as a pre-built SAP operation.
- 02The generic SAP RFC node can call BAPI and RFC functions exposed by your SAP system.
Workflow
How it fits into a Nexus workflow
SAP is not listed among the current trigger sources. Work that involves SAP typically starts from another source, such as a Salesforce poll, an object storage event, a database trigger, a webhook or a schedule, and then reads or writes SAP inside the run.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call BAPI and RFC functions through the SAP RFC node when the prebuilt action does not cover the operation.
02
Use SOAP Request, HTTP Request or a database node where your SAP landscape exposes an approved interface of that kind.
03
Apply Rules + Code for tolerance checks, mapping and reconciliation before anything is written back.
Examples
Workflow examples
Invoice intake and reconciliation
A file in object storage starts the run, SAP is read, a SQL reconciliation source is compared and exceptions go to a finance reviewer.
Order handoff from CRM
A validated Salesforce record is handed to SAP through the connector or an RFC call, with the response reconciled back.
Subscription events into finance
Payment or subscription events are validated and posted toward SAP under finance approval rules.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include SAP
AWS S3 or Azure Blob Storage, SAP, MSSQL or Oracle
Invoice intake and reconciliation with object storage, SAP and SQL
A file lands in object storage, SAP and a reconciliation database are checked, Rules + Code matches the result and exceptions go to a named reviewer.
Salesforce, SAP
Salesforce to SAP order handoff without replacing either system
A Salesforce record detected by SOQL polling is validated, handed to SAP through the connector or an RFC call, and reconciled back.
Stripe, PayPal Subscriptions, Salesforce, SAP
Payment and subscription events into CRM and ERP
A Stripe event or PayPal subscription change is validated and reflected in Salesforce and SAP under one execution record.
Integration patterns
SAP integration patterns
Dedicated patterns that pair SAP with another system in one governed run.
Industry use cases
Processes that use SAP
Public sector
Procurement exception handling
Procurement and invoice exceptions reach a named owner, and SAP changes happen only after approval.
Public sector
Cross-agency file intake and validation
Files from other agencies are validated before they touch finance records, and problems become tickets.
Financial services
Lead to account and ERP handoff
Marketing leads become clean sales accounts, and approved deals reach ERP without re-keying.
Financial services
Invoice approval and procurement
Invoices are checked against procurement records and approved before they are created.
Healthcare
Charge and invoice exception workflow
Administrative charge and invoice mismatches are resolved with approval before finance records change.
Enterprise
Order to cash across CRM, ERP and billing
Won deals become orders and invoices without re-keying, with exceptions reviewed.
Enterprise
Procure-to-pay exception workflow
Invoice, procurement and payment exceptions are resolved with approval across four systems.
Financial services
Expense and budget governance
Budget changes are checked against policy, approved and followed up in SAP with notification.
Enterprise
ERP data to Snowflake
SAP finance and sales data lands in Snowflake on schedule, with load results reported.
Enterprise
CRM and ERP operational analytics
Pipeline and ERP data are modelled together in Snowflake for operational reporting.
Enterprise
CRMConnect order to ERP workflow
CRMConnect orders and contracts become validated SAP sales orders and invoices.
FAQ
SAP connector questions
- How does Nexus call SAP?
- Through prebuilt SAP actions where they fit, such as reading an invoice, or through the generic SAP RFC node for BAPI and RFC functions.
- Can SAP start a workflow?
- SAP is not a listed trigger source. Workflows usually start from another event and then read or write SAP inside the run.
- Does this page list every SAP action?
- No. Nexus includes 97 SAP actions across Core SAP, HR, Invoice, Sales Orders, Finance, Products and Procurement.
- Can SAP steps run in an air-gapped estate?
- Yes, provided SAP is reachable inside the same boundary. Nexus runs where you deploy it.
Related reading
Continue from here
- Salesforce connector
The CRM side of the order handoff.
- Salesforce-SAP integration
Direction, approval points and audit for the pattern.
- Automating legacy systems
Connector, protocol and code across older estates.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how SAP fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.