The problem
The quickest way to get SAP data out is a general function that can read any table. One interface, all the data. That is exactly why security teams say no: such an interface can see far more than it needs to, there is no way to see who retrieves what, and SAP advises against calling it from outside.
The approach: one object per question
Create a dedicated, specific object in SAP for each data question: "open purchase orders per supplier", "stock per warehouse". Such an object:
- retrieves only the data that is needed;
- can be reviewed by the SAP team;
- follows the normal route from development to test and production;
- can be traced afterwards: who uses which data question?
No extra work for SAP developers
The usual objection is that specific objects take a lot of work. That is why we generate them: a team describes the data question, and the platform creates the object, checks it in SAP and records it. The SAP team keeps oversight without having to build every object itself.
A choice per organisation
Not every organisation has the same requirements. Generic table access may be acceptable for a development environment; for production it usually is not. Record per environment which form is allowed.
What to watch out for
- Never give an interface more access than the question needs.
- Keep an overview of all data questions and who uses them.
- Have a specific object tested and transported just like any other custom development.
Would you like advice on secure access to SAP data? Request a free advice conversation.
Updated on