If you use SAP, your CRM talks to SAP.
The authority for customer account, balance, order and invoice data stays in SAP; your sales team sees the same information on the CRM screen. The connection is built with a REST API, OAuth2, signed webhooks and import/export; which data flows in which direction and at what frequency is worked out during discovery and written into an agreed scope.
The data is in SAP; the sales side cannot reach it in their daily work
In a company running SAP, the ERP side does its job: customer accounts are kept, orders are entered, invoices are issued, the books are closed. This page is not arguing about SAP; it describes what happens on the side that never falls within SAP's scope. This is the picture we have seen in our own projects:
- The SAP licence and the training sit in finance, purchasing and logistics; it is not a screen the sales rep uses every day. Finding out a balance comes down to a phone call.
- Even a small field the sales side asks for goes into the IT queue; the change request is tied to the release plan, and its timing is set by that plan's own rhythm.
- So the field team builds its own shadow system: Excel, a personal calendar, a personal phone. The data lives in two places, and one of them is not audited.
- Leads, conversation history, the quotation process and the reason for a loss are not held anywhere — an ERP was not built for that.
- A new quote goes out to a customer whose payment is overdue, because the open balance is not on the screen of the person writing the quote.
- At the quarter close the pipeline report is put together by hand; two different figures turn up in the meeting.
Trying to replace SAP does not close this gap: finance, logistics and the official document side carry on living in the ERP. The setup that works in our own projects is this: the ERP stays where it is, the sales side moves to the CRM, and the two sides are connected by a defined and written flow.
How is the connection built?
There is no out-of-the-box module for SAP, and we will not say there is. The connection is built as an integration project whose scope is set in the discovery call, using a REST API, OAuth2, webhooks and import/export.
These are the three tools we use on the CRM side:
- REST API — the product ships with 183 business objects out of the box, and each one is published in the REST API with its own data and schema endpoint; access is authorised with OAuth2. Schema reading (describe), composite operations and bulk endpoints are supported.
- Outbound webhook — events in the CRM (an opportunity being won, for example) are sent to the external system signed; a failed call is retried.
- Import/export — Excel/CSV transfer through a four-step wizard: upload, map fields, preview, run. You approve the mapping on screen.
Who does the work on the SAP side? In practice your own SAP partner or your in-house integration team — they are the ones who know the interface, the permissions and the change process on the SAP side. Our side is documented: we provide the object schema, OAuth2 access and the field mapping table in writing. If you wish, we can also take on the development on the CRM side.
The limits on our side are measured, not estimated: the REST API exposes object and field definitions through the describe endpoint, processes up to 200 records in a single bulk request, and carries 25 sub-requests in one composite call. The import wizard works on more than 75 objects, up to 100,000 rows per job and 25 MB per file. Let us also write down what we are not saying: we have no reference customer running SAP, and we have no figure for how many enterprise installations have chosen this route.
Why a connection that gets built, rather than an out-of-the-box add-on? Because SAP is not a single product and access differs from one installation to the next: which product and which version, on-premise or hosted, and who holds the authority to open an interface. Handing everyone the same button and saying it will connect at a single press would be a promise that stops working the moment the access conditions change. Instead we choose the method together during discovery and share the scope, and any cost, in writing. We have set out our general approach with the same openness on the integrations page.
Tuesday, 16:00 — the regional sales manager is reviewing the pipeline for the quarter close. Once the connection is in place, this is what changes:
-
1
The open balance and the payment term are on screen while the quote is being prepared
The account balance and payment term transferred from SAP sit as fields on the customer record. The rep sees an overdue balance while preparing the quote; no call to finance.
-
2
A balance over the threshold opens a follow-up task
When a balance passes the threshold you set, a task is assigned to the owner. Collections follow-up is tied to a record rather than to someone's memory.
-
3
Order and shipment status can be read without going into SAP
Orders continue to be entered in SAP and invoices continue to be issued on the SAP side. Status information and amounts are written into the CRM at the frequency defined in the scope; you do not need to open ERP licences for the sales team.
-
4
A field request from sales is not tied to the release plan
Fields such as a risk limit, a payment term or a dealer code are added on the CRM side by an administrator without writing code. Because nothing is touched on the SAP side, the change does not wait in the IT queue.
-
5
A won opportunity is passed to the SAP side with its order details
When an opportunity is won, the order details can be sent to the external system through a signed webhook; the endpoint is consumed by your team on the SAP side. Entering the same data a second time by hand is reduced.
-
6
The quarter close does not arrive with two different totals
Sales and collections by customer and by region appear in the same report, through tabular and summary report types and the drag-and-drop dashboard designer. One figure goes into the meeting.
Flows that can be set up between SAP and Rapitek CRM
Customer record – matching the SAP customer number
Records are matched using the tax number or the SAP customer number as the key. Duplicate records are cleaned up during setup; the matching rule and which side generates the key are stated in the written scope.
Balance and payment term visibility
The account balance and the overdue amount are transferred onto the customer record as fields; they are visible without opening ERP licences for the sales team. The transfer frequency is set in the scope.
Following order and invoice information
Order and invoice header information is followed as a list on the customer record. The authority for the document stays in SAP; the CRM only adds a visibility layer.
Transferring the material and price list
The material catalogue and the price list are transferred from the ERP to the CRM so that quotes are prepared with the right prices. The transfer can be periodic, or it can be built over the API.
Passing a won opportunity to the SAP side
A signed webhook that sends the order details to the external system when an opportunity is won can be set up; the endpoint is consumed by your team on the SAP side. Entering the same data a second time by hand is reduced.
Adding sales fields without waiting for the release plan
Field and object definitions on the CRM side are added by an administrator without writing code; because nothing is touched on the SAP side, the change does not enter the IT queue. Adding custom objects and fields is standard in the product.
Which method, and when?
| Method | What it does | When it is preferred |
|---|---|---|
| REST API (183 business objects out of the box, each with its own data and schema endpoint) | The external system reads and writes records in the CRM; it is authorised with OAuth2 and supports schema reading and composite operations | When a suitable interface and permissions exist on the SAP side, and the flow is meant to run automatically |
| Outbound webhook | Events in the CRM (an opportunity won, for example) are sent to the external system signed; a failed call is retried | For flows that need a notification from the CRM towards SAP; the endpoint is consumed by your side |
| Import (Data Hub) | Excel/CSV extracts are transferred through a four-step wizard: upload, map fields, preview, run. Export is done in the same module; we have not measured its limits | Because it does not require access to be opened on the other side, it can start before the access question is answered; when a periodic sync is enough, or when external access to SAP cannot be opened |
| Your SAP partner or your in-house integration team | The team that knows the SAP side can write the connection itself using the same REST API; we provide the schema, the access and the field mapping table | When the change process on the SAP side runs within your own team |
What we have verified
How is the SAP connection put into service?
-
1
Discovery
We work out which SAP product and version you use, where the system runs and who holds the authority to open an interface. We recommend that your IT lead and your SAP partner join this call.
-
2
Security and architecture review
We fill in your IT team's security assessment questionnaire and describe the architecture and the data flow in writing. We have written down what we have and what we do not have exactly as it stands — it is all listed, item by item, on our security page.
-
3
Scope, boundary of responsibility and method
Alongside which data flows in which direction and how often, the boundary of responsibility between the two sides is written here as well: who will do the development on the SAP side, and who will consume the endpoints. The field mapping table, the scope and the cost are shared in writing.
-
4
Configuration and test transfer
Fields, list views, roles and permission sets are set up on the CRM side; a test transfer is run with sample data. Mappings are verified in both directions, and duplicate and faulty record scenarios are tried out here.
-
5
Training and go-live
Training for the sales team and for managers, then close support during the first week. We do not commit to a timeline before discovery; after the discovery call we give you a date, not a range. The schedule for API-based flows depends on the change process on the SAP side.
Our limits: what we do not promise on this page
In a company running SAP, the person reading this page may well be from IT, and they ask the right question: what can you not do? Our answers are here, in one place.
- We are not SAP certified and we are not an SAP partner. We have no out-of-the-box connection for SAP Business One or S/4HANA; the connection is a project built with the tools described above.
- We have no reference customer running SAP. Today we cannot describe such an installation under a customer's name, and we will not write as though we could. What we can commit to is that the CRM side is documented and open: the object schema, OAuth2 access and the field mapping table are provided in writing; the work on the SAP side is carried out by your partner or your in-house team.
- There are three things we categorically do not promise: that stock will be in sync, that the order → invoice → collection chain will flow by itself, and that the production/MRP side will work as an integrated whole. The reason for each, and what can be done instead, is written out line by line in the limits section of the integrations page; we are not repeating it here.
- We do not issue e-Invoice or e-Archive documents. Rapitek CRM is not a GİB-authorised special integrator; it does not produce official documents and does not track ETTN or GİB status. Information such as the invoice number and the amount can be carried into the CRM as fields.
- Let us be honest about scale. The business Rapitek CRM describes is a B2B company with at least 5 users and a sales or field team. A group running SAP may be at a far larger scale; if so, we do not commit today to being the enterprise CRM for the whole group — rather than making a promise about scale we cannot prove, we say this up front. A realistic scope is one sales unit, one subsidiary or one dealer channel; it grows from there.
- Identity management: single sign-on with OIDC is supported in the product; we have no SAML support and we do not have a configured SSO installation in production today. Two-step verification is mandatory for the administrator web login; API and mobile channels fall outside that requirement. Roles, profiles, permission sets, record sharing and IP restrictions are supported in the product; we configure them according to your policy during setup.
- Certification and commitments: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. Nor do we give an availability (uptime) commitment based on external monitoring — we do not think it is right to commit to something we do not measure.
Data location: your data is held in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no region selection feature. This is a transfer abroad within the meaning of Article 9 of the KVKK; we establish your basis for that transfer together during the contract process. The full architecture, the sub-processor list and what we do not offer yet are on the security page, and the personal data side is in the KVKK privacy notice.
The scope comes out of discovery; the plan prices are out in the open
The cost of the SAP connection depends on the data volume, the direction of the flow and the access available on the SAP side; it is shared in writing after discovery. The plan prices, on the other hand, we publish in one place, with the figures.
Three plans, a scope table and the separately priced items, all on one page.
Frequently asked questions about SAP integration
Is integration between SAP and a CRM possible?
Is there a ready-made SAP module in Rapitek CRM?
Are you an SAP-certified solution?
Does it matter which SAP product we use?
Who does the development on the SAP side?
Is Rapitek CRM's REST API documented, and can it be used from outside?
Our IT team sends out a security assessment questionnaire — do you fill it in?
Can we use single sign-on (SSO)? Do you support SAML?
Our company is at the scale that uses SAP — is Rapitek CRM a fit for that?
Will we have to open SAP licences for the sales team?
Our SAP system is in-house and closed to the outside. Is integration still possible?
Will our stock be in sync with the CRM?
Can we issue e-invoices from the CRM?
Does it replace SAP?
Will the synchronisation be real time?
Where is our data held?
What does SAP integration cost, and how long does it take?
Let us map out your SAP flow in 30 minutes
In the demo call, let us talk through how your customer account, balance, order and invoice data will flow into the CRM, using your own scenario; we will choose the method and the scope together. Bring your IT team along too.
The scope of the setup, and any cost, are worked out in the discovery call and shared in writing.
