SAP at the centre. Everything else connected.
Your ERP doesn't work alone. It talks to your CRM, your payroll system, your banks, the tax authority, your online store and your data platform. We connect SAP Cloud ERP to all of them with SAP's own integration tools, so data moves once, in real time where it matters, and someone knows straight away when a message fails.
Use what SAP has already built before building anything new.
The cheapest integration is the one you don't have to build or run. We always check the three options in this order, and only design a custom flow when the first two don't fit.
Run by SAP
Some connections between SAP's own cloud products come ready-made and SAP operates them. You switch them on and set them up. There's no middleware for you to run.
Prebuilt integration content
SAP and its partners publish ready-made integration packages and documented APIs on the SAP Business Accelerator Hub. We import them into SAP Integration Suite and adapt them to your setup.
A flow designed for you
For local systems and special needs, we build an integration flow in SAP Integration Suite using SAP Cloud ERP's released APIs and events, so it keeps working through every upgrade.
Standard parts on both sides of every connection.
SAP Cloud ERP is built to be connected. It publishes released APIs and business events that SAP keeps stable across upgrades. SAP Integration Suite, on SAP's Business Technology Platform, moves, transforms and monitors the data in between.
Released APIs and events
Hundreds of documented APIs (OData, REST and SOAP) and business events such as "sales order created". Each connection is switched on with a communication arrangement, with its own user and permissions.
Cloud Integration
The engine that runs integration flows: mapping, routing and transforming messages between systems over REST, SOAP, OData, SFTP, IDoc, AMQP and more.
API Management
Publishes your APIs securely to partners, apps and websites, with keys, traffic limits and usage analytics.
Event Mesh
Sends business events to every system that needs them, as they happen, instead of each system asking for updates.
B2B and EDI
Integration Advisor and Trading Partner Management for EDI with large customers, retailers and logistics providers.
Edge Integration Cell
Runs integrations inside your own data centre or private cloud, when data must stay on-premise or systems can't be reached from the internet.
Describe a flow, and Integration Suite drafts it
At SAP Sapphire 2026, SAP announced an enhanced edition of Integration Suite with AI features. They include Text-to-Flow, which builds a first draft of an integration from a plain-language description. Script optimisation, Joule assistance and a gateway that lets AI agents reach non-SAP data through the Model Context Protocol (MCP) are also part of it. We use these to speed up delivery. Our consultants still design, review and test every flow.
The local connections every Sri Lankan SAP system needs.
Global integration content covers the big international products. The systems that make a Sri Lankan business run day to day need local knowledge as well. These are the connections we design most often.
Banks and LankaPay
Supplier and salary payments out as bank files or host-to-host, through SLIPS, CEFTS or RTGS. Bank statements come back in for automatic reconciliation.
IRD RAMIS VAT
Sales invoices, credit notes and debit notes reported to the Inland Revenue Department through the VAT Web API as they are issued, with status and errors returned.
MiHCM and other HR systems
Employees, cost centres and organisation in one direction. Payroll results, EPF and ETF, and expense claims post to finance in the other.
Salesforce CRM
Accounts, products and prices from SAP. Quotes and won deals become SAP sales orders, and order, delivery and invoice status flows back to sales.
Customs and trade
Import and export data prepared from SAP for customs brokers and Sri Lanka Customs systems, and duty and cess costs back into landed cost.
Online stores and marketplaces
Web orders into SAP for fulfilment, stock levels and prices out to the store, and payment gateway settlements into finance.
Tea brokers and auctions
Catalogues, auction results, broker sales and settlements turned into SAP sales, invoices and receivables. No retyping from broker statements.
Data platforms
SAP data shared with Databricks or SAP Business Data Cloud for group analytics and AI, with its business meaning kept.
Warehouses and 3PLs
Delivery orders to third-party warehouses and logistics partners, with confirmations, stock and proof of delivery coming back.
A deal won in Salesforce becomes an order in SAP.
Sales works in Salesforce, and operations and finance work in SAP. A good integration lets each team stay in its own system and still see what the other is doing.
- SALESFORCE1Quote marked won
- SAP INTEGRATION SUITE2Map and call order API
- SAP CLOUD ERP3Order created, priced,credit and stock checked
- SAP CLOUD ERP4Business eventschanged · delivered · billed
- SAP INTEGRATION SUITE5Event received
- SALESFORCE6Status shown to sales
Integrations fail. You should know first.
A bank rejects a file, a customer TIN is wrong, a password expires. These things happen in every live system. What matters is that the right person is alerted straight away, the message can be fixed and resent, and nothing is lost.
Every integration we build gets monitoring and alerting before go-live, plus a written run-book that says who fixes what. When we support your system after go-live, we watch the monitors with you.
Move your interfaces before maintenance runs out.
Many SAP customers still run their interfaces on SAP Process Integration or Process Orchestration. Mainstream maintenance for SAP PI/PO ends in 2027. SAP Integration Suite is its successor, and it includes tools that assess your current interfaces and help move them across.
We start with an inventory of what you have, retire what's no longer used, move the rest, and modernise where a flow can use APIs or events instead.
Every integration project starts with a list.
The number and complexity of interfaces are the biggest driver of integration effort and cost. So the first thing we build with you is an inventory: each system, what moves, in which direction, how often and how much.
| System | What moves | Direction | How often | Method |
|---|---|---|---|---|
| Salesforce | Accounts, prices, won quotes, order status | Both ways | Near real time | Prebuilt content |
| Commercial bank | Payments out, statements in | Both ways | Daily | Bank files |
| IRD RAMIS | Invoices, credit and debit notes | To IRD | Real time | Custom flow |
| MiHCM | Employees, payroll postings | Both ways | Monthly | Custom flow |
| SAP SuccessFactors | Employees, org structure | Into ERP | Daily | Run by SAP |
Example rows. Your inventory also records volumes, error handling and who owns each interface.
See Integration Suite from SAP.
Videos from SAP’s official YouTube channels on how Integration Suite connects SAP and non-SAP systems.
Published by SAP on its official SAP Help and Learning and SAP Developers YouTube channels.
© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice
Straight answers.
Do we need SAP Integration Suite?
Not always. Integrations that SAP runs, and simple direct connections, work without it. Once you connect several non-SAP systems, Integration Suite is the right place to build, run and monitor them. It is licensed separately on SAP Business Technology Platform, and we size it with you.
Will our integrations break when SAP upgrades the system?
Not if they use SAP's released APIs and events, which SAP keeps stable across upgrades. That's why we don't build integrations on internal tables or screens. We also include key interfaces in the regression tests for each release.
Can we keep our existing middleware?
Yes. SAP Cloud ERP's APIs follow open standards, so other middleware, such as MuleSoft, Boomi or Azure Integration Services, can connect to it. We'll tell you honestly where SAP's prebuilt content would save you effort.
Can you connect to systems running in our own data centre?
Yes, through SAP's secure connectivity to on-premise systems, or with Edge Integration Cell when integrations themselves must run on your own infrastructure.
How do you keep integrations secure?
Every connection has its own technical user with only the permissions it needs, encrypted transport and certificate-based authentication where the other system supports it. Personal data is only sent where there's a business reason, and every message is logged.
Does Mawkish work with the other systems too?
Yes. Besides SAP, we're partners for Salesforce, Odoo, MiHCM and Databricks, among others, so we understand both ends of many of these connections.
Map every connection before you plan the project.
In an integration workshop we build your inventory with you and recommend the right method for each interface, starting with what SAP already provides.
- Inventory of systems and interfaces
- Method for each: SAP-run, prebuilt or custom
- Real-time needs, such as RAMIS
- Monitoring and ownership
- Integration Suite sizing
SAP, SAP Cloud ERP and SAP Integration Suite are trademarks of SAP SE. Other names are trademarks of their owners. Screens and diagrams shown are illustrations.
At Mawkish, the Velby Brief is how we keep SAP & Non-SAP Integration work checked, owned and answered for, whoever does the build.