Most migration projects start with the same assumption: if an interface is running today, it must still be needed tomorrow. So the plan becomes “migrate everything.”
Then, a few weeks into the project, someone finds an interface that hasn’t carried real traffic in years, or was quietly replaced two projects ago. By then the time and budget to analyze or rebuild it are already spent. That’s usually the moment someone says out loud what everyone’s thinking: we just migrated something that stopped creating value a long time ago.
The migrations that go well don’t start by asking “how do we migrate everything.” They start by asking “what should we migrate.” A migration is one of the few chances you get to actually simplify your landscape instead of just carrying it forward as-is.
If you want to see which of your interfaces still earn their spot, Figaf’s free trial can show you in minutes.
SAP quietly shipped something agent developers should know about
SAP released the MCP Gateway in SAP Integration Suite this month. API Management can now expose your APIs, iFlows, and even RFCs as governed MCP servers that any agent can consume, complete with OAuth, rate limiting, quotas, and payload protection. So far it’s only shown up as a “What’s New” entry on the Help Portal and a mention in last week’s SAP Developer News, which makes it easy to miss.
Jan Penninkhof didn’t miss it. He makes the case for why this matters more than the quiet rollout suggests: Agents don’t behave like normal API traffic, and a single overeager agent can hammer a backend that was never sized for that kind of load. He also ties it to a governance question that’s been floating around SAP LinkedIn for months, namely where the authorisation boundary actually sits when an agent is calling your landscape.
Worth the full read if you’re thinking about how agents will touch your SAP systems.
Building an MCP server for a SAP CI monitoring assistant
In his latest Technology Blog Post, Prem Sai Daggolu shows how to build a CI Monitoring Assistant using the new MCP Server capability in SAP Integration Suite. Ask in plain language, and the agent queries your tenant for you.
- Exposes MessageProcessingLogs as agent-ready tools
- Runs on Integration Cell, works with Claude Desktop or VS Code
- Read-only by design, the agent can never change your tenant
No more clicking through the Monitor, just ask “show me all failed messages in the last 2 hours.”
Exciting innovations are coming to SAP Integration Suite!
On July 28, 2026 at 16:00 PM CEST, SAP is hosting their monthly update webinar.
Join this webinar to explore newly released capabilities, including:
→ API-Centric Integration with unified API management and integration → MCP Gateway to make existing APIs AI agent-ready
Sign up here, to join the webinar
The most active new CPI addon out there right now
CPI Lens just shipped v3.4.1, with a batch of new features that make working with payloads easier.
Biggest one: Tree View for JSON & XML. Instead of scrolling raw text, you can expand/collapse nodes and find nested elements fast. Useful when you’re debugging an MPL or validating a mapping.
Haven’t tried it myself yet, but worth a look if you are working with payload troubleshooting.
SAP’s Base-Overlay: best practices
Mary Katherine Pulliam from Proclus wrote a post on setting up Base-Overlay mappings, worth a look if you’re juggling multiple business partners on the same message format.
The core idea: one standard Base mapping, with partner-specific quirks handled as Overlays on top, instead of duplicating the whole mapping per partner. Her first tip is settling on a naming convention early, so you can find the right MIGs and MAGs fast when changes come up later.
It’s a decent starting point, but worth reading with a critical eye. Overlay-MIGs are typically partner-specific, so you’d need several per Base-MIG, and it’s not obvious the proposed naming holds up once you’re managing that many. It also points out that SAP doesn’t actually support an Overlay concept for MIGs the way it does for MAGs, so borrowing that terminology risks confusing people about what’s actually possible.
Still, it’s good food for thought if you’re setting up your own naming convention, not just a template to copy.
Getting started with Figaf is easier than you think
A lot of people who haven’t tried Figaf yet assume it’s complicated to get started with. It isn’t.
Setting up Figaf is nothing more than setting up any other new tool. Connect an agent, point it at your system, and you’re running your first test or migration within minutes. No steeper a learning curve than anything else you’ve onboarded in the last year.
We’re here to help if you get stuck along the way. Right now you get 4 free hours of support to get your SAP integration running with Figaf
If you haven’t tried it yet, our free trial is still the easiest way to see what that looks like for your own landscape.
Thanks for reading The Figaf Weekly. If you have questions, feedback, or topics you’d like us to cover in future editions, we’d love to hear from you. See you next week.
