The problem
A low-code team, a BI department or a webshop builder wants "just some SAP data". But if you do not know SAP, you do not know which tables it is in, how they relate or which kind of interface the SAP team will accept. So everyone waits for that one SAP developer.
Model first
The idea: first describe what you need, independent of the technology. Which data, from which areas, with which relationships, filters and sorting. Developers who work with OutSystems know this way of thinking from building a query in a visual editor.
Only at execution is it decided how the data is retrieved: via a standard SAP query, a custom function, or a modern CDS view. That choice can depend on the SAP version and on what the organisation allows.
Why this works
- Future-proof. During an upgrade the data model stays the same; only the execution changes.
- Understandable. The model says in plain terms what is retrieved, even for people who do not know SAP.
- Reusable. The same model can feed an app, a report or an interface.
Help where SAP stays silent
SAP does not record all the relationships between tables. A good tool therefore suggests relationships with a degree of confidence, instead of pretending they are certain. That way, even someone without SAP knowledge gets honest guidance.
How we do it
In our integration builder, a team visually designs which SAP data is needed. The platform turns that into a dedicated, auditable SAP object. The team does not have to be SAP developers, and the SAP team keeps control. That is unlocking SAP data without giving up oversight.
Would you like advice on unlocking SAP data? Request a free advice conversation.
Updated on