What is SAP and who uses it?
SAP, headquartered in Germany, is one of the world's largest enterprise software vendors. In Türkiye we mostly see two product families: SAP Business One, designed for small and mid-sized companies, and SAP S/4HANA, used by large enterprises. Both bring finance, sales, purchasing, stock and production processes together in a single system.
Companies running SAP usually manage their data meticulously, so connections to outside systems call for the same care. The goal of an SAP integration is to exchange data through supported interfaces without bypassing SAP's business rules.
What do we connect with SAP?
| Data | Direction | Frequency |
|---|---|---|
| Material master data, variants | SAP → site / portal | On change |
| Stock quantity (per warehouse) | SAP → site, portal, marketplace | At short intervals |
| Prices and pricing conditions | SAP → site / portal | On change |
| Sales order | Site / portal → SAP | Instantly |
| Customer (business partner) record | Site / portal → SAP | With the order or on approval |
| Open items, balance | SAP → B2B portal | Several times a day |
| Delivery and invoice details | SAP → site / portal | When the document is created |
| Shipment status | Carrier → site | Several times a day |
Every flow that writes records into SAP goes through SAP's own service and interface layers, using a technical user with limited permissions. We do not write directly to the database. Our general approach follows our ERP integration method.
The reporting side
When management reporting is the need, the read-only route is considered first. READERP connects to Netsis and Logo, the ERP systems widely used in Türkiye, and the other common ERP and finance platforms with read-only access, and never writes a single line to the ERP. We assess in writing whether it fits your SAP landscape during the preliminary analysis; in some SAP installations it is better to use the organization's own reporting layer, and we will say so plainly.
Typical scenarios
- Corporate B2B ordering portal: Dealers see prices calculated from the pricing conditions in SAP and place orders; the order lands in SAP as a sales order and enters the approval flow. This is how a B2B dealer portal works on top of SAP.
- A manufacturer's e-commerce channel: A manufacturer on Business One sells its products through IMFLEXI both on its own site and on marketplaces; stock is fed from SAP.
- Custom workflow: Requests collected by the field team are transferred from a custom web application to SAP. Work like this is designed as custom software.
How do we work?
- Analysis: Together with your SAP consultant, we clarify your SAP product, version, hosting model (on-premise or cloud) and existing interfaces.
- Mapping: Material numbers, units, pricing conditions, business partner matching and document types are put in writing.
- Test environment: The flow is tested on the SAP test system; the production system is not touched.
- Go-live: Flows are switched on gradually, and results are checked together with your team.
- Monitoring: The middleware logs every message. A failed record is queued, retried, and raises an alert if it still fails.
What to prepare before we start
In SAP projects, preparation is what drives the timeline most. Gathering the following before the call speeds things up:
- Your SAP product (Business One or S/4HANA), its version and hosting model
- Contact details of your SAP consultant or in-house SAP team
- Existing interfaces: does SAP receive data from other systems today?
- Whether a test system exists and how it can be accessed
- Material groups, warehouses and pricing conditions to be opened to the site or portal
- Your order approval flow: who approves orders in SAP, and at which step?
This information lets us see from the start how the flow will fit SAP's existing business rules.
Security and KVKK
A separate technical user is created for the integration and authorized only for the operations it needs. Credentials and certificates are kept in a restricted configuration, not in the code. Connections run over encrypted channels. For personal data in business partner records, transferred fields are limited to what is necessary; the requirements of KVKK (Türkiye's Personal Data Protection Law) are met in full, at no extra charge. If your SAP is hosted in a cloud outside Türkiye, we assess this together from the standpoint of cross-border data transfer.
Related Globya solutions
- Integration service and API integration
- Manufacturing and industry
- Recommended reading: Data consistency and a single source of truth
To talk about your SAP project, call +90 850 432 55 13 or use the contact page. Pricing follows a written proposal after the discovery call. Describe your needs now in 3 minutes
Frequently asked questions
Do you work together with our SAP consultant?
Yes. Settings and permissions on the SAP side are often your SAP consultant's area; we take on the middleware, the website and the portal, and move forward in coordination.
Do you write directly to the SAP database?
No. Write operations go through interfaces supported by SAP, so SAP's business rules and approval flows stay in place.
Is there a difference between Business One and S/4HANA?
The data logic is similar; the interfaces and scale differ. We choose the method based on your product and hosting model.
Will the integration affect SAP performance?
We design flows to run only as often as needed and in batches, and we do not run heavy queries during peak hours.