SAP Community - User Experience

Customize SAPUI5 apps for business users – make an impact by joining our CEI project

2026-03-01T19:15:53.813000+01:00

SAP Customer Engagement Initiatives (CEI) on https://influence.sap.com allow you, as an SAP customer or partner, to gain early insights into SAP's product developments and work directly with SAP teams to shape future product directions. This project presents a unique opportunity to work with SAPUI5 flexibility product managers and engineering teams, leveraging your expertise customizing SAPUI5 apps with key user adaptation.

Join the upcoming CEI project to make an impact on how key users interact with key user adaptation

If you’re already convinced – join here. If not, read on 🙂

What is key user adaptation?

Key user adaptation is a mode that allows extending SAPUI5 applications for other users right in the browser. It is highly intuitive and requires no technical or programming skills. Just use drag and drop to make UI changes – no modification or copy of SAP standard coding necessary! Read more here.

What is the targeted improvement?

Although the product is mature and widely used, we actively evolve it by delivering new functionality and capability enhancements alongside continuous user experience improvements, informed by UI testing and direct customer feedback.

We are in the process of overhauling key user adaptation’s UI, simplifying the overall approach while making often-used scenarios more streamlined. We’ve taken a close look at the version history (of activated adaptations) and how our users interact with it, extended the “embed third-party content” feature, widened the scope of custom fields that can be added to the UI – and more.

To ensure that we are on the right way, we need your help!

Who should participate?

Users who want to adapt standard SAPUI5 apps for business users. Both key users and technical users are welcome.

Why should you participate?

Gain understanding of SAPUI5 flexibility
Chance to influence a central SAPUI5 feature
Early access to prototypes

How can you participate?

Don’t miss out on this opportunity to share your feedback and engage with SAPUI5 flexibility development teams. Register by March 15, 2026, and make a true impact on how you can customize SAP apps to your needs!

Click here to sign up for our project. (A short overview about how to get started on influence.sap.com can be found here).

After you register for a project, you will be invited to an introductory call where you will get more information. This call is followed by individual or grouped feedback sessions.

Thank you in advance for helping us shape the future of SAPUI5 flexibility!

SAP Fiori for SAP S/4HANA Cloud：增强版 New User Experience Switch 全面解析

2026-03-03T07:45:30.472000+01:00

在 SAP S/4HANA Cloud Public Edition 中，SAP 持续推进用户体验（UX）的革新，其中 New User Experience Switch（新版用户体验切换功能） 是帮助企业顺利完成应用替换的重要机制。最新版本（2602）对该功能进行了进一步增强，让业务用户与管理员更容易适应新旧应用的切换进程。

本文将带你了解这个增强功能的核心设计、工作方式，以及企业在实际使用中可以获得的价值。

一、为什么需要 New User Experience Switch？

SAP S/4HANA Cloud Public Edition 每 6 个月发布一次新版本，其中会逐步引入新应用（phase-in），同时也可能逐步淘汰旧应用（phase-out）。通常，业务用户有 至少 12 个月 的窗口期来适应新的替代应用，但在实际项目中，这段时间可能转瞬即逝。

为避免用户错过迁移时机，SAP 引入 New User Experience Switch，通过界面提示与切换选项来“温和推动”用户尝试并过渡到新应用。

二、New User Experience Switch 的三种提示阶段

切换功能在应用生命周期的不同阶段会呈现不同的提示样式：

1. Information 信息阶段

告诉用户有新的应用版本正在被引入
展示新应用的优势
鼓励用户尝试
用户可以随时切回旧应用

这是“最温和”的阶段，旨在减少用户对改变的抵触情绪。

2. Warning 警告阶段

当旧应用已经被标记为 deprecated（即将淘汰） 时，切换功能会显示黄色的警告信息：

告知旧应用将在未来版本中不再提供
提醒用户尽快完成迁移

3. Alert 紧急阶段

这是旧应用被移除前的最后一个版本，切换功能会以更醒目的方式提示：

强调迁移的紧迫性
显示明确的移除时间点

在这个阶段，如果用户仍然停留在旧应用上，会面临无法继续使用的风险。

三、切换功能如何呈现？

SAP 在 2502 版本引入 New User Experience Switch，在 2508 与 2602 的版本中进一步增强：

旧应用启动时出现提示 popover（气泡提示）
Shell Bar（顶端工具栏）中出现 切换按钮
用户可在新旧应用之间自由切换（取决于阶段）

这些交互方式让用户无需离开当前体验即可了解版本状态并快速做出选择。

四、对业务用户意味着什么？

✔ 更轻松的学习曲线

不再需要由管理员单独告知新旧应用替代关系，系统会自动提示。

✔ 提前感知变化

避免新版本发布后突然发现旧应用“消失”，有效减少工作中断。

✔ 自主试用新应用

在 phase-in 阶段，用户可以自由在新旧体验中切换，加速熟悉度提升。

五、对管理员意味着什么？

管理员可以利用此功能：

提前规划应用替换节奏
知道哪些用户仍在使用旧应用
在企业层面推动统一迁移

这让应用治理更加可控，也能减少升级周期带来的沟通成本。

六、为什么说这个功能“让改变更容易”？

New User Experience Switch 正是帮助企业完成改变的机制：

让改变更加可见
让迁移更加自主
让用户更有掌控感

对于每一个正在推进数字化、云化的企业来说，这种设计都能有效降低内部阻力。

结语：更智慧、更温和的用户体验演进机制

New User Experience Switch 的增强不仅让用户更轻松地迈向 SAP Fiori 的现代化体验，也让管理员和企业能够更从容、可控地管理应用生命周期。

随着 SAP 持续对 UX 的改进（例如 2602 版本中的 AI 辅助、增强的 Launchpad、手机端优化等），未来企业的 SAP 使用体验将更加智能、一致、顺滑。

如果你正在规划 S/4HANA Cloud 的上云旅程或准备迎接新版本，这项功能值得你重点关注。

参考文档：SAP Fiori for SAP S/4HANA Cloud – New User Experie... - SAP Community

How Do I Activate a Situation Type in the Extended Framework?

2026-03-04T11:20:40.372000+01:00

Situation Handling notifies users about issues requiring their attention. You may choose SAP delivered situation templates or design your own use cases. For the extended framework for Situation Handling, we often discussed how you can create custom situation templates. The framework comes also with SAP delivered use cases that you can easily activate.

This blog post explains how you can activate situation types from SAP delivered situation templates with the extended framework for Situation Handling. It has been available since SAP S/4HANA Cloud 2202 and SAP S/4HANA 2021 FPS02.

SAP Delivered Use Cases

Looking for Situation Handling use cases? Visit SAP Help and navigate to Situation Handling, then choose Use Cases. You can narrow your results by filtering for Situation Template Type (either extended object-based or message-based), area, and topic. To learn more about a specific use case, simply check the link in the Situation Template column for a detailed description.

Use Case

For illustration purposes we use the situation template Expiration of Purchase Contracts (PROC_ABOUT_TO_EXPIRE_CTR). Purchasers get a heads-up for purchase contracts that are about to expire.

Activation Overview for 2SL and 3SL

Before discussing the activation steps in detail, let me point out the differences between system landscapes and their specific transport paths.

In the extended framework for Situation Handling, you create a situation type from a situation template. Situation templates are only visible in the quality system of a 2-system landscape (2SL) and the development system of a 3-system-landscape (3SL). The situation type needs to be transported to the production system. The transport paths differ between 2SL and 3SL.

Transport the Situation Type in 2SL

In a 2-system-landscape, you transport the situation type from the quality system to the production system.

In the quality system you
- Create a situation type from a situation template
- Test if the configuration alerts the right users about the situation
- Export the well-defined situation type

In the production system you
- Import the situation type
- Since the data usually differs between quality and production system you need to enter the appropriate values for the condition filters
- Enable the situation type

Transports in 2-System-Landscape

Transport the Situation Type in 3SL

In a 3-system-landscape, transports are required from the development system to both the test and production system. In a 3SL environment you may also have different tenants for development, customizing, and parallel customizing that need to be considered as well.

On the customizing tenant in the development system you
- Create a situation type from a situation template
- Export the situation type

On the test tenant in the test system you
- Import the situation type
- Since the data usually differs between systems you need to enter the appropriate values for the condition filters
- Test if the configuration alerts the right users about the situation
- Forward the well-defined situation type

On the production tenant in the production system you
- Import the forwarded situation type
- Enter the appropriate values for the condition filters
- Enable the situation type

Transports in 3-System-Landscape

Detailed Activation of a Situation Type in 3SL

Now let’s check the detailed steps for a sample use case in a 3-system-landscape as it is more comprehensive. In 2SL the export / import mechanism resembles the one from development system to test system in 3SL.

Depending on your system setting, the transports may also be processed automatically. For optimal clarity, the blog post discusses the transport steps through manual triggers.

Development System

Create a Situation Type from a Situation Template

Log-in as business process configuration expert on the customizing tenant in the development system. Open the Manage Situation Types – Extended app where you see a list of SAP delivered templates. Use the search option to find the template for our use case Expiration of Purchase Contracts (PROC_ABOUT_TO_EXPIRE_CTR). Select the template and an object page opens. In the header, select Create Situation Type.

Create situation type from situation template

A new page opens with the situation type that contains all information from the situation template. You just need to enter an ID, Name and Description. The type is configured and ready to use. Depending on your requirements you could adapt the settings, for example, by adding filter values for the conditions, changing texts or rescheduling the batch job.

I recommend monitoring the instances to see how situations are handled.

Monitor situations

Let’s check the relevant settings and understand how the configuration works.

There are two Situation Triggers that detect situations and cover different usage scenarios. While the batch-based trigger checks for situations in the background, the event-based trigger reacts on every active change of the contract.

Situation triggers

The situation triggers cover the following cases:

The Event-Based Trigger checks the conditions whenever you create or update a purchase contract.
- Condition 1 checks if the validity period of a purchase contract expires within the next 30 days and triggers a situation. The information displayed to the user is defined in Situation Display number 1.
- Condition 2 is only executed if condition 1 did not match. That is, the validity period is not within the next 30 days, for instance when the contract got extended, and the situation is closed. As nobody will be informed about the closure, the texts are empty (Situation Display number 2).

Event-based trigger

In addition to the events, the Batch-Based Trigger regularly checks the validity end date according to the batch schedule.
- Condition 1 checks if the validity period of a purchase contract expires within the next 30 days and triggers a situation.

Batch-based trigger

The configuration for the Batch Job Scheduling specifies that the contract dates are verified every 3 hours throughout the day, beginning at 6:00 a.m.

Batch job scheduling

Export the Situation Type

Log-in as administrator on the customizing tenant in the development system. Open the Export Software Collection app.

On top of the table choose Create Software Collection and a new page opens
Choose Add Items and select the situation type you created
On the header select Check and wait until the check is processed successfully
Then choose Export and wait until the export is finished successfully

Test System

Import the Situation Type

Log-in as administrator on the test tenant in the test system. Open the Import Collection app.

Choose your software collection and a new page opens
On the header select Manual Import and wait until the check is processed successfully
Then choose Import on the bottom and wait until the import is finished successfully

Test the Situation Type

As business process specialist you can test the situation type on the corresponding tenant.

Make sure that the situation type is enabled.

Activate the situation type

Then maintain the conditions. The filter values are not transported since they may differ in the various systems and tenants.

Select the Event-Based Trigger and a new page opens
- Condition 1 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
  - Validity Period End: enter Next30Days, using the value help
- Condition 2 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
- Go back to the main page

Event-based trigger

Select the Batch-Based Trigger and a new page opens
- Condition 1 select Edit and enter the filter values
  - Ext. Reference ID: enter Empty, using the value help
  - Validity Period End: enter Next30Days, using the value help
- Go back to the main page

Batch-based trigger

With the situation triggers, you defined when a situation is detected. Now, you need to define who should be informed about situations. Maintain the team(s) in the Manage Teams and Responsibilities app and ensure that at least one team is enabled. The filter settings work the same way as with the standard framework for Situation Handling.

Situation recipients

Now you can test the situation type in your business area with the corresponding application data. You can check if there are purchase contracts that match the conditions by choosing Trigger Batch and Manage Instances.

Test the type with trigger batch

If no situations were detected you can log-in as purchaser and create or manipulate a purchasing contract. Add an end date within the next 30 days and the save event will trigger a situation.

When you log-in as a team member of the recipients team you can also check, if you were alerted about the situation.

After the successful test you push the situation type to the production system.

Forward the Situation Type

Log-in as administrator and open the Import Collection app.

Select your software collection and a new page opens
On the header select Forward and wait until the validation is processed successfully
Then choose Forward on the bottom and wait until the export is finished successfully

Production System

Import Collection to Production System

As administrator open the Import Collection app on the production tenant in the production system.

Choose your software collection and a new page opens
On the header select Manual Import and wait until the check is processed successfully
Then choose Import on the bottom and wait until the import is finished successfully

Activate the Situation Type

Log-in as business process specialist and open the Manage Situation Types – Extended app. Like in the test system, you need to maintain the situation type.

Enable the situation type
Add the filter values for the trigger conditions
Ensure that at least one recipient team is enabled

Now you are all set.

Further Information

You find many more blog posts in the Best Practices section of Intelligent Situation Handling in the SAP Community. And you can visit SAP Help Portal for further guidance on Situation Handling.

SAP UX Q1/2026 Update – Part 7: SAP Analytics Cloud

2026-03-11T11:00:24.602000+01:00

SAP Analytics Cloud has invested a lot in User Experience, to make it smooth, intuitive and joyful. It supports SAP Business Suite consistency, with the Horizon theme and further updates for navigation, search and more, making it look better and be more intuitive. Users also benefit from the updated home page, AI-assistance, the new My Metrics for staying up-to-date, as well as updates to charts and tables. Story designers also benefit from numerous enhancements to help them produce better content. Finally, we have also made UX enhancements for administrators.

This series of blog posts covers innovations in user experience in our public cloud products from the last six months or so. In case you missed it, Part 1 provides general updates about Joule, SAP Work Zone and SAP Mobile Start, along with links to all the other parts.

I’ve grouped the main UX innovations in SAP Analytics Cloud into these sections:

Updated home page
Design updates for suite consistency
AI-assistance
Personalizing your experience
Chart and table enhancements
Helping designers produce better content
Enhancements for administrators
Further information

Updated Home Page

The home page is the first place that users go to when using SAP Analytics Cloud, and hence it is crucial that it provides the most important information, actions and navigation options. Based on thorough user research, we have now redesigned the page to deliver a more streamlined and user-centered experience. At the same time, the new design also supports our focus on providing a consistent user experience across all products within the SAP Business Suite, as described in the next section.

Figure 1 shows an example.

Figure 1: The redesigned home page in SAP Analytics Cloud. Alt Text: screenshot showing a welcome message “Hello, William Yu” at the top, above a page with 7 cards: one filling a quarter of the screen showing learning news, one showing “Just Ask”, one with four quick actions, and four vertical tiles showing lists of files and resources. The left side has a collapsed vertical navigation menu with icons.

Resizable Cards

You can now resize homepage cards vertically, horizontally, or both (depending on card type). For example, you could choose to make the “Learn about SAP Analytics Cloud" card shown in Figure 1 smaller, as depicted in Figure 2.

The ability to resize cards allows you to personalize the home page to suite your priorities and your way of working.

Figure 2: Resizable cards: Alt Text: On the left a wide card “Learn about SAP Analytics Cloud” is shown, with two columns each with text, image and action button, above a section with a link and a search field for documentation. On the right a card “Learn” half as wide, with a carousel for the columns, showing only one column, above the search field.

Cards for Custom Messages and Announcements

Administrators can create custom cards for providing information to all users, such as announcements on upgrades, maintenance windows, or for promoting key content, such as links to training, process updates or new company guidance. These cards can include images, text, tags, and links. Figure 3 shows an example:

Figure 3: Custom card for informing users. Alt Text: A card with an image above a title and two paragraphs of text, followed by two links to more information.

Design Updates for Usability and Suite Consistency

We have made design improvements which are relevant for a consistent user experience across the entire SAP Business Suite, and which are now also available with SAP Analytics Cloud. As I mentioned in my April 2025 blog post Upcoming Design Updates for the SAP Business Suite (SAP Fiori for Web), consistency of the user experience across the various applications used by a user is an important part of overall usability, helping users to feel confident and at ease when using a suite of products – no unexpected surprises.

In this section, we’ll look at these updates:

Horizon theme.
Further usability improvements (shell bar, navigation menu, user menu, settings, search, illustrations).

Horizon Theme

The visual theme defines the “look” of a product, so I’m glad to say that SAP Analytics Cloud now also provides the Horizon Theme, as shown above in Figure 1. Administrators can switch it on; soon, it will become the default theme. Not only is Morning Horizon available: you will have access to Morning Horizon and Evening Horizon (the light and dark themes) as well as to the high contrast white and black themes that are available for accessibility.

Users can choose which theme they want to use via the new settings UI, as shown in Figure 4 below.

Further Usability Improvements

Shell bar: Figure 1 above already features the new shell bar at the top of the screen, with the product name to the right of the SAP logo.

Navigation: The redesigned navigation bar can be seen on the left side, showing a vertical list of icons representing menu entries for content and tools. Users can hover over each icon to see the name of the module or expand the menu to see all the names shown next to the icons.

User menu (user profile): Figure 4 shows the redesigned user menu. This design is consistent across the SAP Business Suite, with Settings as the first entry, and Sign-Out clearly separated from the other entries.

Unified Settings for Home Page and User Profile: The Homepage settings and User Profile settings are now consolidated and unified in one intuitive interface, which follows the design for consistency across the suite. No need to go to different menus to adjust your personal preferences and homepage layout anymore. Selecting Settings in the user menu brings you to the redesigned settings pop-over. Figure 4 above shows the settings for Appearance, where the user can select the visual theme they would like to use, and Figure 5 below shows the settings for the home screen.

Figure 5: Home Screen settings in the new consolidated settings UI. Alt Text: Screenshot showing the Settings pop-over, with Home Screen selected in the list on the left, and selectors on the right for cards and tools to display on your home screen.

Search: Search now features auto-complete, making it noticeably more convenient and user-friendly. As you begin typing, relevant suggestions appear instantly, streamlining the process of finding models, stories, and files. This enhancement helps you locate what you need more efficiently, even if you can’t recall exact names, ensuring a smoother search experience.

Illustrations: SAP Analytics Cloud has also adopted the new style of illustrations that has been introduced for the whole SAP Business Suite. They are modern, friendly, and visually appealing.

Find out more in this blog post:

Introducing Horizon Themes and Usability Enhancements in SAP Analytics Cloud.

AI-Assistance

AI can significantly enhance the user experience. In Q3/2025 we introduced these innovations where AI is embedded in the application.

AI-Assisted Commenting

If a table has a lot of comments, especially if some of them are quite lengthy, it can take effort to summarize them all succinctly. Now, with AI-assisted commenting, this is easy. It helps you compile highlights, summarizing data point comment threads, and aggregating data point comments from descendant cells. It will also translate this into your language (specified in your profile). When writing a new comment, you can use AI to help you to rephrase comments. Figure 6 below shows an example of what it looks like in Stories.

Figure 6: AI-assisted commenting, embedded in Stories. Alt Text: Screen snippet showing a report with some visible comments and a pop-over menu with the AI-entry “Summarize Comments of Descendants (English)” selected.

AI-Assisted Chart Summary

Planners and analysts often need to present to and share their findings with managers and colleagues. Summarizing charts in an easy-to-understand way is time consuming – but now much less so, thanks to AI-assisted chart summary. Generate concise, human-readable summaries of SAP Analytics Cloud charts embedded in your PowerPoint presentations at a finger tip, helping you to prepare key take aways faster and communicate more clearly. Figure 7 below shows an example, of an embedded SAP Analytics Cloud data visualization along with an AI powered summary in PowerPoint.

Figure 7: AI-assisted chart summary. Alt Text: Screenshot showing a PowerPoint screen with a chart and generated summary of it on the current slide. On the right side is the SAP Analytics Cloud panel with a preview of the chart and a button to Generate Summary.

Find out more about these, as well as AI-assisted advanced formula generation, in this blog post:

Sneak Peek in to SAP Analytics Cloud release for Q3 2025.

Personalizing your experience

For business users consuming stories and dashboards in SAP Analytics Cloud, being able to adapt the experience to suit your way of working and provide the information you need, in the way you need it, is crucial for a good user experience. I already covered some personalization above: the resizable cards in the home page, your choice of visual theme, and the other settings you can make via the user menu. However, we have introduced even more powerful personalization:

My Metrics, your personalized, curated collection of metrics that matter most to you and your business.
Personalizing data visualization: change the way data is visualized using the new Quick Builder and save the visualization for when you return.

My Metrics

With My Metrics you can choose those metrics that matter most to you and put them together on one screen. These can come from multiple stories. In other words, rather than having to navigate to different stories to get the overview that you want, you can get a personalized overview with My Metrics. You can arrange all your metrics into categorized lists, making it easy to spot trends and understand your data at a glance.

The My Metrics Module

My Metrics was introduced as a new module within SAP Analytics Cloud, you can access it via the left panel from the new Side Menu. My Metrics is broken down into three simple areas:

Your Metrics: A collection of all performance cards you have created or that have been shared with you.
Detailed Visualization: When you select a metric, a chart instantly visualizes its data. The type of chart can be set during the creation of the metric. You can also see exactly which filters are currently applied.
Smart Insights: Go beyond the chart with an automated analysis that reveals hidden patterns and important observations in your data.

Figure 8 shows an example:

On the left, the user has selected the “Gross Margin” metric from their list of metrics.
In the middle, the gross margin is visualized with a horizontal bar chart.
On the right, the smart insights explain what the top contributors to the gross margin are, showing the top location contributor and the top product contributor, with a chart showing the gross margin per product.

Figure 8: My Metrics, showing the three areas described in the main text. Alt Text: Screenshot showing the three columns described in the text, each highlighted in a different color and numbered 1 to 3 from left to right.

Find out more about My Metrics in this blog post:

Introducing My Metrics: Your Personalized view of Metrics in SAP Analytics Cloud.

My Metrics Card on Home Page

Now that you can create your own personalized list of metrics, wouldn’t it be great if you could make them available in a card on the home page? The good news is that now you can!

Figure 9 below shows an example, where we have highlighted the My Metrics card with an additional blue border. Clicking on one of the metrics takes you directly to that metric in the My Metrics module: if you for example selected “Gross Margin”, it would take you to the screen shown in Figure 8 above.

Figure 9: The My Metrics card on the home page. Alt Text: Screenshot of the home page with three columns of cards, the rightmost card “My Sales Metrics (9/25)” spanning over the full vertical height and showing five metrics cards.

My Metrics for KPI Monitoring: Alerting

If you want to be alerted when particularly important metrics change, you can do that too: you can subscribe to metrics reports, and set the report frequency (day, week, month). You can also choose to receive reports by e-mail, or through the notification center.

Figure 10: Subscribing to a metrics report. Alt Text: Screenshot of “My Metrics” with a pop-over “Subscribe to Metrics Report” showing a guided procedure with step 1 “General Information” shown, with fields name and description; 2 “Schedule”; and 3 “Distribution List”. “Next” and “Cancel” buttons at the bottom right.

My Metrics also supports collaboration with colleagues: you can share with other users or teams and also use those that they share with you.

To sum up: you get a great user experience with my metrics, since you can personalize the experience to meet your needs: keep an eye on all the metrics that you are interested in, have them front and center on the home page, and ensure that you are notified about changes in ones that you want to track closely.

Personalizing Data Visualization

For you as a consumer of a story, if the way the data is visualized does not suit you perfectly, you can now personalize it yourself – no need to go to the folks who created the stories or dashboards, at least for common cases. The video in Figure 11 shows an example where the user wanted a different representation of the data on career levels shown in the table: with the new Quick Builder, she removed the Headcount column and added the Education Degree dimension, resulting in new rows showing the education degree for each career level.

Figure 11: Using Quick Builder to personalize data visualization. Alt Text: Animated GIF showing two charts above a table “Headcount Analysis”, and then how the user opens the Builder panel and makes the changes to the table described in the text.

Chart and Table Enhancements

We have invested a lot in enhancing charts and tables, providing improvement out of the box for all viewers, as well as giving those who build stories and dashboards more options to get an optimal representation. Beyond that, we have also introduced two new charts: an Area Chart and a Pareto Chart.

Table enhancements

By popular demand from customers, we have introduced a number of improvements to the user experience of tables, providing consistency with chart widgets. The enhancements include undo/redo options, mobile compatibility, expanded tooltip settings, improved data synchronization, and a new intuitive builder panel designed for customizing layouts, assigning dimensions, adding calculations, and filtering data.

Find out more in this blog post:

Sneak Peek in to SAP Analytics Cloud release for Q3 2025.

Chart enhancements

An enhancement available to all viewers is the new design for the Numeric Point Chart, providing more modern dashboard aesthetics and improving readability. With the fresh look, we ensure key figures stand out more prominently, making it easier for users to quickly grasp performance metrics, as shown in Figure 12.

We have also introduced a number of options for your designers to help viewers better understand the data, as shown in Figure 13 below:

You can add titles to axes, so that it is clearer what data is being represented on each axis.
You can add grid lines to a chart, to make it easier to interpret datapoints at a glance, or if their labels are hidden due to collision.
You can choose how thick you want to make the axis line (the figure shows the “thick” option).
You can choose the color and thickness of the category divider line (the figure shows the “thin” option).

Figure 13: New options for designers to optimize chart visualization. Alt Text: The left shows an example previous line chart, the right shows two versions of the new line chart, with different text orientation of the y-axis title (marked as “1”), and indicators pointing to 2 – 4 as described in the text.

Have a look at these in more detail, as well as some enhancements delivered earlier, in this blog post:

Chart Enhancements in SAP Analytics Cloud.

Most recently, we have enhanced the stacked area chart, so that designers can choose a 100% stacked area chart whenever they want to visualize the proportional contribution over time. Figure 14 shows an example, where the proportional contribution barely changes over time.

Figure 14: 100% stacked area chart. Alt Text: An image showing sales for each quarter in 2024, 2025 and 2026, with date on the x-axis, for other (17.6 – 18.0%), food (73.0% - 73.3%) and drink.

Find out more about the 100% stacked area chart here, as well as the new charts covered in the next section:

Expanding Visual Analysis: New Area Chart, Pareto Chart, and Stacked Area Enhancements.

New Charts

The new Pareto chart and Area chart help to explain trends, highlight drivers, and support prioritization.

New Pareto Chart

The Pareto Chart is designed to help Story Designers to prioritize focus, explain trade-offs, and guide action instead of treating all contributors as equally important. The chart gets its name from the Pareto principle, which states that often roughly 80% of the outcome comes from 20% of the causes – the “80/20 rule”.

It is very easy for story designers to use: We automatically calculate the Pareto visualization for you based on selected primary measure or account and the dimension. The chart is sorted from highest to lowest, including cumulative percentage which increases to 100%.

Figure 15 shows an example of building a Pareto chart, where the builder has chosen the Account “Days Order to Shipment” and the Dimension “Reasons for Delay”.

Figure 15: Example of the new Pareto Chart, as seen by a story builder. Alt Text: Screenshot showing Builder panel on the left, and an example Pareto Chart on the right.

New Area Chart

The new Area Chart introduces a powerful option for visualizing trends over time while maintaining focus on the overall shape and direction of the data. Compared to Stacked Area Charts, Area Charts emphasize trend and magnitude rather than composition, reduce visual complexity when multiple series are present, and make it easier to follow a single measure’s evolution across time.

Figure 16: Example of the new Area Chart. Alt Text: Image of an area chart for sales in m USD for drink (22.03 – 36.02), food (41.46 – 71.83) and other, with the total 171.99 to 296.11.

Helping Designers Produce Better Content

So far, we've focused on UX enhancements elevating overall dashboard and Story consumption. Now, let's also explore how we're enhancing the building experience for our Story designers, making it more intuitive and user-friendly to build dashboards your end-users will enjoy using, with:

Design guidelines for designing stories.
Built-in performance and usability guardrails.
Drag and drop for building data visualizations.
Story versioning.
New table building experience.

Design Guidelines for Designing Stories

The first step to creating good content is to understand when to use what. Also, if everybody who creates stories and dashboards follows the same guidelines, the overall result will give your users a consistent experience. That is why we have introduced the Dashboard Design Guidelines for SAP Analytics Cloud. Figure 17 shows the overview page, and the page for Insights Formula.

Our aim to assist you in designing dashboards that effectively satisfy the structural, visual, and content-related needs of your end users. Most of the content is tool-agnostic and broadly applicable to the creation of analytical material.

Figure 17: The Dashboard Design Guidelines for SAP Analytics Cloud. Alt Text: Two screenshots, on the left the start page with introduction and six cards for further details, on the right “The Insights Formula” start page for one of the six detail topics. Both images show a navigation menu on the left with links to the Overview and the six topics.

If you are interested in recommendations for dashboard design, have a look at this blog post series:

Dashboard Design Best-Practices.

Built-In Performance and Usability Guardrails

Beyond the above guidelines, we have introduced built-in guidance and support for story designers.

Performance Recommendations for Story Designers

The info panel now provides crucial insights into the widgets that influence content performance during the design phase. This enhancement builds upon our existing widget in-app analysis, allowing you to proactively identify areas for improvement and close performance gaps, helping your stories to be both engaging and effective. Read more about it:

Performance Recommendations for Story Designers (2025 QRC3)

Consolidated Error Messages in Story Designer

In the past, issues and recommendations were displayed in variuos places, such as individual toast messages or small icons on a widget, whereas performance recommendations were distributed across separate pop-ups or tooltips. This resulted in a fragmented overview, making it easy to miss something.

The new Info Panel consolidates all relevant messages in one location, with three tabs for issues, performance recommendations, and scripting errors. Find out more here:

Consolidated Error Messages in SAC Story Designer (2026 QRC1)

Drag and Drop for Building Data Visualizations

Building data visualizations in a story is now easier, since you can use to drag and drop, as shown in the short video in Figure 18. We have also introduced a stand-alone data panel and hit zones on the chart widgets (not visualized in Figure 18).

Figure 18: Drag and drop for building data visualizations in stories. Alt Text: An animated GIF showing the data visualizaton area for the story on the left and the data panel on the right, and the user dragging a measure and then a measure and a dimension from the list on the right to place it on the left, creating a KPI and a chart respectively.

Story Versioning

Designing good stories in SAP Analytics Cloud typically involves a number of iterations, where story designers try out different layouts and narratives, adjust calculations and incorporate feedback from their stakeholders.

If you are doing this kind of iterative work, you’ll often want to go back a step or two and branch out in a different direction. This is where versioning is very helpful – and is now available with the latest release!

Instead of manually creating copies, or painstakingly documenting each change, we have introduced Story Versioning. This is simple by default, offering up to 10 versions per story. Each of these are created when you explicitly request a new version, to which you can add a note to describe it. Any previous version can be opened read-only, and saved as a new story or restored to become the current version. Have a look at Figure 19 to see how the versions are displayed on the right.

Figure 19: Story Versioning. Alt Text: A screenshot of a story, with a “File Versions” panel on the right, showing a vertical timeline with a call-out “Current Version” with a link “Open” above the call-out “Version 1” with links “Restore” and “Delete”.

Find out more in this comprehensive overview:

Story Versioning in SAP Analytics Cloud: Design with Confidence & Iterate Without Fear!

New Table Building Experience

The 2025 Q3 release introduced a new Table Builder Panel, bringing the table design process closer to that of charts and geo visualizations. As mentioned above, consistency across applications and products makes it easier for users, since they can use the same work patterns rather than learning different ones. Figure 20 shows the previous UI on the left, and the new one on the right. The main enhancements for the panel are:

Available Object Panel, showing list of available objects
Flexible Totals and Parent Node Positioning
Improved Drop-Down List for Object Selection
New Member Selector
Table Add-Ons
Single Source for Table Styling

Figure 20: New table building experience. Alt Text: Two screen snippets, on the left the previous table builder showing one column, on the right the new experience, with two columns, one for the available objects (new), the other for the builder panel, with four additional features labelled.

We have also introduced a number of enhancements to improve the creation and customization of tabular visualizations, such as:

Ranking & Sorting Improvements (includes Custom Order)
Report to Report Interface Enhancements
Blended Table Improvements
Flexibility with the Version Dimension
Show / Hide Threshold Tooltip Details
Hierarchal and Multi-Selection Primary Structure Input Control
New Client Calculations Panel
Enable Excel Add-in

Read about all of these enhancements to the table building experience in these comprehensive blog posts and documentation:

Enhancements for Administrators

We have introduced two new cards for the home page for administrators, making it easier for you to keep an eye on what’s important:

Administrative actions card.
System monitor card.

Administrative Actions Card

This card proactively pushes information about things that need your attention, providing recommended actions. This saves you time, since you don’t have to go looking, and reduces the time spent on root-cause analysis. Figure 21 shows an example.

Figure 21: Administrative actions card. Alt Text: Image of card with three lines, each with a warning icon, a title and a summary, such as “Classic Stories” – “Conversion needed”, and a link on the right.

System Monitor Card

This card gives you a concise summary of system health, showing key system metrics, user licence health, performance hotspots and governance-related recommendations. As a result, you can spot issues and identify trens quickly, again saving time and making it easier to get your work done. Figure 22 shows an example.

Figure 22: System monitor card. Alt Text: Image of a card showing a carousel of three, with Licensing Information currently displayed: used and unused licences, activated users, and a table “Housekeeping Details” with columns License Type, No Log-On, Inactive, Assigned, Limit.

Find out more about these two cards, as well as the new custom card for informing users that I mentioned at the beginning of this post:

What's New on SAP Analytics Cloud Home Screen 2026 Q1 QRC: New Admin Cards.

Further information

To get an overview of all the innovations and enhancements in SAP Analytics Cloud, have a look at these blog posts, video and what’s new documentation:

Top 5 Features in Q3 2025.
Top 5 Features in Q4 2025.
Top 5 Features in Q1 2026.
Documentation: What’s New – 2026 Releases.
Video: SAP Analytics Cloud: Top 5 New Features – Q1 2026 Release Highlights (8:38 minutes).

Another good place to stay up to date is the SAP Analytics Cloud page on SAP Community.

Continue Reading

I hope you enjoyed this seventh part, covering SAP Analytics Cloud. Here's a link to part eight in a few days, covering latest UX innovations for Customer Experience:

SAP UX Q1/2026 Update – Part 8: SAP Customer Experience: Mobile Daily Catch-Up for Sales.

Part 1 of the series lists all the parts, and links to those parts that have already been published:

SAP UX Q1/2026 Update – Part 1: AI, Joule, SAP Build Work Zone, SAP Mobile Start.

Do keep posting your experiences and recommendations yourself in the SAP Community, with the SAP Fiori and/or the User Experience tag! In case you are wondering how to get a list of the most recent blog posts on SAP Fiori and User Experience in our new SAP Community, use these links:

SAP UX Q1/2026 Update – Part 8: SAP Customer Experience: Mobile Daily Catch-Up for Sales

2026-03-16T09:38:10.393000+01:00

The new Daily Catch-Up within the SAP Sales Cloud mobile app is a real game changer for sales reps, since it directly helps you sell more, by helping you prioritize your day, with a three-step flow highlighting upcoming activities, missed items from the day before, and high-priority deals and leads that otherwise would fall through the cracks. Not only that: it is delightful to use, with nice animations and haptics.

Revolutionizing the Sales Experience with Daily Catch-Up

Daily Catch-Up is a major user experience innovation designed specifically for mobile sales reps, and is another example of how we are making work form enjoyable, helping users achieve better outcomes with AI.

We’ve learnt from extensive user research and conversations with customers that sales reps often struggle to prioritize their day due to "scattered signals" that surface throughout the day across emails, chats, and various notification channels. The Daily Catch-Up addresses this "notification overload" by unifying these signals into one predictable, guided experience.

Figure 1 gives a first impression: the first two examples show how you can access the catch-up: via a notification, or from the daily summary card on the SAP Sales Cloud apps’s start page. The third example shows the catch-up screen.

Figure 1: Notification and Daily Summary on home screen lead you to your daily catch-up. Alt Text: Three images of mobile phones, as described in the text. The third example shows a card “Visit Kixo Plant” with date and time, and a “Why Prioritized?” section, statint it is starting in 2 hours, with a “Reschedule” and “AI Summary” button and “Mark as Complete”.

Enjoyable: Intuitive and Tactile Design

The new Daily Catch-Up reimagines the interaction model for mobile CRM by moving away from traditional, cluttered lists to a modern, card-based layout.

Reduced Cognitive Load: By showing only one card at a time, we keep your attention focused on what matters most without the distraction of competing items. Each card has a clear front and back. A simple tap reveals additional details only when the user needs them, keeping the primary view clean and focussed.
Tactile Design: Swiping through cards feels natural, quick, and thumb-friendly, with almost no learning curve. You can use directional swipes to instantly mark tasks as complete or save them for later, without extra taps or navigation.
Delightful Experience: Smooth animations and subtle haptics add a touch of delight and give the flow a light, game-like quality. The overall experience feels faster, more intuitive, and more enjoyable on a small mobile screen – as you can see in the animation in Figure 2 below.

Figure 2: Examples of the animations for flipping the card, and for swiping to the next one within a step. Alt Text: Video of a mobile phone, showing how the card rotates around a vertical axis when tapped on, and how you can swipe it upwards towards top right.

Better Outcomes: Heuristic Prioritization and “Top 5 Focus”

We are helping Sales Reps move beyond simple chronological tracking to achieve better business outcomes through smart prioritization.

Heuristic Scoring: This new version of Catch-Up uses a scoring system that combines machine learning inputs and local context to calculate a priority score. This ensures Reps see what is most urgent and impactful first.
The "Top 5 Focus": Each morning, the system surfaces a "Top 5 Focus" list of prioritized items across opportunities, leads, quotes, orders, accounts or cases that require immediate attention. Ranking follows the same principles of business impact and urgency. Each card includes a short, two-line guidance summary to provide instant clarity.

One Consolidated, Guided Flow

Catch-Up brings everything together, providing a single, predictable way for users to start their day. There are two ways for you to get started: from contextual notifications, or from the app’s homepage, as shown in Figure 3 below:

Figure 3: Contextual notifications and the Daily Summary card on the home page lead you to Daily Catch-Up. Alt Text: Two images of mobile phone. On the left, schematically three notifications are shown on the start screen: “Start Your Day, Focussed”; “You’re at San Francisco International Airport – Do you want to review today’s schedule or follow-ups while you wait?”; “You’re near multiple accounts/leads but don’t have a visit scheduled – Do you want to create a visit?”. On the right the start page, with a Daily Summary card for catch-up, stating “Nice work! You’ve kepe up your Catch-up streak for 3 days straight!”.

Catch-Up has a Three-Step Guided Flow:

Upcoming activities: Highlighting what’s next on the calendar.
Missed items: Covering anything that was overlooked the previous day.
“Top 5 focus”: the high priority items, ranked as described above, that often fall through the cracks because they do not appear in the upcoming activity list.

Figure 4 below shows an animation of how users can move from step 2 to step 3 in the guided flow. You see that on the last card in step 2 you have action buttons to set the status or log a call. Once you swipe it away, you see an example of our new illustration design, with a message saying that CRM is now up-to-date. Clicking on Next Step brings you to step 3, with a prioritized deal. Each card has a “Why Prioritized?” section, explaining why the system has chosen to prioritize this item.

Figure 4: Moving from Step 2 to Step 3. Alt Text: Video of a mobile phone, showing the user swiping up the last card in step 2, getting a message that “Your CRM is now up-to-date – move to next step”, clicking on “Next step” brings up a message “Terry, here are the top 5 things for you to focus on today”, showing a card with the first one.

With Daily Catch-Up, the SAP Sales Cloud mobile app becomes a tool that really helps you sell more, rather than feeling like a tracking tool that your company wants you to use. It becomes a "habit builder" that helps you hit your quotas and stay focused on your real day-to-day goals.

Find out more in the documentation:

Mobile: Daily Catch-Up.

Get the SAP Sales Cloud mobile app in one of the app stores:

Continue Reading

I hope you enjoyed this eigth part, covering SAP Customer Experience – SAP Sales Cloud. Here's a link to the final part nine, covering latest UX innovations for UI technologies:

SAP User Experience Q1/2026 Update – Part 9: UI Design and Technology for Web and Mobile.

Part 1 of the series lists all the parts, and links to those parts that have already been published:

SAP UX Q1/2026 Update – Part 1: AI, Joule, SAP Build Work Zone, SAP Mobile Start.

SAP User Experience Q1/2026 Update – Part 9: UI Design and Technology for Web and Mobile

2026-03-23T09:53:54.363000+01:00

This ninth and last post in my series gives an overview innovations in our UI tools and technologies, making it ever easier to design, build and integrate UIs, for both web and mobile applications. For designing apps, web and mobile, we have added AI content and more to the SAP Design System portal and UI Kits in Figma. For web developers, we have introduced the SAP Fiori development portal, as well as more AI support via MCP servers for SAPUI5 and for SAP Fiori elements, and Joule integration. Beyond that: have a look at how you can use AI to migrate to TypeScript, learn about the new Geomap control, and benefit from the new SAPUI5 runtime repository. Finally, discover the latest updates for mobile design and development with our SDKs and the mobile development kit.

Joule can also be seen as a technology for delivering a great user experience. To find out about recent innovations there, as well as for central entry points and services, have a look at this post, which also contains links to all the other parts of the series:

SAP UX Q3/2025 Update – Part 1: AI, Joule, SAP Build Work Zone, SAP Mobile Start.

In case you missed them, do have a look at my previous posts covering design and technology news, since what I mention here builds partly on what came before:

SAP User Experience Q1/2025 Update – Part 7: UI Design and Technology for Web and Mobile. This post has a lot of information about extensibility, especially for SAP S/4HANA Cloud Public Edition. Do also have a look at the new SAP Extensibility Explorer.
SAP UX Q3/2025 Update – Part 7: UI Design and Technology for Web and Mobile.

First, we’ll have a look at news for creating web UIs, before looking at what’s new for mobile design and development.

News for Creating Web UIs

I’ve compiled the news into these sections:

SAP Design System Portal and UI Kits – now with AI UI Elements.
SAP Fiori Development Portal.
Using AI to Develop UIs – MCP Servers, Joule.
SAP Fiori Tools News.

SAP Design System Portal and UI Kits – now with AI UI Elements

We recently introduced the new SAP Design System portal that brings together the product design guidelines SAP Fiori for web, SAP Fiori for iOS, and SAP Fiori for Android, as well as to the new digital design system guidelines. With its enhanced usability, simplified versioning and improved performance, designers (and developers!) get a better user experience compared with the previous SAP Fiori design guidelines.

End of last year we introduced these AI UI elements for web UIs, as you can see in Figure 1 below:

AI Acknowledgement.
AI Button.
AI Writing Assistant.

Figure 1: AI UI elements available in SAP Design System portal. Alt Text: Screenshot of the portal UI Elements page with a filter at the top containing “AI”, below that “3 results” showing three cards in a horizontal row for “AI Acknowledgement”, “AI Button” and “AI Writing Assistant”.

Get a complete overview of what’s new in the design system portal here

What’s New in the SAP Design System Portal?

UI Kits v8.0 and v9.0 – now with AI components

The new UI Kits available for designers in Figma make it easy for designers to design accessible UIs at enterprise scale, for web applications, mobile iOS and Android applications as well as wearables. The UI Kits provide reusable components for web and mobile, along with web floorplans, which give you what you need out-of-the-box.

In the meantime, we have released SAP Web UI Kit v8.0 which includes a full set of AI components: AI Button, AI Menu Button, AI Split Menu Button, AI Input, and AI Text Area.

The latest release, SAP Web UI Kit v9.0, continues to evolve the system with focused improvements that enhance visual quality, usability, and overall consistency across the kit. It brings:

Updated Icons:
All icons have been refreshed with a 1.5px stroke (down from 1.6px). This improves anti-aliasing and results in cleaner, sharper visuals across interfaces.
Busy Indicator Enhancements:
You now have two Busy Indicator options, static and animated, available on the same page. The new animated version is ready to use out of the box, saving time and implementation effort.
Redesigned Color Palette. Note that the previous color palette component has been removed in order to avoid confusion, and keep the kit cleaner and easier to navigate.

Find out more here:

New SAP Design System Portal for SAP Fiori Design Guidelines, and New UI Kits for Designers.

SAP Fiori Development Portal

I’m also happy to inform you about the new SAP Fiori development portal. It is designed to help developers maximize the benefits of SAP Fiori elements for OData V4, which is more than just a UI framework: it’s a metadata-driven approach that leverages the SAP Design System as its guiding principle, incorporating the most relevant design system options for typical business tasks.

Figure 2: The SAP Fiori development portal. Alt text: A screenshot showing the Introduction page. On the left a menu has entries Using the Portal, Building Blocks, Global Patterns, Floorplans, SAP Fiori Tools. The Introduction page has a full width card “Building Blocks” at the top, with a description and tiles representing various building blocks. Below that “Choose Your Option” heading above two side-by-side cards for “Floorplans” and “Customer Layout”, each with an image and description, and a “Learn More” button.

The SAP Fiori development portal puts building blocks front and center. These building blocks - such as tables, forms, filter bars, and charts - are orchestrated by SAP Fiori elements and form the basis of every OData V4 application. They provide standardized layouts and interaction patterns, ensuring UI consistency and boosting developer productivity. The great advantage of using building blocks is that you can use them to create a customer layout and yet still benefit from the advantages of the metadata driven approach: low code, built in enterprise-grade capabilities such as multi-language support, accessibility, security and performance, and design system consistency.

Find out more in this six-part series of blog posts, here is the first one, which contains links to the others:

Introducing the SAP Fiori Development Portal: Your Gateway to Rapid SAP Fiori App Creation (1 of 6).

We have also restructured our documentation for SAP Fiori elements, with separate entry points for OData V4 and OData V2, and better supporting the building block approach. Read more here:

SAP Fiori Elements: New Documentation Structure.

Using AI to Develop UIs – MCP Servers, Joule

The above posts from Q1/2025 and Q3/2025 introduced a number of powerful ways to accelerate UI development by using AI, such as:

Creating SAP Fiori elements apps from a sketch (in the Q1 post), now integrated in SAP Build Code and Joule (Q3 post)
Joule for SAPUI5 freestyle development (Q1 post)
AI-assisted auto-fix of coding errors with UI5 linter (Q3 post)

Recently, we have gone even further and introduced MCP servers for freestyle SAPUI5 development as well as for developing with SAP Fiori elements and the associated building blocks. These open-source Model Context Protocol (MCP) servers provide AI agents with comprehensive UI5 and SAP Fiori elements knowledge, including best practices and project-aware context information, and thus provide developers with valuable support. Figure 3 shows examples.

Figure 3: Examples of the UI5 MCP Server (on the left) and the MCP Server for SAP Fiori (on the right) in action. Alt Text: both images show screenshots of a CLINE console view with a task entered as text at the top, followed by a list of steps which the system proposes to do to solve the task.

Read about these new MCP servers in these blog posts:

Alternatively, you can listen to these podcasts involving Tim Back and Florian Vogt, talking about the intricacies of the Model Context Protocol (MCP) within the SAP ecosystem:

Spotify: UI5 & MCP - Navigating the Model Context Protocol in SAP.
Apple Podcast: UI5 & MCP - Navigating the Model Context Protocol in SAP.

Latest UI5 MCP Server Enhancements

The UI5 MCP server got extended to help migrate existing JavaScript code to TypeScript, as well as for generating UI Integration Cards.

New TypeScript Migration Feature

With the newest feature of the UI5 MCP server, UI5-specific TypeScript conversion assistance is now available to AI coding agents, making the task much easier. Find out more in this blog post:

UI5 MCP Server's New TypeScript Migration Feature - Real-World Experience and Best Practices

Generating UI Integration Cards

The UI5 MCP Server now supports the development of UI Integration Cards. In its latest version – v0.2.1 – it includes three new tools dedicated to UI Integration Cards:

Best practice guidance for your agent.
Scaffolding a new Integration Card.
Validating the Card’s manifest.

These tools assist Large Language Models (LLMs) in creating new cards from scratch or editing existing ones, following the best practices for card development. Find out more here:

UI5 MCP Server Got Extended for UI Integration Cards Generation.

AI News for SAP Fiori Tools and MCP Server for SAP Fiori

The Project Accelerator can now be launched directly from the SAP Fiori generator, streamlining the initial project creation flow. The previously required staging step has been removed, allowing new projects to be created directly in the selected workspace folder. For projects created using the Project Accelerator, the Application Modeler now offers advanced editing capabilities, such as creating new fields and properties end-to-end, updating the data model, exposing the service, and consuming the changes in the UI in one coherent flow.

AI support has also been extended to mock data generation. Developers can generate realistic mock data using AI directly in the Application Modeler, and this capability is available for all applications whenever the Project Accelerator is enabled.

In parallel, the MCP server for SAP Fiori continues to expand. The server now exposes @sap-ux/create commands as CLI functionality, enabling reliable execution in MCP-supported workflows. App generation has been extended to support CAP Java projects, and a new “search_docs” tool allows the LLM (Large Language Model) to query SAP Fiori elements documentation, annotations, SAP Fiori tools documentation, and SAP Fiori Development Portal resources to quickly find relevant guidance and code snippets.

Joule Enhancement: Create Freestyle SAPUI5 Apps in SAP Build Code

You can now use Joule in SAP Build Code to create new freestyle SAPUI5 apps according to your requirements. The feature is not absolutely groundbreaking, as there are other tools doing a similar job like the Easy-UI5 templates and the recently published UI5 MCP Server. But:

It brings the functionality right to the fingertips of developers using SAP Build Code – no other tools needed.
It extends the template capabilities beyond what the Easy-UI5 templates provide.
Implementing it within the Build Code Joule environment yielded interesting insights and further improvements.

Find out more about the feature, and in the second “making of” post, read about how Andreas Kunz went about building it, and what he learnt from doing it:

SAP Fiori Tools News

In addition to the AI-enhancements mentioned above, we now provide expanded support for SAP Fiori elements building blocks, a new connection manager for SAP Systems in VS Code, and a feature to preview SAP Fiori web apps on mobile devices.

Expanded Support for SAP Fiori Elements Building Blocks

The following enhancements make it easier to adapt applications and allow developers to work more confidently and efficiently with SAP Fiori elements–based UIs.

Developers can now add more building block types to their apps with the Page Editor, including

rich text editors within custom sections,
custom columns for table building blocks, and
the page building block itself.

Managing custom pages is also more intuitive, as building blocks can now be deleted directly from the editor.

To support experimentation and iteration, undo and redo actions are now available when working on custom pages.

New Connection Manager for SAP Systems in VS Code

We have introduced the Connection Manager for SAP Systems as a dedicated Visual Studio Code extension for managing connections to remote SAP systems. The Connection Manager allows developers to create, store, test, and edit connection information that can be reused by the SAP Fiori generator as well as by preview features in SAP Fiori tools.

Preview SAP Fiori Web Apps on Mobile

When developing SAP Fiori applications, simulating a mobile experience in a desktop browser often isn’t enough to fully validate real-world behavior. Touch interactions, performance characteristics, and device-specific rendering can differ noticeably on physical phones and tablets.

To address this, SAP Fiori tools now supports previewing applications directly on real mobile devices. You do this by using @sap/ux-ui5-tooling version 1.19.1 or higher and creating a new run configuration and enabling Remote Access. When you start the run configuration, the terminal provides connection details, including a URL and a QR code, which can be opened directly on a phone or tablet to access the running app.

Find out more here:

News for Mobile Designers and Developers

Let’s first look at updates in the design guidelines and the SDKs, and then look at news for the mobile development kit (MDK).

Mobile Design Guideline and SDK Updates

We have introduced numerous new and enhanced patterns and components this last half-year. I have selected a small number to highlight here, further below you’ll find links to get the full overview.

New for AI

The following two new patterns have been introduced for both the SAP Fiori for Android and the SAP Fiori for iOS design guidelines.

AI Insights Pattern: We have introduced a new AI Insights Pattern, which describes how to present AI insights optimally on mobile devices, as shown in Figure 4. It provides a standardized way to display a summary, analysis, or suggestion generated with AI. This pattern can be applied to a full-screen or a card depending on the scope of content generated by AI.

AI Handoff Pattern: We have created a new guideline describing the AI Handoff Pattern, which defines how a user should transition between contextual embedded AI features and the Joule conversational panel.

Figure 4: Two new AI patterns: AI Insights Pattern and AI Handoff Pattern. Alt Text: On the left two image for AI Insights Pattern, first a full mobile phone screen with title and subtitle at the top, followed by two insights sections, each with two slots for content, at the bottom a user feedback row with thumbs up and thumbs down icons, above a an AI generate button. On the right a diagram for the AI Handoff Pattern showing a schematic mobile module with arrow to and from a schematic Joule UI.

Further news

I have picked two stand-out updates, also made available for Android and iOS.

New Illustrations: We have introduced the new illustrations, that were also introduced in the web, to the mobile design system and the mobile SDKs. You can see a few examples on the left in Figure 5 below.

More flexible card layouts: We offer far more flexibility now in how you use cards to summarize information. For example, you can create wider cards that have the image on the left or the right, and the content block next to it. With the new flex item component, the card’s main header can now be customized to hold more content by adding tags and status info labels outside, on top, between, or below the title and subtitle. Two examples are shown in Figure 5 on the right.

Figure 5: New illustrations and more flexible card layout and content options. Alt Text: On the left three different-size “My Daily Tasks” cards, with images for “You’r all caught up”, “Oops” and “Congratulations”. On the right two card examples: at the top a slim wide card with title, subtitle and one line text on the left, image on the right; below that a larger card with image on the left, title and details with colored indicators and buttons on the right.

Find out more here:

Introducing SAP Fiori for Android/iOS 25.8: Innovative Enhancements for Android and iOS.

For an overview of all updates, have a look at the what’s new sections in the SAP Design System portal and the SAP Mobile Services Documentation

SAP Fiori for Android design: What's New for SAP BTP SDK for Android 26.1 and older.
SAP BTP SDK for Android: What’s New in Release 26.1.2 and earlier releases.
SAP Fiori for iOS design: What's New for SAP BTP SDK for iOS 26.1 and older.
SAP BTP SDK for iOS: What’s New in Version 26.1.2 and earlier releases.

Mobile Development Kit (MDK) News

The Mobile Development Kit, available as part of SAP Mobile Services, enables developers and technical business users to build cross-platform mobile applications. It allows you to build your application once, in an integrated development environment (SAP Business Application Studio / VSCode extension) and run it natively on Mobile Android and iOS devices.

Here I have chosen to highlight one area: enhancements to the calander control, which now supports date range selection as well as allowing you to highlight special events or statuses directly on the calendar.

The new date range selection displays the calendar in a month-view format and allows multiple months to be shown. Users can scroll vertically through the calendar months. This is ideal if you need to plan events or manage schedules over extended periods, since users can select a time period with a start date and an end date (see Figure 6 below):

The first date selected becomes the start date of the range.
The second date selected becomes the end date of the range.

Figure 6: Date range selection supported by the mobile development kit provided by SAP Mobile Service. Alt Text: An image of an iPhone and an Android phone next to each other. The iPhone with the light Morning Horizon theme and a date selection Sep 16 – Sep 29, 2025, the other with the dark Evening Horizon theme and a date selection Mon Sep 29 to Fri Oct 17 2025.

Find out more here:

Blog post: What’s new in Mobile development kit client 25.9.
Documentation: What’s New in Mobile Development Kit 25.9.1 and earlier releases.

Further Information

For creating web applications, do register for the upcoming UI5con virtual conference.

Learn more about it at https://openui5.org/ui5con/faq.html, including how to attend, sponsor, or propose a topic for a session.

For links to design and development tools and technology, have a look at the SAP Fiori topic page in the SAP Community, or go directly to these pages:

Final words

As you can see from all seven posts in the series, we continue to progress rapidly with the user experience of our product portfolio, especially with regards to AI-assistance.

Part 1 of the series lists all the parts, and links to those parts that have already been published:

SAP UX Q1/2026 Update – Part 1: AI, Joule, SAP Build Work Zone, SAP Mobile Start.

For general information on design at SAP and SAP Fiori, check out:

AI and UX sessions at SAP Sapphire 2026 that I’m most excited about

2026-03-31T21:49:43.107000+02:00

SAP Sapphire is where SAP makes its big announcements about its vision for the future of ERP and business applications. This includes showing new products, presenting customers who have transformed their business using SAP’s solutions, and highlighting new technologies that will shape the future.

For 2026, AI will continue to dominate the event. AI will change the way that people consume enterprise software through chat-based interfaces and screens that generate on-the-fly based on what you want to do. Eventually.

In this post, I’ll share the sessions at Sapphire and ASUG Annual Conference that I’m most excited about. For the full menu, you can browse the session catalog. My preferences are, of course, shaped by my role on the Cloud ERP UX Foundation team. I’ll organize by date so you can plan your agenda. You can also use the browser to search by topic or speaker if that makes it easier for you. Some are even available on-demand. Let’s go!

Monday, May 11, 2026

Day / Time / Session ID	Session title and description	Speakers
Monday 10am – 5pm ASUG102	Unlocking Business Value with AI: Strategy, Security, and the Road Ahead Gain a comprehensive and practical overview of SAP Business AI. This workshop will examine core strategies, security frameworks, and future trends while exploring real-world customer stories. The session will conclude with an expert panel and a hands-on AI road mapping session.	Many experts from SAP
Monday 2:00pm – 2:20pm ERP2143	The future of enterprise: Innovations in SAP Cloud ERP Private Discover how SAP Cloud ERP Private solutions enable the next era of enterprise transformation. This introductory session explores how cutting-edge artificial intelligence, trusted data, and integrated applications work in harmony, creating smarter, faster, and more resilient businesses within the security and flexibility of your private cloud.	Nicole Smythe, SAP Vinay V, SAP
Monday 3:30pm – 3:50pm PUX1349	Innovations and value that SAP Business AI offers Learn how you can find the best AI features for your use cases, and understand the business value and associated cost with our self-service tools.	Pascal Mauge, SAP

Tuesday, May 12, 2026

Day / Time / Session ID	Session title and description	Speakers
Tuesday 10:30 am - 11:15 am PUX1228	Creating better user experiences with AI-assisted SAP Fiori apps \| PUX1228 New AI features in SAP Fiori apps boost user productivity and speed onboarding. Starting with the “My Home” page and drilling down into typical SAP Fiori apps, see how AI makes it easier to find information, enter data, automate tasks, and make informed business decisions. Explore how conversational interactions make SAP solutions more intuitive.	Peter Spielvogel, SAP
Tuesday 11:00 am - 11:20 am PUX1346	Great features don’t guarantee success: Experience does Explore SAP Business Suite in the cloud to discover how you can shape the experience of the product for stellar adoption success.	Daniel Becker, SAP
Tuesday 11:30 am - 12:15 pm FOU1861	ASUG Community Conversation: Artificial intelligence Explore platform strategy, embedded and generative AI use cases, integration patterns, and road map priorities with experts in AI and SAP Business Technology Platform. Discuss architecture, data readiness, and clean core alignment while exchanging lessons learned with peers advancing AI innovation.	John Astill, SAP
Tuesday 11:30 am - 12:15 pm ERP1622	SAP ECC to SAP S/4HANA: What’s new, why change, and why now? Learn from more than 2,400 cloud ERP projects as we navigate the shift from SAP ERP Central Component (SAP ECC) to SAP S/4HANA. Compare greenfield, brownfield, and selective data transitions to find the right path. Discover the key differences in SAP S/4HANA, the value of moving now, and how to accelerate AI adoption with modern technology.	Esther Vrieze, SAP Bert Schulze, SAP
Tuesday 11:30 am - 12:15 pm BTM2345	Why ERP transformations fail: The change management gap Organizations expect operational efficiency and digital capabilities from their SAP solution transformations, yet some ERP programs fail to realize full value. The missing link is often adoption. See how integrating organizational change management early in the SAP lifecycle reduces resistance, accelerates adoption, and improves business outcomes.	Kara Beck, Moog Inc.
Tuesday 1:00 pm - 1:45 pm ERP1864	ASUG Community Conversation: Cloud ERP and SAP S/4HANA In this interactive ASUG Community Conversation for professionals in cloud ERP and SAP S/4HANA, explore strategies across migration, operation, and innovation—featuring our road maps, clean core and AI insights, and customer lessons learned. Exchange practical guidance with peers and shape future discussions through open dialogue.	Peter Spielvogel, SAP Nicole Smythe, SAP
Tuesday 1:00 pm - 1:20 pm JOU2645	The future of enterprise applications and AI experiences Unlock real value from agentic AI with insights from SAP experts and peers. Explore what transformation means today and how you can scale AI across the business, overcome common challenges, govern risk, and build an AI-first enterprise that drives measurable top- and bottom-line impact.
Tuesday 2:00 pm - 2:45 pm ERP1178	2026 and beyond: Discover the latest innovations in SAP Cloud ERP Private Running your ERP in the cloud allows you to benefit from innovations at your own pace. Explore recent AI and other functional developments planned for the next releases of SAP Cloud ERP Private solutions to help you prepare for adoption, build your road map, and accelerate time to value.	Maura Hameroff, SAP Rudolf Hois, SAP
Tuesday 3:00 pm - 3:45 pm FOU1559	Build enterprise-grade pro-code agents on SAP Business Technology Platform Unlock the power of autonomous agents with enterprise-grade guarantees. Get technical tips on building pro-code agents on SAP Business Technology Platform that balance innovation with responsibility. Learn to use the Model Context Protocol (MCP) for smooth tool integration while supporting security, ethical AI behavior, and regulatory compliance.	Evgenii Skrebtcov, SAP Tim Back, SAP
Tuesday 3:00 pm - 3:45 pm ERP1834	Extend SAP S/4HANA Cloud while keeping a clean core \| ERP1834 Extend the capabilities of SAP S/4HANA Cloud to address your business needs. Use AI to generate projects in the ABAP programming language and SAP Cloud Application Programming Model from your business requirements. Build SAP Fiori apps based on your written or graphical description, and use natural language filtering to find information in them.	Katja Zoch, SAP Sebastian Steinhauer, SAP
Tuesday 3:30 pm - 3:50 pm JOU2646	AI as the new UI The interface is disappearing, and that's the point. As AI becomes the primary way people interact with enterprise software, the question is no longer how to design better screens but how to deliver better outcomes. Intent replaces navigation, conversation replaces configuration, and the most powerful user experience is the one you barely notice.

Wednesday, May 13, 2026

Day / Time / Session ID	Session title and description	Speakers
Wednesday 10:30 am – 11:15 am SAP1623	SAP ECC to SAP Business Suite: Migration strategies and cloud insights Master the direct transition from SAP ERP Central Component to SAP Business Suite using proven best practices. Compare public, private, and on-premises deployments to define key decision drivers. Learn to navigate annual releases, leverage essential migration tools, and identify the evolving skills needed for a successful, seamless cloud journey.	Esther Vrieze, SAP Bert Schultze, SAP
Wednesday 10:30 am – 11:15 am PUX1819	SAP Fiori in action: How modern UX drives efficiency in cloud ERP Get an overview of how the SAP Fiori user experience (UX) helps users get their work done more easily and efficiently. See how we are using AI today in applications and with the Joule solution. Understand our road map for revolutionizing UX, how AI changes the idea of what an application is, and what all this means for you.	Thomas Reiss, SAP
Wednesday 11:30 am – 11:50 am SUS1523	AI that helps you operate your business As sustainability shifts from reporting to real business decisions, it becomes a control and execution challenge. Explore how you can replace manual processes with AI for trusted, scalable insights and decision support, delivering accountability for operational and financial decision-making.	Sophia Mendelsohn, SAP
Wednesday 11:30 am – 12:15 pm PUX1195	Creating AI-powered UX for your own applications with SAP Design System Learn how to create AI-powered UX for your applications by using SAP Design System (SAP Fiori UX for web and mobile apps) with its powerful set of reusable components, patterns, and floorplans. See how building applications is made easier with our AI-enabled UI technologies for web and mobile apps.	Sophia Levens, SAP Frederic Berg, SAP
Wednesday 11:30 am – 12:15 pm ERP2238	Western Sugar’s success with SAP Cloud ERP Five years after go-live, Western Sugar Cooperative calls SAP Cloud ERP applications “wonderful.” Hear about why it chose public cloud; the value of clean core, best practices, strong configuration and integration, and continuous improvement; its smooth move from a two- to three-system landscape; and readiness for AI-enabled innovation.
Wednesday 11:30 am – 12:15 pm FOU2337	When AI becomes the interface to the enterprise For decades, SAP helped shape enterprise software based on screens and transactions. Today, AI is evolving how we interact with systems. Explore how SAP leads this shift—uniting applications, data, and AI—and what this next phase of transformation means for organizations turning AI into a real competitive advantage.	Florian Heretsch, SAP
Wednesday 1:00 pm – 1:45 pm FOU1557	Getting started with SAP Build MCPs: Create your first CAP app and process Experience the powerful Model Context Protocol (MCP) integration in SAP Build solutions. Produce your first SAP Cloud Application Programming Model (CAP) application and SAP Fiori elements UI, while orchestrating workflows. See how AI-enhanced context improves coding efficiency and helps you build scalable, process-rich apps.	Tim Back, SAP Jason Gabor, SAP
Wednesday 1:00 pm – 1:45 pm BTM1232	The AI-augmented architect: Upgrading architecture in the age of AI AI is reshaping enterprise architecture. To provide value, enterprise architectures must embrace AI tools. Discover SAP technology leveraging AI for enhanced visibility and coordination. Through real-world examples, see how Joule and agentic AI increase information velocity and augment architect capabilities to thrive in this evolving landscape.	Martin Mysyk, SAP
Wednesday 1:30 pm – 1:50 pm PUX1192	From enterprise software to AI native experiences: SAP's UX strategy As AI reshapes the enterprise, SAP's design strategy puts human intent at the center of autonomous, agentic, and multimodal Joule solution experiences, turning complexity into clarity and technology into measurable business value. Take a look at where user engagement and enterprise UX are headed, and how SAP is leading the way.	Arin Bhowmick, SAP Sophia Levens, SAP
Wednesday 2:00 pm – 2:20 pm PUX1210	AI and the future of user experience in SAP software Prepare yourself for the upcoming revolution in user experience by understanding how we are harnessing AI to help users achieve better outcomes. Discover how AI is changing the idea of what an application is—and what this means for you. Learn about our AI design patterns and get a glimpse of the future SAP software user experience.	Emil Voutta, SAP
Wednesday 2:00 pm – 2:20 pm JOU2647	The future of enterprise applications and AI experiences The enterprise application is no longer a system of record but a system of action. As AI moves from assistant to agent, organizations shift from what their software can store to what it can do. Learn why the future belongs to applications that don't just surface information but understand context, anticipate decisions, and act with confidence.
Wednesday 3:00 pm – 3:20 pm PUX1194	User experience innovations and road map for SAP Business Suite Have a look at the latest user experience innovations across our suite of applications, along with exciting web and mobile innovations coming soon. Also check out selected highlights from Ul technologies for creating great UX for your own applications.	Tom Reiss, SAP Christina Salwitzek, SAP

I’m excited to hear what we announce in the keynotes and experience the future of enterprise software. AI will transform how we all interact with apps. The future starts now.

Here are some other summaries of Sapphire sessions from other colleagues.

Inside SAP Build at SAP Sapphire 2026: What to Expect from AI Agents and Agentic Development by Mark Wright

See you in Orlando!

For the SAP Cloud ERP UX Foundation team, Peter Spielvogel.

SAP Developer News for April 16th, 2026

2026-04-16T21:00:00.018000+02:00

ITEMS

UX Innovation Day in Silicon Valley on 11 June

Event page https://events.sap.com/us-ux-innovation-day-siliconvalley-2026/en_us/home.html

SAP BTP ABAP Environment – Pre-Upgrade Option for Release 2605

Blog post https://community.sap.com/t5/technology-blog-posts-by-sap/sap-btp-abap-environment-pre-upgrade-option-for-release-2605/ba-p/14347147

XML Annotations: The Essentials Before Adapting Documentation Samples to Your Project

Mio’s blog post https://community.sap.com/t5/technology-blog-posts-by-members/xml-annotations-the-essentials-before-adapting-documentation-samples-to/ba-p/14369241

OData Deep Dive mission https://developers.sap.com/mission.odata-deep-dive.html

OData Deep Dive rewrite blog post https://qmacro.org/blog/posts/2026/02/02/odata-deep-dive-rewrite-in-the-open/

Edge Integration Cell APIs and Cloud Integration AI-assisted error resolution

Edge Integration Cell APIs: https://help.sap.com/docs/cloud-integration/sap-cloud-integration/local-odata-api-access-for-edge-integration-cell?locale=en-US

AI-assisted error resolution: https://help.sap.com/docs/integration-suite/sap-integration-suite/analyze-message-processing-errors-with-ai-f27f95d7b90b4f13aea22b399418b702?locale=en-US

DYK #12 AI Launchpad Leaderboard

The Model Library topic in the SAP Help Portal https://help.sap.com/docs/ai-launchpad/sap-ai-launchpad/model-library

CHAPTER TITLES

00:00 Intro

00:07 UX Innovation Day in Silicon Valley on 11 June

01:00 SAP BTP ABAP Environment – Pre-Upgrade Option for Release 2605

02:00 XML Annotations: The Essentials Before Adapting Documentation Samples to Your Project

03:16 Edge Integration Cell APIs and Cloud Integration AI-assisted error resolution

04:25 DYK #12 AI Launchpad Leaderboard

TRANSCRIPT

[INTRO]
This is the SAP Developer News for April the 16th, 2026.

[DJ]
If you're in the Silicon Valley area in June and are interested in the intersection between AI and UX, then there's an event just for you. It's on the 11th of June at the SAP AppHaus in Palo Alto, and it's an in-person event only. It's for developers, architects, and technical consultants, and it's all about the AI functionality being built into the SAP Fiori elements framework. There's AI for business users and AI for application developers. The event page has an agenda for the day, which is currently tentative, but it gives us a good idea of the format and content. There's also a link on there for registration. Anyway, check it out. Link in the description.

[Mamikee]
We have an important update for SAP BTP ABAP environment users. We're offering a free pre-upgrade option for release 2605, giving customers and partners the chance to test their existing applications ahead of the standard upgrade, which is planned for May 16th and 17th. Now some of the key milestones have already passed. Planned new features were announced on April April 13th, and pre-upgraded systems are scheduled for upgrade on April 17th, which means teams already participating should now be focused on regression testing and validating their custom-built apps. Now, looking ahead, Hot Fix Collection 2 is planned for April 30th, and any issues found during testing should be reported by May 1st using component BC-CP-ABA. Now, the goal is simple. help make the upgrade a no-event and avoid day one surprises. You can read more in the link below.

[DJ]
Fiori elements based UIs are great, but sometimes it's hard for us to grok how they can be controlled and configured, which is mostly through annotations, which are organized in vocabularies, expressed in metadata, which is usually in the form of XML. So any help is welcome. And in that context, we wanted to point you to a great blog post by SAP community member Mio Yasutake, who takes time to explain these topics in great detail, how things fit together based upon samples and documentation for UI5 and in the context of CAP and RAP-based services. There's lots of detail and it's well worth a read. Thanks Mio! Also if you want more detail to complement this then we have the OData deep dive mission over on the tutorial navigator and in there there are specific tutorials on metadata vocabularies and annotations ready to go as well. Happy learning!

[Antonio]
Hola, SAP Developers! Two quick updates for Edge Integration Cell and Cloud Integration users. First, the local OData APIs for Edge Integration Cell just got better. You can now authenticate using Client ID and Client Secret. More secure, easy to automate. Now, a quick reminder that there are many APIs in Edge Integration Cell that you can use. Monitoring APIs, for example, to track message processing. and management APIs for message stores, data stores, JMS brokers, and variables. These are perfect for building custom dashboards or for automating operations or integrating with your existing monitoring tools. Now, in Cloud Integration, we have AI-assisted error resolution. When your integration flow fails, you can now use AI to analyze the error, get root cause suggestions, and even get remediation steps. So it's like having an integration buddy next to you. which can save time debugging and gets you back on track faster. So check the links in the description for full documentation on both features. ¡Hasta luego!

[Nora]
Did you know that you can compare foundation models right in AI Launchpad? So just jump over to Generative AI Hub in your AI Launchpad and open the model library. And then here you can click on Leaderboard. And now you see all the models that we have available here. and over here you can see the different scores so the HELM score for example tells you how well the model performed in a multiple choice exam across a variety of topics the chatbot arena score tells you how well the model performed in a head-to -head against different AI models and then the AIRBench refusal rate and the AIRBench discrimination bias refusal rate tells you how well the model is handling harmful or biased requests and then all the way over here you have the output and input token cost and the context window size. Now this really helped me to find the right model for my use case depending on cost and context window size and performance overall. I honestly usually don't go to the leaderboard, I head directly to the chart because here you can very easily compare the models.

Step-by-Step Integration of SAP Cloud ALM with S/4HANA for Transport Management

2026-04-20T10:59:35.548000+02:00

This blog outlines the process of integrating SAP Cloud ALM with SAP S/4 HANA to enable efficient transport management. The integration ensures streamlined lifecycle management, improved visibility, and better control over transport activities across the SAP landscape.

The overall process involves the following key steps:

Onboarding SAP Cloud ALM

Before initiating the integration, SAP Cloud ALM must be provisioned and onboarded in your SAP environment.

Prerequisites

Ensure the following requirement is met before starting the onboarding process:

You must have an S-user ID with the “Edit Cloud Data” authorization in SAP for Me.

Procedure

Log in to SAP for Me.
Navigate to Systems & Provisioning.
Under Products Available for Provisioning, locate your entitlement for SAP Cloud ALM.

Choose Start Provisioning.

Select the geographical region in which you would like to provision SAP Cloud ALM

Enter a unique subdomain name.
Specify an SAP Cloud Identity Service, if you have an existing one please select it from the list, if you do not have an existing SAP Cloud Identity Service a new one will be created for you automatically.

After selecting Submit, the provisioning process is initiated. SAP Cloud ALM is automatically prepared by SAP, and the required foundational entities are created to enable the service.

During this process, the following components are provisioned:

A SAP Business Technology Platform (SAP BTP) Global Account and Subaccount dedicated to SAP Cloud ALM are created. Within this subaccount, you will generate the Service API key, which is required to connect SAP Cloud ALM with other systems in your landscape.
A mutual trust relationship is automatically established between SAP Cloud ALM and the selected SAP Cloud Identity Authentication Service tenant to enable secure authentication and user access.

Once SAP completes the setup of these entities, you will receive a confirmation email containing the URL to access your newly provisioned SAP Cloud ALM tenant.

System Prerequisites

SAP_BASIS Release

Your ABAP system must meet one of the following requirements:

SAP_BASIS 7.40 SP16 or higher (or 7.50 SP05 or higher)
SAP_BASIS 7.40 SP09 – SP15 (or 7.50 SP00 – SP04) with implementation of SAP Note 2283880

SAP_UI Version

The minimum required version is:

SAP_UI 740 SP15 or higher

ST-PI Component

Ensure the ST-PI component is properly maintained:

Install ST-PI 7.40 support packages and keep them up to date.
Implement the required collective correction SAP Note 3639977, which includes updates for SAP Cloud ALM compatibility.
Always operate the ABAP system with the latest or second latest support package available on the SAP Support Portal.

ST-A/PI Version

For Business Process Monitoring in SAP S/4HANA or SAP Business Suite 7:

Use ST-A/PI version higher than 01U_731.
Keep the component updated regularly.
If using ST-A/PI version 01W, ensure that the latest related SAP Notes are implemented.

Security and SSL Configuration

The following profile parameters and certificates must be configured in the ABAP system:

Required Profile Parameters

icm/HTTPS/client_sni_enabled = TRUE
ssl/client_ciphersuites must be maintained according to SAP Note 510007

Required Root Certificates

The following certificates must be imported in STRUST under:

SSL Client (Anonymous)
SSL Client (Standard)

Certificates required:

DigiCert Global Root G2
DigiCert TLS RSA4096 Root G5

Required User Authorizations

The user who runs transaction /SDF/ALM_SETUP must be assigned the following PFCG role:

SAP_SDF_ALM_SETUP

Within this role, maintain the authorization object:

S_BTCH_NAM → BTCUNAME

The value for BTCUNAME can be maintained as:

* (asterisk) to allow any user to execute the background job, or
The specific username that will run the background job for data collection.

Background Job User designated to run the data collection background jobs must have the appropriate roles and authorizations required for SAP Cloud ALM data integration.

Configure Transport Management System (STMS) in SAP S/4HANA

Log in to the SAP S/4HANA application server and configure the SAP Transport Management System (STMS) to enable transport management across your system landscape.

In this example, a two-system landscape is used:

Development System: NI2
Production System: PI2

The first step is to establish the STMS configuration between the NI2 (Development) system and the PI2 (Production) system. This configuration ensures that transport requests created in the development system can be properly routed and imported into the production system following the defined transport path.

Make sure CTC parameter value maintained in DEV and prod system as 1

Connecting the On-Premise System to SAP Cloud ALM

Once the SAP Transport Management System (STMS) configuration is completed between the systems, the next step is to integrate the on-premise SAP S/4HANA system with SAP Cloud ALM.

This integration enables SAP Cloud ALM to monitor transport activities, manage deployment processes, and provide centralized visibility across the entire system landscape.

Integration Setup Across System Landscapes

To establish the integration with SAP Cloud ALM, the required configuration steps must be performed in both the Development (DEV) and Production (PROD) systems. In addition, the setup should be executed in client 000 as well as in the productive client of each system.

While the technical configuration steps remain largely the same across environments, the purpose and use cases of each client and system differ:

Client 000 – Typically used for system-level configuration and technical setup activities.
Productive Client – Used for business operations and application-related processes.
Development (DEV) System – Used for development, configuration, and testing activities.
Production (PROD) System – Used for live business operations.

By ensuring that the integration is properly configured across these systems and clients, SAP Cloud ALM can effectively monitor system activities, manage transports, and support lifecycle operations across the entire SAP landscape.

Maintaining the HTTP Destination

To configure the HTTP destination, a service key from SAP Cloud ALM is required. This service key contains the necessary credentials and endpoint details that allow the on-premise system to securely communicate with the cloud environment.

The service key is generated within SAP Business Technology Platform (SAP BTP), where SAP Cloud ALM is provisioned.

Procedure

Log in to the SAP Business Technology Platform (SAP BTP) cockpit.
Navigate to the subaccount associated with your SAP Cloud ALM tenant.
Locate the SAP Cloud ALM service instance.
Generate a service key, which will be used to maintain the HTTP destination in the on-premise system.

The information from the service key will later be used to configure the required communication settings between the on-premise SAP S/4HANA system and SAP Cloud ALM.

Registering the System in SAP Cloud ALM

Enter the background user that was created to perform the data collection tasks. Ensure that this user has the required authorizations as described in the Prerequisites section.

Next, choose Register to initiate the connection with SAP Cloud ALM and register the system. If the registration is successful, an LMS ID from the Landscape Management Service is automatically retrieved and displayed. This ID confirms that the system has been successfully registered in SAP Cloud ALM.

Activating Transport Management Use Cases in SAP Cloud ALM

After registering the system using transaction /SDF/ALM_SETUP, the next step is to activate the required transport-related use cases in SAP Cloud ALM.
The tasks to be activated depend on the system landscape (DEV, QUA, PRD) and the client in which the configuration is performed.

Development System (DEV)

Client 000: Activate the following task:

Transports: Read; This task must be activated on source systems to report transport requests to SAP Cloud ALM so that they can be assigned to features.

Client 100 (Development Productive Client)

Activate: Transports: Create & Export (Client-Specific)

This task must be activated on all development clients used for customizing activities.

For example:

If customizing activities are performed in client 100, activate the task there.
If another client such as 200 is used for development or transport creation, the task must also be activated in that client.

Activating this task triggers the background job:

/SDF/CALM_CDM_TR_PROC_CL_DEP-XXX

This enables the following transport-related functions:

Create transports
Create transport of copies
Release transports
Delete empty transports during release

Transports: Retrofit (Client-Specific)

Activate this task in the development system of your maintenance track if retrofit functionality is required.

Retrofit ensures that changes implemented in one landscape can be synchronized with another development track.

Quality System (QUA)

Client 000; Activate the following task:

Transports: Import

This triggers the background job:

/SDF/CALM_CDM_IMPORT_TRANSPORTS

The job performs the following actions:

Retrieves transports scheduled for import from SAP Cloud ALM
Executes the transport import process into the target system

Target systems typically include:

Quality Assurance (QA)
Pre-Production
Production

These systems are assigned to the project via the deployment plan.

Production System (PRD)

Client 000; Activate the following tasks:

Transports: Import

Allows SAP Cloud ALM to trigger transport imports into the production system.

Transports: Read Landscape

This task reports the STMS landscape configuration to SAP Cloud ALM.

Supported landscape configurations include:

Any consistent Transport Management System (TMS) landscape
The last system in a transport track is always considered the production system
Client-specific transport routes (CTC) are recommended
TMS transport groups are supported

Transports: Check; This feature enables transport impact analysis before importing transports into production.

It evaluates the transport set to identify potential risks or conflicts that may impact the production environment.

Do the same for 000 and productive client of production system as well.

Background Jobs Created After SAP Cloud ALM Configuration

Once the configuration and system registration are completed in SAP Cloud ALM, several background jobs are automatically scheduled in the SAP S/4HANA (or ABAP) system. These jobs are responsible for data collection, system monitoring, transport processing, and communication with SAP Cloud ALM.

Some of the commonly scheduled jobs include:

/SDF/CALM_CDM_DIAGNOSTICS_000
/SDF/CALM_CDM_DIAGNOSTICS_<Productive Client>
/SDF/CALM_CDM_TR_CHECK
/SDF/CALM_CDM_TR_PROC_CL_DEP-<Client No.>

In addition, the following operational jobs may also be scheduled:

CALM Auto Discovery – RFCALMPI1<Client No.> / ZCALM_PI1_00
CALM Heartbeat – RFCALMPI1<Client No.> / ZCALM_PI1_000
CALM Scheduler – RFCALMPI1<Client No.> / ZCALM_PI1_000

These jobs ensure continuous communication, monitoring, and transport management synchronization between the on-premise system and SAP Cloud ALM.

Now go to projects and setup and add the system.

Add the systems to SAP Cloud ALM based on the number of systems available in your landscape. In this example, the environment consists of two landscapes: Development and Production. These systems are added and organized accordingly to enable proper monitoring, transport management, and lifecycle operations within SAP Cloud ALM.

Creating Deployment Plans

The next step is to create deployment plans in SAP Cloud ALM. Deployment plans define how transports move across the system landscape and support different change management scenarios.

These plans may vary depending on organizational requirements and client-specific processes.

Common examples include:

Normal Change
Standard Change etc.

Create the required deployment plans based on your organization’s change management process. After creating the plans, assign the system groups that were configured in the earlier steps. This ensures that transports are deployed according to the defined system landscape and transport routes.

By configuring deployment plans properly, SAP Cloud ALM can effectively manage and control the movement of transports across development, testing, and production environments.

In the next step, assign the required roles for Change and Deployment Management in SAP Cloud ALM. These roles define the responsibilities of users involved in the change management process.

Typical roles include Project Lead, Change Manager, Developer, and other relevant stakeholders. Assigning these roles ensures proper governance, clear accountability, and smooth execution of the change and transport management process.

With these steps completed, the configuration and integration with SAP Cloud ALM are successfully finalized. The on-premise systems are now connected, enabling centralized monitoring, transport management, and change and deployment management across the system landscape

System Refresh Considerations

After connecting your ABAP system to SAP Cloud ALM, the system continuously sends monitoring data to the SAP Cloud ALM monitoring applications.

The monitoring data is associated with a specific ABAP system in the Landscape Management application based on the Landscape Management System (LMS) ID.

When a system refresh is performed—where an ABAP system is overwritten with a copy of another system—the original LMS ID mapping may become inconsistent. As a result, monitoring data may incorrectly be assigned to the source system of the copy rather than to the refreshed system.

To prevent this issue, it is recommended to save and restore the tables containing SAP Cloud ALM monitoring configuration during the refresh process.

Post-Copy Automation (PCA) Integration

The SAP Cloud ALM configuration is integrated with Post-Copy Automation (PCA) to simplify system copy and refresh scenarios.

Prerequisites

Ensure the following components are available:

ST-PI 7.40 SP27 or higher
Implementation of SAP Note 3501074 (System Copy: ST-PI CALM Configuration)

Reports for System Copy and Refresh

If Post-Copy Automation (PCA) is not used, SAP provides dedicated reports to support system copy and refresh scenarios related to SAP Cloud ALM configuration.

Report: /SDF/CALM_SYS_COPY

This report is used after performing a system copy to create a new system based on an already configured ABAP system.

The report deletes the existing SAP Cloud ALM configuration associated with the copied system to prevent incorrect system mapping.

After running this report, the connection to SAP Cloud ALM must be re-established using transaction:

/SDF/ALM_SETUP

To prepare a system refresh, you can execute this report. It creates a Transport of Copies (ToC) with the table content of the SAP Cloud ALM configuration. Export this request and save it. After the system refresh, you can import this transport request again.

SAP User Feedback Days 2026: Two days of listening, learning, & building real connection in Walldorf

2026-04-22T18:07:57.034000+02:00

On April 15 and 16, 2026, we welcomed end users and experts from our customers to SAP Headquarters in Walldorf for a two-day event built around one simple idea: We Create the Future. We can say with absolute certainty that the event was a huge success—and what made it special wasn’t just the agenda, the sessions, or the logistics. It was the people. The honesty. The energy. The shared curiosity. And the feeling—again and again—that when we sit together and talk openly, we move faster and we build better. It is a source of joy and pride for us to host this event at SAP.

What SAP User Feedback Days are really about:

To create a space where customers feel truly heard
To bring product teams and user research together with end users’ face to face
To dig deeply into real use cases and the reality of daily work
To challenge our assumptions (and sometimes our favorite ideas) in a constructive way
To build relationships that last beyond the workshops

Over the two days, we heard a consistent theme from customers: they value not only the chance to influence the future of SAP software, but also the human closeness—the ability to meet the people behind the product, and to meet other experts from other companies who “get it”.

Day 1: Deep dives with real end users—where insights become tangible

The first day was dedicated to hands-on user research and direct exchange on specific AI use cases coming from our product teams. Our user research experts worked side-by-side with customers and our product teams to explore real workflows, pain points, decision moments, and what “good” looks like in practice.

One of the most meaningful things we heard was that some customers said they didn’t realize SAP was truly listening in this way. This is so motivating for us all and to see this in action together —it’s exactly why these days matter. Trust is built in moments like these.

Kicked off with a keynote on "We Create the Future".

Intense, but very fun, sessions with our customers on AI use cases!

Day 2: Looking forward—co-creating what comes next

If day one was about listening deeply to current reality, day two was about looking forward together. Through interactive workshops and collaborative discussions, customers and SAP colleagues explored what the future should feel like: where user experience must evolve, what users need from SAP to succeed, and how we can design for the next set of challenges coming in business and from AI technology —not in isolation, but together.

Our User Research Event lead, Christoph, driving a session with customers.

One of our expert sessions on Fast with Fiori.

Expert sessions and interactive exchanges: making it easy to connect beyond “the session”

In addition to the research activities, customers also had the chance to join expert sessions and explore interactive topics, designed to give space for informal questions, deeper product conversations, and spontaneous discussions.

Many customers told us they were impressed—not only by what SAP is working on, but by how approachable the experts were. These exchanges helped customers see the “why” behind decisions, and helped our teams see where clarity, guidance, and experience design need to be even stronger.

It was also a pleasure to experience our product teams learn more about what is so important about their products and use cases and also sometimes challenge their assumptions and see a different way forward. Plus, it was amazing to see them take time to show our customers our wonderful campus and explain why we like working so much for SAP.

Why this matters: better UX starts with closeness, not distance

We often talk about “customer centricity.” SAP User Feedback Days are what it looks like when we practice it.

Thank you—truly

To our customers and end users: thank you for making the trip, for trusting us with your honest feedback, and for being willing to engage so openly. The event would not be what it is without you—and it genuinely wouldn’t be the same without your presence and energy.

To the SAP colleagues across user research, product teams, and all the experts who supported sessions and exchanges: thank you for the preparation, professionalism, and care you brought into every customer interaction. The way you showed up made a real difference to how customers experienced SAP.

We’re already looking forward to what comes next—and to continuing the conversation, not only at the next event, but in the everyday work between events.

Customer Voices

Just a few comments that I can share from the day from our customers

“I brought my business colleague with me, to show him as well…..to see his excitement when.. he was working through the app, it was very delightful for me.”
“SAP is really going into the AI direction, that can help us automate our processes, which is great for us.”
“Whoever, might be invited in future, I will just recommend to.. use this opportunity to.. come into this exchange. …. it's a great thing.”
“Thanks to SAP for the invitation and the open exchange — this is exactly the kind of practical AI innovation our industry needs.”
Want to see some more proof? Check out the LinkedIn buzz here!!!

What’s next

We’re now consolidating insights and findings from the two days and working with the teams involved to ensure what we learned translates into tangible improvements—both in the near term and in future product direction.

If you joined us in Walldorf: thank you again. And please keep the conversation going—we truly value it!

From a very happy Alex & Walli

And not forgetting thank you from our project dream team!

Celebrating my 300th blog post on the SAP Community

2026-04-22T21:58:49.965000+02:00

I noticed that my last blog post was my 300th on the SAP Community. In those 300 posts, I have covered many topics related to user experience, clustered into a few key areas. To celebrate this milestone, I’ll reflect on how the topics I covered mirrored the evolution of user experience at SAP, what I learned from the community, what’s next, and end with a call to action for you.

My 300 blogs posts contain a historical account on the evolution of SAP’s user experience

Product Marketing is much easier with great products

Before going into the content, let me acknowledge that there is no product marketing without product. All these blog posts about our UX products would not have happened without the amazing development, product management, design, QA, documentation, and other colleagues that build and test these solutions. I’m grateful to the many coworkers over the years who came up with ideas to solve real customer pain points regarding SAP’s user experience. I also appreciate the many customers and partners that provided ideas for blogs posts in online forums, SAP events, and user groups.

The topics I covered mirrored the evolution of user experience at SAP

In my product marketing role, most of my posts fell into one of these broad categories:

Product
Strategy
Events
Customer and partner enablement

The topic mix shifted over time as our team expanded the products we worked on.

Product

Release announcements.
Product-focused posts generally followed the cadence of our release cycles. This shifted from annual or semi-annual service packs for on-prem solutions to continuous innovation / continuous delivery pipelines for our cloud-based tools. My first five years of posts were on SAP Screen Personas. From version 1.0’s first appearance at TechEd 2012 through the release announcements of version 3 SP18, after which Rohith Deraje took over for SP19 and beyond.
SAP Fiori elements and SAP Fiori tools were next to join our team’s portfolio. I posted some of the early announcements for those products until Katrin Polloczek, Christoph Gollmick, Ashley Tung, and Ian Quigley took ownership of the content.
Collaborative ERP was a more recent addition to SAP UX Foundation. I posted the early announcements on our strategy and early versions until Regina Sheynblat picked this up.
Embedded AI in SAP Fiori apps is the newest part of our portfolio, with Conrad Bernal now posting about new innovations and beta opportunities.
Roadmap updates – when you have a product that 1000s of customers use to run their business, they want to know what’s coming next. Towards that end, I drafted many roadmap updates over the years on the various solutions in our portfolio.
Frequently asked questions (FAQ) documents – one of the most interesting parts of my role is interacting with customers in various forums and hearing their questions. Often, we hear the same questions from multiple people. In those cases, it’s worth capturing them into an FAQ document.
Technical tips and tricks – as part of the product team, many customers reach out vie email to ask questions that are more detailed than can be covered in an FAQ document. If their inquiry is relevant to a broader audience, I put together tips they can use to get started on a project or break through a barrier they are facing and post it so others in the SAP Community can learn.
Customer and partner success stories – sometimes our customers want to share their success with SAP UX solutions. In those cases, I have helped them tell their story through the SAP Community.

Strategy

When I looked through my blog posts over time, they followed the same evolution of SAP’s broader UX strategy. We built SAP Screen Personas to improve the SAP GUI user experience, one screen at a time. SAP Fiori elements accomplished this at scale, for the most common business processes. Then we rolled out SAP Fiori tools to make it easier to build Fiori elements apps. Then collaborative ERP to help people team up to solve complex business problems. Most recently, we added AI to both the Fiori apps that we ship and the tools we (and you) use to build them.

Posts on UX strategy explain how all the pieces fit together so customers can plan their digital transformation, SAP S/4HANA migration, or other strategic initiative knowing where SAP is heading. Since customers are not concerned about our internal organizational structures, I blogged on solutions within the UX Foundation portfolio as well as adjacent solutions such as SAP Build, BTP, and Joule. Sometimes we include a peek behind the curtain, so people understand how SAP Fiori powers the apps in SAP S/4HANA and what to expect as we continue to add both simplicity and power to our flagship SAP Cloud ERP solution.

Events

It’s natural to blog about events to help people set the right expectations, plan their agendas, and make the most of their investment in attending the event. Typically, I like to highlight the sessions most relevant to the customers and partners that follow me on the SAP Community and LinkedIn.

For Sapphire 2026, I have a list of recommended sessions on AI and UX, along with what I’m planning with Nicole Smythe on bridging the skills gap to accelerate your AI projects.

My other posts have covered SAP TechEd, ASUG Tech Connect, ASUG chapter meetings, and, of course, our own SAP UX Innovation Day events. Next one is on June 11 in Palo Alto, if you are interested in attending.

Customer and partner enablement

I also noticed a number of blog posts on various training courses for customers, partners, and colleagues. In the early days, we created several openSAP training courses. The ones that are still relevant have moved to learning.sap.com. We also have posts on hands-on exercises from other events or tutorials from our development experts. It makes sense that people appreciate training from the team that builds and supports the products.

The SAP community is for learning, connecting, and listening

I would be remiss if I did not reflect on the SAP Community and the role it played in my personal growth at SAP. I learned so much from the questions and comments that people submitted, and through my interactions with the highly professional SAP Community team.

Much more than the number of blog posts I have written, I’m most proud of how many other colleagues I inspired to start blogging; that list continues to grow.

And thanks to my long-time friend, former colleague, and co-author, Michael Procopio, for getting me started on my blogging journey back in our days at HP Software.

The next UI will build from our Fiori experience and use AI heavily

While SAP Fiori solves many issues, we are still working to simplify how customers consume SAP and developers create apps. Needless to say, AI will play an increasingly important role in both of these dimensions. Your ongoing feedback will continue to drive our development priorities.
You will hear more about this at Sapphire and in our next SAP UX Innovation Day.

In addition to providing your feedback through the SAP Community, you are welcome to join our monthly SAP Developer Roundtable to share your thoughts on developing SAP Fiori apps using our latest tools and technologies.
If you are a public cloud customer, you can join our online user group to discuss UX and adjacent topics with your peers and SAP experts.

We will continue to address your concerns about usability in SAP Cloud ERP.

To count to 300, start with 1: What are you waiting for?

A much bigger milestone than blog 300 is blog #1.
What are you waiting for? There’s no time like the present!
The SAP Community needs your voice. If you want to brainstorm ideas or need help outlining your first post, please let me know. Like the rest of the SAP Community team, I’m here to help.

Thanks for reading all my stuff over the years.

Turning “Moments of truth” into lasting impressions with SAP SuccessFactors Onboarding

2026-04-24T14:30:28.640000+02:00

"Moments of truth" in Onboarding

Admittedly, it has been a while since I studied Service Management at business school, and many of the theories date back to the 1980s. Still, one idea has always stayed with me: people judge experiences by comparing their expectations with their perception. In short, this is how we assess an experience. These are often referred to as “Moments of Truth.”

Even today, this concept remains highly relevant, if you ask me.

In the employee journey, one of the most important moments (of truth) happens after the contract is signed, when preboarding and onboarding begin. This is where expectations are tested, and first impressions are formed through communication, preparation, and early interactions.

It is both emotional and practical, and these first impressions tend to last.

Across industries, a common pattern is that organizations invest heavily in attracting talent, but far less in structuring the onboarding experience from “offer signed” to day one. People and relationships remain essential, but without structure and process support, the experience often becomes inconsistent.

This is where SAP SuccessFactors Onboarding can support organizations by enabling a more consistent, structured, and scalable onboarding experience. If it is used to its full extend.

From candidate to employee - without friction

At its core, SAP SuccessFactors Onboarding connects what is typically disconnected. It brings together systems, processes, and people into one experience.

Instead of handing a new hire over from recruiting into emails, PDFs, and spreadsheets, everything continues in one flow. The candidate becomes a new hire, and then an employee, without changing platform or experience.

The solution supports onboarding, cross-boarding, offboarding, and rehire scenarios in one place. This reflects the reality that employee journeys are not always linear.

In many implementations, the value of having one centralized experience is initially underestimated. In practice, it significantly reduces friction and manual coordination.

A guided, structured onboarding experience that sets people up for success

The system is designed around guided processes. New hires are not expected to figure things out themselves. Instead, they are supported step by step through tasks such as data collection, document handling, learning, and introductions.

Before day one, employees can access a personalized homepage to complete forms and prepare. On day one, the focus shifts to connections, clarity, and productivity. Activities such as buddy assignments, meetings, and onboarding tasks are already planned.

This creates a more consistent onboarding experience while still allowing flexibility for different roles and local requirements.

From a process perspective, this reduces waiting time and helps employees become productive earlier.

Seamless onboarding and data flow across the SuccessFactors suite

One of the most powerful aspects of SAP SuccessFactors Onboarding is its native connection to SAP SuccessFactors Employee Central.

This is not a traditional integration. Data entered during onboarding is written directly into Employee Central. There is no duplication, no interfaces, and no need to re-enter information. From day one, you have one consistent and reliable data foundation.

What makes this particularly strong is that it applies to all actors involved in the process. The new hire, even before officially starting and while still an external user, can access a secure part of the system and enter their own data directly into the core HR system. The same applies to hiring managers and HR, who can update or enrich data during onboarding. Everything is written to the same place, in real time.

This has a clear practical impact. It reduces errors, removes manual steps, and ensures that employee data is available immediately for downstream processes.

Building on this foundation, onboarding also connects to the broader HR landscape. Recruiting triggers onboarding, Learning can assign training, and Performance can support early goal setting.

In many organizations, these processes are still handled separately, and expectations for the first days are often loosely defined and depend on individual managers.

By linking onboarding to structured plans such as 30-60-90 day goals, organizations can define expectations early, assign learning before day one, and track progress from the start.

This is where onboarding moves beyond administration and becomes part of broader workforce enablement.

Bringing structure and control to onboarding

From an HR and manager perspective, the value is not only in the experience, but also in the control.

Dashboards provide visibility into tasks, deadlines, and overdue activities. Tasks can be triggered automatically, reminders can be sent, and bottlenecks can be identified early.

What was previously handled through manual follow-ups becomes structured workflows.

This is particularly relevant in multi-country environments, where consistency and compliance are important.

The system allows configuration of business rules, automation of processes, and integration with the broader HR landscape through APIs. This means onboarding becomes part of the overall HR architecture rather than a standalone process.

What value does this actually create?

If we move beyond system terminology, the value can be summarized in a few key outcomes:

New hires arrive better prepared and ready to contribute from day one
Managers gain clarity on responsibilities and timelines
HR achieves greater consistency and visibility across teams and locations
Time to productivity is reduced through better preparation and alignment
Onboarding becomes structured and measurable rather than ad hoc

And importantly:

Organizations improve their ability to deliver a consistent first impression

Because onboarding is not just an HR activity. It is a key moment where expectations are either confirmed or challenged.

Closing thoughts

Many organizations focus heavily on attracting talent, but less on what happens immediately after.

If onboarding still relies on emails, documents, and manual follow-ups, it may be worth reviewing how the process is structured.

Improving onboarding is not only about efficiency. It is about shaping the employee experience at a critical moment.

Jonas Kyhnau is a SAP SuccessFactors Senior Consultant working at Pentos Denmark.
I help companies optimising and streamlining their core HR processes with practical, scalable solutions. I cover all process areas from Recruiting (including SmartRecruiters of course) through Onboarding to Core HR in Employee Central.

SAP SuccessFactors Platform SAP SuccessFactors Onboarding

#Pentos - SAP SuccessFactors Partner Danmark

SAP Fiori for SAP S/4HANA - What’s New in Moving from Standalone to Embedded Deployment [V3.0]

2026-05-06T16:20:29.705000+02:00

SAP Fiori for SAP S/4HANA – What’s New in the 2026 Update of Moving from Standalone to Embedded Deployment

As you may already know, SAP continues to recommend deploying SAP Fiori for SAP S/4HANA using an embedded SAP Fiori Front-End Server.

Over the years, many customers who initially started with a standalone FES have been transitioning to embedded deployment to reduce complexity, optimise operations, and align with SAP’s long term architecture.
Looking ahead, this direction becomes even more explicit. As outlined in the SAP Fiori Deployment Options and System Landscape Recommendations (as of Guide’s Version 10.3, February 2026) under the section Outlook: Fiori Deployment, the guide explicitly states:

SAP Fiori Deployment Options and System Landscape Recommendations, Section 'Outlook: Fiori Deployment''

“Please be aware that as of SAP S/4HANA 2027 the embedded deployment option will be the only available deployment option”. This effectively makes embedded deployment not just the recommended approach, but the standard going forward for SAP Fiori in SAP S/4HANA landscapes.

In this context, we’re excited to share the updated “Moving from Standalone to Embedded Deployment in SAP Fiori for SAP S/4HANA” guide, based on SAP S/4HANA 2025, which becomes even more relevant for customers planning or progressing through this transition.

The guide was first published in October 2019 (version 1.0). It has since evolved through multiple updates, including version 2.1 in December 2024, which focused on SAP Fiori for SAP S/4HANA 2023. The most recent version, 3.0 released in March 2026, is based on SAP Fiori for SAP S/4HANA 2025.

Moving from Standalone to Embedded Deployment in SAP Fiori for SAP S/4HANA (V3.0)

This latest update (Version 3.0, March 2026) has been driven with strong input from SAP product experts, including Peter Persiel (peterpersiel) , whose contributions have helped shape the guide based on real-world customer experiences and evolving SAP Fiori architecture.

So what actually changed?

This blog highlights the latest updates and key enhancements introduced in the 2026 version of the guide (Version 3.0 March 2026), helping you quickly understand what’s new, what’s improved, and what to consider for your projects going forward.

Why this update matters?

Version 3.0 of this guide is an important refresh. It reflects:

Alignment with SAP S/4HANA 2025 and SAP Fiori for SAP S/4HANA 2025, and important announcements planned in the future releases of SAP S/4HANA.
The continued evolution of SAP Fiori architecture and activation tooling, especially in embedded deployments
Lessons learned from more recent customer implementations, translating real project experience into more practical guidance
Increased focus on clean core, maintainability, and lifecycle management

Why do you need this guide?

This guide is essential for SAP S/4HANA customers currently running or considering a hub/standalone SAP Fiori Front-End Server deployment, and who are planning or preparing for a transition from a hub/standalone SAP Fiori Front-End Server deployment to an embedded deployment.

It provides clear, structured guidance to support a smooth transition, covering both technical and practical aspects of the move. Whether you are upgrading your SAP S/4HANA system or proactively aligning with SAP’s long term architectural direction, this guide helps you plan and execute the transition with confidence.

From planning, installation, and configuration to post migration validation and optimisation, it brings together everything you need to successfully move to an embedded SAP Fiori deployment.

It helps you:

Understand the benefits of moving to embedded FES deployment
Know the right time to make the shift
Navigate technical prerequisites, sizing, and system considerations
Simplify the migration process with actionable steps, tools, and examples
Ensure a seamless experience for users by resolving common issues
Minimise disruptions by retaining user personalisation and role assignments
Gain tips on how to enhance usability and performance

By following this guide, you can align with SAP best practices and unlock the full potential of SAP Fiori embedded deployment.

What's in it / What's new?

Simplified architecture in SAP S/4HANA 2025
Some Front-end components are now part of the core platform, reducing system complexity
More practical, end-to-end guidance
Covers not just migration steps, but also planning, validation, and long term operations
Better control of custom content migration
Helps define what custom content to move and adds validation after migration instead of blindly transporting everything
Improved transport strategy guidance
Real world options for handling transports depending on your landscape and ongoing development activities
Extended launchpad configuration coverage
Includes transport of launchpad parameters, plug ins, and configuration settings beyond just apps and catalogs
Built-in validation step
Dedicated step to validate custom content in the embedded system after migration
Enhanced personalisation migration
Clear guidance using tools like /UIF/MIGRATE_FES_PERSO to retain user settings, homepages, and UI changes
Explicit system alias and RFC adjustments
Clear steps to adjust system aliases and RFC destinations post migration
Smarter SAP Notes handling
Explicit step to identify and implement missing SAP Notes after migration, avoiding common post go live issues
Stronger focus on business roles
Additional step to review and optimise business roles after migration in line with modern Fiori design

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA topic page

SAP User Experience in SAP Cloud ERP 2602

2026-05-12T15:10:04.652000+02:00

The SAP Cloud ERP 2602 release (fka SAP S/4HANA Cloud Public Edition) has been shipped on January 14, 2026.

With every release update, our goal is to make your interaction with the system more intuitive, efficient, and intelligent. The 2602 release is a significant step forward, focusing on consistency, AI-powered assistance, enhanced personalization, and on-the-go mobility. Let's dive into the highlights in the area of SAP User Experience!

The new shell bar is here to stay

Remember the redesigned shell bar we introduced as an opt-in feature back in 2508? Based on positive feedback and our drive for a unified experience, it is now activated by default in the 2602 release.

The new shell bar provides:

An updated user menu: With a larger user image and more space between items, finding what you need is easier than ever. We've also moved "Settings" to the top and separated "Sign Out" for quicker access.
Redesigned notifications: A simplified, more pleasing design with easy sorting (by date or importance) and simple grouping (Today, Yesterday, etc.) helps you stay on top of your tasks without the clutter.

Important note for a smooth transition: As this is now the default, we strongly recommend you check any test automation or RPA scripts you have, as they may need to be adapted to the new user menu structure. For this release only, you can temporarily opt-out via the "Activate New Features" switch (feature `/UI2/SHELL_BAR_TOGGLE`), but please plan to adapt your systems, as the opt-out option will not be available from the 2608 release onwards.

Direct app launch in the SAP Fiori launchpad

We've heard you! Many of our experienced users coming from the SAP GUI world missed the ability to quickly launch an application using its transaction code. I'm delighted to announce that you can now launch apps directly from the SAP Fiori launchpad search bar using the app ID or transaction code.

For power users, this restores a familiar and efficient navigation pattern, lowering the barrier for those transitioning to SAP Fiori, as they can combine new UX principles with known shortcuts.

Enhancements to My Home

My Home continues to evolve as your central, personalized starting point. In 2602, we're giving you more control and enhancing communication:

Required reading for news: Administrators can now mark important news articles, such as new policies or critical process changes, as "required reading." Users must acknowledge these articles, which helps ensure compliance and consistent knowledge across the organization.
Greater layout control: You can now choose to hide the entire "News" or "Pages" sections on your My Home screen. This allows you to reduce clutter and tailor your homepage to display only the information and tools that are most relevant to your role, boosting your personal productivity.

An intelligent assistant for your daily tasks

Artificial intelligence is at the heart of the intelligent enterprise, and we're embedding it directly into your user experience.

The 2602 release distinguishes between base and premium AI features:

Base features (free of charge): After signing the acceptance of SAP AI terms for base AI-assisted features in SAP S/4HANA Cloud Public Edition, you gain access to features like AI-assisted enterprise search, easy filter, and smart summarization.
Premium features (requires license): With the appropriate licenses (like SAP AI units and package Joule Premium for financal management), you can unlock advanced capabilities. In 2602, we are excited to announce the general availability (GA) of AI-assisted smart personalization of applications in My Home and AI-assisted error explanation.

Furthermore, we are continuing to beta test AI-assisted task automation, which allows users to create "smart helpers" to automate repetitive activities. This powerful tool keeps the user in the loop while dramatically improving efficiency. If you're interested in shaping the future of AI in our products, I encourage you to sign up for our beta testing program here: https://influence.sap.com/sap/ino/#campaign/4086

Fast with SAP Fiori

We’re thrilled to announce the launch of our brand-new video series, "Fast with SAP Fiori"! The first three episodes are now live and ready to accelerate your SAP Fiori journey.

What’s coming:

Complete 10-episode series covering essential SAP Fiori concepts
Soon available on YouTube for easy access
Multi-language support including English, German, French, Spanish, Portuguese, and Italian

Ready to dive in? Check out the first three episodes now, and stay tuned for the complete series launch!

Video 1 - https://dam.sap.com/mac/u/a/ce7RMfU?rc=10&doi=SAP1286910
Video 2 - https://dam.sap.com/mac/u/a/Ef5HP5X?rc=10&doi=SAP1286912
Video 3 - https://dam.sap.com/mac/u/a/558Yrrv?rc=10&doi=SAP1286922

Productivity on the go: SAP Fiori for mobile optimization

In today's flexible work environment, being productive on your smartphone is essential. That's why we've introduced SAP Fiori elements mobile phone optimization. This delivers a mobile-first experience by providing a compact, modern, and high-performance framework for key mobile scenarios. We've simplified navigation and reduced complexity by focusing on what's essential for users on the move, allowing you to get business done anywhere, anytime. Feel free to sign up for our beta testing program here: https://influence.sap.com/sap/ino/#campaign/4090

A single front door: Introducing SAP Start (SAP-managed)

Imagine a single, unified landing page for all your SAP Cloud ERP products. That is the vision for SAP Start, and with the 2602 release, we are introducing a new SAP-managed version.

This means you can activate it directly from SAP for Me with no additional implementation effort. In its initial release, SAP Start provides seamless, single sign-on access to SAP Cloud ERP, SAP SuccessFactors, SAP Concur, and SAP Sales Cloud Version 2. This is just the beginning, and we are eager for your feedback through our Early Adopter Care program to shape its future.

Your voice matters: Get involved!

Many of the features in this release, including the highly-requested direct app launch, originated as suggestions on the SAP Customer Influence Portal (CIP.) This is proof that your feedback directly shapes the future of our products.

I encourage you to explore these new features, see how they fit your business needs, and continue to share your insights with us through the SAP Community and the Customer Influence portal.

The 2602 release truly elevates the SAP User Experience, and we can't wait to see how you leverage these innovations to run your business better.

📽️ Watch the replays of our SAP Cloud ERP 2602 Early Release Series!

From January 12-16, we hosted a series of 22 expert-led live sessions to highlight the exciting innovations shipped with the SAP Cloud ERP 2602 release. Missed the live sessions? We've got you covered! Take advantage of the entire series or pick and choose the sessions most relevant to you. You will find the recording and presentation for SAP User Experience as well as 21 other topics of interest. Don't miss this chance and watch them on demand–anywhere, anytime.

🔎 Find all our assets

We at Cloud ERP and SCM Product Success offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

Sapphire 2026. The future of UX is here. Are you ready for an AI -powered world?

2026-05-14T16:20:03.984000+02:00

Sapphire 2026 accelerated SAP’s pivot to AI. Most of the keynote demos were heavy on AI, including introducing new engagement layer experiences to complement the existing application experiences. The magic of the engagement layer is that it allows you to interact with your ERP system in a conversational way, starting with your intent and the system will generate an interface based on the context of your request. While this might represent a more natural way to work, it also represents a major change to how people have been working with SAP applications for the past few decades.

The new engagement layer lets you interact with SAP in a conversational way.

I had the opportunity to see many deep-dive sessions that explained the new UX and how we expect people to work with it. More importantly, I spoke with many customers and partners about their reaction to the way we are moving. Generally, people are excited about the direction we are going and having more automation to free up time for deeper thought and analysis, but they are concerned about trusting AI to do things that might have significant business impact. While Joule Work will certainly be a game changer for many, the big open question is how to get there. As with all IT transformations, it will involve a combination of changes across people, processes, and technology.

Embedded AI meets customers where they are

The first session that I presented was on “Creating better user experiences with AI-powered SAP Fiori apps ASUG.” I started out by talking about overcoming usability challenges with AI and then did a live demo of around 10 cool productivity features. What’s unique about the embedded AI capabilities in SAP Cloud ERP is that it is built into the existing interfaces that people know, so it allows them to go through their work more quickly by using AI to search, summarize, and enter data.

There are many AI-powered features that make people more productive when using SAP Cloud ERP.

The slides from the session (PUX1228) include links where you can see short recorded demos of these features. These capabilities are available for SAP S/4HANA Cloud Public Edition. Some of them are coming to private cloud in upcoming releases.

Some questions that customers asked that might be of general interest:

Does the engagement layer replace SAP Fiori? No – the application experience and engagement layer experience are complementary. They will coexist for the foreseeable future. (Thanks for the question, Tony)
Does the engagement layer use SAP Fiori elements? The answer here is more nuanced. We use the OData metadata that is used by Fiori elements to get the SAP S/4HANA data to render high quality cards in the engagement layer.
So, the engagement layer is independent of the Fiori apps themselves. The engagement layer does not call the Fiori apps for the data, but it uses the same underlying data source, which are the OData services and annotations. (Great question, Kelly)

Lots of people were interested in having a better user experience with AI assistance.

Fear, optimism, and the AI Skills gap

My other presentation was a “community conversation” in the ASUG Hub. My colleague, Nicole Smythe and I facilitated the session along with Liz Tuckwell and Nadalee Williams from ASUG. The goal was to collect ideas on AI adoption from the attendees and equip them with information so they could create a 90-day plan to turn their thoughts into action and move forward with AI in your organization. After providing an overview of Joule Work, we broke into teams and people discussed barriers to implementing AI in their organizations and how they overcame them.

Top problems that the audience identified included:

Data. How to get the data clean so any AI agents can work properly and consistently. Most people know they need to fix their business processes and clean their data before they can benefit from AI.
Governance. People see the need for IT to manage this centrally. Currently, many innovative teams want to get started with AI and are doing things on their own without corporate oversight. We saw this situation a decade ago when some business managers purchased cloud services for sales or HR or other domains if they did not receive sufficient support from their IT teams.
Cost. How to meter AI consumption and allocate charges to different users.
AI Expertise. Upskilling teams on AI and its capabilities. Currently, this is a side job for most people, so they are not putting enough focus on this. Once company had a rotation program where top developers could allocate 50% of their time to learning AI topics and then bring those skills back to their teams.
Talent management. With fewer entry-level workers or people doing repetitive jobs, it is harder to identify the best employees, so you can focus on retention and building a leadership pipeline.

Participants discussed how to overcome barriers to AI adoption.

Other interesting sessions on AI, UX, and AI+UX

Most of the other sessions I attended were on AI, UX, or their intersection. Hearing the questions people asked and what they talked about afterwards will be helpful in refining our agenda for our next SAP Connect Day for UX, which is in Palo Alto on June 11. We’ll go deep on our UX strategy and share some new functionality, both released and unreleased. There will be two hands-on exercises, one on building applications and the other building Smart Helpers (currently in beta).

Katja Zoch and Sebastian Steinhauer had a session on how to extend SAP S/4HANA Cloud while keeping a clean core. They focused on what is clean core, why its important, and how to extend your core ERP system using clean core principles.
Chris Hoffmann had several sessions on the show floor. They all focused on different dimensions of the AI-powered user experience in the SAP Business Suite. One was a broad survey of functionality, another focused on AI-assisted task automation, and the other talked about roadmap items. All showed how AI adoption is on the path towards human‑supervised autonomous ERP.
Tom Reiss presented on SAP Fiori in action, highlighting how modern UX helps users get their work done more easily and efficiently. He also had a roadmap session with Christina Salwizek featuring web and mobile innovations that are on the horizon.
Sophia Levens had some great sessions on the new Joule user experience, focusing on both how it works and the implications for users. She also had a strategy-focused talk with SAP’s chief designer officer, Arin Bhowmick, where they explored where user engagement and enterprise UX are headed.
Bert Schultz and Esther Vrieze spoke about different ways to migrate to SAP S/4HANA and the relative benefits among the different approaches.
Maura Hameroff and Rudi Hois talked about SAP Cloud ERP Private and the many innovations that customers can expect to see in upcoming releases.

We held our SAP Fiori Development Roundtable live from the show

To add a little extra energy to our already lively discussions, I joined my co-host Sebastian Werner live from the show floor. We spent lots of time talking about Joule Studio and how it fits with our existing development tools. If you want to join the next monthly call, please register.

AI vibe from across the conference

While the sessions are a great way to learn about hot topics, the best way to hear about how customers are using our solutions and what they are planning is in the hallways, food areas, UXpresso Café (successor to the Fiori Café), happy hours, and demo pods. The questions after sessions are also revealing. This year, the customers I spoke to were concerned about:

How the new engagement layer (Joule Work) fits with SAP Fiori
How to get started with AI, especially in private cloud and on-prem environments
If their existing Fiori apps will continue to work (yes!) and if they should continue to build new Fiori apps (yes!)
All the topics listed above from the ASUG community conversation (data, governance, cost, AI skills, and talent pipeline)

Next steps

Perhaps you are still digesting all the announcements from Sapphire and figuring out their impact on your business. To help you prepare for the future, consider discussing the following questions with your team.

What business problems are most pressing and can benefit from automation? How will we meter the costs, set appropriate limits, and measure the return on investment?
Is our data clean, consistent across different parts of the business, ready to train the AI system, and be part of automated workflows? How much autonomy are we willing to give agents and what is the best way to supervise / manage / audit their activities?
How will we integrate AI into our SAP landscape? Are we using SAP’s embedded capabilities, Joule, the new engagement layer, or external AI-powered apps running on SAP data (subject to the API policy)?
How will we address change management with our business users?
How will we manage AI governance, risk, and security? Using SAP’s AI simplifies the answer to this question as we cover much of this, but you still need robust AI policies in your organization

If we did not meet at Sapphire and you are interested in joining the conversation about SAP Fiori application development and how AI makes it better, faster, and cheaper, please join our monthly SAP Fiori development roundtable group or sign up for our bi-monthly newsletter.

If you are in the Silicon Valley area or can fly there on June 11, please join us for SAP Connect Day for UX. We'll go deeper into all the UX and related AI topics listed in this post.
https://events.sap.com/us-ux-innovation-day-siliconvalley-2026/en_us/home.html

For the UX Foundation team, Peter Spielvogel.

SAP UX Update: The New Joule Work Engagement Layer Experiences

2026-05-14T20:29:10.769000+02:00

What is Joule Work, and what does it mean for you? What do the new Joule Work engagement layer experiences mean for existing application experiences? How can you try it out? Read on to get an overview of Joule Work and answers to these questions.

What is Joule Work?

Joule Work provides an AI-based user experience that transforms how work happens. With Joule work, people express what they want to accomplish, and Joule surfaces the right insights, automates routine work, and coordinates AI agents across systems to achieve it – all in one dynamic workspace. It acts as an engagement layer that spans across SAP products and beyond, and coexists with current experiences provided by pre-defined application UIs.

It represents a new way of interacting with business systems, since it provides:

One single place where a user can get tasks done, rather than the traditional app-centric interaction model, where users need to navigate to different applications or even to different products.
An intent-driven, situational experience, where users state their intents in natural language and the system builds on the fly accordingly, taking the current business and user context (the current situation) into account: fetching data, triggering AI agents, and visualizing the outcome appropriately.

Figure 1: Joule Work experiences: Conversations, Spaces, and Develop. Alt Text: The image shows 3 screenshots, one each for the three experiences. The top of the image has a heading “Joule Work”, above a row with five attributes: Dynamic, Proactive, Agentic, Intent-based, Omnipresent.

Joule Work provides these experiences:

Conversations: this experience allows people to express intent and explore what they want to accomplish through dialogue with Joule. It is an AI-powered chat supporting role-based intents, multiple conversation threads, with type-ahead, auto-suggestions and multi-facetted types of responses (text, tables, charts etc.). Joule brings together guidance and outcomes from across SAP and third-party systems. Conversations can also act as an entry point to Spaces for more complex workflows.
Spaces: provides flexible AI-generated spaces that dynamically adapt content based on user intent and context, for dealing with simple as well as complex tasks and issues. Each space is composed in real time to bring the right data, tools, and context together for a specific goal, allowing people to work in an environment that adapts to their present goal, instead of navigating applications and their pre-defined UIs.
Develop: this experience is provided by Joule Studio, enabling developers to vibe-code, test and deploy AI agents, applications, and automations across SAP and third-party systems. Joule Work provides a convenient entry point to Joule Studio for developers and business users alike, giving them an AI-powered user experience for pro-code and low-code tools.

To get a better idea of these experiences, have a look at Joule Work in action:

Click on the image to start the video.

Joule Work mobile app

The Joule Work mobile app provides Joule Work Conversations and Spaces for mobile phones and tablets. Figure 2 shows some examples.

Figure 2: Joule Work mobile app, examples of Conversations and Spaces. Alt Text: two pairs of iPhone images. On the left Joule Work Conversations, showing a start and a screen listing some return orders and a user prompt. On the right a screen with text “Create a new space” and a user input “Create a space to sow my open customer returns for BikePro”, and a screen showing the resulting space with a chart, some cards with recommended tasks, and a return order analysis.

Find out more here.

Joule Work mobile app is here!

What are the benefits for businesses and their users?

Businesses expect that the new AI/agentic, intent-driven way of working that is taking hold across the industry is ushering in a new era of user interaction and user experience, that will bring them gains in productivity and data quality, along with better business insights and outcomes, while saving training costs and reducing user-support costs.

Joule Work from SAP has an ingrained understanding of the customer’s business processes: hence it is best placed to deliver on the above promise. It can provide experiences that bring together the right data and services from across our applications to guide users from initial intent to a successful outcome.

It helps users get their work done faster, more easily, and with better outcomes, by:

Providing one place to get their work done, so they don’t have to navigate to many different applications and products, and don’t have to navigate through layers of application UIs, thus reducing the number of clicks and interactions significantly.
Allowing users to state their intent in natural language with a conversational interface, then triggering the relevant actions to achieve their intent, and showing the outcome(s) in a personalized way, tailored to the user’s needs.

Which target groups of users and use cases is Joule Work meant for?

Business and technical users. The goal is to help all our customer’s SAP users get their work done more easily, focusing on outcomes, so it is not limited to specific target groups.

The Joule Work Develop experience is provided by Joule Studio. Find out more about the new version of Joule Studio in this news article:

Announcing New Joule Studio for Enterprise Scale Agentic Development.

What does this mean for existing UIs and SAP Fiori apps?

Existing SAP products and applications built with SAP’s UI technology stack, as well as other apps in our portfolio, will continue to progress with their roadmap and planned product strategy. Joule Work has no impact on existing UIs, instead it complements them. Customers will continue to get the benefits from existing applications and their investment is protected.

Joule Work provides an additional option for users to interact with the system. Wherever they find that it helps them get tasks done more easily and/or with better outcomes, they are likely to do those tasks with Joule Work. Wherever they feel that their familiar, pre-defined applications are better suited to a task, they will continue using them.

This means that SAP delivers two kinds of experiences:

Application experiences (from SAP Cloud ERP, SAP SuccessFactors, SAP Analytics Cloud, etc.): SAP and customer-built transactional and analytical application experiences.
Engagement layer experiences (Joule Work experiences): AI-native, agentic, and generative experiences that help users interact with and orchestrate work across those applications.

Our users are used to application UIs and pre-defined navigation paths, how to manage the transition?

The existing product home pages and cross-product entry points such as SAP Build Work Zone and Joule Work mobile app (formerly called SAP Mobile Start) continue to be available for providing pre-defined as well as customer-defined pages and navigation menus. Similarly, the existing applications continue to be available, with their application experiences.

Users working in the web browser can open Joule Work from Joule and hence start getting familiar with the new way of working. Since the new experience co-exists with the current experience it will be easy for users to adapt and adopt. We expect the transition to be user-led, in that they will choose whichever experience helps them get specific tasks done more easily and/or with better outcomes.

If users are already familiar with popular consumer applications such as ChatGPT, Google Gemini or Claude Sonnet, then they will be able to build on this to leverage the next generation user experience provided by Joule Work, with the new ways of interacting.

Does it complement or does it replace existing solutions such as SAP Start, SAP Build Work Zone, and SAP Mobile Start?

It complements them. The existing solutions allow customer administrators to pre-define layouts, content and navigation options, which helps users access applications and information using familiar pages, menus and links. It makes it easy for them to understand the site and feel comfortable using it in their daily work. This is something that benefits all users but is especially helpful for users new to the system to get started quickly and get familiar with their work environment.

SAP Mobile Start has been rebranded to Joule Work mobile app, accompanied by a new app icon and an updated user experience. For customers previously accessing Joule within SAP Mobile Start, the Joule entry point has transitioned from the diamond in the header bar to a full-screen interface to be accessed via the tab bar. All core functionality and features remain unchanged, ensuring continuity for both customers and end users with no disruption to existing workflows. In addition to the core functionality, it provides the Joule Work engagement layer experience for mobile devices. Find out more here:

SAP Mobile Start - Rebranding of the app, enhanced Joule and improved single sign-on functionality.

For SAP Cloud ERP Private: would we need to go to SAP Fiori (implement SAP Fiori launchpad), or can we skip it and go to Joule Work directly?

You would need to implement the SAP Fiori launchpad for Joule Work to work with SAP Cloud ERP Private: they use the navigation and authorization information defined by customers in the SAP Fiori launchpad to access the system. Also, Joule only runs in the browser on desktops and is launched from the launchpad. Similarly, if users navigate from Joule Work to applications, this navigation will be to browser-based applications running in the launchpad.

How can partners and customers extend standard SAP functionality for Joule Work – as a key user or as a developer?

The established programming model for creating extensions continues to be valid. Joule Work accesses OData services and their meta-data (amongst others) and hence will also access extensions or custom OData services that have been developed according to the SAP BTP Developer’s Guide.

Using Joule Studio or SAP Build is the way to build extensions and agents, for Joule Work as well as for pre-defined applications.

If you are building new applications, follow the SAP BTP Developer’s Guide, and use Joule Studio or SAP Build. You can build agents on top of the APIs you create, and Joule Work will access the OData services and meta-data of your new applications. The Fiori apps you create using SAPUI5 / SAP Fiori elements will allow users to use your new functionality using apps with pre-defined UIs, an experience that they are familiar with. Also, users can use these UIs to confirm that what was done by Joule Work is indeed correct and hence build trust in it.

What is available today (Sapphire 2026)

As described above, this first version of Joule Work provides Conversations, Spaces, and Develop, with the Joule Work Develop experience being provided by Joule Studio. The Sapphire scope:

Supports integration to SAP S/4HANA Cloud Public Edition and SAP SuccessFactors.
Supports exactly one SAP S/4HANA Cloud Public Edition, you cannot connect to more than one.
Does not support document grounding in Joule.

How can customers get Joule Work, and what are the pre-requisites?

If you are interested, you can sign up to the limited Early Adopter Care (EAC) program. The pre-requisites for this at the time of writing are as follows:

Joule needs to be SAP-managed.
- New SAP-managed Joule instances are supported
- Existing customers with customer-managed Joule would need to transition to SAP-managed Joule.
Available only in specific regions: USA and EU.

Final words

I hope you are as excited as I am about the huge potential these Joule Work experiences have for helping our users get their work done faster and more easily, with better outcomes. It will be interesting to observe how people in various roles adopt this new way of working, and how fast they adopt: for which tasks do users prefer to use Joule Work, for which ones do they continue to prefer application experiences – and why?

If you want to dig a bit deeper, have a look at how we are designing these new experiences, and see how we are evolving the SAP Design System for AI-driven UX:

If you want an overview of interesting UX shown at Sapphire in Orlando this week, have a look at Peter Spielvogel's nice summary:

Sapphire 2026. The future of UX is here. Are you ready for an AI -powered world?

SAP Fiori for SAP S/4HANA - Technical Catalog Migration – Easier Than Ever with New Features!

2026-05-18T15:59:18.768000+02:00

As UX specialists in the SAP S/4HANA Regional Implementation Group and the Fiori Launchpad ABAP team, we often get to work with customers keen to leverage the significant capabilities of SAP Fiori. Are you still using the Fiori Launchpad Designer to maintain your SAP Fiori content? If so, it's time for some good news: migrating to modern tools just got a whole lot easier with SAP S/4HANA 2025.

Why This Matters to You

In recent years, SAP Fiori Launchpad Designer has been slowly deprecated and replaced with new tools. Refer to:

With technical catalog migration, you can make your SAP Fiori content future-proof, clean-core compliant - and benefit from improved tools.

About this Blog

The tool for technical catalog migration - transaction /UI2/MGR_TC - is available from SAP S/4HANA 2023 FPS01 and is covered in these excellent blogs:

This blog builds on these earlier posts by sharing some exciting news: SAP S/4HANA 2025 brings new features that make technical catalog migration easier and more flexible than ever before. We cover the following:

1. Recap of Technical Catalog Migration
2. The Challenge: What Held Customers Back
3. The Game changer: Partial Migration
4. What Happens Behind the Scenes During a Partial Migration
5. SAP S/4HANA 2025: Partial Migration - Example
6. When To Migrate
7. Frequently Asked Questions
8. Prerequisites & Limitations

Refer to:

1. Recap of Technical Catalog Migration

In our new launchpad content model, tiles and target mappings are still being used in technical catalogs, but the way of storing them has changed:

Previously, tiles and target mappings were loosely coupled.
Now, with Launchpad App Descriptor Items (LADIs), they are closely coupled as a pair.

To make your launchpad content future-proof, technical catalogs created with the deprecated SAP Fiori Launchpad Designer must be migrated to the SAP Fiori Launchpad App Manager (transaction /UI2/FLPAM).

Tiles and target mappings / LADIs

Technical catalogs created in the deprecated Fiori Launchpad Designer:

NOTE: Technical catalogs created in the Fiori Launchpad Designer are only are visible in App Manager, only after migration.

Migrated technical catalogs and catalogs created in Launchpad App Manager:

Now the technical catalogs are maintained in App Manager. They are also visible (read-only) in the Fiori Launchpad Designer

Migrated technical catalog

2. The Challenge: What Held Customers Back

Until now, the migration tool required that your technical catalogs are perfect before migration. If a catalog had some apps that could be migrated and some that couldn't, the entire catalog was marked as "Not Ready for Migration." This meant you had to clean up everything before you could start the migration. The migration tool has always provided detailed error descriptions and suggested fixes, but fixing all errors could still be a time-consuming process.

Here's what could block migration:

Tiles or target mappings with configuration errors
Mixed catalogs, containing originals and references
Catalog names outside the customer namespace for workbench objects
Content not following best practices

3. The Gamechanger: Partial Migration

With SAP S/4HANA 2025, we have introduced a feature that makes your life easier: partial catalog migration.

Now you can migrate the apps that are ready, while keeping the problematic ones in the old format temporarily. Affected catalogs have the status: "1c Ready for Partial Migration."

Additional bonus: if your old catalog name doesn't meet current naming requirements, you can correct the name during migration. The tool automatically updates all references, so nothing breaks in the process.

Partial migration

Note: The partial migration transfers all your translations automatically – as long as they're in the same system. Maintaining translations separately? You have two options:

Retranslate the content in the new Fiori Launchpad App Manager-based catalog after partial migration, or
Clean up your technical catalogs first and use the full migration path available from SAP S/4HANA 2023 FPS01.

What this means

You're no longer blocked! Migrate what you can today and handle the exceptions separately. Apps that can't be migrated stay in the old catalog, while everything else moves to the modern tools where you can maintain them more easily.

Already have clean catalogs that follow best practices? No problem! The 'Full Migration' option from SAP S/4HANA 2023 FPS01 is still fully supported in 2025. Refer to the blogs below:

4. What Happens Behind the Scenes During a Partial Migration

Before migration: Let’s look at a technical catalog Z_OLD_CATALOG_TC (created in the Fiori Launchpad Designer) that stores both original and reference tiles and target mappings (i.e. a mixed catalog).:

During migration: This is shown below in steps 1 and 2.

Step 1: Original tile and original target mapping are combined into a newly created LADI (launchpad app descriptor item) in an existing or new Launchpad App Manager based catalog Z_NEW_CATALOG_TC.

Step 2: In the old catalog Z_OLD_CATALOG_TC, convert the Fiori Launchpad Designer based original tile and target mapping into references pointing towards the newly created LADI from step 1. This prevents the broken references in our launchpad content. (Note: The picture below shows a different catalog name, where special characters have been replaced with compliant characters according to naming conventions.)

Before / after migration

After the migration: The new catalog Z_NEW_CATALOG_TC can be seen in the SAP Fiori Launchpad Application Manager

After migration

The Fiori Launchpad Designer based catalog Z_OLD_CATALOG still exists and may have the following statuses:

- "Not Ready" – This happens if some tiles/target mappings in the catalog could not be migrated.

Reference tiles and target mappings are the same as before the migration.
Originals that could be migrated have become references.
Original apps that do not conform to the requirements in SAP Note: 3397026 - SAP Fiori Launchpad - Technical Catalog Migration - Content Cleanup Risks stay as originals. These cannot be migrated without manual cleanup activities. Check their status for detailed errors. If you still need these apps, clean them up and migrate them automatically. Alternative: if you recreate the apps manually in App Manager, make sure to adjust your Business Catalogs to point to the new apps.

- "Not Relevant" - all originals have successfully been migrated and only references are left (known as Business Catalogs)

Summary: You're no longer blocked by unmovable apps. Migrate what you can and handle the rest separately!

5. SAP S/4HANA 2025: Partial Migration - Example

Let’s look at a real-life catalog that is not perfect and requires partial migration, ZCL_MGR_EXAMPLE_02_TC. Besides some originals, it also contains a reference, and it needs assignments of tiles to target mappings.

Migratable:
- Intent DevelopmentObject-translate
- Tile only
Migratable, but manual tile-target mapping assignment required:
- Intent DevelopmentObject-connect: 1 tile matching 2 target mappings
- Intent DevelopmentObject-map: 2 tiles matching 1 target mapping
Reference, no need to migrate:
- Intent FLPBusinessCatalog-manageCrossClient

Partial migration steps

1. Run transaction /UI2/MGR_TC, enter your technical catalog name (ZCL_MGR_EXAMPLE_02_TC here) and click on 'Execute':

Run transaction /UI2/MGR_TC

NOTE: The selection screen of transaction /UI2/MGR_TC works as a filter to show only the technical catalogs that you want to work with. You can use ‘Z*’ (or your naming convention) to get an overview of your custom technical catalogs.

2. Select Migration Status as '1c Ready for Partial Migration':

Status 'Ready for Partial Migration''

3. Now you can see the technical catalog ZCL_MGR_EXAMPLE_02_TC, along with a list of statuses for each tile / target mapping.

4. Select the technical catalog (in this case ZCL_MGR_EXAMPLE_02_TC) and click 'Start Partial Migration'.

Start Partial Migration

5. Here, we have selected to create a new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC. Choose an existing catalog or create a new one and click on the green tick.

NOTE: Please follow your naming conventions for technical catalogs, you do not need to use a keyword like 'MIGRATED', it is used here purely for illustration purposes.

Select technical catalog6. Depending on the content of the catalog, you see a screen for pairing tiles and target mappings. Normally there is one tile matching to one target mapping with the same semantic object / action and parameters, in this case the tile and target mapping assignment screen is skipped.

If there is more than one tile matching a target mapping or vice versa, like for our example catalog, user interaction is required.

What you see:

A list of intents (on the left) that needs assignment or are missing a default tile
Only intents with unclear tile-to-target-mapping connections are shown by default. Click ‘Show All Intents’ in the toolbar to include intents that could be resolved automatically.

Key difference from before migration and after migration:

Before (in the Fiori Launchpad Designer): Tiles and target mappings are loosely connected via matching intents.
After (in Launchpad App Manager): Tiles and target mappings are coupled entities with the target mapping taking the lead.

Steps you need to complete:

a) Process all intents marked Assignment Needed (marked with a red 'X' in the status column below). See Step 6.1

b) Assign each tile to a matching target mapping. See Step 6.2

c) If multiple tiles match one target mapping, select which tile is the default. (Any additional tiles will be labelled as "Additional Tiles".).See Step 6.3

d) Click Start Partial Migration. See Step 6.4

6.1 Click on the first intent in error (in the example, it’s DevelopmentObject-connect, with 2 target mappings matching 1 tile) The status text of the tile tells you to ‘Assign to target mapping’, so select the correct target mapping and click on Assign to Target Mapping.

6.2. Now you see a green tick for both the intent and for the tile: tile and target mapping have been paired, and all uncertainties have been resolved.

6.3 Now select the remaining intent, DevelopmentObject-map (1 target mapping matching 2 tiles) and the status text of the target mapping tells you to ‘Set default tile’. Select the correct tile and click on Set as Default Tile.

6.4 Now you can see that all intents have the green tick and that a Default Tile has been chosen. Click on Start Partial Migration:

7. When prompted, enter a suitable development package and select a transport (if required). In this example, we are saving the new standard technical catalog as a Local Object (Package = $TMP).

8. Now you can see the migration of the technical catalog to ZCL_MGR_EXAMPLE_02_MIGRATED_TC has been completed successfully. It is displayed in the list of catalogs with status ‘4 Migration Finished’. Select the technical catalog and click on Open SAP Fiori Launchpad App Manager.

9. Your newly created technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC is displayed in SAP Fiori Launchpad App Manager, where you can view the corresponding LADIs.

10. The old Fiori Launchpad Designer Catalog ZCL_MGR_EXAMPLE_02_TC is now in status 'Not Relevant for Migration'. It is now a business catalog that contains only references. Below you can see this in both the migration tool (transaction /UI2/MGR_TC) and the Fiori Launchpad Designer:

Consider the deletion of the old Fiori Launchpad Designer technical catalog if you are sure that it is not used anymore.

11. For the end user, the Fiori launchpad will look the same, before and after migration. Below, you can see a sample screenshot of how this new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC looks in the SAP Fiori Launchpad:

6. When To Migrate

If you’re already on release SAP S/4HANA 2025, it’s easy: migrate as soon as possible.

If you’re on release SAP S/4HANA 2023 FPS01+, it depends on your content. Run transaction /UI2/MGR_TC to check if any catalogs need special attention and what issues need to be resolved:

Are all catalogs in status ‘Ready for Migration’, or ‘Ready for Migration – Assignment Required’? Great. Migrate on SAP S/4HANA 2023 FPS01.
Are some of your catalogs in status ‘Not Ready for Migration’? Check the list of migration issues to see how much manual rework would be required. You can minimize the effort by upgrading first and running the migration on SAP S/4HANA 2025.
Do you need to rename your technical catalogs? This is only possible with the partial migration in release SAP S/4HANA 2025. Upgrade first and run the migration on SAP S/4HANA 2025.

7. Frequently Asked Questions

Question: Can I migrate client-specific catalogs?

- Answer: Yes. Note that migration will transform them into cross-client catalogs, for better reuse and because the resulting launchpad app descriptor items are cross-client workbench objects.

Question: Does the technical catalog migration provide any options for moving cross-client catalogs to the client-specific layer?

- Answer: No. Cross-client and client-specific technical catalogs are always moved to cross-client. This is because LADIs are always cross-client.

Question: Do I have to change my authorizations after upgrade?

- Answer: No authorization changes are required. References and links in your business catalogs stay intact, no rework is required

Question: Can admins see the new technical catalog in the old Fiori Launchpad Designer after migration?

- Answer: Yes, admins can see the new technical catalog in the old Fiori Launchpad Designer, but only as read-only (they can view it but not change it). To edit the technical catalog, administrators must use Launchpad App Manager tool instead.

Question: What object directory entries are involved?

Answer:

Technical catalogs created in the Fiori Launchpad Designer - Object Directory Entry R3TR / UIAC
Technical catalogs that have been migrated have Object Directory Entry R3TR / UIAD

After migration, SAP recommends using the following tools:

Launchpad App Manager – for technical catalogs
Launchpad Content Manager – for business catalogs

8. Prerequisites & Limitations

Question: Are there any prerequisites, or any limitations concerning the content that can be migrated with release SAP S/4HANA 2025?

Check SAP 3397026 - SAP Fiori Launchpad - Technical Catalog Migration - Content Cleanup Risks for prerequisites.
Apps with system aliases other than LOCAL are not supported in Launchpad App Manager yet.

Recommendation: Keep target mappings with other system aliases (plus tiles with the matching intent) in the deprecated Fiori Launchpad Designer.

Custom tiles are in maintenance mode. They are not supported in Launchpad App Manager, only by the deprecated Fiori Launchpad Designer.

Recommendation: Consider replacing your custom tiles with standard tiles. If that is not possible, keep your custom tiles in the deprecated Fiori Launchpad Designer. Even if some tiles and target mappings need to stay in the deprecated Fiori Launchpad Designer, SAP recommends that you migrate the rest of the catalog using partial migration.

Resources worth knowing:

You'll find much more on the community topic page for SAP Fiori for SAP S/4HANA

Other helpful links in the SAP Community:

Follow our tag S4HANA RIG - SAP Community for more from the SAP S/4HANA Customer Care and RIG
See all questions and answers about SAP Fiori for SAP S/4HANA
Follow SAP Fiori for SAP S/4HANA for more blogs and updates
Ask a Question about SAP Fiori for SAP S/4HANA

Brought to you by the SAP S/4HANA Customer Care and RIG and the Fiori Launchpad ABAP Team.

Building a Compelling Learning Experience in SAP Work Zone

2026-05-27T23:29:10.356000+02:00

If you're running SAP SuccessFactors Work Zone alongside SAP SuccessFactors Learning, you've already got the foundation for one of the strongest learning experience setups in enterprise software. Work Zone gives you the unified workspace. SuccessFactors Learning gives you the system of record. The standard out-of-the-box LMS integration cards put learning functionality directly into the Work Zone experience: Learning Plan, Learning History, Goals, Curricula Status, My Classes, Learning Recommendations, Manager Approvals

That's solid. It's structured, reliable access to your SuccessFactors Learning data, surfaced where your people already work.

But there's a question worth asking. Does that meet the needs of the modern learner? And does it justify standing up a Work Zone layer at all, if Work Zone is only being used as a light-touch surface for SuccessFactors Learning?

The three layers, named

It helps to name the three layers explicitly.

SAP SuccessFactors Learning is the system of record. It holds your courses, your compliance trails, your assignments and your completions. It is the backbone — and it is not going away.

SAP Work Zone is the canvas. It pulls SuccessFactors data, SharePoint, Teams and other systems into a single, unified workspace for the employee. It is the place where work — and learning — converge.

The experience layer is what sits between the learner and the content. It is the difference between seeing a list of assignments and being guided through a learning journey. It is what determines whether your LMS is something employees are told to use or something they actually want to use.

For many organisations, the standard Work Zone LMS cards quietly become this third layer by default. That is where the opportunity sits.

What standard cards do — and where they stop

Standard cards expose SuccessFactors Learning data. They list. They link. They surface.

They do not curate. They do not personalise. They do not recommend beyond SuccessFactors. They do not host the social, gamified, journey-based behaviours that move adoption and completion rates.

Concretely, with standard cards alone:

The catalog appears as a flat list — no interactive search or visual discovery
There is no welcome experience and no personalisation
No trending content, no recommendations from network or peers
No playlists, tracks, or learning journeys
No gamification, knowledge checks, or social interactions on content
No path to layer in Skills and Talent Intelligence Hub content alongside learning
Managers appear only as approvers, not as part of the experience

If your L&D strategy is compliance and completion, standard cards may be enough. If your strategy includes capability, engagement and skills-led growth, they aren't.

What Blend LXP adds on top of Work Zone + SuccessFactors Learning

This is where Blend LXP earns its place. Built natively for the SuccessFactors Learning + Work Zone stack and co-developed with global enterprise customers, it picks up where the standard cards stop. The shape of the value sits in six areas.

Personalisation. A welcome experience tuned to the individual. Trending content based on interests. Recently accessed items, bookmarks, and recommendations that go beyond what SuccessFactors alone can see.

Discovery and search. Interactive catalog browse instead of a flat list. Smart search across SuccessFactors Learning, SharePoint, Teams, LinkedIn Learning, Coursera and other content sources. Featured Content, Featured Topics and Upcoming Events as first-class objects, not afterthoughts.

Curated learning experiences. Pre-filtered widgets, Playlists, Tracks, Learning Journeys — the building blocks L&D teams use to design for campaigns, audiences and moments of need rather than dumping everything in a single catalog.

Engagement and gamification. Points, badges, leaderboards, knowledge checks, social interactions on courses (like, recommend, share), and recommendations from peers and network. These are not nice-to-haves; they are the levers that materially move adoption and completion rates.

Manager surface. A team dashboard, manager views of learning plans, record-learning on behalf of the team. Managers become part of the experience, not just self-service onlookers.

Skills. Surface skills-tagged content, skills-aligned recommendations, and skills progress alongside the rest of the learning experience. As Talent Intelligence Hub and skills-based talent strategies move to centre stage, this is where the L&D and skills agendas converge.

Standard cards expose data. Blend LXP turns data into behaviour.

Build it yourself? Think twice.

One of Work Zone's real strengths is that it gives you the tools to build custom integration cards and apps. For many use cases — internal tools, niche workflows, departmental dashboards — that's exactly the right answer.

A learning experience platform is rarely one of them.

The reason is the pace of change. Personalisation engines, AI-driven recommendations, multi-source content aggregation, gamification, social learning, Skills tagging, GenAI authoring, agentic AI — these are all moving fast. Building custom means signing up to chase that roadmap with your own team, every quarter, indefinitely.

This is where the economics of SaaS earn their place. A purpose-built LXP like Blend LXP brings continuous capability gains without your team writing a line of code or owning the upgrade. The roadmap is somebody else's job. The feature gap shrinks rather than grows.

The other side of the same coin is technical baggage. Every custom integration card or app you build becomes something you have to maintain — across SAP upgrades, security reviews, browser changes, accessibility standards, language localisation. Multiply that across the surface area of a real learning experience — personalisation, search, content aggregation, gamification, social, manager dashboards, Skills tagging, AI — and you're staring at a perpetual development programme inside a part of HR that typically runs lean.

The build-vs-buy question for the experience layer isn't can we? It's should we? And for most organisations the right answer is to buy the experience layer and let engineering capacity go to the things only you can build.

Three recent capabilities worth a fresh look

Blend LXP has not stood still over the last two years. Three additions in particular materially change what's possible on top of the SuccessFactors + Work Zone stack.

Auto-tagging all content with Skills. Every video, document and course in Blend LXP is tagged automatically against your skills framework. This eliminates a long-standing operational overhead — the slow, manual content-tagging step that has historically blocked skills-based learning at scale. With it solved, the path from "skills strategy" to "skills running in the learner's daily experience" gets dramatically shorter.

Content tracking and resume on informal content. Tracking engagement on videos, PDFs and documents — and letting learners pick up exactly where they left off — adds a real engagement layer to the informal content that doesn't live inside formal courses. For organisations where the majority of learning happens outside formal courses, this is significant.

GenAI content creation with one-click translation. Create learning content with GenAI, then translate into Spanish, Brazilian Portuguese and other languages with a single click. Build fast, localise for your audience, ship in days not weeks. This changes the economics of content for global learning teams.

Each of these would have been a standalone roadmap item two years ago. In Blend LXP, they ship today.

What's next

Blend LXP's roadmap goes further. Agentic AI capabilities are opening up a dynamic, chat-based learning experience. Intelligent Q&A lets learners ask, and the platform answers from your own content. Scenario-based simulations move learning from consumption to deliberate practice.

The point isn't any individual feature. The point is that the experience layer is moving fast — and the distance between "standard cards" and "what Blend LXP makes possible" is widening, not closing.

The question worth asking

If your organisation runs SuccessFactors Learning and Work Zone today, there is a quiet decision sitting in front of you.

You can let the standard LMS integration cards be your experience layer. That is a viable choice, especially for compliance-led L&D strategies where the goal is structured access to assignments and completions. Your learners get a list. The list is accurate.

Or you can ask whether your learners deserve more than a list — and look at what Blend LXP, sitting on top of SuccessFactors Learning and Work Zone, makes possible. Personalisation, journeys, gamification, social, manager engagement, skills, and now AI — integrated into the Work Zone experience your people already use every day.

It's a question only your organisation can answer. But it is worth answering deliberately, not by default.

TalenTeam is an SAP SuccessFactors specialist partner and one of the earliest Work Zone implementation partners in the ecosystem. Blend LXP is our flagship Learning Experience Platform, co-developed with customers including GSK, with Vodafone and Scotia Bank as ongoing roadmap contributors. I

SAP Connect Day for UX in Silicon Valley focused on AI strategy and tactics for implementation

2026-06-17T23:00:08.361000+02:00

SAP Connect Day for UX in Silicon Valley was a chance for customers to connect with each other, SAP experts, and selected partners to discuss how AI will improve the lives of SAP Cloud ERP users and the developers who build apps for SAP S/4HANA Cloud. The AppHaus in Palo Alto was filled with energy as we shared knowledge through a combination of lectures, hands-on sessions, and informal conversations. In this post, I’ll share some of the highlights and where you can learn more about the topics we discussed.

Strategy starts with where AI fits into SAP Cloud ERP

We showed demos of the latest user experience innovations in SAP Cloud ERP, also known as SAP S/4HANA Cloud. Starting with My Home, we explored enterprise search, card creation, smart situations, and AI-powered recommendations. In the SAP Fiori apps, we demonstrated proven productivity saving tools such as easy filter, easy fill, and smart summarization.

We briefly discussed SAP Fiori, including how it relates to design, development, and delivery of new apps in SAP Cloud ERP. This foundational session set the stage for the rest of the day, covering how SAP is bringing embedded AI to business users while keeping the SAP Design System and enterprise product standards at the center of the user experience.

Your data and queries are safe when using SAP AI.

There is often confusion when we talk about embedded AI and Joule. These two approaches are complementary. Joule provides a conversational interface to access SAP’s broad range of capabilities. It spans the entire autonomous suite.

Embedded AI provides targeted capabilities in both My Home and SAP Fiori elements apps within SAP Cloud ERP (SAP S/4HANA Cloud Public Edition). People can use their existing apps and business processes while benefitting from the productivity enhancements that AI provides. Any embedded AI capabilities can also be accessed through Joule.

Partners focused on bringing AI to customers on any platform

The sponsors demonstrated a deep knowledge of the SAP market with everyone sharing different ways of bringing AI capabilities to customers, regardless of whether they were running on-prem or in the cloud. Here is a list of the partner sessions:

SAP UX Eras tour: from Dynpro modifications to clean core – what we learned and how to do it right in 2026 (Dassian)
Disappearing Ink: Use Agents to Automatically Eliminate Manual Data Entry Across Your Business (cbs – Corporate Business Solutions)
From On-Premise to the Future: Enabling Agentic AI Across SAP Landscapes (eXXcellent solutions)
Have Your Agent Call My Agent: 20 Joule Agents, Claude, and Reimagining of the Fiori Experience (Mindset Consulting)

Each session offered a different angle on the same broad question every SAP customer is asking right now: how do I bring AI and agents into my SAP landscape in a way that delivers measurable value? The variety of approaches sparked great discussion and gave attendees plenty of reasons to visit the partners during the breaks to go into more detail than the 20-minute talks allowed.

Successful AI implementation is about productivity – the hands-on workshops demonstrated this

The afternoon sessions we split into two blocks: one on application development and the other on new features.

In the application development talk, we talked about SAP Fiori elements, SAP Fiori tools, and building apps using clean core principles. We followed that up with a hands-on exercise where participants could build an app using our latest tools and have the chance to try vibe coding to add and change features in the app without coding. They commented that this was much faster than traditional methods for developing new custom apps.

SAP Fiori elements makes it easy to build apps with enterprise features.

The next section was on Smart Helpers, a new way that business users can automate routine tasks in SAP Fiori apps in their SAP Cloud ERP system. We discussed the reasons why we built this capability and encouraged people to think about areas in their business where they could streamline recurring tasks in SAP. Then, they had a chance to try out the capabilities on a few simple scenarios. Smart Helpers operate according to these principles:

The user is in charge
IT remains in control
They are built on SAP Fiori apps
No coding is required

People shared several scenarios they would consider automating with Smart Helpers.

Tour of the Experience Center highlighted broader SAP capabilities

To provide a broader look at SAP’s Autonomous Suite we scheduled a tour of the Experience Center in the AppHaus. Visitors followed fictitious company, S.Tech, to see how they transform complex operational and supply chain challenges into opportunities. People saw different SAP solutions working together in a manufacturing scenario and enjoyed seeing the new demos.

What’s next for UX innovation in SAP Cloud ERP?

The day closed with a sneak preview of new functionality around Smart Helpers and a deeper dive into Joule Work. This triggered a rich discussion on Joule Work and how it fits into SAP’s portfolio. We addressed the following questions:

Does Joule Work replace SAP Fiori?
No – the application experience and engagement layer experience are complementary. They will coexist for the foreseeable future.
What is the future of SAP Fiori apps?
SAP Fiori apps will coexist with Joule Work for the foreseeable future, just as SAP GUI transactions coexist with SAP Fiori apps. We are continuing to build SAP Fiori apps for SAP Cloud ERP and enhance the tools that we use and you can use to develop your own SAP Fiori apps. Tooling will include increasing amounts of AI to reduce the amount of coding required to create new apps.
When will we see all the cool embedded AI innovations in SAP S/4HANA Cloud Private Edition?
We are working on moving most of the embedded AI capabilities to private cloud. Here is our current plan as of May 2026. As with any development plans or roadmaps, this is subject to change.

	Public Beta	Public GA	Private GA
AI-assisted in My Home
AI-assisted Smart Personalization (Cards)		x	Planned
AI-assisted Smart Personalization (Apps and Tiles)		x	Planned
AI-assisted task automation (Smart Helpers)	x		Planned
AI-assisted smart solutions for situations in My Home	x		Planned
Smart summarization and broadcast via email for executives	x		Planned

AI-assisted beyond My Home
AI-assisted enterprise search		x	FPS02
AI-assisted easy filter		x	FPS02
AI-assisted smart summarization		x	FPS02
AI-assisted error explanation		x	Planned
AI-assisted easy fill	x		Planned
AI-assisted task automation (Smart Helpers)	x		Planned

Thanks to everyone who made the day a success

Thank you to our partners for their thoughtful sessions, to the behind-the-scenes team of developers, architects, product managers, and colleagues who built the features we showed, tested the systems, and created the hands-on exercises, and to the logistics team who made everything run smoothly.

Most of all, thank you to the attendees. Your enthusiasm, probing questions, and hallway conversations help us understand where you are in your SAP Fiori journey and how we can best prioritize what comes next.

Next steps

Register for the monthly SAP Fiori development roundtable call to meet other developers and architects who build SAP Fiori apps.
Subscribe to the SAP Fiori development newsletter, in which we share updates on SAP Fiori elements, SAP Fiori tools, SAPUI5, and SAP Build Code every other month.
Join us at an another SAP Connect Day for UX in 2026 – we are finalizing locations, dates, and some new event formats.

On behalf of the SAP UX Foundation Team, Peter Spielvogel.

Provisioning a Solution in SAP Data Accelerator: A Step-by-Step Guide

2026-07-01T14:01:31.819000+02:00

Hi, community!

SAP is introducing SAP Data Accelerator, an SAP-managed service that enables secure access to data from supported SAP systems through authorized partner solutions. It replaces the customer-managed connectivity setup used in supported partner access scenarios with an SAP-operated service layer designed to support enterprise security, regulatory compliance, and operational availability, while helping reduce brittle integrations, simplify operations, and minimize transition effort.

This guide walks you through the end-to-end process of provisioning a new solution in SAP Data Accelerator using SAP for Me. It is intended for administrators and technical users who need to set up and access a new SAP Data Accelerator tenant. By the end of this guide, you will have a fully provisioned solution and the credentials to sign in to it.

Step 1: Open SAP for Me

Open SAP for Me in your browser and navigate to Portfolio & Products > Applications and choose Start Provisioning in the SAP Data Accelerator Hub tile.

SAP for Me dashboard showing Applications in Products & Portfolio

Step 2: Use the Create Solution Wizard

The Create Solution wizard opens and displays four steps: General Information, Select Applications, Configure Parameters, and Review. The wizard starts at Step 1: General Information. Wait for any loading indicator to finish before proceeding.

Step 3: Enter General Information

Fill in the required information: Name (1), Path (2), and choose Next Step (3).

General Information page

Step 4: Enter Configure Parameters

Fill in the required information: Region, Cloud Connector Auth Data Password, External System Name, Certificate (PEM): copy and paste the entire certificate from "begin" to "end", External System Name, Certificate (PEM): copy and paste the entire certificate from "begin" to "end", and choose Review.

Step 5: Review the Information

Review the information entered and if everything looks correct, choose Finish.

Step 6: Download the Authentication Data

You will receive a pop-up screen informing you that provisioning has started and that the resources are being provisioned in the selected resource group. Choose the View in Resources button to check the status of your request. While the tenant is in Processing state (1), a View Notifications button (2) becomes available. Use this button to access the Download connection details link (3).

Tenant Notifications screen

Step 7: Connect the Cloud Connector to SAP Data Accelerator

The authentication data downloaded from your SAP Data Accelerator instance includes the subaccount details required for the setup in Palantir's platform, such as the region, subaccount, login email address, and password.

Subaccount details

Use the information from those details to connect the Cloud Connector to the SAP Data Accelerator subaccount, as described in the SAP Help Portal page Connecting to SAP Data Accelerator. Complete this step within 5 minutes of downloading the authentication data. The activation link expires 1 hour after it is generated.

Step 8: Start Using SAP Data Accelerator

Once the account has been activated, your SAP Data Accelerator is ready to use (1). You can log in to your SAP Data Accelerator either using your SAP Data Accelerator URL or using the Main URL (2) provided in the Access Information of the SAP Data Accelerator tenant.

Account ready to use

The purpose of this blog post is to guide you step by step through the process of provisioning a solution in SAP Data Accelerator. For a list of the prerequisites and more information, I suggest you visit the SAP Help Portal documentation Provisioning SAP Data Accelerator.

For more information about SAP Data Accelerator, see SAP Data Accelerator product page.

If you liked reading this post, feel free to share it with your colleagues. Also, I invite you to follow my profile and leave a comment or a question.

All the best,

Eduardo