SAP + governed AI agents
SAP access is rarely refused on technical grounds — it is refused because nobody can describe exactly what the integration would be able to do. A reviewed action list, a scoped credential and an approval trail is an answer to that question.
Connecting SAP
| Definition | Import the OData service definition for the specific services you want reachable, usually through SAP API Management rather than directly. |
|---|---|
| Credential | Basic auth against a technical user, or OAuth 2.0 via your gateway. The credential lives in your vault. |
| Stored as | A secret:// reference to your own vault. FlozentAi never holds the value. |
Actions teams usually publish
Action names are yours to choose during review — these are the shapes most teams end up with. Anything that writes is confirmation-gated unless you deliberately publish it otherwise.
| Action | Kind | What it does |
|---|---|---|
businesspartner.get | Read | Read a business partner record. |
salesorder.list | Read | List sales orders by customer. |
salesorder.create | Write | Create an order after approval. |
What people build with it
- Order and delivery status inside a customer-facing assistant.
- An internal agent that assembles order detail for a human to submit.
There is no field in the console that accepts a token or a password. You store the secret in your vault and give FlozentAi a reference; the runtime resolves it inside the execution layer, after the policy decision.
SAP questions
Do you support RFC or IDoc?
Not directly. FlozentAi calls HTTPS endpoints described by an OpenAPI or OData definition. Teams that need RFC usually front it with a gateway service and import that.
Use cases that involve SAP
Connect SAP the governed way.
Import the specification, review what it found, and publish only what you want reachable.