SAP's documented BYOA pattern lets Joule call remote code-based agents over A2A, including asynchronous task updates. Orchestrate can be exposed behind that handoff while SAP applications remain the system of record and final business authority.
Keep the surrounding platform responsible for what it already does well. Use Orchestrate where durable cross-estate execution and one delegation/audit chain become the requirement.
A Joule capability can call a remote BYOA agent over A2A; SAP business events or APIs can also create or resume runs.
Use the surrounding enterprise trust model at ingress, then bind the run to an Aizen grant and preserve delegation context internally.
Resolve destinations and credentials only at the governed boundary; SAP backends still enforce their own business authorization.
trigger / delegation / intelligence
durable state · joins · HITL · identity
governed side effect
This sequence illustrates how the integration pattern maps into a durable run. Production topology, permissions, latency, and exact APIs depend on the customer's envirnment.
A Joule interaction, business event, or API call creates the run with invoice and caller context.
Orchestrate can fork matching, supplier-data, compliance, or enrichment work while the parent waits durably.
An approval or exception decision can suspend the run without holding an execution worker.
The final posting or update crosses governed egress and remains subject to SAP business authorization.
The initiating experience receives a final result with the relevant lineage and artifacts.
Describe Orchestrate as compatible with SAP's documented remote-agent/A2A architecture when implemented that way. Do not imply SAP has selected, certified, endorsed, or formally partnered with Aizen unless that relationship is separately established. Likewise, treat registration or telemetry into specific SAP governance products as a separately validated integration capability.
.svg)