SAP Community - SAP Build

Joule Studio: How to Create Document Grounding

2026-01-14T05:50:29.875000+01:00

Several people have reached out to me this week to describe the new way you set up document grounding with Joule Studio. So here goes.

What is Document Grounding

Many of you may know about Document Grounding, but for those who don't here's a very brief explanation.

The basic way we use AI is to send a prompt to an LLM (a set of "indexed" information).
If we want the LLM to take into account additional information it may not have, we can provide "context" (though the amount of "context" you are allowed to send may be constrained).

One of those pieces of context may come from a set of documents (e.g., housed in SharePoint or in the SAP BTP Object Store service). In order to use those documents as context we must perform Document Grounding, which takes the documents, "chunks" them into small pieces, and then "embeds" them so they can be used as context in our AI requests.

In Joule Studio, when we create agents, we essentially specify an LLM to handle specific types of prompts, and then provide context and instructions for what we want the agent to do.

The "Old" Way in Joule Studio

The old way we performed Document Grounding in Joule Studio was to go into AI Core and create a resource group, connect that resource group to a content store (e.g., the place we store the documents), and have AI Core chunk and embed the documents so we could use the content within an agent or for use when sending a prompt to AI Core. Joule Studio would be configured to connect with a specific AI Core, and the developer of an agent would type in the name of a resource group in AI Core to use with their agent.

Here we can see in the SAP AI Launchpad that we are connected to the "dbw" resource, and we have created a "pipeline" with documents.

If we click inside, we can see that this pipeline has 4 documents, each chunked and embedded.

But doing this required going into the SAP AI Launchpad, creating Generic Secrets by encoding credentials in Base64, and several more steps in tools we may not be familiar with.

Joule Studio still makes use of the same mechanism in AI Core, but now takes care of creating all the artifacts behind the scene (and enables some new capabilities).

1. Prerequisites

You need an instance of SAP AI Core, SAP AI Launchpad and an S3-compatible document store such as the Object Store service in BTP. I won't go into setting these up, but you can find out more information here:

AI Core (extended plan)
AI Launchpad (standard plan, and pointing to your AI Core)
Object Store (s3 -standard plan)

The plans listed are what I am told is required, and happens to be what I have experimented with.

If you need more information, leave a comment.

Note you can define many instances of AI Core and Object Store to be used with Joule Studio.

2. Destinations

You need to set up destinations to AI Core and Object Store on both your SAP Build tenant and your Joule tenant.

AI Core Destination

Get the service key of your AI Core instance, and create a destination as shown below.

Append /oauth/token to the url value of the service key and use this for the destination's Token Service URL.

Add the additional property sap-joule-studio-document-grounding-ai-core and set it to true. This makes the destination visible within the SAP Build Control Tower.

Object Store Destination

Similarly, get the service key for the object store service instance and set the following destination fields with the corresponding service field value:

Destination Field	Service Key Field
URL	access_key_id
Client ID	host (add https://)
Client Secret	secret_access_key
Token Service URL	host (add https://)

Add the following additional properties:

Additional Property	Value
region	region value from service key
bucket	bucket value from service key
username	username value from service key
type	S3
sap-joule-studio-document-grounding-object-store	true

The additional property sap-joule-studio-document-grounding-object-store makes the destination visible within the SAP Build Control Tower.

3. Set Up in Control Tower

In the Control Tower, the SAP Build admin will decide:

From which object stores to create Document Grounding.
In which AI Core instances to create these Document Grounding pipelines.

The Control Tower now has a Joule section, including a Document Grounding tile so the admin can create Document Grounding and make it available to Joule Studio developers.

Click the Document Grounding tile. You can now create sets of Document Grounding.

Note that while in the SAP AI Launchpad you could create different pipelines with different sets of documents in the same resource group, here each object store will create a separate resource group.

Click Add.

Give the resource group a name.

Select the AI Core instance in which to create the resource group.

And finally select the object store whose documents you want to ground.

Click Add.

The status of the resource group will be Pending.

After about a minute (depending on the size of the documents), the status will change to Completed.

(Early on, I occasionally got Error messages, or Pending simply remained for a long time, and sometimes they would alternate between those messages. In such cases, make sure the destinations are configured properly and make sure the documents in the Object Store are not corrupted.)

If you now look in SAP AI Launchpad, and go to SAP AI Core Administration > Resource Groups, you will see a new resource group whose name is the name you specified (without spaces) with a Unix timestamp appended.

Though the resource group should immediately appear on the Resource Groups page, it may take a few extra minutes for the resource group to appear on the Workspaces page.

Once it does, you can select it and see the pipeline and Document Grounding inside the resource group.

4. Add Document Grounding to Your Agent

Now that the admin has set up a resource group and triggered the document grounding for a set of documents, developers of Joule Studio agents can use them in their agents.

Inside an agent, the developer can specify tools, including documents. Select Add Tools > Documents.

This opens a dialogue to specify which resource group created by the admin to use. Specify a name for the documents (as seen in the agent) and a description to help the agent know when to use them.

Then select from among the resource groups created by the admin.

Advantages

The advantages of this method are:

Admins and developers no longer have to work in AI Launchpad, including creating Generic Secrets and dealing with Base64 encoding of credentials.
Admins decide what document grounding gets used in Joule Studio agents.
- From the look of the UI, admins will eventually be able to assign a resource group to a specific environment, giving admins even more control
Developers have a predefined set of resource groups to choose from, using a dropdown list.
More than one AI Core instance and more than one Object Store instance can be used to define document grounding for a Joule Studio.

Note that this method creates a single document grounding pipeline in each resource group it creates; using AI Launchpad, you can create multiple pipelines in a single resource group.

There may be more advantages and limitations. Please add a comment with your opinion about this feature, or anything I missed.

Improve Build Apps UIs to Allow Keyboard Click / Control Focus

2026-01-15T07:43:49.523000+01:00

I was doing this great tutorial by my colleagues @Rekha_DR and @shrinivasan_neelamegam about creating a chatbot using Build Apps and AI Core, a topic they delivered in the SAP TechEd developer keynote in 2024: https://github.com/SAP-samples/teched2024-developer-keynote/blob/main/topics/DEV100A-build-chatbot-apps-aicore/README.md

It worked perfectly.

The tutorial let you create a chatbot where you typed a prompt, got an answer, and then could send a new prompt, like a regular chatbot. (By the way, one of the clever designs of theirs was that the context of the conversation was always sent back to the AI Core with every subsequent prompt.)

I thought what would make the app even more helpful would be:

To be able to press Enter after typing in each prompt.
To place the cursor automatically in the prompt input box so the user could just start typing the next prompt.

Allow Enter Instead of Button Click

To do this, you first want to create a custom event for the logic that you want connected to the button click / Enter press.

Drag a Receive Event flow function onto the canvas.

Set the Event Source to Fired from "Trigger Event", and give the event a name, like SendChat.

Attach your logic (in this case the calls to AI Core) to the event.

Now all that's left is to trigger this event when the user clicks the button, or presses Enter.

For the button click, select the button click, drag a Trigger Event flow function, and connect it to your Component Tap event for the button.

Configure the Trigger Event flow function by selecting your new event to be triggered.

To enable the logic to be triggered by pressing Enter, highlight your input box, and create the following logic on the input box's onKeyPress event.

To the onKeyPress event, add an If Condition flow function with the following formula:

outputs["Receive event"].eventValue == "Enter"

And then to the top output add a Trigger Event, configured the same as for the button click logic above.

Place Cursor in Input Box

Every time I send a prompt, I want the cursor to return to the input box so I can type in the next prompt.

Install the Focus Input flow function from the Marketplace.

After the logic for sending the prompt and receiving the answer from AI Core, add this flow function and specify the input box.

😽

Partner learning accelerator: SAP Build Developer Express Academy

2026-01-19T09:00:00.039000+01:00

Our “Partner learning accelerator: SAP Build Developer Express Academy” is a focused 3-hour live session built specifically for experienced SAP Partners who want to boost their exam readiness across the SAP Build portfolio.

Across one concentrated session, we’ll revisit how to:

Design enterprise-grade applications and model business data
Integrate SAP systems and APIs on SAP BTP
Automate key processes and build digital workspaces with SAP Build

You’ll get prescriptive guidance, practical tips, and space to clarify those “I’ve seen this in a customer project, but how does it show up in the exam?” questions.

If you’ve already worked with SAP Build and followed the “Developing with SAP Build – from apps to automation” learning journey, this academy is the natural next step.

Register now and turn your project experience into certification confidence. https://partneredge.sap.com/en/library/education/psd/2025/mar/e_oe_te_w_PSD_WEB_00009457.html

#SAP #SAPPartner #SAPBuild #SAPBTP #SAPCertification #PartnerLearning

Use SAP Integration Suite to connect SAP and AWS services

2026-01-20T11:36:09.592000+01:00

Bridging the gap between SAP and 3rd party systems

Everyone already knows that SAP Integration Suite is the election tool to connect your SAP services. But did you know that it is also your tool to integrate Everything, Everywhere, All in One Place? (yes, almost like the Oscar award winning movie 🏆)

Use SAP Integration Suite to connect SAP and AWS services is a new official SAP Discovery Center Mission that focus on showcasing how easy it is to integrate not only SAP systems but also non-SAP systems using SAP Integration Suite.

For this mission, we decided to use the AWS platform as the example of third-party cloud services provider, but the same rational with this set of best practices and capabilities can be used to integrate with other cloud providers. By following the cards provided in the mission, you will see step-by-step how you can start to integrate an application developed with SAP BTP development tools with AWS services, such as S3 for image storage and Rekognition for image identification.
You can even use a SAP BTP Trial account to perform the SAP BTP parts of the mission, even though you will always still require also an AWS account to connect with the S3 and Rekognition services (and IAM for user and roles management on the AWS side). Either if you are a technical user or more of a business user interested in rapid application development, cloud integration strategies and/or AI-powered business solution, this mission is for you!

The following architecture shows the big picture of what the final result of the mission should look like, seamlessly combining the best of both SAP BTP and AWS platforms:

Use Case Description

The use case followed trough out the mission focuses in enabling a Supplier to donate surplus food ingredients through an AI-powered mobile and web application built using SAP Build Apps, a low-code/no-code solution within SAP Business Technology Platform (SAP BTP), seamlessly integrated with AWS capabilities for storage and artificial intelligence–based image recognition. For the integration part, you will leverage and combine different integration capabilities that are part of the SAP Integration Suite. The intended outcome of the use case is to minimize food waste while simplifying the donation process and facilitating redistribution to organizations in need.

Solution Components:

SAP Build Apps: The low-code/no-code application development service used to create the application (frontend and logic) where the Supplier can donate the surplus ingredients by taking or uploading photos
SAP Integration Suite: The secure and centralized integration management service for all your integrations, making them easier to manage, monitor and troubleshoot
Amazon S3: The Amazon service for simplified and cost-effective image storage capabilities
Amazon Rekognition: The Amazon service for AI-powered identification and categorization, in this case used to identify the ingredients in the images taken or uploaded from the application to a S3 bucket

The Use Case Flow:

A Supplier captures or uploads an image of surplus ingredients through the mobile/web app (developed with SAP Build Apps)
The image is securely stored in Amazon S3 via SAP Integration Suite (using Cloud Integration, Pre-built Open Connector and API Management capabilities)
Also via SAP Integration Suite, the app then calls Amazon Rekognition to automatically identify and categorize the ingredient present in the image (using Cloud Integration, Custom Open Connector and API Management capabilities)
The results are sent back to the app and ready for further processing

Learning Outcomes

By completing this Discovery Center Mission, you'll gain practical experience in:

Building low-code applications with SAP Build Apps
Configuring SAP Integration Suite for AWS connectivity
Implementing secure cloud-to-cloud integrations
Leveraging AI services for business process automation
Managing integration flows and monitoring capabilities

Getting Started

Once you open and start the Mission, you will see in the Project Board the different cards that will guide you step-by-step, divided in 7 columns.

Make sure you fullfill all the requirements indicated in the SET UP and PREPARE columns. After that, you can start with the EXECUTE columns. You will first explore the Open Connectors capability of SAP Integration Suite (in the Execute - OpenConnectors), followed by the Cloud Integration and API Management capabilities of SAP Integration Suite (in the Execute - Security Material and Integration Flow) and lastly you will get to visually create a simple app screen with SAP Build Apps (in Execute - Build app) .
After finishing the mission, don't forget to mark all the cards as completed and we encourage you to leave your feedback and share your experiences with the rest of the SAP Community.

And now, for those who saw the movie Everything Everywhere All at Once, DON'T "Just be a rock" and start the mission here! -> SAP Discovery Center Missions - Use SAP Integration Suite to connect SAP and AWS services

What's New in SAP BTP - Q4 2025 Innobytes

2026-01-21T17:28:03.157000+01:00

Happy new year and welcome back to the SAP BTP Innobytes! 2026 is going to be an exciting year and we have big ideas and a strong strategy for the year ahead! In the meantime, let’s see how we finished out last year with some innovative highlights.

Check out the video below and explore the latest features in Application Development, Integration and more. Enjoy watching!

Data & Analytics

My Metrics

To keep up with the important numbers and data, let me introduce you to your personalized watchlist to keep up with what really matters: My Metrics in SAP Analytics Cloud on SAP BTP.

You can find it via the My Metrics Card on the new Homepage, bringing together performance cards from stories and models into one easy-to-access space with these core areas:

Your Metrics to manage cards
Detailed Visualization with instant charts and active filters
Smart Insights surfacing automated observations

You can create lists from My Metrics page or directly from a story chart: select a data point that you want to track and add it to an existing list or create a new one. You can name the metric and customize suggested comparisons and default visualizations. It’s now possible to rename, delete, copy or move metrics between different lists. You can Share multiple metrics with tailored permissions and distribute it with different SAC users or teams.

See these steps in action (starting at 0:09).

Learn more

MyMetrics Blog Post

App Dev Highlights

Analytical Table with RAP and SAP Fiori

Real-time data analysis tools are essential for decision-making, that’s why SAP BTP ABAP introduced these powerful features for business users.

By adding the annotation @odata.applySupportedForAggregation: #FULL to your data model, you can now unlock advanced aggregation, grouping, and subtotalling directly in Fiori analytical tables. View real-time summarized business data, group by key fields, and dynamically sort and analyse profitability. This way you can simplify analytics for end users, enabling faster, data-driven decisions.

Watch the demo starting at 1:37 to get more insights.

Learn more

Developing Read-Only RAP Analytical Tables

SAP Build Extensibility Wizard now available in SAP SuccessFactors

You might already know the SAP Build Extensibility Wizard, supporting developers in process creation and UI extensions directly from Cloud ERP apps. This feature is now also available in SAP SuccessFactors.

In this example we want to simplify the process of requesting personal data from new hires in the onboarding process:

Launch the process variant manager from the SAP SuccessFactors application and select the specific HR process you want to extend.
To let the new hire know, that their data has been accepted, we want to add a step of approval. The wizard will walk you through the familiar steps to set up our extension.
You can jump directly into SAP Build to customize this process.
View the process from the SAP SuccessFactors application, reviewing the new hires and the personal data they have collected.
HR will get a notification in the Task Center Inbox and can select approve, notifying the new hire.

The Extensibility wizard can now practice its magic in SAP SuccessFactors, delivering a better experience for our employees with SAP Build.

To watch this innovation example, start the video at 2:41.

Learn more

Joule Studio Agent Builder

When it comes to making decisions for your business, transparency and control are essential. AI agents can help speed up the process but building AI agents that are both powerful and enterprise-ready is a challenge. How do you combine development speed with the governance and trust your business demands?

Describe your business goals to your AI conversational Partner and let Joule build an agent that fits your needs. It automatically discovers tools and connects to external systems through the framework support for MCP. Giving the agent deep business context enables smarter decision-making. The timeline feature gives you full transparency, showing every step of the agent's logic, essential for debugging and governance.

Start the demo at 4:21 to learn all about the Agent Builder in Joule Studio.

Learn more

Integration

Local OData API access & SAP HANA support in Edge Integration Cell

When it comes to manage persistence and monitoring in hybrid landscapes, integration is an essential step to make it more flexible.

Edge Integration Cell now supports SAP HANA as both a database and datastore, offering an alternative to PostgreSQL and Redis. If your landscape already runs on HANA, avoid maintaining separate persistence systems by unifying your data layer. One SAP HANA instance can be used for multiple Edge to keep everything consistent and centralized. To ensure the reliability of your integrations even if the cloud connection isn’t available, try the Local OData API access for your Edge runtime. You can retrieve message processing logs, data stores, and other runtime info through local GET APIs.

To use the Local API Access,

Activate the API Plan support to the cluster using the ELMO UI
Modify the configuration by adding a valid API Virtual Host and an API Virtual Host Key Alias

These settings are also available upon onboarding a new Edge node, allowing a stronger performance and visibility into your integrations.

Watch this part (starting at 5:36) to get more insights.

Learn more

Security

SAP Key Management Service

SAP Key Management Service (KMS) enables customers to manage encryption keys to business compliance and regulations. Group systems and keys in key configurations according to your requirements.

The Primary Key is the active one for encryption. The SAP KMS supports Hold Your Own Key (HYOK) and Bring Your Own Key (BYOK) by importing Your Key. Revoke a key at any time by disabling or deleting it, leading to a shutdown of the connected systems, locking the data. When assigned to a KMS tenant, connect the system seamless via the UI. The four-eye-principle secures tasks like connecting a system or a key action.

To see this demo in action, watch the video (starting at 7:04).

Share your thoughts

These videos are for YOU, and we would love to hear your impressions. How do you like the video? How can we improve the upcoming videos? Please share your feedback by liking this post or leaving a comment below.

Thank you for your support and happy viewing, sharing, and enjoying!

What’s New in SAP Build Q4 2025: Release Highlights

2026-01-28T11:57:02.493000+01:00

In Q4, we rolled out AI-powered enhancements for SAP UI5 development, digital experiences, and SAP Mobile Start, along with improved operational control and visibility for automating business processes. Most significantly, the agent builder in Joule Studio is now generally available, empowering developers to build custom Joule agents.

Check out our Top 10 Q4 2025 Release Highlights!

Enhancements and AI-Powered Development

AI-guided development for building agents in Joule Studio.

1. Building custom agents with Joule Studio

Now generally available, the agent builder in Joule Studio lets developers create custom Joule agents using natural language, Model Context Protocol (MCP) enabled integrations, multi-agent orchestration, and existing SAP Build content. With this capability, you can build scalable, production-grade agents designed to deliver real business impact across your enterprise.
Learn more in this blog post.

2. AI-powered capabilities in SAP Build Work Zone

Joule is now integrated across all SAP Build Work Zone editions, helping employees navigate complex workflows within their digital workspace using natural language queries. With context-aware answers, content generation, and proactive insights, Joule helps teams work more productively.
Learn more in this blog post.

3. Enhanced AI support for SAPUI5 development

With the new /ui5-create-app slash command in Joule for SAP Build Code, developers can now generate freestyle UI5 applications. The AI assistant/Joule guides the conversation, producing a ready-to-use, best-practice app as a starting point. This streamlines development, reduces setup effort, and helps teams follow consistent UI5 standards from the very beginning.
Learn more in this blog post.

How the AI-supported freestyle SAPUI5 app generation works. Learn more in this blog post.

4. Define status flows in SAP Cloud Application Programming Model (CAP)

The new status flow feature in CAP lets developers define application workflows with minimal effort using just three CDS annotations. With @flow.status, @from, and @TO, developers can mark status properties and define transitions, while the system automatically generates the necessary handlers and UI annotations. This reduces manual coding, provides a robust framework, and still allows developers complete control to override and customize the generated logic.
Learn more in the guide.

Enhanced Operational Control and Automation

5. Streamline migration to SAP Build Process Automation

With the “No Correlation” feature in Process Visibility, organizations can smoothly transition from SAP Workflow Management to SAP Build Process Automation. This feature enables tracking of legacy and new processes in a single, unified view without data duplication or reporting disruptions, helping organizations modernize their operations while maintaining visibility, accuracy, and performance.
Learn more in this blog post.

6. Expanded functionality for process automation

Template-based notifications: You can now compose template-based notifications using HTML as part of your process logic, enabling teams to design more flexible e-mails that fit complex business scenarios.

Learn more.
Preserve and combine results for Decision Tables: Decision Tables in process automation now support aggregating and preserving outputs from multiple tables. With the new append operation, users can accumulate results across multiple rule evaluations, enabling richer decision outcomes.
Learn more.

When opening an existing decision that uses list-type results, users will see a banner notification indicating that the behaviour has changed.

If the user clicks on “Update Decision Table Behavior”, the user gets to select to continue with the existing behavior or choose the new behavior to append the content to the result.
Enable or disable individual Decision rules: While modeling decisions in process automation, you can now activate or deactivate individual rules based on business requirements. The deactivated rules are skipped during execution but remain accessible, providing greater control of Decision artifacts.

Learn more.
Manage workflow tasks in process automation: Workflow monitoring applications now support assigning tasks to a group, improving flexibility and reducing manual effort. Administrators can search for users or groups, reassign running workflow instances, and receive clear confirmation or error messages, ensuring business continuity.

Learn more.

7. Expanded trigger options for SAP Build Process Automation

SAP Build Process Automation now offers enhanced trigger options that enable scalable automation across SAP and non-SAP systems:

Queue triggers to start a process: These triggers leverage UiPath Queue Management to start SAP Build Process Automation processes automatically, enabling the smooth automation of repetitive tasks. Learn more.
UiPath connector triggers: These event-driven triggers powered by UiPath Integration Service enable automation across non-SAP systems, providing real-time responsiveness to critical business activities with minimal configuration effort. Learn more.

Digital Experience & Mobile Start Innovations

8. Enhanced user experience for mobile and desktop in SAP Build Work Zone, advanced edition

SAP Build Work Zone, advanced edition now provides a coherent and intuitive navigation model across desktop browsers and SAP Mobile Start. Employees can quickly access the apps and business content they need on the go through structured spaces and pages. By organizing content into logical workspaces, essential tools open in seconds, reducing operational friction, minimizing errors, and enabling users to stay productive while moving between tasks.
Learn more in the Help Portal.

9. Updates to SAP Mobile Start

SAP Mobile Start adopts Apple's new Liquid Glass design language released with iOS 26.

SAP Mobile Start continues to elevate the mobile experience for end-users with several new features that improve usability, efficiency, and visual design:

Adoption of Apple’s Liquid Glass design: SAP Mobile Start now incorporates Apple’s new Liquid Glass design language introduced with iOS 16. This provides a more dynamic user experience and increases screen space as the navigation bar collapses when not needed.
Additional To-Do filter option “Group”: End-users can now filter their To-Dos by semantic groups defined in Task Center, making it easier to organize and prioritize tasks.
New compact list view for To-Dos: To-Dos can now be displayed in a more compact list view instead of the traditional cards view, allowing users to see more items at a glance and manage tasks more efficiently.

Learn more in the latest blog post.

10. Expanded content capacity in SAP Build Work Zone sites

SAP Build Work Zone sites can now host thousands of documents and translations without technical limits. This lets administrators build richer site architecture that supports multiple regions and languages while keeping content organized, giving employees faster access to a comprehensive and well-structured digital workplace.

Ready to see these in action?

Join us for the next What’s New in SAP Build Webinar on February 5th as we explore building custom agents with Joule Studio, AI support for SAPUI5, and more!

Choose your session:

🕘9:00 AM - 10:00 AM CET → https://url.sap/al5xcu

🕓 4:00 PM - 5:00 PM CET → https://url.sap/egqfui

SAP CodeJam Roadshow 2026 - Brazil edition 🇧🇷 (Kicking off in March and continuing in April)

2026-01-30T12:35:15.511000+01:00

Oi SAP Developers!

I've got some exciting news to share with you. The SAP CodeJam roadshow is coming back to Latin America! This time, we will do a special edition in Brazil. We will have many stops on the roadshow starting the 1st week of March, doing CodeJams as part of SAP Inside Tracks, organised by local community members, and then continuing in April. Also, we'll organise a couple of meet-ups as we've done in previous year. :-).

Keep an eye on this blog post as more events will be announced as part of the roadshow shortly

SAP CodeJam events and meetups part of the roadshow (Register Now!)

Below is a listing of the SAP CodeJam events and quedadas (meetups) on the roadshow schedule:

Dates	CodeJam topic	Location	Registration
2 Mar	Build AI services using the CAP and Generative AI Hub	Campinas, Brazil 🇧🇷	Link
3 Mar	Joule Studio: Create Joule Skills and Agents Without Coding	São Paulo, Brazil 🇧🇷 🇧🇷	Link
3 Mar	São Paulo meetup	São Paulo, Brazil 🇧🇷	Link
4 Mar	SAP Build: Create Event-Based Processes	São Paulo, Brazil 🇧🇷	Link
5 Mar	Getting started with Generative AI Hub on SAP AI Core	Rio de Janeiro, Brazil 🇧🇷	Link
13 Mar	Getting started with Generative AI Hub on SAP AI Core	Joinville, Brazil 🇧🇷	Link
14 Mar	SAP Inside Track - Joinville	Joinville, Brazil 🇧🇷	Link
20 Mar	Getting started with Generative AI Hub on SAP AI Core	Belo Horizonte, Brazil 🇧🇷	Link
21 Mar	SAP Inside Track - Belo Horizonte	Belo Horizonte, Brazil 🇧🇷	Link
6 Apr	Combine SAP CAP with SAP HANA Cloud to Create Full-Stack App	São Paulo, Brazil 🇧🇷	Link
7 Apr	ABAP AI: Capabilities in SAP Joule for Developers CodeJam	São Paulo, Brazil 🇧🇷	Link
8 Apr	ABAP AI: Capabilities in SAP Joule for Developers CodeJam	Londrina, Brazil 🇧🇷	Link
10 Apr	Getting started with Generative AI Hub on SAP AI Core	Curitiba, Brazil 🇧🇷	Link
10 Apr	SAP HANA Cloud for AI Applications: ML, Vectors, and Knowledge Graphs	Ribeirão Preto, Brazil 🇧🇷
13 Apr	SAP HANA Cloud for AI Applications: ML, Vectors, and Knowledge Graphs	São Leopoldo, Brazil 🇧🇷
14 Apr	Extending Joule with Code Based AI Agents	São Leopoldo, Brazil 🇧🇷
16 Apr	SAP HANA Cloud for AI Applications: ML, Vectors, and Knowledge Graphs	Recife, Brazil 🇧🇷
17 Apr	Extending Joule with Code Based AI Agents	Recife, Brazil 🇧🇷

Make sure to register to secure your place. It is likely that the places available will go fast.

What if the CodeJam topics do not cover the SAP technology that you focus on? We've organised additional local meetups just to get together and have a chat. See you all somewhere in Brazil on the roadshow!

Ask Me Anything with SAP Champions – Monthly Series (Session 1)

2026-02-02T08:07:05.474000+01:00

Hello Community,

My name is Sebastiano Marchesini, SAP Champion and SAP BTP architect. I moved from Italy to the US and currently work as a technology lead consultant, focusing on SAP BTP and enterprise architectures. I also love running 🙂

From my experience at SAP TechEd, learning sessions, and live events, the most valuable moments are always the same:

Asking questions, any kind of question, and getting direct, honest answers from experts.

For this reason, the SAP Champions are launching a new monthly AMA (Ask Me Anything) series starting in 2026.

Each month, a different SAP Champion with a specific area of expertise (BTP, architecture, integration, development, automation, career growth, and more) will answer questions from the community, both technical and non-technical.

This blog post is the first of the series.

You are invited to ask any questions you have, openly or anonymously, using the form below.
No topic is off-limits: architecture doubts, product choices, real-life SAP challenges, or even questions about working in the SAP ecosystem, running (lol).

Let’s make this a space for open discussion, real experience, and practical answers.

You can ask anonymously here

AMA Champion Anonymously Questions

(or below as anwer of the blog)

Submit your questions by early February and get answers in our upcoming SAP Communities video and blog recap.

This AMA session will be open for questions until the last week of February.

After that, selected questions will be answered in a recorded video published on the SAP Communities YouTube channel.
A blog recap summarizing the questions and answers will also be published for the community.

Only questions submitted during this window will be considered.

New Shell Bar in SAP Build Work Zone - What Admins Need to Know

2026-02-02T19:44:57.930000+01:00

--- LATEST UPDATE: We’ve decided to delay the dates for when the updated shell will become the default for all sites, giving customers more time to review their custom plugins and automations. The blog post has been updated with the revised timeline based on current planning. ---

Hello, SAP Build Work Zone enthusiasts! 🌟

We’re excited to share some important updates that may have gone unnoticed during the holiday season, particularly regarding UX consistency-related (UXC) changes designed to enhance your SAP Build Work Zone experience.

Since the December 10, 2025 release, there is a new improved shellbar available with SAP Build Work Zone, standard edition, which will eventually become the default for all Work Zone sites. This updated shellbar delivers a more consistent user experience and an enhanced user menu. Additionally it simplifies logo customization in your site’s shell bar without requiring an entirely new theme, thanks to the new Shell Bar customization options! For more details, please check 🔗 SAP KBA 3673380 .

What’s New?

1. Toggle the New Shell Bar Experience

Admins can now choose whether to enable the updated Shell header component on a per-site basis. Here’s how it works:

OFF (Default for existing sites until mid May 2026): Your site will continue rendering as before.
ON (Default for new sites and after mid May 2026): Your site will adopt the new UXC changes, giving you a fresh, modern look!

2. Customize Your Site Header

When UXC changes are turned ON, you can further personalize your site with:

Custom Label: Set a unique name for your site header.
Custom Logo & Alt Text: Add a link to your own logo for a branded experience.

3. Future-Proof Your Work Zone

By mid of May 2026: All sites will render with UXC changes by default (but you can still turn them off).
By mid of September 2026: The toggle will be removed, and all sites will adopt the new UX design.

This ensures alignment with SAP’s latest UX standards while giving you time to prepare.

What to Watch For

If you enable the new Shell Bar, some automation scripts, custom plugins, or SAP Companion hotspots may need adjustments. Here’s what to do:

✅ Update automation scripts interacting with the DOM.

✅ Reconfigure custom SAP Companion hotspots if selectors have changed.

✅ Test custom plugins to ensure they work with the new Shell Bar.

For detailed guidance on how to resolve possible issues, check out: 🔗 SAP Note 3627739.

Call to Action: Try Out the New Shell Bar Today!

We encourage all customers to turn on the new Shell Bar in a test environment and explore the enhancements. By checking these changes upfront and applying the new settings to all your sites, you can ensure a seamless transition without any disruptions to your productive sites. Ideally, we recommend turning on the new setting for productive sites before the default behavior changes.

Your feedback is invaluable to us. If you encounter any issues or have suggestions, please share your experience or get in touch with us via the comments section.

🚀 Try it now:

Go to Site Settings → Site Branding.
Toggle "Apply New Shell Bar" to ON.
If you want, you can customize your logo and label.
Test your scripts, plugins, and workflows.

Site Branding area in the site settings. Also notice the information bar informing about the new option.

Let us know how it goes. We’d love to hear your thoughts!

Stay tuned for more updates, and happy customizing! 🎉

— The SAP Build Work Zone Admin Environment Team

When Innovation Meets Real Business Impact - VNSG SAP BTP Hackathon 2026

2026-02-04T13:53:21.455000+01:00

A community powered by creativity

The VNSG SAP BTP Hackathon has once again shown what happens when passionate people, real business challenges, and SAP Business Technology Platform come together. Teams of customers, partners, and experts turned ideas into tangible solutions that demonstrate how SAP BTP can drive measurable value in day-to-day operations.

Over the course of the Hackathon, every team brought its own perspective, business context and technical skills – from integration and automation to SAP Business AI and extensions on SAP BTP.

The result: a set of working prototypes that not only impress technically, but are rooted in real customer needs and adoption potential.

Celebrating the 2026 finalists

After intense jury deliberation, three teams earned a spot in the grand final at SYNC 2026 for their strong presentations, clear business impact, and high potential for real-world rollout.

Promocean (supported by SOA People) – “Operational Excellence through SAP Business AI”: A showcase of how SAP BTP and Business AI can streamline operations and enhance decision-making in a very pragmatic way.
Ecotone (supported by Expertum) – “Interface Maintenance”: A smart solution addressing the often underestimated pain of interface management, using SAP BTP to bring transparency, stability and control.
NTT Data – “ProTrack”: A forward-looking use case that leverages SAP BTP to better track, steer, or optimize processes

These finalists did not just deliver “cool demos”, they delivered stories where business and technology reinforce each other, with SAP BTP at the core as the innovation platform.

A strong field beyond the finalists

Of course, a hackathon is about much more than just three winners. Aarini Consulting, Nederlandse Spoorwegen, and Simac IT & BSC also delivered impressive solutions that made the jury’s job anything but easy.

Each of these teams tackled real business scenarios and used SAP BTP services to create innovation that can move quickly from prototype to production. The organizers explicitly encourage all teams to work with their coaches on post-hackathon follow-up to drive implementation and adoption, because the real success of a hackathon is measured when the ideas go live.

SYNC 2026: where the stage is yours

As recognition of this milestone, the three finalist teams are invited to present at SYNC 2026, the VNSG Annual Conference on March 12. During the opening session, each finalist will pitch their solution live on stage to the SYNC audience. The audience will then vote to determine the VNSG SAP BTP Hackathon Champion – a great opportunity to showcase innovation, customer impact and the power of SAP BTP in front of the wider SAP community.

Keep the momentum going

For everyone involved – finalists, other teams, coaches and the broader community – this hackathon is a starting point, not an ending. The next steps are about refining solutions, planning production rollouts, and scaling adoption so that the innovation created during the hackathon translates into lasting business impact.

If you are part of the VNSG or wider SAP community and feel inspired by these stories, take this as a call to action: bring your own business challenges, experiment on SAP BTP and co-innovate with partners and customers.

The SYNC 2026 VNSG SAP BTP Hackathon has proven once more that with the right mix of creativity, collaboration and platform capabilities, you can turn ideas into value – fast...

SAP Business Technology Platform SAP Build SAP Integration Suite

@hansvp @qmrjvd @sricsi98 @BvE @mdschoenmakers @tamasszirtes @f_van_leeuwen @Petra1 @BartvdKamp @tedcastelijns @Arjan_deMol @dvvelzen @JdTeuling @AnnikaHeus @LaurensSteffers

2026 SAP BTP GTM strategy and priority initiatives for Partners

2026-02-05T16:48:43.612000+01:00

If you’re planning your 2026 GTM motions, this is one session you’ll want on your calendar.

SAP Business Technology Platform is no longer just “the platform behind the scenes”. It’s becoming the engine of a consumption-led, AI-first go-to-market strategy — and Partners play a central role in making that real for customers.

In this executive-level webinar, SAP’s BTP Customer Success and Ecosystem leaders will walk through how SAP Build, SAP Integration Suite, CIAM, and Core AI fit together as one coherent story. Not in theory, but in actual GTM scenarios Partners can use to drive pipeline, bookings, and long-term consumption.

We’ll look at how SAP BTP shows up across RISE with SAP and GROW with SAP, why cACV matters more than ever, and how partners can align clean core principles with real customer outcomes. Plus, we’ll share concrete partner-led GTM plays, and enablement programs designed to help you scale.

If you’re focused on sharpening your SAP BTP value proposition and building repeatable GTM motions for 2026, this session is for you.

👉 Register now https://partneredge.sap.com/en/library/education/psd/2026/feb/e_oe_te_w_PSD_WEB_00012968.html

#SAP #SAPPartners #SAPBTP #PartnerGTM #SAPBuild #EnterpriseAI

Build custom Joule Agent to analyze blocked freight order in S/4HANA TM

2026-02-08T01:49:35.777000+01:00

In this blog, the objective is to build a custom Joule agent with multiple skills that analyzes a blocked freight order in the S/4HANA Transportation Management (TM) solution.

To keep the scenario simple, the agent analyzes blocks caused by time conflicts and explains them in simple business language.

What you will learn

By the end of this blog, you will understand:

The prerequisites for building this use case
How to expose TM documents as OData services consumable by Joule
How to create Build Actions, Joule Skills, and a Joule Agent
How to write basic instructions for the Joule Agent
How to test and fine-tune the agent

All of this can be done with minimal or no coding. With the right access and setup, even a business user can follow these steps and build a basic scenario in about 30 minutes. The approach is similar across S/4HANA solutions, with different OData services used to fetch backend data.

Let’s look at the high-level steps

Pre-requisites
Identify available CDS views in S/4HANA TM and wrap it with an OData service
Configure SAP Cloud Connector – Joule (from public internet) needs secure communication channel to connect your ERP environment
Define Destinations on your BTP subaccount - connect to the OData service via cloud connector
Define Actions in Joule Studio
Define Joule Skills
Define Joule Agent
Test!

Let’s look at the steps in detail.

STEP 1: Pre-requisites

You need the following to run this scenario,

An S/4HANA private or on-premise environment
Eclipse IDE with ABAP Development Toolkit (ADT) – see the tutorial if you haven’t done
SAP Cloud Connector installed in your landscape – follow this if haven’t done
An SAP BTP subaccount with Joule Studio (Joule studio is one of the components of SAP Build) – follow SAP Discovery Center Mission for steps to do that.

STEP 2: Identify available CDS views in S/4HANA TM and wrap it with an OData service

Look at the SAP documentation for all available standard S/4HANA CDS views. For S/4HANA TM, see here. In this use case, we require data from Freight Order, its item and stop nodes. So, let’s login to S/4HANA system and create an OData service for the three CDS views.

Select a package and create a service definition

Select referenced object as the respective CDS view and create and activate the service definition for the three CDS views.

Once created the definition, create a service binding by right click on each definition. Follow the wizard and after creation, activate the binding and then publish it. You can see the service URL and note that down. You can as well test the service now.

STEP 3: Configure Cloud Connector

Login to your SAP Cloud connector and Configure cloud to On-premise for the subaccount you are going to use for Joule. ‘/’ expose all which is not ideal, but fine for testing environments.

STEP 4: Define Destinations on your BTP subaccount

Now login to your BTP sub-account and navigate to ConnectivityDestinations and create a destination of type ‘HTTP,’ proxytype ‘OnPremise’.

The URL must be constructed by combining virtual host URL in cloud connector with service end point. Also add additional properties as shown in the screenshot.

STEP 5: Define Build Actions

Now navigate to your Joule Studio (SAP Build) environment.

Navigate to the ConnectorsActions and create an action to fetch freight orders which are blocked.

Once you click create, select OData Destinations as API source. It will display all OData destinations defined in the subaccount. Pick the destination created in step 4.

It displays the available services in the underlying CDS view. Select Next and provide a meaningful name and description. Then navigate to the created action project.

Initially, the OData service will be with its basic definition. We need to add filter to fetch only filter blocked freight order (just pick execution blocked).

For this, click $filter parameter and then click Value F4 help in the popup. You can use condition editor or Text Expression.

Reduce output fields

In the Output tab:

Select the Body parameter.
Remove unnecessary fields.

For this scenario, keep only:

Order number
Description
UUID

You can test the action under the Test tab by selecting the destination and clicking Test.

If destination is not visible, Go to Control Tower view of Build and select Destinations and add the destination you created before.

Do these steps to create three actions to fetch root, item and stop information. Idea here is, first fetch root and then PRD item. From item node, get the FU and go to FU stop to get acceptable and planned dates. Provide all this information to Joule for analysis.

While creating action for item,

add a filter to restrict only PRD items.
Reduce the Output to have only freightUnitUUID field.

While creating action for stop,

Reduce output to pick only location, stoprole, stopcategory,acceptable start and end time and planned time.

STEP 6: Define Joule Skill

Navigate to Build Lobby and click create and select Joule Agent and skill. Once the project is created, click create and select Joule Skill. Provide a clear name and description of the skill.

Click on conversation starter and provide the prompt. Example ‘get execution blocked freight order with stop details and analyze the reason for block’

You don’t need any other input from user as we already did filter in our action to pick execution blocked freight orders.

Add the action by clicking the ‘+’ button and select our action to fetch freight order root.

Navigate to skill parameter (select anywhere in the editor and click >> button to view skill parameter). Select the output for http 200 code as shown below.

Finally bind the skill output to the trigger end of action.

Likewise create other skills to fetch item and stop nodes.

For item skill,

Skill input must be TransportationOrderUUID
Map skill input to action input as shown below

Finally map skill output to trigger end.

For stop skill,

Skill input must be FreightUnitUUID
Map skill input to action inputs shown below

STEP 7 – Create Joule Agent

In the project, create ‘Joule Agent’ and navigate to agent definition screen.

Define ‘Expertise’ which provides the persona of the agent and ‘Instructions’ as system prompt on how to analyze reason for blocked freight order. Write that in plain, simple English. An example as shown below.

Provide some few-shot learnings to the agent as part of instructions. Example below

##Example 1 (case with date 'TranspOrdStopPlanTranspDteTme' is before date 'TranspOrdStopAccptblStrtDteTme')

Given the following Freight unit stop details:

- Transportation stop acceptable start date: 10-January-2026

- Transportation stop acceptable end date: 12-January-2026

- Transportation stop planned date: 8-January-2026

// Business Rule: date 'TranspOrdStopPlanTranspDteTme' must be after date 'TranspOrdStopAccptblStrtDteTme'

// Analysis: 8-January-2026 is NOT after 10-January-2026

// Expected blocked freight order Analysis result: Since planned date is not after acceptable start dates, freight order is blocked

Select your desired LLM provider, base and advanced model. Example OpenAI, GPT-4o Mini and GPT-4o. Save the agent definition.

Navigate to the Tools tab and add the three skills to the Agent you created before,

At the end, your project will have one Joule Agent and three Joule Skills.

STEP 8: Testing!

Click on the Test icon at the top of the project. Select the actual destinations within BTP to be used at runtime.

The conversation starter will appear and click that.

The agent will:

Select the required skills
Execute them in the appropriate sequence
Map parameters between skills
Evaluate the data
Return a business-friendly analysis using the selected LLM

Summary:

This example demonstrates how easy it is to build custom Joule agents and skills.
The same approach can be applied to other S/4HANA solutions and a wide range of use cases.

This blog should help anyone new to Joule get started and build a simple proof of concept.

Vibe Coding with Joule Studio: Bringing Your Own Model with NVIDIA NIM

2026-02-11T08:34:47.058000+01:00

As we build the future of enterprise AI at SAP, our vision for Joule Studio is clear: to provide a platform where you can build, manage, and scale intelligent agents that are deeply integrated with your business processes. The out-of-the-box capabilities, powered by SAP's native models and the generative AI hub, are designed for robust, reliable, and context-aware orchestration within the SAP ecosystem. But what if you want more control over how your agent thinks, codes, or reasons? What if the model you want isn’t (yet) available in Joule Studio or the generative AI hub? What if you could build it all using natural language?

That’s where Bring Your Own Model (BYOM) meets Vibe Coding in Joule Studio.

The Idea: Build a Joule agent powered by external models.

With this example, you can vibe code a custom Joule agent in Joule Studio that uses a Joule skill to call an external AI model like Nemotron hosted via NVIDIA NIM, one of the most powerful open-access foundation models specifically designed to build high-performance, specialized agentic AI systems.

To be explicit about how this works, it’s a "best of both worlds" approach:

The Agent's Core Reasoning: The Joule agent itself continues to leverage its powerful, default Large Language Models for its primary job: reasoning, planning, and orchestrating the overall workflow. The agent's runtime is optimized to perform best with these native models.
The Skill's Specialized Task: Then, for a specific task — like integrating with Nvidia’s NIM models in this case — the agent uses a Joule skill to leverage the power of NVIDIA Nemotron model. The skill acts as a bridge to specialized intelligence and deep reasoning.

Accelerate Agent development with Vibe Coding in Joule Studio

Vibe coding allows you to transform your ideas into a Joule agents quickly. Here is what you can do with vibe coding in Joule Studio:

Build Joule skills with drag and drop simplicity
Build a Joule agent by prompting in natural language. The agent’s expertise and instructions will be filled automatically with SAP best practices
Enable the tools that the Agent can utilize to generate an optimized response to the user, including the Joule skill with external model, MCP Server or Document Grounding via AI Core.
Test your agent in the private environment
Deploy the agent when ready and share it with colleagues

Vibing Coding in Joule Studio generating Agent's Expertise & Instructions

After the agent is ready, the conversation flow is simple:

The user interacts with the Joule agent in natural language.
Joule asks the user to choose the Nemotron model. Here, I am using: nvidia/llama-3.1-nemotron-nano-8b-v1 and nvidia/nemotron-3-nano-30b-a3b.
A Joule skill sends the user query and the selected model to the NVIDIA Nemotron API.
The selected NIM model processes the request and sends the output to the Joule agent.
The Joule agent evaluates the response, checking how the model solved the required task.
The response is then presented to the user.

The key detail: the user can choose which Nemotron model to use, enabling dynamic querying and true BYOM experience.

Joule Runtime conversation:
"A developer asks Joule to generate a BAPI extension. Nemotron reasons through the logic, generates the code, and explains why it chose that approach."

Joule conversation - User Query, Model Selected & Response from Nemotron.

Model name and response logged in Joule Timeline.

By combining Joule's orchestration with NVIDIA's Nemotron Models, the agent can be scaled to generated responses with deep reasoning, visual contextualization, document analysis and multimodal research.

Example of a Scenario: The Business Problem
"A procurement manager receives hundreds of POs daily. They need to identify risks, anomalies, and optimization opportunities - but it requires analyzing data across multiple SAP systems + deep reasoning."

The Agentic Flow
Agentic Flow leveraging external Models
Some more examples:

Upload images of defective parts/machinery to identify defects and receive recommendations using multimodal AI.
Analyze invoice PDFs to get explanation of charges and identify missing information using Vision Language models
Accurately forecast customer buying capabilities or inventory fulfilling using predictive models.

Why Use External Models Like NVIDIA Nemotron?

Using models outside Joule Studio or generative AI hub unlocks several real-world benefits:

Freedom to bring your own model
Use cutting-edge or domain-specialized models that are not yet natively supported by SAP.
Ship Innovative Agents faster
Experiment with new reasoning, vision, or code-focused models without waiting for platform updates.
Choose the right model
Choose different NIM models for coding, analytics, logistics reasoning, or document understanding.
Future-proof architecture
Your Joule agent becomes model-agnostic, making it easier to swap or upgrade models later.
Enterprise-safe orchestration
Joule Studio still handles identity, governance, and process integrations - only the intelligence is externalized.

Conclusion

You can now build intelligent agents that vibe with your users, adapt on the fly, and leverage state-of-the-art models as of today. Furthermore, your agent can execute at scale to solve more complex problems by empowering them with tools like MCP Server, Document Grounding and Calculators while leveraging the power of external models.

It’s time to build AI agents that unlock the true potential of your business with tools and models of your choice. Here is how you can get started too: Read the blog here.

Creating a ‘Hello World’ Joule Agent

2026-02-11T11:55:37.566000+01:00

Building on Michael Ameling's excellent Agent Builder in Joule Studio announcement and The Joule Studio Learning Series, this post will guide you through building your first Joule Agent.

I'll walk you through the steps to build a "Hello, World" agent. Along the way, you'll get familiar with the basic workflow in SAP Build, explore the UI, avoid at least one common pitfall, and have your agent up and running in just a few minutes. By building the simplest possible agent, you'll gain the confidence that building agents is easy, and creating more sophisticated ones will feel like a natural next step. Let's get started.

Setup and Prerequisites

The setup of SAP Build Apps, the activation of Joule, and the SAP Agent Builder are described in these two blog posts:

I'll assume that's done, and we'll start our journey in the lobby of SAP Build Apps.

Creating a Project

Click on the "Create" button, and select "Joule Skill":

Enter a name and a description:

Creating the Joule Agent

You'll be forwarded to the overview of your project where you can create the Joule Agent:

Again, enter a name and a description. A proposal for the identifier will be generated automatically:

On the details page of your Hello World Agent, you could fill in the fields manually, but let's use Joule to create a proposal. In the top left, click on the Joule icon to open the Joule sidebar. Enter a prompt like this:

"Can you please update our existing Hello World agent by filling in the expertise, instructions and additional context? The agent should respond to every prompt with "Hello, World!"."

As a result, Joule updates the agent, and we're almost done. We just need to add a placeholder tool, for example the calculator, because Joule Studio does not allow an agent to be saved without a tool assignment:

Now you can save the agent, and we can move on to testing the functionality we've just implemented.

Testing the Joule Agent

When you click on the "Test" button (just above the "Save" button), you'll be asked which environment you'd like to test in. Select the environment associated with your email address.

If your email address doesn't appear in the dropdown, you need to activate your private environment first. To do so, click on the SAP Build icon in the top left corner, click on "Control Tower" in the left-hand menu, and then click on the "Environments" tile:

On the Environments screen, click the button to activate your private environment:

Afterwards, you can resume testing and your private environment should appear in the dropdown as described above.

Now we're ready to test the agent, for example with a prompt like "Let's test the agent".

As we can see, the agent correctly responds with "Hello, World!" 😅

To end the test session, just click on the "Stop Testing" button.

Deploying the Joule Agent

To get our agent out of the testing environment, we need to deploy it to a real environment.

Let's create a Hello World environment. Navigate to the Control Tower, select the Environments tile, and click on "Create". Enter a name and description for the environment. The proposal for the identifier will be generated automatically.

Your user will be automatically added to this new environment. If you see a blank screen when you want to view the environment details, just try refreshing the page in the browser. It may take a little while to generate.

Once the environment is active, we can deploy our agent. Click on the "Release" button in the agent overview.

In the subsequent pop-up, enter a release note and click on "Release".

Once released, switch to version 1.0.0 at the top of the screen by clicking on the dropdown next to the title.

In the released version, there is a "Deploy" button instead of the "Test" and "Release" buttons. Click on the "Deploy" button, select the Hello World environment, and click on "Deploy".

After a few moments, the status of agent version 1.0.0 will change to "Deployed and Active".

Testing the Deployment

As a final step in this tutorial, let's test our deployed agent in the Hello World environment.

Open the Hello World environment via the Control Tower and view the environment details by clicking on it in the list. There, you will see the deployment of the Hello World agent we just made.

To test it, open the Joule tab for this environment. Depending on your screen resolution, this may be hidden in the "More" drop-down. On this tab, click the "Launch" button.

Joule will open in a new tab and we can prompt it to test the agent, for example like this: "Run the Hello World agent."

To confirm that Joule actually called the agent, you can investigate the log by clicking on the icon in the top right of the title bar.

Conclusion

Congratulations, you just implemented your first Joule agent! As intended, the overall result is "just" a Hello World agent, but this is an important first step in your journey to becoming a Joule agent builder. You familiarized yourself with the UI and performed the full workflow from start to finish, including creating a project, creating an agent, testing, and deploying it. Along the way, we also used Joule itself to fill in the agent's configuration details.

From here, there are many more topics worth exploring, like Joule skills, MCP integration, or agent-to-agent communication. However, for me, it's always important to build a Hello World example first without getting lost in the details. With more complex starter scenarios, it's easy to get stuck on technical details and lose sight of the big picture. Now that you've completed your "Hello World", you can iteratively add more features and build more sophisticated agents. What's the first use case you're going to tackle?

POV on How to Approach Custom Agents in the Enterprise - Blog Series

2026-02-14T00:45:50.136000+01:00

You've invested in AI agents across your enterprise - some from SAP, others from your broader tech stack. But as your AI ecosystem grows, so does a critical question: how do I approach my use cases strategically across this diverse landscape?

This blog addresses that question by addressing several POVs on how you can approach your AI agentic use cases both with SAP and non-SAP.

The POVs I will focus on are:

Read BEFORE the POVs:

You first need to understand when you would require a custom agent as there is always additional governance and build effort associated with maintaining an agent’s lifecycle.

SAP recommends that custom agents or agent extensions should only be created when your prioritized use case does not already exist out-of-the-box (OOTB). How would you know if it exists OOTB? Easy! Our SAP Discovery Center contains an AI Catalog that you can filter by solution and/or business area to see what Agents and Embedded AI capabilities are available for out-of-the-box use.

Image taken from AI Catalog

If the agents meet partial or no requirements, then it is safe to say you can create a custom agent extension.

What will you get out of this Blog Series?

By the end of this blog, you'll understand how to approach your AI agent strategy - from leveraging existing SAP capabilities to building custom solutions that integrate and orchestrate collaboration between SAP and non-SAP agents across your enterprise landscape.

Click to begin reading POV 1 - Creating Custom Agents in SAP.

POV 1: Create Custom Agents in SAP (Part 1/4)

2026-02-14T00:46:44.476000+01:00

This Blog is Part 1 of a Blog Series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

POV 1: Create Custom Agents in SAP

If your business requirements cannot be fulfilled with the out-of-the-box SAP Joule Agents and you wish to use SAP data for your custom agent, then SAP Build's Joule Studio Agent Builder is the recommended solution.

In Joule Studio Agent Builder, you can use no-code/low-code as well as natural language prompting (through embedded Vibe Coding) to create custom Joule skills and Joule Agents. As a reminder, Joule skills are deterministic meaning they will be able to complete a specific task relatively quickly. Joule agents, on the other hand, reason and problem solve across multi-step scenarios within a defined business domain.

Image taken from Joule Studio Agent Builder; showcasing embedded Vibe Coding used to create a custom Restocking Agent. Source

Why would you want to create SAP agents within SAP?

SAP knows SAP best - Joule is the agent orchestrator that allows it to be proactive and is deeply connected to business context and deep domain knowledge. SAP's business context is the "magic" of joule that helps determine the sequence and which agents or tools to use. SAP Agents will always have the business context to understand what is being asked of them and how to answer, therefore resulting in more reliable and relevant responses.
Controlled Enterprise-wide Governance - Joule is strictly role based. Meaning it is tightly integrated across the SAP security landscape through BTP's Cloud Identity Service (CIS) - which manages user authentication and access between your apps and Joule. For example, if Joe with US specific Finance roles & authorizations (R&A) is given access to a custom agent containing world-wide Finance info, Joe will only see financial data/information relevant to the US as per his assigned R&A. Similarly, Joe will be able to prompt Joule regardless of the SAP cloud application, if he has access. For example, if he has access to S/4HANA Cloud, SuccessFactors, and Work Zone - he will be able to use any app’s Joule interface to prompt it. Joule’s security landscape results in responsible responses across the SAP landscape. Please see the Architecture Diagram for detailed architecture of Joule Studio and CIS.
Connect non-SAP data - Joule allows you to connect non-SAP data sources using APIs, as well as grounded external/internal documents allowing you to blend non-SAP and SAP data with your grounded policies and documentation.

In short, creating an SAP Agent outside of SAP will result in additional effort to rebuild business context and security.

Next POV?

To check out Part 2 of the Blog Series click: POV 2 - Agent to Agent Collaboration with SAP and non-SAP Agents.

Or click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

Source: Blog by Michael on Joule Agent Builder

Source: Blog by Amit Bangora on Joule Skill Build

POV 2: Agent to Agent Collaboration with SAP and non-SAP Agents (Part 2/4)

2026-02-14T00:55:30.928000+01:00

This Blog is Part 2 of a Blog Series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

POV 2: Agent to Agent Collaboration with SAP and non-SAP Agents

*A2A Interoperability Coming Soon in 2026

In some cases, you may want to leverage your non-SAP Agents with SAP agents. As discussed in POV 1, bringing SAP data outside of SAP will result in challenges in security, governance, and business context - compromising the agent’s responsibility, relevance, and reliability.

This is a great opportunity to combine the best of both worlds - SAP & non-SAP Agents through Agent-to-Agent collaboration.

How? The A2A open protocol, developed by Google, handles inter-agent communication allowing agents, regardless of their vendor, to communicate complex tasks. Many of you may have already heard of MCP (Model Context Protocol), however if you would like a refresh – check out this blog by Pramod. It is important to note that A2A does not replace MCP but rather works alongside it. Think of A2A as the communication handler between agents where one agent assigns a subtask to another and the MCP enables the agents with the right tooling to complete the task. Using A2A with MCP enables autonomous AI agents regardless of if they are SAP or non-SAP.

From SAP the key orchestrator of agent collaboration is Joule, as discussed in POV 1, where it orchestrates the sequencing of tasks and workflows using deep domain knowledge and business context. What does this mean in terms of what autonomous agent-to-agent collaboration can achieve between SAP and non-SAP?

Agents are Discoverable - AI Agents will have discoverable endpoints that will be captured in the SAP AI Agent catalog acting as an adapter between SAP and non-SAP agents. As per the diagram below there will be an auto-assigned ORD (capture agent metadata) to ensure the Agent is discoverable. Through this, Joule will know what the agents can do to ensure the right one is selected to complete a task. (see architecture diagram below)
Delegate tasks/artifacts - There are 2 types of agents to facilitate A2A communication: a client agent and remote agents where the client agent sends the task (eg. prompt or system triggered) and the remote agent receives the task, matches the tools, and executes the task. A2A is designed to be task-oriented and with the combination with its discoverable endpoints and deep domain knowledge, business context, Joule will understand how to orchestrate internally and with external agents.
Operate securely and interoperable across systems - As per the diagram below, all external agents will be routed through the Agent Catalog making them discoverable and preventing direct exposure of SAP Agents to external agents. In addition, Agents will have a secure tool layer (Tool catalogue) where agents will have access to tools within trust boundaries that respect security policies.
Scale your enterprise – rather than operating agents in silos, you can now have a connected interoperable agentic ecosystem with distributed functionality/tasks making it easier to scale.

The above image shows A2A Architecture with SAP. For example, a customer service rep receives a billing inquiry in their email. The service rep initiates a dispute resolution process through Joule and engages with a Google Agent (e.g. BigQuery data Source) that retrieves the required data and shares it back to Joule - collaborating to generate insights and resolution recommendations. To see this lab preview A2A scenario in action, check out this github.

Therefore, you can leverage all your investments, SAP & non-SAP, to have a connected Agent ecosystem.

Next POV?

To check out Part 3 of the Blog Series click: POV 3 - Using Integration Suite as Your Governed MCP Server Platform.

Or click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

Source: A2A Blog by Google

Source: SAP A2A Architecture

POV 3: Using Integration Suite as Your Governed MCP Server Platform (Part 3/4)

2026-02-14T01:04:11.131000+01:00

This Blog is Part 3 of a Blog series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

POV 3: Using Integration Suite as Your Governed MCP Server Platform *Coming Q2/2026

If you didn't have a chance to tune in to SAP Tech Ed's IN200v | Empower your agents to be responsible (2025) then it is notable that in Q2/2026 SAP Integration Suite's API Management will allow you to apply additional security policies to APIs in your MCP servers and publish your secure APIs with MCP documentation for Agent consumption via the API and MCP Gateway.

Why is this important?

MCP allows agents to access external information for systems, APIs, documents all while reducing agent complexity. In summary, agents with a MCP client will rely on the MCP server to provide structured metadata to the APIs/Protocols. However, these APIs within the MCP server will likely not meet all security requirements and pose some security risk.

With SAP Integration Suite's API and MCP gateway, you will be able to apply additional API Policies around multi-protocol connectivity, routing, transformations (eg. JSON to XML), mapping, traffic management, and security requirements to further secure, monitor and govern your APIs being leveraged as part of your MCP. This will be incredibly powerful for both SAP Agents and non-SAP agents.

Image taken from SAP Tech Ed's IN200v | Empower your agents to be responsible (2025)

How is this relevant to on-premise users?

Users that are on-premise (eg. ECC, S/4HANA on-prem) can leverage Integration Suite to create custom APIs through OData Services or modify prebuilt S/4HANA APIs (see Business Accelerator Hub) and apply additional API policies to reduce security risk. These APIs can then be leveraged in SAP as well as non-SAP agents. However, it is important to consider the rebuild effort of business context and security when accessing SAP data outside of Joule agents (as described in POV 1).

Where else can Integration Suite and SAP help in my Agent Build?

SAP Business Data Graphs! Within Integration Suite you can explore, design, and extend Graph APIs (Odata V4 or GraphQL) for agent consumption.

Think of this as a semantic layer (connecting multiple entities) that sits on top of the API that allows your agent to receive a mix of entities from one central entity - removing the Agent’s effort to combine the entities together.

Graphs are powerful because the projections between data sources (entities) are automatically created between SAP data as SAP leverages the One Domain data model. However, there are also capabilities for developers to extend to non-SAP. Therefore, allowing you to have a simplified semantically rich API ready for Agent consumption with the bonus to apply additional API policies on top of it, resulting in a secure Graph API. For more information on Graph APIs please check out this blog on an Intro to SAP Graphs & Graph in Integration Suite Blog.

An example of this can be seen in the image below that summarizes the demo shown at SAP Tech Ed's IN200v | Empower your agents to be responsible session. You can see that a user prompts an Agent that leverages MCP API tools with additional governance policies applied to the Graph API. This showcases secure and semantically connected data across SAP Risk assessment, Supplier Plant, and Supplier plant materials entities - resulting in higher performing responsible, relevant and reliable AI Agent response.

Source: Graph – SAP Help

Source: Watch Tech Ed sessions on-demand

Next POV?

To check out Part 4 of the Blog Series click: POV 4 - Putting it all Together Across Your Enterprise.

Or click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

POV 4: Putting it all Together Across Your Enterprise (Part 4/4)

2026-02-14T01:13:05.033000+01:00

This Blog is Part 4 of a Blog Series (4 Parts!). Click on the following to navigate back to the main menu of POV on How to Approach Custom Agents in the Enterprise - Blog Series.

POV 4: Putting it All Together Across Your Enterprise

Keeping in mind POV 1, 2, and 3 - POV 4 focuses on bringing your enterprise-wide agents together with an additional layer of security and governance.

As discussed, Integration Suite will allow you to create custom APIs - SAP and non-SAP- including Business Data Graph APIs. These can then be further consumed, whether it’s a custom API through SAP or non-SAP or an API that’s part of a MCP server. In other words, both Joule and non-SAP agents will be able to leverage secure governed APIs and MCPs in an interoperable agentic ecosystem.

In simpler words: Integration Suite and Joule Studio will be the key to unlocking secure, governed, and business context rich agent ecosystems.

In Summary

We opened with a critical question: How do you approach your use cases strategically across your diverse AI landscape? The answer lies in three integrated capabilities:

SAP Joule provides the foundation for responsible, reliable and relevant custom agents with Joule through its deep domain knowledge, rich business context, and secure governance capabilities.
Joule can be used for both SAP specific use cases as well as non-SAP Agent collaboration - bringing the best of both worlds together.
Finally, Integration Suite's API management and MCP Gateway capabilities will be key to unlocking an additional powerful security and governance layer for your agents across your enterprise.

This concludes the Blog Series: POV on How to Approach Custom Agents in the Enterprise.

Leveraging SAP Build Process Automation for Intelligent Invoice Extraction from Outlook

2026-02-17T08:27:43.106000+01:00

Imagine a world where your inbox doesn’t just store invoices, but actively processes them. No more manual downloads, no more mind-numbing data entry, and zero "human-error" bottlenecks.By integrating the "digital eyes" of SAP Document Information Extraction with the orchestration power of SAP Build, organizations can now transform unstructured email attachments into clean, high-fidelity structured data in seconds. This blog explores the seamless end-to-end journey of an invoice—starting from the moment it hits an Outlook inbox, through its automated recognition and validation phase, to its final state of readiness for your core business systems.

Phase 1: Environment Readiness

The Local Bridge: The Desktop Agent 3.0 must be installed and registered to the tenant. This acts as the execution engine, enabling the cloud-based SAP Build environment to interact directly with the local Outlook application and file system.

-To set up the agent, follow this: Install and Set Up Desktop Agent 3 | SAP Tutorials

Phase 2: Agent Configuration: Creation, Assignment, and Project Binding

Once the agent is installed, it must be assigned to an environment within the SAP Build Lobby to authorize automation execution.

Create the Environment: Navigate to Control Tower > Environments and select Create. Provide a name, Identifier and click Create.

Register the Agent: Open the newly created environment and select Agent Management > Add Agent.

Define Agent Attributes: Navigate to Control Tower > Agent Attributes and select Create. Provide a name and choose the Type:

Free: For dynamic parameterization of values.

Predefined: For assigning specific, fixed values.

Assign Attribute to Agent: Under Control Tower > Agents, locate your agent and ensure it is connected. Select Manage Attributes, choose your newly created attribute, enter the corresponding value, and confirm.

Bind Attribute to Project: In your project’s Process Builder, navigate to Settings > Attributes. Add the same attribute and value, then save. This creates the final link, ensuring the project triggers specifically on your configured agent.

Phase 3: Building the Automation Logic

Now that the technical "handshake" is configured, we can begin building the automation. This phase focuses on creating a reliable bridge between your email inbox and your local storage.

Initializing the Automation

Start by creating a new automation in the Process Builder. This will be the engine that handles your file and email operations. Ensure you have the Outlook SDK and File System SDK added as dependencies in your project settings.

The following is the flow for extracting info from invoices, which includes opening Outlook, searching for specific emails, saving attachments, and processing the data:

Phase 4:Preparing the Workspace: Local and Outlook Setup

For the automation to successfully process documents, you must establish a specific "landing zone" for your files. This requires the following manual configurations:

1.Local File System: Manually create a folder on your computer at the path C:/temp/attachments. This folder acts as the dedicated directory where the bot will download and store email attachments before they are uploaded to the cloud or processed by the extraction logic.

2.Outlook Folder Configuration: Inside your Outlook application, you must create a new folder specifically named Invoices.

Setup for Testing: To test the flow, move an email containing an invoice attachment into this Invoices folder.
The Unread Status: Ensure the email is marked as Unread. The automation is designed to search for unread items to prevent processing the same invoice multiple times.

Phase 5: Configuring BTP Destinations

Destinations are secure connection points that allow your automation to communicate with external services. This is a two-step process: first creating them in the BTP Cockpit and then configuring them within SAP Build.

Creation in SAP BTP Cockpit

In your BTP Subaccount, navigate to Connectivity > Destinations and create the following:

1.Service & Extraction Destination: Create a destination to handle both internal routing for the Process Automation engine and the connection to the Document Information Extraction (DOX) service.

2.SAP Document Store Destination: Create a mandatory destination for sap_process_automation_document_store. This allows the bot to move files from your local C:/temp/attachments folder into the secure SAP Document Management Service (DMS) for centralized cloud archiving.

Configuration under SAP Build

After creating them in BTP, you must explicitly link them to your project to establish the necessary communication channels:

Mapping: In your project settings, go to the Destinations tab. Map your BTP destinations to the corresponding project requirements. This step ensures that the automation knows exactly which BTP service to call for extraction and storage.

Phase 6: Deployment and Execution

With the logic built, folders prepared, and destinations mapped, the system is now a cohesive unit. The final step is to move the project from the design stage to active execution.

1.Releasing and Deploying

In the SAP Build Lobby, you must Release your project to create a version snapshot. Once released, navigate to the Deploy button. This sends the instructions to the cloud environment, where it waits for your local agent to "pick up" the task.

2.Monitoring

Once the automation completes, navigate to the Monitoring tab in SAP Build. Here, you can view the execution logs for your job.

grossAmount: The bot has correctly identified the total (e.g., $93.50).

filePath: The bot confirms where it stored the document locally (e.g., C:\temp\invoice-a (1).pdf).

recipient: It captures the specific email address the invoice was sent to.

3.The Final Flow in Action

The following is the automated flow created for extracting info from invoices:

Outlook Monitoring: The bot identifies an unread email in your manually created Invoices folder.

Local Storage: It downloads the attachment directly into C:/temp/attachments.

Data Extraction: Once the file is stored locally, the bot uses the extraction activity to communicate with the cloud. At this stage, we can successfully obtain the extracted info from the invoice.

Conclusion:

By linking Outlook to SAP Document Information Extraction through SAP Build, you transform the inbox from a storage bin into a high-speed data engine. This setup doesn't just save time—it eliminates manual errors and ensures your business systems receive accurate data instantly. It’s a simple yet powerful blueprint for turning administrative friction into a seamless, automated advantage.

Disclaimer:
All the views and opinions in this blog are my own and are made in my personal capacity. SAP shall not be responsible or liable for any of the contents published in this blog.