One question that keeps popping up: Do we actually own our own SAP Integration Landscape?
Here’s a pattern we see constantly. A consulting team builds or migrates a solution. They document it. Then they leave for the next project.
What’s left behind often has no real operational backbone. You can’t make a change without risking something breaking that you didn’t even know was connected.
The alternative: A system where every change gets logged automatically. Where you can run a test in minutes and know if a change is safe, before it hits production.
On Wednesday, August 5, we are running a live webinar on exactly this: How the Figaf DevOps Suite gives you back ownership of your SAP landscape, and helps you deliver faster once you have it.
Start taking ownership of your SAP Integration Suite: Sign up for the webinar here
SAP’s new Git integration for iFlows: does it actually make things easier?
Watch on YouTube Git integration for SAP Integration
SAP Integration Suite just added native Git integration. You can publish or sync iFlows back and forth to a Git branch.
In theory, that means real Git workflows for CPI development. Make changes in Git, sync to the iFlow, sync back. In practice, I am not convinced it simplifies much yet. And you are still limited to one developer per iFlow.
Missed the SAP Integration Suite July knowledge transfer session?
The recording is now available.
Catch up on the latest SAP Integration Suite developments, including SAP’s new API-Centric Integration strategy, the introduction of MCP Gateway for AI agents, native GitHub integration for Cloud Integration, enhanced retry handling, shared runtime configuration, and the latest Pipeline for Cloud Integration improvements.
Watch the recording or take a look at the PDF whenever it suits you. And stay up to date with the latest developments from the SAP Integration Suite product team.
