Four components. No invisible boundary.
An illustrative pattern for connecting SAP workflows to customer-approved AI. The final topology depends on the landscape and security review.
01 / SAP landscape
A bounded, approved API or supported extension point. Validate release support, least privilege and whether a request actually needs to read business data.
02 / Application layer
A CAP-based service on an agreed BTP runtime coordinates authorization, input validation, timeouts and the workflow response. It does not automatically inherit SAP end-user authorization.
03 / Approved gateway
An authenticated, approved route to the customer's gateway. Review network controls, API compatibility, model selection, logging and retention.
04 / Selected model
The gateway may route to a customer-hosted or managed model. Confirm the actual provider, region, data-use terms and trust boundary; never infer them from the gateway address.
Your SAP
Approved interface
PODBEL layer
CAP · controls · review
Your gateway
Approved route & policy
Your model
Deployment you select
Your next SAP workflow.
A clearer way forward.
Bring the use case. We'll help define the data path,
the controls, and what a pilot should prove.