Raw Transcript: SAP Joule Architecture Explained | How Joule Integrates with S/4HANA Cloud (2026)

Okay, so imagine this. You walk up to your enterprise system, your ERP, but instead of clicking through, you know, a dozen different menus, you just you just talk to it. >> Yeah. And we're not talking about some uh some basic chatbot that's just bolted on. >> No, not at all. This is deep, secure, conversational interaction. Something that actually understands your business, >> right? like picture saying, "Show me open purchase orders for Plant 1010." >> Or maybe, "Take me to supplier invoices that are blocked for payment." >> Or even something like, "Summarize sales trends for this quarter." >> And you get a response that's instant, contextaware, and you know, totally secure. >> Well, that's pretty much here. It's called SAP Jewel. And today, we're really going to dig into the architecture of this new AI co-pilot that's built right into S4ANA Cloud Public Edition. >> It's a huge shift, right? moving from all that manual navigation to to intelligent guidance. >> It really is. >> And I think for, you know, for the architects and the decision makers listening to this deep dive, the real question isn't just is this cool. I mean, it obviously is. The real question is, what does it actually take to get it running? It sounds like it could be a massive integration project. >> And that's exactly our mission today. We're here to answer that one question. What does it take to get SAP Jewel securely up and running in a live environment? Okay, >> we've gone through the architectural docs, the implementation guides, all of it to really unpack the prerequisites, and um what it takes to build those necessary trust connections. >> Great. So, let's do it. But before we get into the, you know, the plumbing of it all, we should probably ground ourselves in what Juul actually is because the source material is very clear. This is not just another offthe-shelf AI tool. >> Exactly. We have to establish that this is a contextual enterprisegrade assistant. It's built for the, you know, the complex world of a real enterprise. It's not just looking for keywords. It's understanding intent. >> That's a critical distinction. Yeah. There are three main things Juul does for a user. >> And I think that really defines its value. First up, and maybe the biggest win right away is just intelligent navigation. You can ask it in plain language to take you somewhere and it finds the right Fiori app. No more T-codes, no more menu paths to memorize. >> And that alone is a game changer for training. But like you said, it goes deeper. The second big function is secure real time data retrieval. >> Right? This isn't cache data. >> No, it's pulling live business data directly from the S4 Anna core. Real time inventory, live cast positions. It's the actual data you need for decisions. >> And the third piece is that guided help. It's like having an expert sitting next to you helping you start a workflow or fill out a form right inside the application. >> And what's really fascinating here is the why. You know why it's enterprisegrade? It's because it understands your specific business context before it even answers. It knows your role. >> It knows your permissions. >> Exactly. It knows what you are and are not allowed to see. >> That part is non-negotiable in an SAP world. It has to respect the rules. It can't just give a procurement person access to HR data because they ask nicely. >> And that's the whole value proposition right there. It's that combination of plain language with, you know, rocksolid enterprise security. And it means the setup isn't about installing software. >> It's about connecting things. >> It's about making sure that security framework is flawlessly connected across the whole landscape. That's what defines the architecture. >> Okay. So that brings us right to the architecture. The four foundational pillars that have to be in place. >> Let's get into it. >> So we're moving from the what it does to the how it's built. >> Yeah. >> And the docs really hammer this point home. Setting up Juul is about securely integrating four essential SAP cloud pillars. >> It's a total shift in thinking, right? It's not about monolithic installation anymore. It's about connectivity. And you need these four services to be perfectly integrated for Juul to work. >> Oh, by the way, if you're looking to upgrade your skills in SAP AAI, check out the SAPAI masterass. The number one best-selling and toprated SAPAI training on Udemy built by XSAP employees. This course gives you lifetime access and includes all future SAPAI updates so you stay relevant as SAPAI continues to evolve. If you're an SAP professional, this course helps you stay ahead of clients with real world SAP. I use cases, clear architecture insights, and hands-on skills you can apply immediately. Whether you're looking to boost your resume, earn internal or customer recognition, or explore new career opportunities, this is your edge in the competitive SAP market. A special discount coupon is available at www.zquans.ai. >> And you need these four services to be perfectly integrated for Juul to work. >> I mean, let's start with pillar number one. This is sort of the brain, the home base. We're talking about the SAP business technology platform, BTP. BTP is uh yeah it's absolutely non-negotiable. It's where the Juul service actually lives and executes. And to get it ready, you have to do three things. Create a BTP sub account, enable Cloud Foundry, and then activate the Juul service itself. >> Why the specific focus on Cloud Foundry? What does that do? >> Well, Cloud Foundry gives you that managed scalable environment for cloudnative apps. Juul needs that platform to reliably run its, you know, its advanced logic and integrations. Without BTP, the brain has nowhere to operate. >> Got it. So if BTP is the brain, then the next pillar is kind of like the map SAP build work zone. >> That is a perfect analogy. Work zone is Juul's internal directory. It's the service that knows which Fiori apps exist, who can access them, and how to organize all that content for the user. >> Okay, but hold on. Why do you need work zone for that? Wouldn't the roles inside S4A already know which apps a user can access? What's works on adding that's so essential? >> That's a great architectural question. So Esport Anna knows what roles exist. Sure. But work zone is what aggregates the content and crucially provides the semantic layer for Juul. >> The semantic layer. >> Yeah. So when you ask Juul to handle supplier invoices, it's the work zone structure that tells it the exact URL, the app ID, and the RO context it needs to launch that specific task. It's the single source of truth for the user interface. >> Ah, okay, that makes sense. It unifies the front-end experience for the AI. H >> okay so pillar three the security guard SAP cloud identity services >> this is probably the most critical piece for any enterprise we're talking about IAS the identity authentication service and IPS the identity provisioning service >> authentication and provisioning >> right it handles both who you are and what you can see it ensures single sign on work so when you log in your identity and permissions just flow seamlessly and securely across the landscape >> so we're not just logging in once we're creating a chain of trust that follows the user are everywhere. >> Exactly. It avoids that nightmare of separate login and ensures Jules's context is always current. >> And that brings us to the last pillar number four, the source of all the data. The SAP S4 A9 cloud system itself. Yep. The engine room. Its job in this setup is to securely expose the business roles, the Fiori apps, and of course the actual business data to Juul. And the key word there is securely via APIs. >> And why APIs? Why not some other kind of integration? Because APIs are the modern standard for secure cloud-tocloud interaction. They're like controlled gateways. They make sure Juul only requests and receives very specific defined pieces of data for the conversation. It limits exposure and gives you a full audit trail. >> So to sum it up, okay, >> we've got the brain BTP, the map work zone, the security guard identity services, and the data engine Sorana. It sounds like linking all four of those could be a really complex errorprone project. >> It absolutely can be and that complexity is precisely why the implementation guides push you towards using automated tools which leads us right into the setup journey. >> Okay, let's talk about that simplification piece right away. If connecting those four pillars is the main pain point, what's the solution the documentation offers? >> The big takeaway here is the automated help you get from the booster tool. Now, it's not a magic wand, but it's a very powerful wizard that is designed specifically to simplify that whole connection process. >> And how does it do that in practice? What is it automating? >> It's all about that security handshake. It automatically builds the destinations, sets up the communication arrangements, and exchanges the security certificates you need to link BTP, S4 ANA, and identity services. It just it cuts down so much on the potential for manual errors. So the booster tool basically runs through the four-phase journey for you. >> That's a good way to put it. It automates the execution of that journey. >> Okay, then let's walk through that journey. It seems like a very logical sequence starting with trust and then ending with validation. >> Exactly. You have to establish the lines of communication before you can worry about what flows through them. >> Right. So phase one is the foundation. What's the main goal here? >> The goal here is establishing secure mutual trust. It's making sure S4SHana, BTP, and identity services all recognize and trust each other's credentials. You're setting up the secure channels, the certificates. Think of it like exchanging diplomatic keys between three digital countries. >> Okay. Once that trust is there, we can move on to phase two. Yeah. Content exposure. This sounds like it's all about feeding the map, the work zone. >> That's it. Exactly. This is where you synchronize that semantic layer. You're taking the business roles, the Fiori apps, the user mappings from S4 Hannah and syncing them up to the SAP build work zone. This tells Juul what content exists, where it is, and who's allowed to see it. >> So if work zone is the map, this phase is basically loading all the current streets and addresses into it. >> Perfect analogy. Then you get to phase three, identity sync. So we've got trust, we've loaded the content, but you know, business is dynamic, people change roles, new people get hired. This phase is all about making sure users and their roles are constantly aligned across all the systems. >> So if a user's security profile changes in the ERP, this guarantees Juul knows about it immediately >> instantly. Continuous alignment is crucial to avoid security gaps. And then finally, you wrap it all up with phase 4, security validation. This is the last non-negotiable check. >> What are the key checks in this final phase? >> You're validating that all the trust certificates are active. You're enabling single sign on across the whole environment and you're guaranteeing that all the data privacy settings are correct. It's the final step to make sure the system isn't just working, but it's compliant and safe. >> And the result, the outcome of running through those four phases, either with the booster or manually. >> The result is that little visual confirmation everyone's looking for. That sparkling diamond jewel icon appears right there in your Fiori launchpad, ready to go. It's the signal that all four pillars are securely connected and synchronized. >> So, if we zoom out, what does this whole deep dive really tell our listeners about the long-term impact of SAP Juul? >> Well, the bottom line from the source material is pretty clear. Juul isn't just some AI add-on that got bolted onto the side. It really represents the future of how users are going to interact with core SAP systems. It changes the whole paradigm. >> Yeah. from clicks to conversation. It's an intelligent workspace and it's built on BTP powered by responsible AI and deeply integrated with S4 Hannah. It's core to the platform strategy >> which means for you the architect or decision maker on S4 Hannah cloud the message is clear. The architecture is ready. The time is right to start exploring this because Juul is designed to lift productivity in every single role in the company. >> And it's such a significant shift. We're not talking about managing software installs anymore. We're talking about managing the constant sync, the trust relationship, and the secure connection between all these separate cloud services. >> That transformation and philosophy from monolithic installs to a synchronized ecosystem. That's the defining feature of this whole new intelligent workspace, >> which I think raises a really important final thought for you to take away from this deep dive. Given that Juul's success relies entirely on managing the continuous trust and synchronization between these three cloud services as for HANA BTP and identity services what new considerations does this connected architecture introduce for your long-term maintenance governance and scaling strategies >> the conversation really moves from deployment to continuous operational alignment. Thanks for joining us for this deep dive. >> We'll catch you next time.