Custom SAP integration development — BAPIs, RFC function modules, OData services, IDocs, and SAP Integration Suite — from a Zeeland, MI company that connects SAP ECC and S/4HANA to your external systems without forcing you into SAP's six-figure connector licensing.
SAP sells integration the same way it sells everything else: as a licensing event. Need to connect your SAP ECC system to your e-commerce platform? That will be SAP Process Integration at $150,000+ in license fees before a single line of configuration is written. Need real-time inventory visibility between SAP and your warehouse management system? SAP Integration Suite starts at $50,000 per year in subscription costs, requires SAP BTP (Business Technology Platform) credits on top, and assumes you have an SAP Basis team on staff to manage it. For a company doing $20M-$100M in revenue with 50-500 employees, these licensing costs represent an absurd proportion of IT budget — often exceeding the cost of the integration development itself by 3-5x.
The result is predictable: mid-market SAP customers end up with disconnected systems. The ERP handles financials, materials management, and production planning, but everything else — CRM, e-commerce, WMS, quality management, customer portals, business intelligence — operates on a separate island. Data moves between SAP and external systems through CSV exports, manual re-keying, or a tangle of flat-file IDocs that someone configured in 2014 and nobody has touched since because the consultant who built them left the country. Finance closes the books five days late because the revenue recognition data in SAP does not match the order data in Shopify. Purchasing creates duplicate vendor records because the supplier portal has no connection to SAP's MM module. The warehouse ships against yesterday's production schedule because the WMS polls SAP via a batch job that runs at midnight.
SAP's own integration tools are powerful, but they are built for Global 2000 companies with dedicated SAP Basis teams, integration architects, and six-figure annual maintenance budgets. SAP PI/PO (Process Integration/Process Orchestration) requires its own ABAP stack and Java stack, its own hardware or cloud instance, its own monitoring, and its own specialized consultants at $200-$300 per hour. SAP CPI (Cloud Platform Integration, now part of Integration Suite) is simpler but still requires BTP licensing, iFlow development expertise, and ongoing subscription costs that compound every year. For a mid-market company that needs five or six integration points between SAP and external systems, these platforms are architectural overkill — equivalent to buying a commercial aircraft when you need a pickup truck.
There is a third option that SAP's sales team will never mention: building custom integrations directly against SAP's native interfaces. Every SAP system — ECC, S/4HANA, Business One — exposes integration points through BAPIs (Business Application Programming Interfaces), RFC (Remote Function Call) modules, OData services, IDocs (Intermediate Documents), and in S/4HANA, RESTful ABAP Programming (RAP) APIs. These interfaces exist in your system right now, fully licensed, requiring zero additional SAP software purchases. The barrier is not licensing — it is expertise. You need developers who understand both SAP's internal data model and modern integration patterns, and that combination is genuinely rare.
SAP PI/PO or Integration Suite licensing costs $50K-$150K+ before any development begins — often exceeding the integration build cost itself
Manual data transfer between SAP and external systems: CSV exports, re-keying, batch IDocs running on overnight schedules
Finance closes books 3-5 days late because revenue, cost, and inventory data must be manually reconciled across systems
No real-time inventory visibility: warehouse, e-commerce, and SAP MM module show different stock levels at any given moment
Duplicate master data (vendors, customers, materials) across SAP and external systems because there is no synchronization layer
Legacy IDoc interfaces configured years ago by a consultant who is no longer available — nobody understands the mappings or dares to modify them
SAP Basis team is 1-2 people (or outsourced) and cannot absorb the overhead of managing PI/PO or Integration Suite infrastructure
S/4HANA migration planning stalled because current integrations are built on deprecated SAP interfaces with no documented migration path
Our engineers have built this exact solution for other businesses. Let's discuss your requirements.
FreedomDev builds custom integrations that connect SAP ECC and S/4HANA to your external systems using SAP's native interfaces — no SAP PI/PO, no Integration Suite, no BTP subscription required. We write code that talks directly to your SAP system through the same interfaces that SAP's own middleware uses, but wrapped in modern, maintainable integration services that your existing IT team can monitor and support. The approach is straightforward: identify the SAP business objects and transactions your integration needs to read or write, select the appropriate interface (BAPI, RFC, OData, IDoc, or RAP API), build a middleware service that handles authentication, data transformation, error handling, and retry logic, and deploy it on infrastructure you already own or can provision for $50-$200 per month.
For SAP ECC systems, BAPIs and RFC function modules are the workhorses. A BAPI is a standardized function module with a defined interface that SAP guarantees will remain stable across releases — it is the closest thing SAP has to a public API. There are over 5,000 BAPIs in a standard ECC installation covering every business process: BAPI_SALESORDER_CREATEFROMDAT2 for creating sales orders, BAPI_MATERIAL_GETLIST for querying material master data, BAPI_CUSTOMER_GETDETAIL2 for reading customer records, BAPI_ACC_DOCUMENT_POST for posting financial documents. RFC function modules extend beyond BAPIs to include custom Z-modules that your ABAP developers may have already built. We connect to these using the SAP NetWeaver RFC SDK or the SAP Java Connector (JCo), wrapping them in REST APIs that any modern system can consume.
For S/4HANA, OData services are the primary integration interface. SAP has published over 600 standard OData APIs in S/4HANA that cover sales, purchasing, production, finance, warehouse management, and master data. These are true RESTful services — they accept JSON payloads, support CRUD operations, implement OData query parameters ($filter, $select, $expand, $orderby), and authenticate via OAuth 2.0 or SAP's communication arrangements. If a standard OData service does not cover your use case, we build custom OData services using S/4HANA's RAP (RESTful ABAP Programming) model or CDS (Core Data Services) views with OData exposure annotations. The result is a clean API that feels like any other REST service, except it reads from and writes to SAP's database through SAP's application layer with full transaction integrity.
IDocs (Intermediate Documents) remain the right choice for specific scenarios: EDI transactions with trading partners, asynchronous batch processing where guaranteed delivery matters more than real-time response, and integration with older external systems that already speak IDoc. We configure IDoc message types, set up partner profiles, build custom IDoc segments when standard ones do not fit, and create inbound/outbound processing logic in ABAP. But unlike a decade ago when IDocs were the only viable integration option, we now treat them as one tool in a toolkit — not the default. For most real-time integration needs in 2025 and beyond, BAPIs, RFCs, and OData services deliver faster, with less overhead, and with significantly easier troubleshooting than IDoc processing chains.
We connect external systems to SAP ECC using the 5,000+ standard BAPIs and RFC function modules that already exist in your system. Sales order creation, material master lookups, vendor management, financial postings, inventory movements, production order management — all accessible through RFC connections without any additional SAP licensing. We build middleware services using the SAP JCo (Java Connector) or PyRFC (Python) libraries that wrap these calls in modern REST endpoints your other systems can consume.
S/4HANA exposes 600+ standard OData APIs covering every major business process. We consume these directly from your external systems or build custom OData services using CDS views and RAP when the standard APIs do not cover your requirements. Full support for OData V2 and V4, batch operations ($batch), deep inserts, navigation properties, and server-side filtering. Authentication via OAuth 2.0 client credentials, SAML bearer assertions, or communication arrangements.
For EDI, batch processing, and guaranteed-delivery scenarios, we configure IDoc interfaces end-to-end: message types, segments (standard and custom Z-segments), partner profiles, ports, process codes, and inbound/outbound ABAP processing logic. We migrate legacy ALE/IDoc setups to current standards, document the undocumented, and build monitoring so you actually know when an IDoc fails instead of discovering it three weeks later during month-end close.
Real-time bidirectional integration between SAP (ECC or S/4HANA) and Shopify, Magento, WooCommerce, BigCommerce, or custom e-commerce platforms. Orders flow into SAP as sales orders within seconds of placement. Inventory availability updates from SAP MM/WM to the storefront in real-time. Pricing, customer-specific discounts, and ATP (Available-to-Promise) checks execute against SAP data so your e-commerce storefront always shows accurate information.
Connecting SAP's inventory management (MM/WM/EWM) to external warehouse management systems or third-party logistics providers. Goods receipts, transfer orders, pick/pack/ship confirmations, ASNs (Advance Shipping Notices), and inventory adjustments flow bidirectionally between SAP and your warehouse system. We handle unit-of-measure conversions, batch/serial number synchronization, and the notorious SAP storage location and plant mapping that breaks most generic integration attempts.
Customer master, vendor master, material master, BOM (Bill of Materials), and pricing condition records synchronized between SAP and your CRM, supplier portal, product information management (PIM) system, or business intelligence platform. We build conflict resolution logic for bidirectional sync scenarios, handle SAP's multi-level master data structures (customer hierarchies, material classifications, condition record layering), and implement change detection so only modified records trigger synchronization events.
We were quoted $180,000 for SAP PI/PO licensing plus another $120,000 in consulting to connect SAP to our Shopify store and WMS. FreedomDev built direct BAPI integrations for a fraction of that cost. Orders flow from Shopify into SAP in under 10 seconds, inventory syncs in real-time, and we did not have to buy a single additional SAP license.
We log into your SAP system and inventory every available integration interface: existing BAPIs and RFC function modules (standard and custom Z-modules), OData services (for S/4HANA), configured IDoc message types, RFC destinations, and any existing PI/PO or CPI iFlows. We map which business processes need integration, which SAP transactions and tables are involved, what data needs to move in which direction, and at what frequency. We also assess your SAP authorization model because integration users need specific RFC and BAPI authorization objects (S_RFC, B_BAPI_METH, S_SERVICE for OData) — getting this wrong is the number one reason SAP integration projects stall. Deliverable: a technical integration blueprint with specific BAPI/RFC/OData endpoints per use case, authorization requirements, estimated data volumes, and a prioritized build sequence.
For each integration point, we select the optimal SAP interface. This is not a generic decision — it depends on the specific business object, the direction of data flow, real-time versus batch requirements, and what your SAP system version actually supports. A sales order creation will use BAPI_SALESORDER_CREATEFROMDAT2 on ECC or the A_SalesOrder OData service on S/4HANA. An inventory check might use BAPI_MATERIAL_AVAILABILITY or a custom CDS view depending on whether you need ATP (Available-to-Promise) logic or simple stock levels. We then map every field between SAP and the external system, including data type conversions (SAP's DATS format to ISO 8601, CURR fields with implied decimals, NUMC fields, LANG codes), value mappings (SAP plant codes to WMS location IDs, SAP customer numbers to CRM account IDs), and transformation logic for fields that do not have a one-to-one correspondence.
We build the integration middleware — a lightweight service layer that sits between SAP and your external systems. This is typically a Node.js, Python, or Java application deployed on your existing infrastructure, a cloud VM, or a container platform. The middleware handles SAP connection pooling (RFC connections are expensive to establish and must be managed carefully), authentication and session management, request queuing for high-volume scenarios, data transformation between SAP's formats and modern JSON/REST conventions, error handling with automatic retry for transient failures, and dead-letter queuing for transactions that need manual review. When standard BAPIs or OData services do not cover a use case, we develop ABAP enhancements inside SAP: custom function modules wrapped as RFCs, CDS views with OData exposure, BAdI implementations for event-driven outbound integration, or custom IDoc segments and processing logic. All ABAP development follows SAP's naming conventions (Z/Y namespace), includes unit tests, and is transport-ready for your QA-to-production promotion process.
Every integration is tested against your SAP QA or sandbox system before touching production. We run through the full transaction lifecycle for each integration point: create, read, update, and where applicable, reverse or cancel. We test with realistic data volumes — not five test records, but thousands — because SAP BAPIs and OData services behave differently under load (connection pool exhaustion, RFC timeout handling, OData pagination with $skip/$top, IDoc queue bottlenecks). We simulate failure scenarios: what happens when SAP is down for a kernel update, when an RFC connection drops mid-transaction, when an OData service returns a 503 because the ICM (Internet Communication Manager) is overloaded, when an IDoc gets stuck in status 51 (application error). Every failure scenario has a documented recovery path. We validate SAP authorizations by testing with the actual integration user's profile, not with SAP_ALL — authorization failures in production are the most common go-live blocker for SAP integrations.
We deploy the middleware service to your production infrastructure and promote all ABAP transports through your SAP landscape (DEV to QA to PRD). We configure monitoring that covers both sides of the integration: middleware health checks, SAP RFC connection status, OData service response times, IDoc processing status, and business-level metrics (orders processed per hour, master data sync lag time, failed transaction count). For SAP-specific monitoring, we set up SM58 (transactional RFC monitoring), WE05 (IDoc monitoring), BD87 (ALE monitoring), and /IWFND/ERROR_LOG (OData error log) alerts that notify your team when something needs attention. We run in parallel with existing manual processes for 1-2 weeks, comparing automated output against manual output transaction by transaction. Ongoing maintenance covers SAP Support Pack and Enhancement Pack impact analysis, OData service deprecation monitoring, BAPI interface changes in SAP Notes, and middleware service patching.
| Metric | With FreedomDev | Without |
|---|---|---|
| Licensing Cost | $0 additional SAP licensing (uses existing BAPIs/RFCs/OData) | SAP PI/PO: $150K+ license; Integration Suite: $50K+/yr subscription |
| Infrastructure Requirements | Single VM or container ($50-$200/mo) | SAP PI/PO: dedicated ABAP+Java stack; CPI: BTP credits + iFlow runtime |
| Required Expertise | SAP functional + modern dev (we provide both) | SAP Basis admin + PI/PO developer + ongoing SAP platform management |
| Time to First Integration | 4-6 weeks including testing | SAP PI/PO: 3-6 months (platform setup + development); CPI: 2-4 months |
| Ongoing Cost (5 integrations) | $1K-$3K/mo middleware hosting + maintenance | SAP Integration Suite: $50K+/yr + consultant hours for iFlow changes |
| S/4HANA Migration Path | OData/RAP APIs are S/4HANA native — already future-proofed | PI/PO is deprecated; must migrate to Integration Suite (another project) |
| Legacy ECC Support | Full BAPI/RFC/IDoc support on ECC 6.0 EHP0 through EHP8 | Integration Suite pushes toward S/4HANA; ECC support is maintenance-mode |
| Troubleshooting | Standard HTTP debugging + SAP transaction logs (SM58, WE05, ST22) | PI/PO: SXMB_MONI message monitoring; CPI: cloud-based iFlow trace logging |
Schedule a direct technical consultation with our senior architects.
Make your software work for you. Let's build a sensible solution.