TalkTalkA recorded or written talk.See every one →SAP TechEd — session catalogue
Onboard a trading partner from agreement to live monitoring
One trading partner onboarded from scratch in Trading Partner ManagementTrading Partner ManagementPartner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of Cloud Integration so one flow serves every partner, inside SAP Integration Suite.sap official, btp: a trading partner agreementTrading partner agreementsKeeping track of who business documents are exchanged with and what is set up with each partner: a profile per partner with its contact person, identifiers, communication protocol and B2B standards, an agreement per partner, and one generic flow parameterised from them in place of a flow per partner. What a message looks like and how it maps is B2B message mapping, and executing the exchange is integration flows.SAP only configured, a business document mapped with ML-assisted mapping proposals, which is B2B message mappingB2B message mappingDefining the structure of business messages exchanged between partners using different standards, and mapping one structure onto another. This includes interface specifications, schemas and transformations; executing them in middleware belongs to integration flows.SAP only, and a transaction run and monitored live, all inside SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp with no EDI tooling outside it. The abstract names the steps and not the document standard or the partner's protocol. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Claudia Carabineiro, Marco Ertel, Marton Luptak and Tobias Griebe, written here from SAP's abstract; the recording is not yet published.
Where it sits
Explains
Trading Partner ManagementBTPTrading Partner ManagementPartner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of [Cloud Integration](artifact:btp-cloud-integration) so one flow serves every partner, inside [SAP Integration Suite](artifact:btp-integration-suite).SAP Integration SuiteBTPSAP Integration SuiteSAP's integration service on BTP: [Cloud Integration](artifact:btp-cloud-integration) for orchestration, [API Management](artifact:btp-api-management) in front of it, and an MCP gateway that serves a managed API to agents.Trading partner agreementsBTPTrading partner agreementsKeeping track of who business documents are exchanged with and what is set up with each partner: a profile per partner with its contact person, identifiers, communication protocol and B2B standards, an agreement per partner, and one generic flow parameterised from them in place of a flow per partner. What a message looks like and how it maps is [B2B message mapping](capability:b2b-message-mapping), and executing the exchange is [integration flows](capability:integration-flows).B2B message mappingBTPB2B message mappingDefining the structure of business messages exchanged between partners using different standards, and mapping one structure onto another. This includes interface specifications, schemas and transformations; executing them in middleware belongs to [integration flows](capability:integration-flows).
Properties
About this work
Published on
Group by49 of 49 pieces
Piece, what it offersStill applies
How Have SAP Customers Adopted n8nHow Have SAP Customers Adopted n8nA Devtoberfest 2026 session on what SAP customers are building with the standalone edition of n8n, from a partner who maintains an SAP OData node for it: use cases across purchase-to-pay, sales, finance and IT service, two live workflows, and the rules he works to — released SAP APIs only, no LLM in the decision path, exceptions to a person. The tool-choice half is where the edges hold: SAP Integration Suite is placed as the job for governed, high-volume system-to-system integration, and its MCP server is what the agent in the second demo reads SAP data through, while process automation is the concern the session sorts between document intake, approvals and the bot inventory that stays with RPA. The first demo is an order-confirmation check that reads a PDF, compares the lines against the purchase order over OData, asks a person, then writes the confirmation back.SAP Developers, published 2026-10-08
Powering Enterprise-Ready Agentic AI with SAP Integration SuitePowering Enterprise-Ready Agentic AI with SAP Integration SuiteA Devtoberfest 2026 session (INT-31) from SAP Integration Suite product management on the MCP gateway. The demo creates an MCP server in a design package from an API already deployed on the tenant, exposes two of its 300-odd resources as tools, attaches authentication and quota policies on a policies tab, and publishes the deployed endpoint as an AI product in Developer Hub of API Management, where an agent subscribes and receives a token, URL, key and secret; the calls then show up in monitoring, in message processing logs and in the analytics dashboard, which is the MCP exposure and the tool governance the edges rest on. Three AI features inside Cloud Integration follow: a content migration agent that converts a PI/PO Java mapping into a Groovy script and generates a second integration flow for its lookup, memory profiling during a flow simulation, and root-cause analysis on a failed message processing log.SAP Developers, published 2026-10-07
🔴 Your Agent Wants to Call SAP. Now What?🔴 Your Agent Wants to Call SAP. Now What?Devtoberfest 2026 session INT-23, on what belongs between an agent and an SAP system. A solution advisor and an enterprise architect point Joule Desktop extensions at MCP servers built on API Management inside SAP Integration Suite, and ask it for business partners, orders and line items from an S/4HANA demo system; asked for the ten largest customers it answers from a sample of 200 orders rather than reading the whole table. They then open the API proxy behind it, where a spike arrest policy caps the backend at ten calls per second and the MCP server is configured to expose only the GET resources of the business-partner API so that an agent cannot create one, which is where the edges to Serve your application over MCP and Rate limiting hold. For totals across all sales orders they send the agent to SAP Business Data Cloud instead of the transactional system, since it aggregates and is read-only, and back through Integration Suite for writes such as journal entries.SAP Developers, published 2026-09-30
Expose RFCs as MCP Tools in Integration SuiteExpose RFCs as MCP Tools in Integration SuiteWalks through creating an MCP server in SAP Integration Suite from an RFC source: an on-premise RFC destination labelled for Integration Cell inclusion, a search over the backend's function modules (minimum seven characters), and up to 50 selected modules each becoming a tool. Covers the resulting server's configuration (Source, Tools and Prompts, with no Resources section for this source) and the two scopes an RFC-based server's policy adds beyond an API-sourced one, API.invoke and ESBMessaging.send, plus the RFC receiver adapter used at runtime. Demonstrates the flow with a purchase-order scenario where an AI client calls BAPI_PO_CREATE1 and BAPI_PO_GETDETAIL1 as MCP tools.ronit199666, published 2026-09-24
From APIs to Agent Tools: How MCP Gateway changes what Integration meansFrom APIs to Agent Tools: How MCP Gateway changes what Integration meansThe opening session of the Devtoberfest 2026 integration track, in which two product managers for SAP Integration Suite set out why the suite puts an MCP gateway between agents and backend systems, and then build one. The demo turns an HTTP endpoint and its OpenAPI specification into MCP tools on the integration cell runtime, does the same on top of an existing API-centric integration, and shows the policies tab where authentication through an external provider, quotas, spike arrest and IP filtering sit, plus the trace of the JSON-RPC calls in monitoring and the agent they are earmarked against in analytics. That is where the serve your application over MCP and tool governance edges hold; RFCs and BAPIs as sources are stated as supported, and MCP federation, custom domains and edge integration cell as roadmap.SAP Developers, published 2026-09-23
Supercharge Joule Desktop: Connect Any SAP API in Minutes with MCP GatewaySupercharge Joule Desktop: Connect Any SAP API in Minutes with MCP GatewayDevtoberfest 2026 session INT-13, in which an SAP solution advisor connects a live S/4HANA system to the desktop experience of Joule Work through the MCP gateway in SAP Integration Suite. One OpenAPI specification covering business partners, sales orders, material stock, billing and purchase requisitions is uploaded as an MCP server artifact, deployed to integration cell with XSUAA inbound authentication, and registered as an MCP connector; the destination behind it is then switched from basic authentication to principal propagation, and the Cloud Connector monitor shows the same question arriving as the presenter's own user. That demonstration is the serve your application over MCP edge, and the second half is Joule Work itself: a Markdown skill that fixes the steps and format of a customer briefing, and a Space the skill rebuilds with each run.SAP Developers, published 2026-09-23
SAP Just Became AI-Agent Ready — Here's a Step-by-Step MCP WalkthroughSAP Just Became AI-Agent Ready — Here's a Step-by-Step MCP WalkthroughBuilds an MCP Server on SAP Integration Suite's Integration Cell, in front of a Cloud Integration flow that passes an OData V4 backend through untouched, with three tools generated from an OpenAPI spec. Secures it with OAuth 2.0 on SAP BTP client_credentials against XSUAA, and walks through the scope mismatch — the service key issues ESBMessaging.send, not the server's default API.invoke — that returns 403 until corrected; the finished server is then registered as a tool in Claude Code.published 2026-09-04
SAP Integration Suite + MCP: A Practical Architecture for AI Agents and SAPSAP Integration Suite + MCP: A Practical Architecture for AI Agents and SAPLays out the runtime chain for exposing S/4HANA APIs to an AI agent through SAP Integration Suite: the agent calls a tool on the MCP Gateway, which is built from a governed API Artifact, which still runs on Cloud Integration for mapping, routing and error handling before reaching the backend. It states that the API-artifact approach requires the Integration Cell runtime rather than the normal CPI message-processing runtime, an OAuth-secured REST or OData artifact on OpenAPI 3.0.0-3.0.3, and an entitlement that is service-plan dependent (citing SAP Note 2903776) — so the architecture question is whether the landscape already has the right MCP entitlement, runtime and API foundation.aayushaggarwal, published 2026-09-02
SAP API Management for Beginners – Part 1: What Is APIM & A Complete Features TourSAP API Management for Beginners – Part 1: What Is APIM & A Complete Features TourA features tour of SAP Integration Suite's API Management capability, opening a five-part beginner series: what a governed API proxy adds over calling a backend directly, and a walkthrough of API Providers, Proxy and Target Endpoints, the Policy Editor and Policy Templates, Products, the Developer Hub, and Key Value Maps. It names rate limiting's two complementary policies as APIM implements them: Spike Arrest, which caps requests per second or minute against bursts, and Quota, which caps total calls per day, week or month against overuse.Rudhra, published 2026-08-03
RFC/BAPIs Meet AI Agents: Why SAP Integration Suite MCP Server MattersRFC/BAPIs Meet AI Agents: Why SAP Integration Suite MCP Server MattersExplains that SAP Integration Suite's MCP Server artifact can expose RFC-enabled BAPIs, alongside API artifacts and HTTP endpoints, as MCP tools — letting BAPIs on SAP ECC or on-premise S/4HANA participate in agentic workflows without rewriting business logic or waiting for a full ERP transformation. Frames RFC support as a bridge for organisations still modernising rather than a recommendation to build new RFC-based integrations, and notes the exposed BAPIs inherit the server's existing authentication, rate limiting and IP filtering. A demo built against an SAP ECC backend shows an MCP client discovering and invoking several read-only BAPIs from natural-language prompts, with no custom wrapper code.arunmaarirajha_kv, published 2026-07-28
MCP Servers on SAP Integration Suite : Build Your First MCP Server from an APIMCP Servers on SAP Integration Suite : Build Your First MCP Server from an APIWalks through building an MCP server on SAP Integration Suite from an existing managed API — SAP S/4HANA's Purchase Order API — rather than from an HTTP endpoint or an RFC, which the same creation wizard supports but a later post in the series is left to cover. Selected API operations become MCP Tools with generated input and output schemas, the server inherits its Authentication policy from the source API, and a Process Integration Runtime service instance supplies the OAuth credentials an external client needs to invoke it. Ends by connecting the deployed server to Cline in VS Code and having it chain tool calls to answer a natural-language purchase-order query.published 2026-07-15
Turn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free TrialTurn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free TrialWalks through building an MCP server on SAP Integration Suite's free trial from an existing API artifact — the Business Partner API against a public S/4HANA Cloud sandbox — rather than from an HTTP endpoint with an OpenAPI specification or from RFC-enabled function modules, the creation wizard's other two source types, left unexplained here. Covers the API artifact's Content Modifier policy that injects the Business Accelerator Hub API key before the backend call, and the "Trust Upstream MCP Authorization" setting that lets the MCP server delegate authorization checks to that source API instead of duplicating them. Ends by fetching an OAuth token from a Process Integration Runtime service key and pointing an MCP client at the deployed server over streamable HTTP.published 2026-07-13
Building MCP Servers with SAP Integration Suite: What to Design, Not Just How to ConnectBuilding MCP Servers with SAP Integration Suite: What to Design, Not Just How to ConnectArgues that the tool design, not the connection, is the hard part of putting an API in front of an agent. Works one request — create a customer — through eight endpoint-shaped tools, where the agent carries ids between calls and rebuilds the business rules each run, then through a single intent-shaped create_customer that hides the sequence; and says what separates the two: a business operation for a name, parameters a caller can supply without a lookup, the rules in the server rather than the prompt, and a description written for an agent choosing a tool. The SAP Integration Suite half is short — three creation paths, an iFlow behind the API artifact when a tool has to cross systems — and it closes on a checklist to run before publishing.published 2026-07-07
Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario Part - 3Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario Part - 3Builds the inbound side of a custom EDIFACT-to-IDoc scenario on Trading Partner Management: an iFlow picks a file from SFTP and sets headers for adapter type, document standard, namespace, version and sender and receiver IDs, and a second iFlow assembles them into the agreement's plain partner ID and matches it in the Partner Directory. A Groovy script then calls PartnerDirectoryService.getParameter to read a partner's custom activity parameters and general value-mapping data stored under the agreement, so dynamic field mapping comes from the agreement rather than a flow per partner. Third of a series on setting up trading partner agreements in SAP Integration Suite, after the TPM foundation and the agreement itself in parts 1 and 2.amysh95, published 2026-03-10
Stop Building From Scratch: Unlocking SAP Cloud Integration’s Standard ContentStop Building From Scratch: Unlocking SAP Cloud Integration’s Standard ContentArgues against building integrations from scratch by pointing to the Discover space of Cloud Integration: over 700 prebuilt integration packages and nearly 4000 iFlows, covering common scenarios such as S/4HANA-to-Salesforce business-partner and order sync, included at no extra cost under an SAP Integration Suite licence. Walks through where to find and copy a package, and the support trade-off it creates: SAP keeps supporting the standard baseline, but once a flow is directly modified the customer owns the lifecycle of that change, which the author sets against patterns like overlay mappings and wrapper orchestrators that preserve support.Punith_Oswal, published 2025-12-19
Enhancing Business Processes with SAP BTP AI in SAP Integration SuiteEnhancing Business Processes with SAP BTP AI in SAP Integration SuiteWalks through a post-exit iflow in SAP Integration Suite that calls an LLM through SAP AI Core's Generative AI Hub to turn a customer's free-text return comment into one of a fixed set of SAP rejection-reason codes, so an inbound ORDERS05 IDoc carries a decision (E1EDP01-ABGRU) the ERP can act on without pausing for manual review. The worked example is a Commerce Cloud returns flow into S/4HANA; the piece argues the same bounded-classification pattern fits other narrative fields — delivery-exception remarks, expense-claim justifications — where the cost of an LLM call is repaid by removing a human review step, and points to a colleague's post on the Generative AI Hub orchestration workflow for the guardrailing (prompt templating, data masking) it only names.arunmaarirajha_kv, published 2025-12-15
Completing the B2B migration into SAP Integration Suite visionCompleting the B2B migration into SAP Integration Suite visionWalks through migrating SAP PI's B2B integrations — EDIFACT, X12 and other partner formats — into Trading Partner Management in SAP Integration Suite: recording test messages from SAP PI, creating partner profiles, and filling a Self Partner Agreement template that references the MIG and MAG guidelines SAP's own migration path builds on. The author's migration tool, Figaf, turns each Operation Mapping into a Process Direct flow, carrying its UDFs to Groovy or SAP's Cloud Integration Function Libraries, then reruns the recorded test cases against the result.DG, published 2025-09-09
Edge Integration Cell on HyperscalersEdge Integration Cell on HyperscalersSAP's architecture for Edge Integration Cell, the runtime of SAP Integration Suite that executes integration flows in a Kubernetes cluster the customer runs, while design, monitoring and governance stay on SAP BTP and the runtime reaches BTP over outbound-only channels. The main page gives the reasons SAP names for it: data residency, security policies that forbid inbound access, and latency to a distant BTP region. Three sub-pages draw the same setup on AWS, Azure and Google Cloud, each with a private network across three availability zones, a managed Kubernetes cluster, managed PostgreSQL and Redis, sizing left to an SAP Note, and each says it outlines a small production deployment to be treated as a starting point.published 2025-04-18
API Managed IntegrationAPI Managed IntegrationSAP's reference architecture for API-managed integration, which puts the API Management capability of SAP Integration Suite in front of business applications as API proxies that intercept each call to apply security policies, transformations and governance and to collect usage metrics. SAP defines it as a pattern that complements the other integration patterns, and draws three routes behind the proxy: a managed API forwarded to its provider for simple transformations and protocol adaptations, the Graph capability exposing data from several sources as one connected API, and Cloud Integration for mediation beyond API Management's scope, with the edge integration cell runtime for managing APIs in a customer-managed Kubernetes environment. SAP states that it delivers no predefined scenarios for this pattern, so the proxies and policies are the customer's or partner's to build.published 2024-08-01
Application to Application IntegrationApplication to Application IntegrationSAP's reference architecture for application-to-application integration, where messages carrying transactional data such as sales orders pass between business applications in near real time and each one triggers the next process step. When the sender's and receiver's APIs do not match, Cloud Integration in SAP Integration Suite sits between them to determine receivers, filter, map structures and convert protocols, which is the ground of integration flows; SAP Connectivity service, Cloud Connector and SAP Destination service reach on-premise receivers, and the edge integration cell runtime keeps processing inside a customer-managed landscape where compliance requires it. Direct exchange without middleware is allowed when the two APIs already align, asynchronous communication is the default the page states, and it is drawn at the level of the pattern, following SAP's Integration Solution Advisory Methodology, without designing any one flow.published 2024-08-01
Business to Business IntegrationBusiness to Business IntegrationSAP's reference architecture for business-to-business integration, the exchange of business documents with customers, suppliers and other trading partners over agreed standards such as EDIFACT, ANSI X.12 and IDoc and protocols such as AS2. Its design-time steps are Cloud Integration in SAP Integration Suite, the predefined content of SAP Business Accelerator Hub, and Integration Advisor, which defines message implementation and mapping guidelines and generates runtime artifacts from them; Trading Partner Management then turns partner profiles into agreements pushed to the Partner Directory, and generic integration flows on Cloud Integration read those agreements at runtime to exchange messages with each partner. The alternatives it names are API-based exchange where an industry has standardised its APIs, and SAP Business Network with the managed gateway for spend management in place of connecting partners one by one.published 2024-08-01
Connect Business Processes with SAP Master Data IntegrationConnect Business Processes with SAP Master Data IntegrationSAP's reference architecture for keeping master data such as materials, business partners and cost centres consistent across applications with SAP Master Data Integration, a central hub that stores every change in an event log and distributes it to the solutions that consume it. Cloud Integration in SAP Integration Suite carries what the hub does not reach, SAP solutions it does not yet support and third-party or on-premise systems, through an SAP Master Data Integration adapter, which is where the design meets integration flows; newer SAP S/4HANA releases connect to the hub without it. Consolidation, data quality and central governance are outside the architecture and left to SAP Master Data Governance, and SAP Master Data Integration itself has no entry in the atlas yet.published 2024-08-01
Information Map – Introduction Series: Graph in SAP Integration SuiteInformation Map – Introduction Series: Graph in SAP Integration SuiteIntroduces Graph, an enhancement to API Management within SAP Integration Suite that gives developers a single API onto an organisation's business systems, modelled as one semantically connected business data graph, later renamed API Composition. Splits the work between an administrator, who enables SAP BTP destinations to the backend systems and builds the business data graph, and a developer, who explores it in the Graph Navigator tool and builds an application against the resulting Graph API.published 2024-02-21
More than 100 trading partners, one platform: Scalable B2B at Algoma SteelMore than 100 trading partners, one platform: Scalable B2B at Algoma SteelB2B integration at Algoma Steel on SAP Integration Suite: more than 100 trading partners served through Trading Partner Management and one generic integration flow architecture, ML-assisted mapping for the documents, and EDI at that scale after a move from SAP Process Integration and SAP Process Orchestration. The abstract names the three pieces, which is the trading partner agreements model, and not the partner standards or the mapping tooling behind them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Jagesh Lakdawala and Marco Ertel, written here from SAP's abstract; the recording is not yet published.
Third-Party MCP Server Access to SAP Solutions on BTPThird-Party MCP Server Access to SAP Solutions on BTPDescribes external MCP servers and custom servers on BTP, assigning their operators responsibility for authentication, scoped identity, API limits, logging and lifecycle. The permitted use remains conditional on the SAP API Policy, while SAP Integration Suite and Joule Studio are described as SAP-provided paths. Hosting a server on BTP does not automatically supply its governance controls.Dhawal Joshi, Harut Ter-Minasyan, Mirko Günther
Model Context Protocol (MCP)Model Context Protocol (MCP)Frames the Model Context Protocol as the answer to an M-times-N integration problem: one shared protocol turns M agents and N tools into M plus N connections, and one server can be called by any compliant agent. On SAP BTP its implementation section lists an SAP MCP Hub as a no-code way to expose enterprise tools, SAP Integration Suite's MCP Gateway as what it calls the governed path for exposing SAP and non-SAP APIs as MCP-compliant tools, custom SDK-based servers, SAP's MCP servers for development, and an MCP adapter for CDS as a CAP plugin marked coming soon. That is the ground MCP servers covers; for security it points at a separate page.
MCP Gateway in Practice: Architecture, configuration, and hands-onMCP Gateway in Practice: Architecture, configuration, and hands-onA Devtoberfest 2026 integration-track session (INT-21) on the MCP gateway of SAP Integration Suite: curated enterprise APIs served to agents as MCP tools over JSON-RPC, behind the authentication, authorization and traffic policies an API artifact already carries, with the existing API layer left in place. The hands-on half composes S/4HANA plant, material-stock and supplier data with a non-SAP location-risk source into one business data graph, downloads its OpenAPI specification, creates an MCP server artifact with tools, prompts and a surge-protection policy over that endpoint, and publishes it as a product in Developer Hub of API Management, where an agent developer subscribes and gets OAuth credentials. An MCP client then asks for 15 brake pads and ranks plants by stock, location risk and distance from Walldorf, which is what the agent access to your systems edge rests on; the Q&A covers principal propagation to the backend, how errors reach the model, and which Integration Suite editions carry the gateway.SAP Developers
Edge Integration Cell - what's new?Edge Integration Cell - what's new?A Devtoberfest 2026 integration-track session (INT-41) on Edge Integration Cell, the runtime of SAP Integration Suite a customer runs on their own Kubernetes cluster while design, configuration and monitoring stay in the cloud tenant. It names what the customer has to provide — a supported Kubernetes platform, SAP HANA or PostgreSQL, Redis or Valkey as data store, a load balancer — then the Edge Lifecycle Management cockpit with its monthly rolling updates, the inbuilt and the external Cloud Connector options and why a DMZ placement calls for the second, and the adapters available only on Edge: RFC sender, NFS, OFTP2 and UNF. The demo deploys an OFTP-to-file flow to the Edge runtime and shows the same flow rejected when its runtime profile is switched to cloud, which is where the Integration flows edge holds.SAP Developers
MCP Server — SAP Integration SuiteMCP Server — SAP Integration SuiteSAP's own page for the MCP Server artifact in SAP Integration Suite, and where the gateway that runs it is described: MCP clients and API clients reach the same backends through two gateways that share security, traffic management and multi-protocol connectivity. Sets out the three primitives a server may expose — tools derived from API operations with an input and output schema, resources addressed by URI for context rather than action, and prompts as reusable interaction patterns. Says availability depends on the Integration Suite service plan, and points at the three creation paths as separate pages.
OData entity as a governed query surface for agents, not a toolOData entity as a governed query surface for agents, not a toolAn OData entity, generated from the annotations a service already carries, as the surface an agent queries over SAP data: filterable, selectable and sortable fields, authorisation injected on the server side, and a bound query cost, instead of the entity as a tool. SAP's abstract sets this against the MCP gateway in SAP Integration Suite, where exposing an API is the easy part and getting an agent to pick the right one is not, which is the tool governance concern read through OData. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Aleksandr Ivanov and Evgenii Shirokikh, written here from SAP's abstract; the recording is not yet published.
Build an AI-assisted known error database with SAP Integration SuiteBuild an AI-assisted known error database with SAP Integration SuiteThe AI adapter in SAP Integration Suite builds a known error database for integration support: runtime exceptions are captured, analysed by a model, matched against past incidents, and a resolution is proposed, so the base grows with each case. SAP's abstract names the adapter and the four steps, and claims shorter troubleshooting time without a figure. A TechEd 2026 session (Wednesday 28 October, Berlin), with no speaker listed in the catalogue at the time of writing, written here from SAP's abstract; the recording is not yet published.
Building API-centric integration flows with SAP Integration SuiteBuilding API-centric integration flows with SAP Integration SuiteAn API-first way of working in SAP Integration Suite: one integration case, its API artifacts built, configured and run, then reused in other scenarios, with the abstract putting the gain in reuse and lifecycle management for teams used to point-to-point integration. It does not say which Integration Suite capability holds the API artifact or how it sits beside an integration flow. A two-hour hands-on TechEd 2026 session (Wednesday 28 October, Berlin), presented by Karsten Strothmann, Kathrin Widenmann, Marton Luptak, Nils Lorenz and Shivani Borkar, written here from SAP's abstract; the recording is not yet published.
Govern AI-supported actions across enterprise systemsGovern AI-supported actions across enterprise systemsGoverning what an AI agent may do once it takes business actions across enterprise systems, which is the Tool governance concern, with SAP Integration Suite as the place it is enforced. The abstract lists the mechanisms, scoped APIs, event-driven workflows, runtime policy enforcement, exception handling and observability across SAP and third-party systems, and names no Integration Suite feature behind any of them. A TechEd 2026 session (Tuesday 27 October, Berlin; also IN200V, virtual), presented by Finny Babu and Piyush Gakhar, written here from SAP's abstract; the recording is not yet published.
Accelerate your migration to SAP Integration SuiteAccelerate your migration to SAP Integration SuiteMigrating from SAP Process Integration and SAP Process Orchestration to SAP Integration Suite, which is the Platform migration concern on the integration side. The abstract promises the services and tools available for the move, new AI-assisted innovations among them, and guidance for a migration project; it names none of the tools, so what the session covers beyond the migration path itself is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Morten Wittrock and Nils Lorenz, written here from SAP's abstract; the recording is not yet published.
Mercedes-Benz’s journey to SAP Integration SuiteMercedes-Benz’s journey to SAP Integration SuiteMercedes-Benz's move from SAP Process Integration and SAP Process Orchestration to a centrally governed integration platform on SAP Integration Suite, run for several business domains at global scale, which is a Platform migration case told by the customer. The abstract promises the architectural and operational decisions behind it and states none of them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Oliver Weng and Sebastian Buhlinger, written here from SAP's abstract; the recording is not yet published.
Build integrations faster with AI-assisted design and operationsBuild integrations faster with AI-assisted design and operationsAI-assisted integration development in SAP Integration Suite: the abstract names embedded generative AI tools that speed up building integrations, agent-ready APIs and event-driven architectures that connect SAP and third-party systems. The Integration Suite edge holds because it is the subject; the Integration flows edge rests on the phrase integration development alone, since the abstract names no tool, no capability area and no feature. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Finny Babu and Shilpa Vij, written here from SAP's abstract; the recording is not yet published.
Modern integration at TÜV Rheinland: APIs, events and cloud transformationModern integration at TÜV Rheinland: APIs, events and cloud transformationTÜV Rheinland's migration from SAP Process Orchestration to SAP Integration Suite with API-led connectivity and event-driven architecture, told through business cases. The abstract names what was used: the SAP Integration Suite, Event Mesh capability, API Management, generative AI for faster development and SAP Cloud ALM for monitoring. It states nothing about how any of them was used, so the edges rest on the names and on the Platform migration the story starts from. A TechEd 2026 session (Wednesday 28 October, Berlin), written here from SAP's abstract; the recording is not yet published.
Modernisation and migration to SAP Integration Suite made simpleModernisation and migration to SAP Integration Suite made simpleA hands-on platform migration of SAP Process Integration and SAP Process Orchestration scenarios into SAP Integration Suite: the migration assessment run against a legacy landscape to see what converts automatically, the migration tooling in Integration Suite run on the scenarios, and the resulting integration flows adjusted and deployed. What the assessment classifies a scenario by, and which adapters convert, is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Claire Tseng, Craig Stasila, Nils Lorenz and Sunny Kapoor, written here from SAP's abstract; the recording is not yet published.
Model context protocol (MCP) unlocked: Enable governed access to AI agentsModel context protocol (MCP) unlocked: Enable governed access to AI agentsThe MCP Gateway in SAP Integration Suite: the place policy, security and analytics are applied to a curated set of MCP tools before an AI agent reaches enterprise tools and APIs through it, tool governance done in the integration layer and agent access to your systems routed through one gateway. The abstract names the gateway and its three functions and does not say how tools are curated, which policies exist or how the agent authenticates. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Bruno Renzo, Emily Mui, Markus Winter and Sunny Kapoor, written here from SAP's abstract; the recording is not yet published.
Build an integration scenario from scratch with AI assistance at every stepBuild an integration scenario from scratch with AI assistance at every stepBuilds an integration scenario in SAP Integration Suite from nothing and takes it through design, deployment, optimisation, monitoring and resolution with AI assistance at each step, which is the Integration flows concern worked end to end. The abstract names the phases and the kinds of help, development, analysis, troubleshooting and continuous improvement, and no feature or tool that gives them. A TechEd 2026 hands-on session (Tuesday 27 October, Berlin), presented by Craig Stasila, Finny Babu, Prashant Gautam and Shilpa Vij, written here from SAP's abstract; the recording is not yet published.
Road map for SAP Integration Suite: What ships next across all capabilitiesRoad map for SAP Integration Suite: What ships next across all capabilitiesSAP's road map for SAP Integration Suite across its capability areas: API Management, event-driven integration, business process and trading partner integration, and hybrid runtimes for SAP and third-party systems. The abstract promises recent deliveries and the planned innovations that make the platform agent-ready within SAP Business AI Platform; it names the areas and no shipping item, so the edges rest on the product and the one area it names by a product name. A TechEd 2026 session (Thursday 29 October, Berlin; also IN804V, virtual), written here from SAP's abstract; the recording is not yet published.
Roadmap to upgrade from SAP Process Orchestration: Agentic era preparationRoadmap to upgrade from SAP Process Orchestration: Agentic era preparationThe road map for moving from SAP Process Orchestration to SAP Integration Suite, a platform migration with two named items: AI-supported migration tooling in Integration Suite that takes manual effort out of the conversion, and the Edge Integration Cell runtime as the governed hybrid runtime for secure deployments, in the abstract's words. Neither is described beyond its name, so what the tooling converts and what Edge Integration Cell runs is not stated. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Arti Gopalan, Shilpa Vij and Udo Paltzer, written here from SAP's abstract; the recording is not yet published.
Intelligent, governed, and agentic integrations with SAP Integration SuiteIntelligent, governed, and agentic integrations with SAP Integration SuiteSAP Integration Suite positioned as the control plane that connects and governs agentic workflows across SAP and third-party systems, set against the abstract's claim that exposing back ends directly to AI brings security, compliance and cost risks. That governing role is the Tool governance concern; the abstract promises recent innovations and names none. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Finny Babu and Piyush Gakhar, written here from SAP's abstract; the recording is not yet published.
Evolution of the Code10 CI Accelerator add-on for SAP Integration SuiteEvolution of the Code10 CI Accelerator add-on for SAP Integration SuiteThe Code10 CI Accelerator, a partner add-on that puts a process monitor over pipeline concepts and patterns in Cloud Integration, the Edge Integration Cell runtime and more of SAP Integration Suite, and how it has changed as the suite has. The add-on is not in the atlas, so the edges rest on the Integration Suite capabilities it monitors; the abstract names no pipeline pattern and no feature of the add-on. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Antonio Valladares Fernandez, written here from SAP's abstract; the recording is not yet published.
B2B integration factory: How Versuni verified more than 200 EDI interfacesB2B integration factory: How Versuni verified more than 200 EDI interfacesHow Versuni prepared its EDI landscape for a migration to SAP Integration Suite using Int4 Suite: automated validation across more than 200 interfaces, trading partner dependencies removed from the test, issues found earlier, and a repeatable approach for large B2B programmes. Int4 Suite is not in the atlas, so the piece enters on Integration Suite as the migration target and on the Platform migration concern; what was validated and how is not stated beyond the count. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Henk Wouda and Michal Ibrom, written here from SAP's abstract; the recording is not yet published.
Integrating automation with agentic AI and complex file transfer needsIntegrating automation with agentic AI and complex file transfer needsDeterministic automation around SAP's agentic offerings, Joule Agents among them, with SAP Integration Suite on the automation side and new managed file transfer capabilities in it that SAP's abstract names without describing. A panel of automation practitioners and the suite's product managers; the abstract states that the file transfer feature exists and nothing of its shape. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Morten Wittrock, Sven Kohlhaas and Udo Paltzer, written here from SAP's abstract; the recording is not yet published.
SAP Integration Suite as the foundation for enterprise agentic AISAP Integration Suite as the foundation for enterprise agentic AISAP Integration Suite as the way an agent reaches systems: SAP's abstract says it gives agents governed access to APIs, events, applications, trading partners and processes across SAP and third-party landscapes, with AI assistance in the design, deployment and operation of the integrations. That is agent access to your systems through middleware; the abstract names no protocol and no gateway. A TechEd 2026 session (Tuesday 27 October, Berlin; also ST104V, virtual), presented by Markus Winter and Udo Paltzer, written here from SAP's abstract; the recording is not yet published.
AkzoNobel: Modernizing integration at enterprise scaleAkzoNobel: Modernizing integration at enterprise scaleAkzoNobel moving webMethods, SAP Process Orchestration and Microsoft BizTalk onto SAP Integration Suite, with Rojo Consultancy: SAP's abstract states more than 100 third-party applications on the new platform and the preparation for event-driven and AI-enabled integration. A platform migration told by the customer; the abstract names the three source platforms and not the tooling used to convert them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Oussama Zoubairi, Piyush Gakhar and Sander Kool, written here from SAP's abstract; the recording is not yet published.
Build real-time event-driven integrations for your enterpriseBuild real-time event-driven integrations for your enterpriseEvent-driven integration with SAP Integration Suite, advanced event mesh inside SAP Integration Suite: where events beat request-response, how publish and subscribe decouple systems, and what a phased move to event-driven integration looks like. Event Mesh as architecture; the abstract names no broker protocol and no CDS mapping. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Daniel Dorst and Karsten Strothmann, written here from SAP's abstract; the recording is not yet published.
Details
Graph
Trading Partner Managementartifact
SAP Integration Suiteartifact
Trading partner agreementscapability, core only
B2B message mappingcapability, core only
SAP TechEd — session cataloguepublishing source
SAP TechEd — session cataloguebuild/teched
Source
Type
talk
Published on
Host
sap.com
Discovered via
First seen
History
- Entered the atlasDiscovered via SAP TechEd — session catalogue · build/teched.
For your agent
- Ref
content:teched-2026-in161- JSON
- /content/teched-2026-in161.json
- MCP
- Connecting an agent