- How do I connect an app to SAP without writing code?
- In Arctory you describe the app you need, choose your SAP access method and paste the connection details into a secure input. The agent then generates a server-side workflow against the SAP OData service and builds the screens on top of it. In the demo, a production-planning app shows 500 live production orders from SAP S/4HANA about three minutes after the app was created.
- Which SAP systems and access methods does Arctory support?
- Arctory connects to SAP S/4HANA through OData services, using an API key or OAuth client credentials, or to an internal SAP endpoint with username and password. The demo uses the standard S/4HANA Production Order OData service with an API key. If an endpoint or authorization is not yet in place, the agent offers to work through the access setup with you.
- Does the AI see my SAP credentials?
- No. The SAP base URL and API key are entered in a dedicated secure input, stored as secrets and used only by the server-side workflow that calls SAP. The AI agent never sees the values, and they are never sent to the browser, so app users get the data without ever holding the SAP credentials.
- Can Arctory apps write data back to SAP, or only read it?
- Both are built the same way: each SAP call is a server-side workflow that uses the stored credentials. The demo reads production orders and their details. Write-back calls, such as posting a confirmation, are added as further workflows and depend on the OData services and authorizations your SAP team enables for that user.
- What happens if SAP is unreachable or returns an error?
- The app shows it. The generated views include empty, loading and SAP-error states, and when SAP returns an access error the screen displays the returned status so the endpoint or permissions can be checked. Each workflow can also be run on its own in Arctory to test the SAP call and inspect the raw response.
- How long does it take to build an app on SAP data with Arctory?
- Minutes for the first working version. In the demo the full path from creating an empty app to live SAP production orders in a filtered table, a Gantt timeline per work center and a production deployment takes about three minutes. Further screens and logic are added by describing them in plain English or German.