- Market
- Saudi Arabia
- Written for
- CIO, COO
- Decision
- Integrate an installed SAP system with the estate around it
The doors SAP gives you
The doors SAP publishes, and why an integration has to use them
SAP offers specific, supported interfaces for exactly this, and each exists to make sure an integration cannot do what a user could not. Choosing the right one per flow is most of the work; reaching past all of them into the tables is the mistake.
BAPIs for transactional writes
A BAPI posts a document the way a transaction would, running the same validation, authorisation and number assignment SAP applies to manual entry.
What using it protects: A posting that reconciles and that an audit can trace to a rule, not to a raw insert.
IDocs for asynchronous exchange
IDocs carry documents in and out on SAP’s own message format, with status tracking and reprocessing when a partner system is slow or offline.
What using it protects: An exchange that does not lose a document because a downstream system blinked.
OData services for reads
Gateway and OData expose data to other systems and front ends over a stable web contract, rather than each consumer querying the core its own way.
What using it protects: Reads that do not compete with the postings the business is making right now.
Distance from custom Z-tables
Custom tables and undocumented structures change across support packs and a conversion; an integration bound to them breaks the next time SAP moves.
What using it protects: An SAP upgrade that is a project of its own, not an integration outage.
The failure to avoid
The invoice that appeared in SAP with no one behind it
The tempting shortcut is to treat SAP as a database and insert straight into its tables when another system needs a document created. It runs, it is fast, and it skips the number range, the validation and the audit entry SAP would have applied. The defect stays hidden until a reconciliation does not balance or an auditor asks who authorised a figure, and the honest answer is that no person did — a script placed it through the back. At that point the one thing SAP exists to provide, numbers you can defend, is gone.
The disciplined route is more work and the only one worth building: every write goes through a BAPI or an IDoc, so SAP’s validation, its authorisation and its document flow apply to the integration as they would to a person entering the same document. The integration becomes an accountable actor inside SAP rather than a hole in its side. It costs more because the supported interfaces demand more than a raw insert, and that demand is precisely the value — it is the line between feeding the system of record and quietly corrupting it.
The shape of it
The systems that post to SAP and the ones that read it, through one gateway
SAP sits at the centre of finance and operations, and the estate around it should meet it at a governed boundary rather than through a private wire per system. Inbound documents arrive through BAPIs and IDocs; outbound reads are served through OData from beside the core.
A surface diagram: sales, procurement, field and HR systems post into a single SAP interface boundary that routes every write through a BAPI or IDoc and every read through OData, then serves reporting, portals and downstream analytics from beside the SAP core.
Sales and commerce
Orders and customers arrive as documents through BAPIs, validated against SAP’s model before they post.
Procurement and field systems
Goods receipts and completed work flow in as IDocs, tracked and reprocessed rather than lost on a bad day.
HR and payroll
Cost and headcount data meets SAP’s cost-centre structure instead of forcing SAP to bend to another system’s.
What we do
The SAP interface boundary
One place where every write goes through a BAPI or IDoc and every read through OData, so SAP’s validations and audit apply and the transactional core is never queried directly.
Reporting and BI
Dashboards read through OData or a layer beside SAP, so a heavy query never stalls a month-end close.
Customer and partner portals
Order and account status is served to outside users without exposing the SAP transactional system itself.
Downstream analytics
Authoritative figures leave SAP once, in an agreed shape, rather than being scraped differently by every consumer.
SAP stays the owner of the document; the boundary is what lets the estate use it without endangering it.
Our role
What we integrate into SAP and what your SAP team keeps owning
- 01
Every write through a supported door
We build inbound flows through BAPIs and IDocs so SAP’s validation, authorisation and document flow apply to our integrations exactly as they do to a user, and nothing reaches the tables by a side route.
- 02
Reads that spare the core
We serve other systems through OData and a read layer beside SAP, so reporting and portals do not contend with the postings the business depends on during a busy close.
- 03
The SAP configuration stays yours
Which BAPIs are enabled, what a posting must validate and who may authorise it are your SAP team’s and finance function’s decisions; we make the integration obey them rather than negotiate around them.
SAP’s model and its financial controls are yours and your implementation partner’s to set; we build integrations that post and read through the interfaces SAP supports without weakening what makes its documents defensible, and leave a boundary your team can extend.
Common questions
What buyers ask
Can you write to SAP directly, or does everything have to go through BAPIs?+
Everything that changes SAP data goes through a supported interface, and for transactional writes that usually means a BAPI or an IDoc. Direct table writes are possible and are the wrong answer: they skip the validation, the number assignment and the audit entry that make an SAP figure defensible, and they break unpredictably when SAP changes its internals. The supported interfaces are more demanding to build against, and that is the point — they make the integration accountable to the same rules a user is. We reach for a table read only where SAP genuinely exposes no other route, and never for a write.
We are moving from ECC to S/4HANA. What happens to our integrations?+
The ones built the disciplined way carry across with far less pain than the ones that took shortcuts. S/4HANA changes underlying data structures and leans harder on OData and published APIs than ECC did on RFC and IDoc, so an integration bound to ECC’s internal tables or custom structures is exactly what a conversion breaks. Integrations built against SAP’s supported interfaces are insulated from most of that, because those interfaces are what SAP commits to keeping. Part of a conversion is reviewing each interface, retiring the ones that reached into internals, and moving reads onto OData where S/4HANA now prefers it.
Do we need SAP’s Integration Suite, or can you integrate without it?+
Both are viable, and the choice is about where you want the integration logic to live rather than about whether integration is possible. SAP’s Integration Suite gives you a managed place to run flows with prebuilt content for common SAP scenarios, which earns its keep when you have many flows and want them centrally operated. Integrating without it, through BAPIs, IDocs and OData from your own integration layer, is entirely valid and often the right call for a smaller estate or where you already run an integration platform. What does not change either way is the rule that writes go through SAP’s supported interfaces; the Integration Suite is one way to call them, not a substitute for respecting them.
In this cluster
Next step
Map your SAP doors
A mapping session that names which SAP objects each surrounding system may post through, which reads move to OData, and which controls no integration may bypass, before an interface is built.

