SAP API Integration Services | S/4HANA, Business One & ByDesign

SAP is the most widely adopted enterprise resource planning platform in the world and sits at the core of finance, logistics and manufacturing operations for thousands of organisations. The product family spans several editions: S/4HANA is the cloud-native successor built on the HANA in-memory database, Business One targets small and midsize enterprises with a leaner feature set, and ByDesign delivers a fully hosted cloud ERP for companies that prefer not to manage their own infrastructure.

The API landscape across SAP editions is powerful yet fragmented. S/4HANA exposes OData V2 and V4 services that let external applications read and write business objects such as sales orders, purchase orders and material documents. Business One ships a Service Layer, a REST-like interface that runs on the application server and provides broad access to its data model. Legacy environments still rely heavily on BAPIs and RFC function modules, which can be made accessible to the outside world through SAP Cloud Connector or the SAP Integration Suite.

For organisations that combine SAP with custom portals, mobile applications or partner-facing web apps, a well-designed integration layer is not optional. Without it, staff end up copying data between screens, introducing delays and errors into processes that should run seamlessly. MG Software connects bespoke applications to various SAP editions, always starting from the specific API capabilities available in your environment.

One thing that sets SAP integration apart from connecting lighter SaaS tools is the depth of business logic enforced by the ERP itself. Mandatory fields, credit checks, automatic pricing procedures and complex authorization checks all play a role. A successful integration respects these layers and translates them into clear feedback loops inside your application so end users know exactly what is happening.

Companies running SAP almost always operate additional software that falls outside the SAP ecosystem. A customer portal where buyers place their own orders, a planning tool for factory floor staff, or a B2B storefront that must flow directly into the ERP are all common examples. When these channels are not connected, they rely on manual data entry, which is slow and error-prone.

The real cost of broken information flows is often underestimated. Sales orders typed by hand arrive late, credit notes take weeks to process, and stock levels drift from reality. These issues cascade into customer dissatisfaction and, ultimately, lost revenue. Integration eliminates the gap and turns what used to be a batch of spreadsheets into a continuous, verified data stream.

Beyond simple data transfer, a well-built integration brings SAP business logic forward into the user experience. When a customer places an order through your portal, the integration can immediately confirm whether stock is available, what the realistic delivery date looks like, and whether the credit limit is sufficient. This saves back-and-forth communication and gives your team real control over the process.

At MG Software, we treat SAP integration as more than a technical project. We start by mapping the business processes involved, identify which SAP entities are relevant, and work alongside your SAP consultants to agree on the right approach. Code comes after alignment, not before.

The technical approach depends heavily on the SAP edition and the existing landscape. For S/4HANA Cloud, OData V4 services are the primary integration method, offering CRUD operations on business objects like sales orders, purchase orders and material documents. S/4HANA on-premise environments typically expose OData V2 services through SAP Gateway, while Business One uses its Service Layer, a REST API running on the application server that grants direct access to business objects.

When standard OData services fall short, we build custom CDS views or consume existing BAPIs and RFC function modules. These are securely exposed to external systems through SAP Cloud Connector, which establishes an outbound tunnel without requiring inbound firewall rules. The SAP Integration Suite (formerly Cloud Platform Integration) can serve as middleware for complex routing, data mapping and monitoring needs.

IDoc processing remains relevant for organisations with established EDI flows or that integrate with trading partners running legacy systems. In these cases, we build a translation layer that maps inbound or outbound IDocs to your application data model. The choice between synchronous and asynchronous communication is made per entity: stock availability checks are typically synchronous, while order creation fits better with asynchronous processing and confirmation messages.

Error handling deserves special attention. SAP systems return detailed error messages in specific formats that must be translated into actionable feedback for end users. We implement dead-letter queues with automatic retry logic, log every interaction with context, and build monitoring dashboards so your operations team can intervene quickly when a sync fails.

Performance management is equally important. Large batches of orders or material changes can burden the SAP backend if they are not throttled. We implement rate limiting, pagination and delta synchronisation to keep the load manageable and smooth out traffic peaks.

SAP security is layered and requires attention at every level. At the transport layer, we secure connections with TLS and, where applicable, mutual certificates between systems. SAP Cloud Connector provides a secure tunnel with no inbound firewall rules, which minimises the attack surface.

At the application layer, we work within the SAP authorization model. Each integration user receives a technical account with only the roles and authorization objects it needs. We avoid SAP_ALL and follow the principle of least privilege. For S/4HANA Cloud, we use Communication Arrangements with business catalogs that can be scoped per API endpoint.

For sensitive data such as financial records or personal information, we implement field-level masking in the integration layer so your external application only receives what it actually needs. Logging every API call with timestamps and user context enables audit trails that satisfy the compliance requirements common among SAP customers.

One of the biggest hurdles in SAP integration is the authorization model. SAP uses a fine-grained system of roles, profiles and authorization objects. Setting up a technical integration user with exactly the right permissions is time-consuming and demands close collaboration with the SAP Basis team. We document every required authorization upfront to prevent surprises during testing.

Custom ABAP extensions represent another concern. Many organisations have modifications in SAP that affect standard API behaviour: additional mandatory fields, custom number ranges, or business rules not covered in official documentation. We inventory these extensions during the landscape analysis and test explicitly against them.

Finally, the sheer complexity of the SAP landscape itself can be a factor. Organisations sometimes run multiple SAP systems side by side, each with its own configuration and master data. Transporting configuration between environments and aligning test data requires careful planning and close coordination with the SAP administration team.

SAP releases regular updates that can influence API behaviour. S/4HANA Cloud receives quarterly feature updates that may introduce new fields, changed validations or deprecated services. We recommend making regression testing of the integration part of your SAP update cycle.

In addition, we monitor runtime behaviour with alerting on error rates, response times and queue depths. When anomalies are detected, we investigate before small issues escalate. Periodically we review integration flows to assess whether optimisations or extensions are appropriate based on changing business needs.

SAP integrations are typically more complex than connecting cloud-native SaaS platforms. The discovery phase takes more time because of the variety of editions, modules and custom extensions that must be mapped. Expect an initial engagement of several weeks for a first flow, depending on the availability of API documentation, test environments and in-house SAP expertise.

We prefer to work in phases with clear acceptance criteria per phase, which gives you control over both cost and outcome. The first phase focuses on a bounded flow that delivers value quickly, after which additional flows are added in subsequent sprints.

Cost transparency matters to us. After the landscape analysis, you receive a detailed scope description with effort estimates so you can make an informed decision before development begins.