In short
Many companies build apps and portals in OutSystems on top of their SAP system. The usual route is SAP OData, via the OData services SAP provides: the OutSystems platform calls them as a web API, retrieves data and sends changes back.
How to approach it
- First look for an existing service. SAP provides many standard APIs, described in the SAP Business Accelerator Hub (formerly API Business Hub), often with an OpenAPI description you can import.
- Put the integration in its own module. One integration module per SAP service, with clean actions such as "Get order" or "Create notification". The screens only use those actions and know nothing about SAP.
- Retrieve only what you need. Use OData's filter and selection options ($filter, $select, $top), so you do not pull entire tables over the line.
Writing to SAP
For changes, SAP Gateway first requires a CSRF token, which must be sent along with the change request. Handle that once in the integration module. Check SAP's error messages and pass them on to the user in an understandable way.
Security
- If the integration works with a single technical user, SAP cannot see who made the change. Where that matters, you use principal propagation: the actual user is passed on to SAP.
- Let the OutSystems server talk to SAP, not the user's browser.
What to watch out for
- OData in OutSystems is meant for apps that display and edit data, not for bulk data transfer.
- An app that creates documents in SAP can have licence implications (indirect or digital access).
- Consider keeping master data that rarely changes as a local copy, and read fast-changing data live.
Would you like advice on SAP and OutSystems? Request a free advice conversation.
Updated on