The core stays untouched
No modifications to your ERP, no new fields, no migration. Reading only, through official interfaces.
Integrations · Enterprise ERP
SAP stays in the back.
Clarity comes forward.
Large ERP systems are dependable and expensive to change — which is exactly why we do not replace them. We put a layer on top where a person finds their bearings in a minute instead of a training course.
The usual state of things
A system that ten people
out of three hundred can drive.
Enterprise ERP is built for accuracy and completeness, not for a fast answer. The result is that managers wait for a report from controlling, and controlling spends days assembling exports. Our layer removes that step in between: the data stays in ERP, the answer is immediate.
Legible to non-specialists
Nobody needs to know transaction codes or module structures. They see their task and their numbers.
Across modules
Finance, sales, materials and HR in one view instead of four separate screens.
Systems
The interfaces
we can go through.
Large systems usually offer several routes out at once. We pick the one that is official, survives upgrades, and puts the least load on your environment.
SAP
SAP- How we read it
- OData through SAP Gateway, CDS views, or RFC and BAPI
- What you get from it
- finance FI/CO, sales SD, materials MM, assets, HR
Technically straightforward. Before any code is written, the indirect access licensing has to be settled — that is a commercial question rather than a technical one, and we help you work through it.
HELIOS iNuvio, Nephrite
Asseco Solutions- How we read it
- MS SQL database and views, REST through the eServer module
- What you get from it
- finance, sales, manufacturing, projects, assets
A useful combination: SQL lets us prove the value quickly, then production reads go through the official interface.
Money S4, S5
Seyfor- How we read it
- API module — REST and GraphQL over HTTPS
- What you get from it
- accounting, stock, sales, orders, banking
The most open of the larger systems on this market. The API module is a separate licence item, so we confirm you have it.
SOFTIP PROFIT PLUS
SOFTIP- How we read it
- today mostly database and exports; an open API is part of the modernisation under way
- What you get from it
- finance, stock, manufacturing, HR
A Slovak vendor with a strong presence in manufacturing and the public sector. We verify the state of its interfaces at project time, because it is changing right now.
Dynamics 365 Business Central
Microsoft- How we read it
- OData v4 and REST API
- What you get from it
- the full finance and sales ledger
One of the easiest connections there is. If this is your system, we can stand a dashboard up very quickly.
Two things first
What we settle
before the technology.
With large systems the obstacle is usually commercial or organisational rather than technical.
Indirect access licensing
When another application reads from ERP it can carry a licence implication — with SAP in particular. We work through it with you and your vendor before a line of code is written. Better to know the constraint at the start than after go-live.
Who releases which data
In a large organisation the question is not “can it be read” but “who is allowed to see it”. So we build views on the roles and permissions that already exist in your ERP — we adopt them rather than work around them.
Read-only start
The first phase never writes anything.
We begin by reading only. Your processes, approvals and audit trail stay exactly as they are. Writing or approvals can be added later — once you have seen for yourself that it makes sense.
Continue
Start with one process
Tell us which numbers
take you longest to find.
In the first consultation we go through your systems, establish what can actually be read from them, and propose the one view that saves you the most work.
Book a consultation →