Figaf

Not a decade from now. 12 months. AI is no longer just a helpful tool on the side, it's becoming part of the core workflow. Writing Groovy and XSLT, tracing errors, building iFlows, documentation, landscape governance, the tasks that defines the job today are all being compressed. We recently launched Figaf AI, giving developers a new way to interact with their integrations through chat. It's one piece of a much bigger shift. Join us for a free webinar where we dig into exactly this, the factors shaping how integration is being built right now, our vision for where it's heading, and an honest conversation about what it means for your team. 🤝 The SAP Integration Developer in the Age of AI 🗣️ Daniel Graversen 🗓 Tuesday, June 23, 2026 🕒 15:00 CEST | 14:30 IST | 9:00 AM EDT | 21:00 SGT 💻 Virtual & free to attend We'll look at the factors shaping how integration is being built right now, share our vision for where this is heading and have an honest conversation about what it means for integration teams. We don't have all the answers yet. However, we think it's a conversation worth having now.

Over the next 12 months, the role of a SAP Integration developer is going to change more than it has in the last decade. AI is moving from a useful assistant to an active part of the development workflow. Every core task integration developers do today from writing Groovy and XSLT, tracing errors, building iFlows, documenting, governing landscapes is going to be compressed. That's not a small shift. That's a fundamental change in what the job looks like. We're hosting a free webinar to dig into exactly this. 🤝 The SAP Integration Developer in the Age of AI 🗣️ Daniel Graversen 🗓 Tuesday, June 23, 2026 🕒 15:00 CEST | 14:30 IST | 9:00 AM EDT | 21:00 SGT 💻 Virtual & free to attend We'll look at the factors shaping how integration is being built right now, share our vision for where this is heading and have an honest conversation about what it means for integration teams. We don't have all the answers yet. However, we think it's a conversation worth having now.

How to Govern your SAP TPM data. Understanding whether you have created the correct structure for your B2B migrations can be highly complicated. There are many small elements that make it difficult to scale what you are up to. We have explored what a governance application would look like. That could give you this overview. You can see more at https://lnkd.in/ezXsAamX

A simpler way to work with Groovy in SAP Cloud Integration is to use the Figaf Bot. And yes, AI does not always just magically give the right result. When creating a demo, you could have used a super prompt to generate the result you want in just one step. I could probably have run a few more experiments on the prompt and gotten better results. But the whole idea is that you can continue to develop and achieve better results with it. If you check the result, it looks somewhat okay to start; it gives the correct result. But the code could be simplified, making it easier to maintain. But it does give a new way to work. And XSLT can be handled in the same way. What is your experience with AI groovy script development?

Governance is a word that sometimes seems to mean everything and then again nothing. So I want to show how and why it is key to your B2B implementation, not just talk about it. In this walkthrough, you will see how Figaf can govern the SAP Integration Suite B2B in a 3-layer architecture, how governance rules are applied, and a live demo of the first PoC of a B2B Governance Validator app in action. What's in the video: ▸ The 3-layer model — SAP Integration Suite as the runtime foundation, Figaf as the governance and DevOps middle layer, and a new app layer where AI agents handle the operational toil and humans approve only what matters. ▸ How customer-specific rules are utilized and enforced across every app and every AI agent. One rule set, every environment. ▸ Real governance applied to a running app: agreement and MIG / MAG naming, deprecated-status checks, EDI metadata alignment, partner whitelisting. Why is this needed? The blunt version for IT leaders: SAP doesn't yet provide a consolidated transport for all Integration Suite B2B objects (MIG, MAG, TPM) with system-purpose alignment/tranlation. Figaf does — across tenants, with approvals, rollback, and a full audit trail. While applying and enforcing governance. 🎬 Watch the video: https://lnkd.in/esiWtZy7 Quick question: what's the single biggest governance gap you're feeling on Integration Suite TPM right now? Naming spagetti? Transports wild west? Partner onboarding via slow train? Or something else?

SAP Sapphire 2026 is coming soon and I’ll be attending in Orlando. SAP Sapphire this year feels especially important for the SAP world. With the 2027 migration deadline getting closer, I’m especially looking forward to what SAP and its partners will present around SAP Integration Suite, modernization, and what comes next for customers still planning or already working through their migration journey. I’m looking forward to the conversations, the announcements, and meeting people across the SAP integration community in person. Will you be in Orlando too? If so, let’s connect and let me know which SAP Integration topics or sessions you’re most interested in.