SAP Agent Gateway 入站 A2A 于 2026 年 10 月 GA:外部助手可呼叫受支持的 SAP 代理
据行业解读,SAP 于 2026 年 10 月 27 日确认 Agent Gateway 入站 Agent2Agent(A2A)互操作正式可用:采购等请求可从外部 AI 助手进入受支持的 SAP 代理,执行仍受用户业务授权约束;出站 A2A/MCP 仍属后续方向。
企业里真正卡住智能体落地的,往往不是「会不会写提示词」,而是流程能不能在现有 ERP 权限边界内交接。
据 @marvelqualities 对 SAP 架构中心与 TechEd(2026-10-27)材料的整理:SAP Agent Gateway 的入站 Agent2Agent(A2A)互操作在 2026 年 10 月一般可用(GA)。示意场景是:采购请求可从第三方客户端发起,由 SAP Sourcing Assistant 在 Ariba Sourcing 中准备 RFP 草稿,业务专家审阅确认后再创建 sourcing 事件,事件 ID 与链接再回到原客户端——帖文写明这是示意而非已披露的客户实测结果。
关键变化在于请求的起点:业务过程可以留在受支持的 SAP 代理一侧,而不必在每个外部助手里重写一遍。Agentic Resource Discovery(ARD) 用于发现可用代理,AgentCards 描述能力与 A2A 端点;管理员仍须在 SAP for Me 完成外部客户端接入、身份与信任,并授权选定代理。执行继续受用户业务权限约束。帖文同时提醒:当前里程碑是入站(外部呼叫 SAP 代理);出站 A2A 与 出站 MCP 被列为后续方向,不能据此承诺财务、HR、采购全场景同一体验。
对企业经营与集成团队,更稳妥的试点是跑通「一次完整 sourcing 请求」——含审阅、拒绝与回传链接——而不是只验证连通性。上线前应核对受支持代理清单、Onboarding 指南与审计要求。
flowchart LR
E[外部 AI 助手] -->|入站 A2A| G[SAP Agent Gateway]
G --> S[受支持的 SAP 代理]
S --> R[业务用户审阅 / 授权]
R --> O[Ariba 等业务对象回传]
SAP opens inbound A2A route to SAP agents via Agent Gateway
SAP News 🔗 SAP opens an inbound route from external assistants to SAP agents
A procurement request can start in another AI assistant and reach an SAP sourcing agent without asking the user to switch applications. SAP’s 27 October announcement confirms October general availability of inbound Agent2Agent (A2A) interoperability through its Agent Gateway.
📦 One request, a defined SAP destination
SAP’s illustrative sourcing scenario starts in a third-party client. The SAP Sourcing Assistant prepares an RFP in Ariba Sourcing; the specialist reviews and confirms the draft before the event is created. Its ID and link return to the original client. This is an example, not a reported customer result.
The useful change is where the request begins. The business process can stay with a supported SAP agent rather than being rebuilt inside each external assistant.
🔑 Discovery is only the start
Agentic Resource Discovery (ARD) identifies available agents. Their AgentCards describe capabilities and A2A endpoints. Administrators must still onboard the external client in SAP for Me, establish identity and trust, and permit access to selected agents. Execution remains bounded by the user’s business authorizations.
For delivery teams, our read is to pilot one complete sourcing request, including review, a refused request and the returned event link. A successful connection alone does not prove the business handoff works.
🧭 Check the direction before planning the rollout
This milestone is inbound: external agents calling supported SAP agents. SAP lists outbound A2A and outbound MCP as future direction. It does not make every assistant or business task interoperable today.
Watch the supported-agent coverage and onboarding guidance before promising the same experience across finance, HR and procurement. Start with a task whose completion a business user can verify.
Which would you test first: preparing a sourcing event or checking overdue receivables?
Sources: SAP Architecture Center and TechEd, 27 October 2026 https://t.co/KQXQhj7lHU https://t.co/7Wa4WKokVe
━━━━━━━━━━ 📬 Practical SAP news and analysis. Subscribe free 👉 https://t.co/CktXI2MysY
#SAP #SAPAriba #BusinessAI #EnterpriseIntegration