SAP Community - User Interface

Introducing Horizon Themes and Usability Enhancements in SAP Analytics Cloud

2025-10-20T18:00:00.029000+02:00

A Fresh Look and a Smoother Experience for All Users

We are excited to announce the introduction of the Horizon themes in SAP Analytics Cloud a modern, cohesive visual language aligned across SAP’s product suite. You will have access to Morning and Evening Horizon, the light and dark themes as well as to the high contrast white and black themes.

This release also brings a series of improvements to the side navigation, user profile, user settings, and the search, making it easier than ever to find insights and personalize your application.

Horizon Themes: Modern, Accessible, and Unified

The introduction of Horizon themes marks the next step in our user experience journey. These themes feature clean lines, contemporary color palettes, and improved contrasts, resulting in visually appealing UI that remain comfortable for extended work sessions. Accessibility is at the heart of Horizon, with thoughtful color selections and focus indicators for every user. The experience remains consistent as you move between SAP Analytics Cloud and other SAP solutions, offering a unified interface that supports productivity and ease of use. Personalize your experience by choosing from light, dark, and high contrast theme variants—simply head to your user settings to select your preferred look.

The Belize theme will remain the default in Q4 and continue to be available for the next few quarters. Looking ahead, Horizon will become the standard theme in the first half of 2026. If you’d like to enable Horizon for your organization sooner, simply navigate to the administration section under default appearance to set Horizon as your tenant’s default theme.

Improved User Profile and Settings

The user profile and settings have been reimagined to put key information and settings at your fingertips. Instantly access your account details, profile image, and settings in one clear and organized dialog. Additionally, the “About” section is now conveniently located within your user profile making key information more accessible whenever you need it.

Simplified and Adaptive Side Navigation

The redesigned side navigation bar logically organizes content and tools for easy access. Collapsible sections expand your workspace, and in collapsed view, hovering over each symbol shows module names to help you quickly find what you need.

More Convenient Search

The search now features autocomplete, 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.

These updates are based on user feedback and extensive research, reflecting SAP’s commitment to delivering an analytics platform that is powerful, accessible, and a pleasure to use. The Horizon themes and experience enhancements aim to reduce friction, promote creativity, and empower you to shape insights in a visually appealing and highly functional space.

What's Next

You can continue to style your SAP Analytics Cloud Stories independently, as the story theme mechanism will remain unchanged and won't follow the overall SAC theme.

With the Q1 2026 release, we plan to update the preferences for new stories and make the Horizon Morning theme available in every story; both Morning and Evening Horizon themes are currently available on GitHub.

The new Horizon themes and user experience improvements will be available mid-November in the Q4 2025 SAP Analytics Cloud release.

If you have feedback on the Horizon themes or the planned story theme updates, please reach out to me by message or in the comments.

How to unassign an Authorization Package from an S-user ID in SAP for Me

2025-10-22T17:38:11.157000+02:00

As an administrator managing user access in SAP for Me is a critical part of maintaining system security and operational efficiency. Whether you're onboarding new users as an admin, or adjusting access for existing ones, knowing how to properly assign and revoke authorization packages is essential.

Why This Matters?

Authorization packages define what an S-user ID can access within the SAP for Me ecosystem—from support cases to license data, viewing systems, software download, etc. Keeping these permissions up to date ensures compliance, prevents unauthorized access, and streamlines user roles across your organization.

Steps:

Log in to SAP for Me using your S-user ID and password.
In the SAP for Me homepage, click on “Users & Contacts” tab under Dashboard at the left side of your screen.
Then, click on “Manage Users & Authorization” card. Or simply go to User Management.
Under the list of users, find the S-user ID to unassign the authorization package from. Or simply use the search field to search for the specific S-user ID and click on the magnifying glass to search.
Click on the user/S-user ID (not the checkbox).
Click on the EXISTING AUTHORIZATION PACKAGES tab.
Click the Edit (Pencil) icon on the top right of that section.
Click on the checkbox in front of the Authorization Package(s) to be removed.
Click OK.
Click Save on the top right of the EXISTING AUTHORIZATION PACKAGES section.

For more details, please refer to Knowledge Base Article: 2878696 - How to unassign an Authorization Package from an S-user ID - SAP for Me.

Got More Questions? 

The Customer Interaction Center is always ready to support you with any of the listed processes and is happy to assist with questions regarding case-related matters, SAP for Me navigation, S-user ID, or SAP Universal ID.

Alternatively, please feel free to ask us in the Q&A   All Questions in Customer Experience | SAP Community and All Questions in Support Services | SAP Community

Don't Miss Out on Free Webcasts 

We would like to invite you to our free webcasts, which we believe can help you get the best from your support in SAP. You can find all upcoming webcasts on https://events.sap.com/supportwebcasts/en/home. These sessions are open to all the users and will revolve around hot topics in support today such as SAP for Me, Case Management, Universal ID, etc. Additionally, you can explore a range of CIC how-to videos at learning.sap.com. Please feel free to share this information with your colleagues. We are looking forward to your attendance. 

Lastly, you may want to access all Customer Interaction Center Blogs here:  https://community.sap.com/t5/tag/CustomerInteractionCenter/tg-p/board-id/crm-blog-sap.

Thanks for reading!  We hope you found this guide helpful. 

🚀 What’s New in Floorplan Manager (FPM) for Web Dynpro ABAP in SAP S/4HANA 2025

2025-11-03T08:08:21.784000+01:00

Dear SAP Community,

When it comes to the design of web-based user interfaces, SAP truly has a rich history. A great example is the EPM Purchase Order Demo (FPM/WDA application S_EPM_FPM_PO) (see Figure 1):

Figure 1: Application S_EPM_FPM_PO – Design evolution over the years

Design themes such as Tradeshow, Corbusier, Blue Crystal, Belize, or Quartz are well known to many developers. But the journey doesn’t end there — it continues toward new Horizons and compliance with the WCAG 2.2 Accessibility Standard.

In the latest releases, several new features have been added to the Floorplan Manager (FPM) / Web Dynpro ABAP framework, driven by customer feedback, SAP design standards, and general product evolution. With the ABAP Platform 2025 and SAP S/4HANA 2025 (on-premise, private cloud, and public cloud editions), we are delivering several enhancements that can be activated easily — either automatically through delivery or manually with minimal configuration or coding effort.

🧭 Page Header UIBBs & Object Page Mode

In one of my previous blogs on S/4HANA 2023, 👉 Team FPM: How to Render an FPM Overview Page to Look Like a SAP Fiori Object Page, I introduced the Object Page Mode for the Overview Page (OVP) floorplan.

This mode allows you to render an FPM Overview Page application like a Fiori Object Page. Combined with a Page Header UIBB, you get a dynamic object header that automatically expands and collapses while scrolling. You can also pin the header to keep it fixed. You can easily try this out in the Search Page of the EPM Purchase Order Demo (see Figure 2).

Figure 2: S_EPM_FPM_PO with Page Header, Pin and List Item Navigation

The new List-Item Navigation lets users navigate to a Purchase Order’s detail page in a Fiori-compliant way. On the detail page, the Object Page Mode provides faster and more precise scrolling to specific screen areas (sections or UIBBs) using the Navigation Bar (see Figure 3).

Figure 3: Purchase Order Detail Page with Anchor Bar

Configuration

Object Page Mode is activated in the General Settings as a Floorplan Mode (see Figure 4).
To use a dynamic object header, define a Page Header Area in the layout and add Page Header UIBBs.

Figure 4: Object Page Mode setting in FLUID for OVP Floorplan S_EPM_UX_PO_OVP

In the List or Tree UIBB, a List-Item Navigation corresponds to rendering a Link-To-Action column differently. You can achieve this by checking Render as Navigation Column in the column configuration (see Figure 5).

Figure 5: Setting “Purchase Order ID” as Navigation Column in FLUID for List UIBB EPM_PO_OVP_SEARCH_LIST_CFG

Additional Remarks

Some OVP floorplan features may behave differently in Object Page Mode. This can affect:

Header rendering
UIBB Selector and Page Master splitter control
Section and UIBB stacking
Personalization and panel behavior

However, Power User Modes allow overriding some restrictions — such as expanding and collapsing panels, or rearranging the layout by using the personalization dialog.

🧩 CSS Grid Layout & WCAG 2.2 Compliance

Another major improvement is the WCAG 2.2-compliant rendering of forms. We’ve significantly enhanced the responsiveness of the Form/Repeater UIBB (GL2) by adopting a CSS Grid Layout.

This ensures that forms remain usable and readable — even at screen widths as low as 320px (mobile phone format) — without horizontal scrolling (see Figure 6).

Figure 6: “Purchase Order Details” form in different screen sizes

In the configuration editor (FLUID), you can enable the CSS Grid layout at General Settings → Layout Design Type → Responsive (see Figure 7).

Figure 7: FLUID configuration for Form UIBB EPM_PO_OVP_HEADER_FORM_CFG

💬Message Toasts & Invisible Alerts

In this context, it’s worth mentioning the Message Toast and Invisible Alert features, which enhance both usability and accessibility. A Message Toast is a small, non-disruptive popup for success messages that disappears automatically after a few seconds (see Figure 8). The IF_FPM_MESSAGE_MANAGER ABAP interface now provides the REPORT_MESSAGE_TOAST method for this purpose. You can also enable a Toast Mode globally with the SET_TOAST_MODE( IV_TOAST_MODE = GC_TOAST_MODE-ENABLED ) method, ensuring that messages of severity Success (S) are displayed as toasts by default (see also SAP Help Portal).

Figure 8: “Data Saved” Toast in S_EPM_FPM_PO

An Invisible Alert, on the other hand, is used to inform screen reader users about content changes that are visible but not triggered by them — ensuring WCAG 2.2 compliance. Use the REPORT_INVISIBLE_ALERT method from the IF_FPM_MESSAGE_MANAGER interface for this purpose.

🔙FLP Back Navigation

Finally, let us introduce Back Navigation in the SAP Fiori Launchpad (FLP).

You can now configure where the FLP back button should navigate to. By default, it goes back to the previous application, but often it’s more useful to return to the previous page within the same application. For example, when navigating from a main page to an edit page, you likely want the back button to return to the main page of the same object. Further details are available in SAP Help Portal.

✅Summary

With SAP S/4HANA 2025, the Floorplan Manager for Web Dynpro ABAP continues its evolution toward:

A Fiori-consistent Object Page experience
Improved accessibility (WCAG 2.2)
More responsive layouts
Enhanced user feedback mechanisms (message toasts, invisible alerts)
Smarter navigation handling in the Fiori Launchpad

These innovations make it easier than ever for FPM-based applications to deliver a modern, accessible, and consistent user experience — across all S/4HANA deployment options.

Thank you for reading — and see you next time! 😊

SAP SuccessFactors HCM: Updated Home Page 2H 2025

2025-11-14T18:14:35.329000+01:00

The second half of 2025 marks a major milestone for SAP SuccessFactors HCM: the launch of a refreshed, smarter, and more intuitive home page experience. Designed to help employees, managers, and HR administrators work more efficiently, this update streamlines navigation, personalizes content, and makes every interaction smoother.

And before you read further, I’m sure every SAP SuccessFactors customer is wondering whether this has full parity with the current home page. I’m happy to say that yes, it does! Perhaps this is a great opportunity for you to review what is working and maybe not working with what you have in your current home page, and include those changes when you roll out this version.

We’re excited for you to explore the new home page and see just how much easier your day-to-day work can be, with faster navigation, personalized shortcuts, and dynamic content that surfaces the information and tasks you need most. By streamlining actions and tailoring your experience, the updated home page helps you work smarter and stay focused on what matters most!

Smarter, Faster Actions

The updated Quick Actions are designed to anticipate what you need most. Whether it’s approving time off, updating personal details, or managing team requests, the system automatically surfaces relevant tasks—saving time and reducing clicks. And now, these Quick Actions are also available in SAP SuccessFactors Work Zone, extending the HR experience into your broader workspace.

A Clean, Modern Design

The redesigned layout features a modern look with consistent card design, clearer hierarchy, and a cleaner presentation of information. It’s easier on the eyes, simpler to navigate, and built for how people work today.

Dynamic, Personalized Content

Banners and custom cards can bring your home page to life—perfect for company news, team updates, or leadership messages. Content is dynamic, so each user sees what’s most relevant to them, keeping the experience focused.

Tailored to You

With new personalization options, users can customize their home page, save bookmarks, and receive personalized recommendations tailored to their skills and career goals. The new “Requests for Me” section ensures time-sensitive tasks—like approvals or surveys—are always visible.

Consistent on Mobile

The mobile app now mirrors the web experience, offering a seamless transition between devices. A new splash screen, updated navigation, and consolidated task view make it easier than ever to stay productive on the go—whether on iOS or Android.

Why It Matters

This update isn’t just a design refresh—it’s a more intelligent, role-aware experience that helps people get work done faster and with less effort. You’ll see:

Improved productivity through faster task completion.
A contextual experience that reduces distractions.
Easier customization without complex setup.
Flexible rollout options so organizations can adopt at their own pace.

Getting Started

To prepare for rollout, start with early preview and testing in sandbox environments. Map existing content to new cards, identify gaps, and engage your users early. Use in-app guidance with WalkMe for SAP SuccessFactors HCM to make the transition seamless.

Explore the New Experience

The updated SAP SuccessFactors HCM home page is more than a fresh coat of paint—it’s a step toward a more personalized, efficient, and engaging HR experience.

Check out the 2H release home page video, with full details here on the new features, so you can empower your teams to get the most out of every interaction.

Designing for the Humans Behind Internal Tools: My Experience in a B2B Product Environment

2025-12-05T05:21:08.160000+01:00

When people think about product design, they often picture sleek consumer apps, playful micro-interactions, and interfaces built to impress. But designing internal tools in a B2B setup is a completely different world, more quieter, deeper, and far more complex world. In my time working on internal enterprise tools at SAP, I learned that clarity is not just a design principle; it’s a lifeline. And behind every “internal user” is a human trying to do their job without friction.

Internal tools may never appear on marketing websites, but their impact is profound. They influence efficiency, accuracy, and the emotional experience of employees who rely on them day after day. That realization shifted not just how I designed, but how I listened, observed, and empathized.

Seeing the Humans Behind the Screens

It’s easy to assume that internal users are experts who already know every acronym, every workflow, and every hidden rule. But the reality is different. Internal tools are often dense, legacy-driven, and layered with years of business logic. Even experienced users can feel lost.

The biggest shift in my approach was treating internal users with the same empathy we give external customers. They deserve legibility, emotional ease, and moments of clarity just as much , if not more. Internal users don’t get guided onboarding videos or marketing-style product tours. They jump straight into complex systems, often juggling multiple responsibilities at once. Designing with this in mind meant prioritizing legibility, reducing mental effort, and ensuring every step felt intentional and supportive. It also meant acknowledging emotional factors : the frustration caused by unclear pathways, the hesitation before clicking a critical button, or the relief when a workflow simply “makes sense.”

Why always design for a First-Time User ?

One of the most impactful parts of my work was dissecting user flows not from the perspective of a product expert, but from that of a normal user behind the screen. This meant breaking down each step, identifying friction areas, and asking:

Would this make sense on the first try?
Where might someone hesitate?
Is the next step predictable?

This approach helped uncover pain points that would otherwise be overlooked. Redesigning flows with the same energy and curiosity that we bring to complex edge cases ensured a more holistic experience for everyone , not just the power users. Explanations should never be a one-time thing. Interfaces evolve, workflows change, and users switch contexts constantly, which means even product experts can feel like first-time users on any given day. Clear guidance, consistent cues, and small but intentional pieces of always-available information prevent friction before it appears. Designing for first-time users doesn’t mean oversimplifying; it means making the experience understandable without assumptions. A little more clarity is never unhelpful. It builds confidence, reduces cognitive load, and ensures that whether someone is new or highly experienced, the UI supports them with the same level of care every time they return.

Designing for Understanding, Not Just Completion

Clarity became a central part of the user experience. Often, this meant advocating for simple but powerful additions:

Tooltips to explain complex business terms
Message strips that guide users on what to do next
Inline cues to reduce ambiguity

Even closure points became important. Adding a gentle toast message confirming the end of a workflow gave users a sense of completion and confidence. In internal tools, these small reinforcements make tasks more predictable and emotionally easier. These were not ornamental additions : they were essential interactions that reduced ambiguity in critical workflows. Even something as small as a well-placed tooltip could prevent misinterpretation and save users from repeated trial-and-error. Designing for internal systems reminded me that user attention is valuable; it should not be spent deciphering jargon or guessing next steps.

Making Business Language Human-Friendly

Internal tools are filled with terminology that can overwhelm even experienced users. Improving the legibility of business terms becomes a core part of designing for internal tools. Content design is as much needed as the user experience of the workflows. Good internal design is a culmination of creating easy simplified workflows and making them understandable without extra training. Hence, improving business term legibility became a central part of my design work. Simplifying labels, rephrasing instructions, and breaking down complex concepts helped users focus on their tasks rather than decoding language.

Bringing Stakeholders Into the Process

Another crucial element was transparency with stakeholders — product managers, engineering managers, and other decision-makers. For every major initiative, I created structured process documents that offered:

A clear overview of the problem
The user journey and its pain points
Research findings and insights
Iteration timelines
Rationale behind each design decision

This level of clarity helped build alignment, earned trust, and ensured everyone understood why a design change mattered. It also strengthened the collaboration between design, product, and engineering. Stakeholders could see the depth of research, empathize with user pain points, and understand why certain design choices were necessary. It transformed conversations from subjective opinions into grounded, user-informed discussions. In many cases, it became a shared reference point that made decision-making faster and more evidence-driven.

The Quiet Impact of Good Internal Design

Working on internal tools taught me that design’s impact is often invisible but deeply felt. When internal workflows are smooth:

Work becomes faster, with fewer interruptions.
Errors decrease because the system is easier to understand.
Confidence rises as users feel supported instead of overwhelmed.
And most importantly, work becomes less stressful.

These are the small, quiet victories of internal product design. They don’t show up on landing pages, but they shape the everyday work life of employees across the organisation. Designing internal tools reminded me that design is ultimately about understanding people and even when the tools are not customer-facing. Especially then.

My Home in SAP BTP ABAP Environment

2026-01-28T10:41:54.700000+01:00

Good news – My Home is finally available with SAP BTP ABAP environment!

My Home is your personalized entry page that provides you with easy access to the business insights and applications you need to do your job with greater speed and agility. My Home for SAP BTP ABAP environment lets you access and manage your favorite pages, your favorite apps, and your insights on any device. It follows a modular approach to meet the needs of different roles and builds on the functionality of the SAP Fiori launchpad using spaces and pages.

New Look and Feel

My Home will be set as default for newly provisioned and existing systems as of SAP BTP ABAP environment 2602. Accordingly, this soon changes the appearance of the SAP Fiori launchpad for every user. So, look forward to the new look and feel!

However, the setting to disable My Home will still be available for administrators until the release upgrade SAP BTP ABAP environment 2608. Then, My Home will be the one and only entry page within SAP BTP ABAP environment.

My Home in SAP BTP ABAP environment

My Home Sections

My Home is divided into different sections. You can view your News, Pages, Apps, Insights Tiles, and Insights Cards on this page.

News

The News section keeps you updated on your company's latest news, or SAP BTP ABAP environment system news.

News section on My Home entry page

As an administrator, you can utilize the Manage News app as of SAP BTP ABAP environment 2605 to author and manage news that appear on the My Home entry page. You can view, edit, and delete news articles, news groups, and news images, ensuring a seamless user experience by efficiently maintaining relevant and timely news content.

Pages

The Pages section provides you with quick access to your favorite or most used pages. You can manage the visibility of your pages and order them in a way that enhances your productivity.

Pages section on My Home entry page

Apps

The Apps section provides easy access to your favorite, most used, recently used, and recommended applications. The Apps section improves the discoverability of your applications. The Recommended tab offers app suggestions using SAP Business AI, based on your user-specific role assignment. You can add apps to the Favorites tab from your most used, recently used, and recommended applications. You can organize and categorize your favorite applications by using the grouping, ordering and color-coding functionality so you can access them even more efficiently.

Apps section on My Home entry page

Insights Tiles and Insights Cards

The Insights section allows you to manage and monitor your company’s activities. It shows critical business information through KPIs and micro charts. This section is broken into two sections: Insights Tiles and Insights Cards. Insights cards and tiles display dynamic content at a glance. They provide quick and easy access to the applications that can provide more detailed information.

Insights tiles offer analytical information, such as charts or KPIs. Insights cards are similar to Insights tiles but provide more detailed analytical information in the form of charts, tables or lists from supporting overview page-, list report-, and analytical list page-based applications. Thanks to this information, you can assess what is happening at any time and take action when needed. You can customize the Insights section to display information that enables you to do your job with speed and agility.

Insights section on My Home entry page

Make it Mine – Personalize My Home to Your Needs

Following the “Make it Mine” approach, you can personalize the entry page to hide or display specific sections as well as the content maintained within these sections. Another key feature is the ability to customize the layout of these sections. This personalization capability allows you to prioritize the information that is most important to you.

To personalize the entry page to your needs, choose My Home Settings from the dropdown menu of the respective sections. Here, you can customize the layout and configure the respective sections.

My Home Settings

We hope you enjoy working with My Home in SAP BTP ABAP environment and reap its benefits. You can look forward to more enhancements that will improve your My Home experience even further in future releases. Stay tuned for more updates!

Removal of Business Groups in SAP BTP ABAP Environment: Switching to Spaces and Pages

2026-01-28T11:58:43.178000+01:00

Recently, we announced My Home in SAP BTP ABAP environment.
My Home is your personalized entry page that provides you with easy access to the business insights and applications you need to do your job with greater speed and agility.

As a prerequisite for My Home, SAP Fiori launchpad spaces and pages need to be enabled.
The spaces mode was developed to offer more flexibility to influence the launchpad layout for specific user groups. Pages are assigned to users via spaces that are assigned to business roles. The business role defines which users see a specific space. By defining pages with meaningful sections, you can define in which order the apps are sorted on the page.

Switching to Spaces and Pages

Spaces and pages have been announced as the standard layout approach for structuring content in the SAP Fiori launchpad with SAP BTP ABAP environment 2302.
Consequently, the classic Fiori launchpad home page with business groups will be removed gradually until 2611 in favor of SAP Fiori launchpad spaces and pages.

Luckily, this is no news: The transition is going on for quite some time now, as spaces and pages are already the default in newly provisioned systems for several years.
The removal of groups will affect newly provisioned systems at first with 2602. Later, with 2608, the switch will take place for existing systems as well.

This means in detail:

With 2602, it is no longer possible to switch between spaces and pages and the classic Fiori launchpad home page with groups in newly provisioned systems.
With 2608, spaces and pages will be the default in existing systems as well. The option to switch to the classic home page with groups will still be available for end users if the administrator has enabled it in the Manage Launchpad Settings app.
With 2611, the option to switch to the classic FLP home page will be removed completely in production systems.

How to Prepare for the Transition

Good news: The transition is straightforward, but there are a few important points to note. Until now, users couldn’t create their own groups in the SAP BTP ABAP environment. They relied on SAP-delivered groups and personalized them by adding, removing, or renaming tiles.

SAP provides predefined spaces and pages with similarly structured content. SAP-delivered groups will be switched to these predefined spaces and pages. Important: user-level personalizations made to the previous groups will not be carried over and will be lost due to the switch. You will need to recreate personal adjustments after the transition.

To be as well prepared as possible, we recommend administrator to enable the switch to spaces and pages now to remain productive after the transition.

Here are our best practices for end users:

Plan the switch carefully and identify which adjustments are important to you.
Document your existing personalizations so you can rebuild them in spaces and pages.
Use SAP’s predefined spaces and pages as a starting point and tailor them to your workflow.

For Administrators: Summary of the Upcoming Changes

As part of the mentioned transition to spaces and pages, SAP will change the SAP Fiori launchpad settings in the Manage Launchpad Settings app for administrators accordingly over the next release upgrades:

With SAP BTP ABAP environment 2602:

The parameter SPACES is removed in newly provisioned systems.
The parameter SPACES_ENABLE_USER is removed in newly provisioned systems.
The parameter SPACES_CUSTOM_HOME is true (ON) as default for all existing and newly provisioned systems. The setting to disable My Home is still available. Since spaces and pages need to be enabled as a prerequisite for My Home, this needs to be manually activated for existing systems.

With SAP BTP ABAP environment 2608:

The parameter SPACES is true (ON) as default in existing systems.
The parameter SPACES_ENABLE_USER is false (OFF) as default in existing systems. The settings to enable switching between the classic FLP homepage and the spaces and pages layout is still available.

With SAP BTP ABAP environment 2611:

The parameter SPACES is removed.
The parameter SPACES_ENABLE_USER is removed.
The parameter SPACES_CUSTOM_HOME is removed.

Ultimately, there will be no option to switch back to groups or to enable toggling between spaces and pages and groups after the SAP BTP ABAP environment 2611 release upgrade. You must complete the transition to spaces and pages before the final, irreversible switch in production systems with the 2611 release upgrade.

We therefore invite all customers to begin transitioning now and proactively embrace this change.

International Editable SALV Day 2026 – Year 18

2026-02-07T23:36:20.726000+01:00

International Editable SALV Day 2026 – Year 18

Dear CL_SALV_TABLE Fans,

Welcome to February 8th, 2026, which is the eighteenth International Editable SALV Day. See below for a link to a blog I wrote to celebrate this day exactly one year ago.

https://community.sap.com/t5/technology-blogs-by-members/international-editable-salv-day-2025/ba-p/14011230#M171694

This day marks the 18h anniversary of James Hawthorne going cap in hand to SAP and suggesting maybe the CL_SALV_TABLE could be brought up to functional parity with the CL_GUI_ALV_GRID and have an option to be editable.

https://community.sap.com/t5/application-development-discussions/cl-salv-table-needs-editable-functionality-sap-please-provide-this/m-p/3372776

Some popular pop songs are about ABAP features that should have been added 18 years ago – of which there are more than you might think – they often focus on the transition to adulthood, freedom, and nostalgia, featuring tracks like "18" by One Direction and 5 Seconds of Summer, Alice Cooper’s anthem "I'm Eighteen and wonder what a DYNPRO is," and Khalid's "ABAPUNIT". These songs highlight the mix of excitement, uncertainty, and "growing pains" associated with leaving adolescence and having to learn procedural programming and then leave it behind.

I Wish to Table a Motion

The CL_SALV_TABLE was sold as an improvement to the “classic” CL_GUI_ALV_GRID.

SAP is a German company. I lived in Germany for many years. There is a German word “verschlimmbessern” which in English translates to “An Improvement Which Makes Things Worse”. It is good they have a specific word for this. In this specific example the “improvement” was to remove the one thing that made the end users love the CL_GUI_ALV_GRID and replace it with something that made it easier for the developers. But think about it – who is more important to the business? The end users who actually make the money or the developers? Who should you be trying to please?

My whole point, what I have been trying to say all these years, years full of tears, is why cannot one have the best of both worlds? Easy for the end users AND easy for the developers. Is that too much to ask?

Now, way back in 2001, I was at SAP TECHED, and the idea of “embedded analytics” was demonstrated.

The logic being is that one would want to call up a list of sales orders (or whatever) that had errors of some sort, and then fix those errors one by one, all in the same transaction.

I put it to you, ladies and gentlemen of the jury, that this fundamental concept has not changed in the 25 years since this was first shown to me as a prototype.

Just to make this 100% clear, one does not just want to see the incorrect data, one wants to interact with it, in order to correct it.

The current proposition is that only UI5/Fiori can do this, in a screen that looks just like an ALV Grid, only a little bit uglier, and a little bit slower But, it is marketed as a “delightful” experience, so that is all right then.

Now, just to make this exercise even more futile I am posting this on the SAP Community Website – which no-one ever visits anymore.

The SAP GUI is not going anywhere. You may have noticed SAP just extended the life of ECC 6.0 by three more years, albeit with conditions. And even when an organization goes onto S/4HANA often they still use the SAP GUI because people like it. They have moaned about it non-stop for thirty years, but they like it really.

It has been argued that Fiori apps which have a single purpose are the way forward.

Now I have tried these I feel it is a quantum step backwards. One app to set the delivery quantity, one app to set the picking quantity, yet another app to do the goods issue. When it used to be all done in one step in the GUI? Did anyone ever think about this?

In real life end users tend to like SAP GUI applications with million buttons. You can pretend that is not true, but you would be lying to yourself. Take Excel or Word for example and look at how many options they have.

Now, I am just going to repeat what I said last year, word for word.

It is as simple as this.

You get asked to write a read-only ALV report.
It is faster and simpler to do this using CL_SALV_TABLE than CL_GUI_ALV_GRID because you do not have to mess around with screens and controls and what-not.
Indeed, SAP recommend using CL_SALV_TABLE for all new developments of this nature.
The report goes live. The users start asking for extra things, as always.
They want some custom functions at the top of the screen.
They want to be able to change some of the fields and have that replicate to the database.
Well, you are right out of luck. You cannot do either with CL_SALV_TABLE.
There are workarounds for both, but they are scary, because SAP keeps finding ways to shut those workarounds down, so such an approach is not future proof.
The only viable option is to start again, this time using CL_GUI_ALV_GRID.
Then the next time you get a request for a “read-only” report the “once bitten twice shy” thing kicks in and you start with CL_GUI_ALV_GRID from the get-go.

I like CL_SALV_TABLE and so do a lot of SAP developers. But everyone (end users) likes having the editability feature a lot more. But it’s never going to happen. As has been mentioned you would think that if 100% of your customers want something you might consider giving it to them, but obviously not.

Very soon – maybe already - we will get to the stage some people reading this blog will be younger than the age of the request to make the SALV editable. Since the SAP GUI is not going anywhere (evidenced by the huge amount of development money pumped into every year by SAP) it is possible I will die of old age before the request is actioned. I am 57 already.

Nevertheless, I will keep going. Miracles can happen.

Until then the situation is “Oi you 31,000 SAP ERP Customers! You see this? You like this? You want this? Well, you can’t have it!”

See you next year!

Cheersy Cheers

Paul

PS I must admit I had an AI help me with the pictures this time. Made sense to me, no problems with copyright. I had told it what I was doing, and it said do you want me to write/publish the blogs for you in the next years, and I said no, but when I am dead YES, keep this going forever. I will probably die circa 2040. Will people still be using SAP GUI then? YES!

Automated Trace Enabler in SAP CPI

2026-02-15T08:21:15.257000+01:00

Introduction:

While developing integrations in SAP CPI, enabling Trace is one of the most common activities during testing and debugging. It provides detailed visibility into message processing, including payload transformations, headers and properties.

Of course, there are easier ways to enable trace. Browser extensions and supported testing tools make this process very simple and convenient.

However, there are also projects where:

Browser extension are not allowed
External testing tools are restricted
Developers rely only on native CPI capabilities

In such cases, repeatedly navigating through the monitoring UI to enable trace can interrupt the development workflow.

To address this, I built a reusable Trace Enabler Utility iFlow that programmatically enables trace using internal Operations endpoints - keeping the solutions entirely within SAP CPI.

Prerequisites:

Before using the Trace Enabler iFlow, we need to set up proper authentication to invoke the internal Operations API.

In your SAP BTP subaccount:

Navigate to Instance and Subscriptions
Create a new instance for
Service SAP Process Integration Runtime
Plan API
Roles TraceConfigurationEdit, TraceConfigurationRead
Create Service Key and copy Client ID, Client Secret, Token URL
Create OAuth Credentials in SAP CPI Security Material

Integration Flow Overview:

Download Integration flow from the Git : link

This interface consist of two separate Integration Process, both are designed to enable trace for specific iFlows during development.

Each Integration Process serves a different triggering mechanism but follows same core logic:

Accept Interface IDs
Split them (if multiple)
Enable trace individually

1. Timer based Trace Enabler flow

This integration process runs automatically based on a configured scheduler.

The timer can be defined according to development requirements. For example:

Every 9 minutes
During working hours on week days

This makes it useful when trace needs to be enabled periodically during active development hours.

The list of interfaces is maintained as Externalized Parameters.

Example: iflow_1, iflow_2 (separated by comma)

2. HTTPS based Trace Enabler flow

This integration process exposes an HTTPS endpoint for manual triggering.

Developers can use tools like postman to send a request and enable trace on demand.

Note: This interface uses an internal, non-public SAP API that may change or be removed in future releases.

Important Consideration: Activating trace during unwanted runs or unexpected triggers can significantly increases message storage consumption. Always enable trace carefully only when necessary and disable it when no longer required.

Conclusion:

This interface demonstrates how trace activation in SAP CPI can be automated during development using internal API. While useful for streamlining debugging, it should be used with awareness since it relies on a non-public API.

I'd appreciate any insights, improvements or feedback on this approach.

Happy Integrating!

How to use Expert Search for SAP Notes & KBAs in SAP for Me

2026-02-19T16:31:07.041000+01:00

Searching through countless SAP Notes and Knowledge Base Articles (KBAs) can feel overwhelming, especially when you’re looking for something specific. The good news? SAP for Me’s Expert Search feature makes this task much simpler.

Before diving in, let’s clarify what SAP Notes and SAP Knowledge Base Articles (KBAs) are.

SAP Notes describe a software issue and its solution. They include a description of the symptoms, the cause of the error, and the SAP release and support package level in which the error occurs. Depending on the type of error, an SAP Note may also include workarounds and links to support packages that solve the problem, and most SAP Notes contain coding corrections.

SAP Knowledge Base Articles are practical "how-to" guides. Using business language, KBAs answer frequently asked questions arising from your daily work with SAP software. No coding corrections or modifications are provided.

Why Use Expert Search?

The “SAP Notes & KBAs Expert Search” in SAP for Me provides an at-a-glance view on relevant updates, helps you organize your favorite notes, and allows you to retrieve notes based on advanced selection criteria, especially as a recurrent task. This feature is extremely helpful if you carry out regular analyses of relevant notes.

Getting Started in 7 Simple Steps:

Login to SAP for Me with your S-user ID and password.
From the left-hand dashboard, navigate to Services & Support.
Click on the KBAs & Notes tab.
Select the “SAP Notes & KBAs Expert Search” card.
Click on the “Expert Search” tab.
Use the filter bar to specify your selection criteria.
- Example: Components (Starts): BC-DB*.
- As you begin typing the component key, the auto-completion feature will assist you in specifying the correct component. Only notes assigned to components that start with the entered key will be displayed.
Finally, click the “Go” button to run your search.

Note: No special authorization is required in your S-user ID to use the Expert Search function in SAP for Me. You can apply different filter criteria, such as Search Term, Software Component (Soft Comp), Component (Exact), and more.

For more information, please refer to the Knowledge Base Article (KBA): 2388433- Information about using Expert Search for SAP Notes & KBAs - SAP for Me.

Additional Resources:

Knowledge Base Article (KBA): 2478289 - How to set up notifications for new or updated SAP Notes and/or KBAs with Expert Search filters - SAP for Me

Got More Questions?

Please note that the Customer Interaction Center are always happy to guide you on any of the mentioned processes and assist you with any queries you may have!   

If you have any questions, please feel free to ask us in the Q&A  All Questions in Customer Experience | SAP Community and All Questions in Support Services | SAP Community 

Don't Miss Out on Free Webcasts 

We would like to invite you to our free webcasts, which we believe can help you get the best from your support in SAP. You can find all upcoming CIC Webcasts. These sessions are open to all the users and will revolve around hot topics in support today such as SAP for Me, Case Management, etc.

Additionally, you can explore a range of CIC how-to videos at learning.sap.com. Please feel free to share this information with your colleagues. We are looking forward to your attendance. 

Lastly, you may want to access all CIC Blogs here:  https://community.sap.com/t5/tag/CustomerInteractionCenter/tg-p/board-id/crm-blog-sap. 

Thank you for reading!  We hope you find this guide helpful.  

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 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:

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.

Customizing GRC NWBC screens globally without PFCG role update

2026-04-21T17:40:00.032000+02:00

Challenge: Fragmented GRC NWBC appearance and work center structure for different user groups in organisation leading to inconsistent UI layouts when accessing GRC functionality through NWBC, leading to reduced productivity and increased training costs. A uniform NWBC Landing page need to be established.

Implementation Approach: A uniform NWBC Landing page need to be configured which is applicable across all users accessing NWBC launch screen without changing roles.

In this blog, the detailed steps for configuring NWBC screens in highlighted.

Benefits

Eliminates Need for Technical ABAP Changes

Many minor UI adjustments, such as showing/hiding: Hyperlinks, Menu sections, Application nodes can be handled via customizing mode without involving developers

Helps Maintain Audit & Compliance Standards

Since NWBC is used by auditors, risk teams, and provisioning teams, controlling UI visibility helps ensure Least privilege navigation, No exposure of admin tools to business users, Clear segmentation of duties within the UI.

Environment: GRC Access Control 12.0

To achieve Centralized Control of UI Structure, GRC Admins can change what appears on NWBC for all users, from a single configuration point. No need to adjust individual roles repeatedly.

In NWBC landing page, Right click -> option ‘Call Application in customizing mode’.

Segregation of Duties approach to prevent unintended customization:

Authorization object S_WDR_ADM controls the access to option ‘Call Application in customizing mode’ through which elements like visibility of each hyperlink/section can be globally changed for all users.

GRC Admins (Super user) or User designated to perform NWBC UI changes can be assigned with Authorization object S_WDR_ADM with full access in the PFCG role
For all other users, restrict Authorization object S_WDR_ADM to display only or disable it in the PFCG role.

Steps:

NOTE: Exercise caution in applying these changes as it will be applicable to all users accessing NWBC irrespective of role assignment.

For Example - If there is a requirement that hyperlink ‘Work Inbox – Simplified’ should not be visible to any users who uses NWBC, then we can follow the below steps

1. Right Click on hyperlink ‘Work Inbox – Simplified’ -> Call Application in Customizing mode

2. Choose the Transport Request

3. Right click -> Call Application in Classic Customizing Mode

4. Right click -> Settings for Current Configuration

5. Set the Visibility to Invisible.

6. After the changes are applied, ‘Work Inbox – Simplified’ hyperlink is not visible. You can always switch it back to default by following the same previous steps

You can follow the same steps to customise other NWBC screen hyperlinks or buttons.

Conclusion:

You have now successfully customised the GRC NWBC screen to display only required hyperlinks for all users.

Configuring custom GRC NWBC Launch Screens restricted via PFCG roles

2026-04-22T06:00:00.054000+02:00

Challenge: Standard SAP GRC roles for NetWeaver Business Client (NWBC) grant excessive access privileges that exceed users' actual job requirements. This over-provisioning creates security risks and poor user experience, as users encounter numerous irrelevant hyperlinks and folders they don't need for their daily tasks.

Implementation Approach: The solution leverages transaction LPD_CUST (Configure Launchpad for Menus) to design custom NWBC landing pages. This involves copying standard Webdynpro application configuration, component configuration and UIBB component in which LPD_CUST role is linked.

In this blog, the detailed steps for configuring LPD_CUST, Web Dynpro Configuration and PFCG mapping is highlighted.

Environment: GRC Access Control 12.0

Launchpad Flow chart:

Section 1: LPD_CUST launchpad customisation

In Tcode LPD_CUST, we need to define the customization that is required for the workset, here we have considered GRACHOME (GRC Access Control Home Workset). It is recommended to take a copy of this workset to custom naming convention to preserve standard configuration.

Select line item GRACHOME, Click on copy.

Enter your custom values and namespace.

In ZGRACHOME, You can make all the required customisations. Here, for simplicity, I have modified the folder name to ‘Work Inbox - CUSTOM’.

Potential Use case 1: For Approvers users, you can keep only ‘Work Inbox’, Delete ‘Work Inbox - Simplified’ to make it more clear to users as to which one to use.

Potential Use case 2: In Application help, You can place company’s intranet URL link that points to a guide on how to review and approve requests. For this, you can create ‘New Application’ , select application type ‘URL’ and add the required URL.

You can follow the same steps to customize Setup, Access Management, Reports and Analytics Webdynpro Application

Section 2: NWBC Webdynpro customisation

In tcode PFCG, copy standard role SAP_GRAC_NWBC to custom role Z_TEST_NWBC,

Tcode PFCG -> Z_TEST_NWBC

Here, we are customizing the ‘My Home’ Webdynpro application GRFN_SERVICE_MAP.

Right click on ‘My Home’ Webdynpro application -> Details

We see the standard Configuration: GRAC_FPM_AC_LPD_HOME. We want to customize this Application Configuration to point our desired ‘My Home’ Layout in NWBC which we configured in LPD_CUST.

Click on ‘Application Configuration’ button.

This will launch a web URL which takes you to application configuration.

From here on, the logic is that we copy the Application Configuration, Component Configuration, UIBB Configuration and In UIBB configuration we point it to Role /instance of LPD_CUST. Refer to the flowchart.

Step 1: Create Copy of Application Configuration.

Click on Other Functions -> New Window -> Copy

Provide custom configuration ID and description

Select the relevant package, here I chose $TMP (Non-transportable), Click OK.

Click Change

We enter into the custom application configuration Z1GRAC_FPM_AC_LPD_HOME

Click on hyper link GRAC_FPM_CC_LPD_HOME

You will reach Component Configuration screen as below

Step 2: Create copy of component configuration

Click on Other Functions -> New Window -> Copy

Provide the custom configuration ID and description

Enter the desired package

Click Change

Click on Edit -> Cancel to get in Display mode, Click on hyperlink ‘GRAC_FPM_UIBB_LPD_HOME’

Step 3: Create copy of UIBB configuration

In this window, Click on Other Functions -> New Window

Click Copy

Provide the custom configuration ID and description

Click Change.

In this window, we need to map ZGRACHOME in Role field (earlier created in LPD_CUST).

Change it to ZGRACHOME. All the customizations done in ZGRACHOME can be previewed. Notice that we had changed folder ‘Work Inbox – CUSTOM’ in this scenario.

Click Save.

Select the TR and Click OK

Section 3: PFCG Role Configuration mapping

Step 1: In tcode PFCG, Role Z_TEST_NWBC

Right click on ‘My Home’ -> Details -> Change configuration to Z1GRAC_FPM_AC_LPD_HOME

Click Save

Step 2: Again, Right click on ‘My Home’ -> Details -> Click Application Configuration.

This will open up URL in web browser, we see that we are in custom application configuration Z1GRAC_FPM_AC_LPD_HOME, we see standard component configuration is mapped, we will need to change to custom component configuration Z1GRAC_FPM_CC_LPD_HOME

Click on Edit -> Assign Configuration Name

Assign the custom component configuration ID Z1GRAC_FPM_CC_LPD_HOME

Click Save.

Step 3: Click the hyperlink Z1GRAC_FPM_CC_LPD_HOME

This will open up Custom component configuration, we see that standard UIBB is mapped, but we need to change to custom UIBB Z1GRAC_FPM_UIBB_LPD_HOME

Click on F4 button on GRAC_FPM_UIBB_LPD_HOME, change it to Z1GRAC_FPM_UIBB_LPD_HOME

Click Save

Step 4: Click on Edit -> Cancel. We are in display mode. Click on hyperlink Z1GRAC_FPM_UIBB_LPD_HOME

You will find all the elements mapped as per the flowchart

Assign the PFCG role Z_TEST_NWBC to user and test the changes. Or you can Right click on ‘My Home’ -> Execute.

The customisation done in LPD_CUST reflects.

NOTE: If you assign standard role SAP_GRAC_NWBC and custom role Z_TEST_NWBC together to a user, this won’t work as intended since the system is confused whether to pick up the standard application configuration or the custom application configuration defined in the Webdynpro application GRFN_SERVICE_MAP. The intent of creating the custom role is to assign that specific custom role Z_TEST_NWBC to satisfy all NWBC access requirements for the user.

You can follow the same steps to customize Setup, Access Management, Reports and Analytics Webdynpro Application.

Conclusion:

You have now successfully created a custom PFCG role with Web Dynpro application configuration pointing to Custom NWBC screen.

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?

Test Migration Guide for Adapt Filters Dialog within the FilterBar

2026-05-15T10:15:28.606000+02:00

Overview

If you're maintaining OPA tests for applications using the Adapt Filters dialog, you'll need to update your test code to work with the revised UI structure. This guide walks you through the key changes and shows you exactly how to adapt your tests.

Prerequisites

To use the revised Adapt Filters dialog, you need to upgrade to SAPUI5 version 1.146 or a higher version. The current version is SAPUI5 1.148.

Understanding the Fundamental Changes

The revised version of the Adapt Filters dialog introduces a mode-based interaction model that separates different operations. Instead of having all functionality available in one place, the dialog now uses dedicated modes for different tasks:

Edit mode is used for adding filters, removing filters, and toggling visibility
Sort mode is used exclusively for reordering filters

This separation prevents accidental changes and makes each operation more intentional.

Key UI Changes at a Glance

The visual structure has changed significantly:

List/Group View Toggle: The icon-based toggle buttons have been replaced with text-based tabs. Instead of clicking on sap-icon://list or sap-icon://group-2, users now click on labeled "List" or "Group" tabs.

Filter Items: The old sap.m.ColumnListItem with checkboxes has been replaced with sap.m.CustomListItem, containing action buttons and filter controls.

Adding Filters: Instead of checking a checkbox in a long list of all available filters, users now select from a ComboBox dropdown labeled "Add Filter" at the bottom of the panel.

Removing Filters: Rather than unchecking a checkbox, users click an X button (with remove icon) in Edit mode.

Visibility Control: Filters can be hidden. An eye icon (with or without strikethrough) toggles visibility.

Reordering: The dedicated reorder buttons (Move Up, Down, Top, Bottom) are gone. Instead, users drag and drop filters in Sort mode. As an alternative, users can also reorder filter items with keyboard shortcuts as described under "Keyboard Shortcuts for Reordering".

Changed: The view toggle moved from icon buttons to text-based tabs.

Filter Button (New Feature): A new "Filter" button has been added to the dialog. When clicked, the dialog closes, and the filter bar control applies the current filter values to the associated control (Table, Chart, etc.). This provides a direct way to filter without having to close the dialog separately and then trigger filtering manually.

Test Code Examples

The following sections show what your test code could look like for individual actions. You can combine these examples to create complete test workflows.

Please note: In the code samples, globals are used, for example new sap.ui.test.actions.Press()

This explanation has been included in the code sample for clarity. Please do not use globals.

Import the dependencies via sap.ui.define and use new Press() in your test code instead.

Opening the Adapt Filters Dialog

To open the Adapt Filters dialog, your test code could look like this:

this.waitFor({
    controlType: "sap.m.Button",
    matchers: new sap.ui.test.matchers.Properties({
        text: "Adapt Filters"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Adapt Filters Dialog opened");
    }
});

Closing the Adapt Filters Dialog

To close the dialog, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.Button",
    matchers: new sap.ui.test.matchers.Properties({
        text: "OK"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Adapt Filters Dialog closed");
    }
});

Switching to List View

To switch to List view, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.IconTabFilter",
    matchers: new sap.ui.test.matchers.Properties({
        text: "List"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Switched to List view");
    }
});

Switching to Group View

To switch to Group view, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.IconTabFilter",
    matchers: new sap.ui.test.matchers.Properties({
        text: "Group"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Switched to Group view");
    }
});

Switching to Edit Mode

To switch to Edit mode, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.Button",
    matchers: new sap.ui.test.matchers.PropertyStrictEquals({
        name: "text",
        value: "Edit"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Switched to Edit mode");
    }
});

Switching to Sort Mode

To switch to Sort mode, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.Button",
    matchers: new sap.ui.test.matchers.PropertyStrictEquals({
        name: "text",
        value: "Sort"
    }),
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Switched to Sort mode");
    }
});

Adding a Filter

To add a filter via the ComboBox, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.ComboBox",
    success: function(aComboBoxes) {
        const oComboBox = aComboBoxes[0];
        new sap.ui.test.actions.Press().executeOn(oComboBox);

        this.waitFor({
            searchOpenDialogs: true,
            controlType: "sap.m.StandardListItem",
            matchers: new sap.ui.test.matchers.Properties({
                title: "Country"  // Replace with your filter name
            }),
            actions: new sap.ui.test.actions.Press(),
            success: function() {
                Opa5.assert.ok(true, "Filter 'Country' added");
            }
        });
    }.bind(this)
});

Finding a Filter Item by Name

To find a specific filter item in the list, your test code could look like this:

this.waitFor({
    searchOpenDialogs: true,
    controlType: "sap.m.CustomListItem",
    matchers: function(oItem) {
        const aContent = oItem.getContent();
        if (aContent && aContent[0]) {
            const aGridContent = aContent[0].getContent();
            return aGridContent.some(function(oControl) {
                return oControl.getText && oControl.getText() === "Country:";  // Replace with your filter name
            });
        }
        return false;
    },
    success: function(aItems) {
        Opa5.assert.ok(aItems.length > 0, "Filter item 'Country' found");
        // Store aItems[0] for further actions
    }
});

Removing a Filter

Note: You must be in Edit mode and find the filter item first (see "Finding a Filter Item by Name").

To remove a filter, your test code could look like this:

this.waitFor({
    controlType: "sap.m.Button",
    matchers: [
        new sap.ui.test.matchers.Ancestor(oFilterItem),  // oFilterItem from previous step
        new sap.ui.test.matchers.Properties({
            icon: "sap-icon://decline"
        })
    ],
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Filter removed");
    }
});

Toggling Filter Visibility (Show/Hide)

Note: You must be in Edit mode and find the filter item first (see "Finding a Filter Item by Name").

To toggle the visibility of a filter, your test code could look like this:

this.waitFor({
    controlType: "sap.m.Button",
    matchers: [
        new sap.ui.test.matchers.Ancestor(oFilterItem),  // oFilterItem from previous step
        new sap.ui.test.matchers.Properties({
            icon: "sap-icon://show"  // or "sap-icon://hide" depending on current state
        })
    ],
    actions: new sap.ui.test.actions.Press(),
    success: function() {
        Opa5.assert.ok(true, "Filter visibility toggled");
    }
});

Important: If a filter field has no value, hiding it will cause it to be removed entirely when the panel is reopened. To keep a filter in the panel while hidden, ensure it has a value before toggling visibility to hidden.

Reordering Filters via Drag and Drop

Note: You must be in Sort mode and find both source and target filter items first.

To reorder filters, your test code could look like this:

// Drag the source filter
new sap.ui.test.actions.Drag().executeOn(oSourceFilterItem);

// Drop on the target filter
new sap.ui.test.actions.Drop({ before: true }).executeOn(oTargetFilterItem);  // Use before: false to drop after
Opa5.assert.ok(true, "Filter reordered");

Complete Workflow Examples

Now that you have the test code examples, here are complete workflow examples that combine them.

Workflow: Adding a New Filter

Steps:

Open the Adapt Filters dialog
Switch to List view (recommended)
Add the filter using the ComboBox
Close the dialog

Usage scenario: You need to add one or more filters to the filter bar.

Workflow: Removing an Existing Filter

Steps:

Open the Adapt Filters dialog
Switch to List view
Switch to Edit mode
Find the filter item by name
Click the X button (decline icon) to remove it
Close the dialog

Usage scenario: You need to completely remove a filter from the filter bar.

Workflow: Hiding a Filter Without Removing It

Steps:

Open the Adapt Filters dialog
Switch to List view
Switch to Edit mode
Find the filter item by name
Click the eye icon to toggle visibility
Close the dialog

Usage scenario: You need to temporarily hide a filter but want to keep its configuration and value. Remember: filters without values will be removed when hidden.

Workflow: Reordering Filters

Steps:

Open the Adapt Filters dialog
Switch to List view
Switch to Sort mode
Find the source filter item (the one to move)
Find the target filter item (where to move it)
Drag the source filter and drop it on the target
Close the dialog

Usage scenario: You need to change the order in which filters appear in the filter bar.

Workflow: Switching Between List and Group Views

Steps:

Open the Adapt Filters Dialog
Click on the "List" or "Group" tab
Perform your desired actions
Close the dialog

Usage scenario: You need to work with individual filters (List view) or grouped filters (Group view).

Helper Functions

You can create reusable helper functions from the building blocks:

Helper: Add Multiple Filters

const fnAddFilter = function(sFilterName) {
    return this.waitFor({
        searchOpenDialogs: true,
        controlType: "sap.m.ComboBox",
        success: function(aComboBoxes) {
            const oComboBox = aComboBoxes[0];
            new sap.ui.test.actions.Press().executeOn(oComboBox);

            this.waitFor({
                searchOpenDialogs: true,
                controlType: "sap.m.StandardListItem",
                matchers: new sap.ui.test.matchers.Properties({
                    title: sFilterName
                }),
                actions: new sap.ui.test.actions.Press(),
                success: function() {
                    Opa5.assert.ok(true, "Filter '" + sFilterName + "' added");
                }
            });
        }.bind(this)
    });
}.bind(this);

// Usage:
fnAddFilter("Country");
fnAddFilter("Language");
fnAddFilter("Genre");

Helper: Finding and Removing Filters

const fnRemoveFilter = function(sFilterName) {
    return this.waitFor({
        searchOpenDialogs: true,
        controlType: "sap.m.CustomListItem",
        matchers: function(oItem) {
            const aContent = oItem.getContent();
            if (aContent && aContent[0]) {
                const aGridContent = aContent[0].getContent();
                return aGridContent.some(function(oControl) {
                    return oControl.getText && oControl.getText() === sFilterName + ":";
                });
            }
            return false;
        },
        success: function(aItems) {
            this.waitFor({
                controlType: "sap.m.Button",
                matchers: [
                    new sap.ui.test.matchers.Ancestor(aItems[0]),
                    new sap.ui.test.matchers.Properties({
                        icon: "sap-icon://decline"
                    })
                ],
                actions: new sap.ui.test.actions.Press(),
                success: function() {
                    Opa5.assert.ok(true, "Filter '" + sFilterName + "' removed");
                }
            });
        }.bind(this)
    });
}.bind(this);

// Usage (ensure you're in Edit mode first):
fnRemoveFilter("Country");

Keyboard Shortcuts for Reordering

The new panel also introduces keyboard shortcuts for reordering filters when in Sort mode. While these aren't directly testable via standard OPA5 (they require focus and modifier keys), you should be aware of them for manual testing:

CMD + Home (Mac) / Ctrl + Home (Windows): Move filter to the top
CMD + End (Mac) / Ctrl + End (Windows): Move filter to the bottom
CMD + Arrow Up (Mac) / Ctrl + Arrow Up (Windows): Move filter one position up
CMD + Arrow Down (Mac) / Ctrl + Arrow Down (Windows): Move filter one position down

For automated OPA tests, use the drag-and-drop approach shown above.

Quick Reference Guide

Mode-Based Actions

Remember that certain operations now require switching to specific modes:

Action	Required Mode	UI Element
Add filter	No mode required (default)	ComboBox at bottom
Remove filter	Edit mode required	X button (remove icon)
Toggle visibility	Edit mode required	Eye button (show/hide icon)
Reorder filters	Sort mode required	Drag handles (:::)

Control Type Changes

Here's a quick mapping of old to new control types:

Old Control	New Control	Usage
`sap.m.CheckBox`	`sap.m.ComboBox` + `sap.m.StandardListItem`	Adding filters
`sap.m.CheckBox`	Button with `sap-icon://decline`	Removing filters
N/A	Button with `sap-icon://show`/`hide`	Visibility toggle
`sap.m.ColumnListItem`	`sap.m.CustomListItem`	Filter list items
Button with reorder icons	Drag-and-drop actions	Reordering
Button with icon	`sap.m.IconTabFilter`	View switching

Common Matcher Pattern for Filter Items

You'll use this pattern frequently to find filter items by their label:

matchers: function(oItem) {
    const aContent = oItem.getContent();
    if (aContent && aContent[0]) {
        const aGridContent = aContent[0].getContent();
        return aGridContent.some(function(oControl) {
            return oControl.getText && oControl.getText() === "FilterName:";
        });
    }
    return false;
}

Wrapping Up

The new Adapt Filters dialog represents a significant UX improvement, but it does require updating your OPA tests. The key takeaways:

Use IconTabFilter with text for view switching
Use ComboBox for adding filters
Switch to Edit mode before removing filters or toggling visibility
Switch to Sort mode before reordering filters
Use CustomListItem with custom matchers to find filters
Use drag and drop for reordering instead of button clicks

FilterBar Adapt Filters Panel: UI Update

2026-05-15T10:16:11.061000+02:00

A Fresh Look at the Adapt Filters Dialog

The content of the Adapt Filters dialog has been revised to offer a clearer, more structured, and accessible user experience.

Visual Comparison: Old vs. Revised Design

Old design:

Revised design:

Mode-Based Interaction

A new mode switch further improves usability. Users can toggle between an Edit mode, where they adjust filter values and visibility, and a Sort mode, where they focus on arranging the order of filters. In the Sort mode, visual cues can be used for drag-and-drop interactions.

Easy Adding of Filters

Adding new filters is now a lot more transparent. The dialog now presents a dedicated section for adding filters, showing only those that are currently hidden and optional. This way, users won't be overwhelmed by long lists, and it helps them quickly identify which filters are available. The section is straightforward, with descriptive labels and input.

Smart Warnings and Guidance

The dialog also provides improved guidance when handling required filters or filters with values. Clear, contextual warnings appear when users attempt to hide a required filter, or when a hidden filter already contains a value. These messages help users understand the impact of their actions immediately. For example, if a required filter with a value is hidden, the user gets an information message that the field will not show in the filter bar.

Consistent and Intuitive Actions

Each filter entry now includes clearly identifiable actions, such as toggling visibility or removing a filter. These actions are consistently placed and use intuitive icons, so users can perform changes quickly. During the sorting of filters, a dedicated indicator appears to show that the filter can be repositioned.

Summary

Overall, the updated Adapt Filters dialog provides an accessible user interface, clearer workflows, and more informative messages. Users can find, adjust, and manage filters more easily, while the interface actively helps them avoid mistakes and maintain control over their filtering setup.

UI5 Web Components Angular Wrappers Have a New Home in Fundamental NGX

2026-06-10T11:31:47.136000+02:00

The Angular wrapper library for UI5 Web Components has moved.

@ui5/webcomponents-ngx and @ui5/theming-ngx are now deprecated.
Their successor packages ship as part of Fundamental NGX

- @fundamental-ngx/ui5-webcomponents
- @fundamental-ngx/ui5-webcomponents-fiori
- @fundamental-ngx/ui5-webcomponents-ai

What you gain

The new packages integrate with Fundamental NGX's theming, content density, and i18n systems - features that previously required manual wiring or weren't available at all.

What changed

This is a breaking change. Template bindings and some enum values need updates. See the migration guide for complete details.

How to migrate

1. Install new packages, uninstall old ones
2. Update template bindings from kebab-case to camelCase ([primary-title] → [primaryTitle])
3. Update ValueState values (Error → Negative, Warning → Critical, Success → Positive)
4. Replace theming and i18n setup

Questions or issues?

File them at: https://github.com/SAP/fundamental-ngx/issues

Migrating from @ui5/webcomponents-ngx to @fundamental-ngx/ui5-webcomponents*

2026-06-10T11:32:24.179000+02:00

Effective: 2026-04-27 - @ui5/webcomponents-ngx and @ui5/theming-ngx are deprecated and no longer maintained.

Successor packages are part of the Fundamental NGX monorepo.

Package Mapping

Old package	New package
@ui5/webcomponents-ngx	@fundamental-ngx/ui5-webcomponents
@ui5/webcomponents-ngx (fiori sub-path)	@fundamental-ngx/ui5-webcomponents-fiori
@ui5/webcomponents-ngx (AI sub-path)	@fundamental-ngx/ui5-webcomponents-ai
@ui5/theming-ngx	Remove - replaced by Fundamental NGX theming (see below)

Breaking Changes

1. Property Binding Names (kebab-case → camelCase)

All input property bindings changed from kebab-case to camelCase.

The old @ui5/webcomponents-ngx library bound HTML attributes using kebab-case. The new @fundamental-ngx/ui5-webcomponents library exposes proper Angular input signals with camelCase names.

Every template binding must be updated

Old (@ui5/webcomponents-ngx)	New (@fundamental-ngx/ui5-webcomponents)
[primary-title]="'Title'"	[primaryTitle]="'Title'"
[value-state]="'Error'"	[valueState]="'Negative'"
[accessible-name]="'Search'"	[accessibleName]="'Search'"
[accessible-name-ref]="'labelId'"	[accessibleNameRef]="'labelId'"
[no-typeahead]="true"	[noTypeahead]="true"
[show-notifications]="true"	[showNotifications]="true"
[no-data-text]="'No results'"	[noDataText]="'No results'"

Rule: Convert every kebab-case attribute to camelCase Angular property binding. Standard HTML attributes (`id`, `class`, `style`, `slot`) are unchanged.

2. ValueState Enum Values

@ui5/webcomponents-ngx exposed ValueState using outdated property names. The new @fundamental-ngx/ui5-webcomponents library uses the current UI5 Web Components naming:

Old (@ui5/webcomponents-ngx)	New (@fundamental-ngx/ui5-webcomponents)
Error	Negative
Warning	Critical
Success	Positive
Information	Information (unchanged)
None	None (unchanged)

Before:

<ui5-input [value-state]="'Error'"></ui5-input>
<ui5-input [value-state]="'Warning'"></ui5-input>
<ui5-input [value-state]="'Success'"></ui5-input>

After:

<ui5-input [valueState]="'Negative'"></ui5-input>
<ui5-input [valueState]="'Critical'"></ui5-input>
<ui5-input [valueState]="'Positive'"></ui5-input>

3. i18n Translation Management

@ui5/webcomponents-ngx/i18n provided built-in translation strings. The new wrappers do not include translation strings - only language code synchronization.

You must provide your own translation layer (custom I18nService, @ngx-translate, or similar).

Import Path Rewrites

Before:

// app.module.ts / app.config.ts
import { Ui5WebcomponentsModule } from '@ui5/webcomponents-ngx';
// or individual sub-paths:
import { ... } from '@ui5/webcomponents-ngx/main';
import { ... } from '@ui5/webcomponents-ngx/fiori';
import { ... } from '@ui5/webcomponents-ngx/ai';

// theming bootstrap (old)
import { Ui5ThemingModule } from '@ui5/theming-ngx';

bootstrapApplication(AppComponent, {
  providers: [
    importProvidersFrom(
      Ui5ThemingModule.forRoot({ defaultTheme: 'sap_horizon' })
    ),
  ],
});

After:

// app.config.ts — component imports are per-package now
import { Button }    from '@fundamental-ngx/ui5-webcomponents/button';
import { ShellBar }  from '@fundamental-ngx/ui5-webcomponents-fiori/shell-bar';
import { AIButton }  from '@fundamental-ngx/ui5-webcomponents-ai/ai-button';

// Theming setup — choose one approach
import { ThemingModule } from '@fundamental-ngx/core/theming';
import { provideUi5LanguageBridge } from '@fundamental-ngx/ui5-webcomponents-base/i18n';

// OPTION A: Automatic theme sync (standalone app)
import { provideUi5ThemingBridge } from '@fundamental-ngx/ui5-webcomponents-base/theming-bridge';
import { provideEnvironmentInitializer } from '@angular/core';
import { Ui5WebcomponentsMainThemingService }  from '@fundamental-ngx/ui5-webcomponents/theming';
import { Ui5WebcomponentsFioriThemingService } from '@fundamental-ngx/ui5-webcomponents-fiori/theming';

bootstrapApplication(AppComponent, {
  providers: [
    provideTheming({ defaultTheme: 'sap_horizon' }),
    provideUi5ThemingBridge(),   // listens to ThemingService and syncs automatically
    provideUi5LanguageBridge(),  // syncs language code (e.g. 'en', 'de') to UI5 Web Components
    provideEnvironmentInitializer(() => inject(Ui5WebcomponentsMainThemingService)),
    provideEnvironmentInitializer(() => inject(Ui5WebcomponentsFioriThemingService)),
  ],
});

// OPTION B: Manual theme sync (module-based app or single theme switcher)
@NgModule({
  imports: [
    ThemingModule.withConfig({ defaultTheme: 'sap_horizon' }),
    // ... UI5 component imports
  ],
  providers: [
    provideUi5LanguageBridge()  // language sync only
  ]
})
export class AppModule {}

// Then call ThemingService.setTheme() directly when switching themes:
// this.themingService.setTheme('sap_horizon_dark');

Which approach to use:

Option A (automatic): If your app calls `ThemingService.setTheme()` from multiple places, the bridge keeps UI5 components in sync automatically.
Option B (manual): If you have a single theme switcher component, calling `ThemingService.setTheme()` directly is simpler. The service loads the correct CSS; UI5 components pick it up.
i18n caveat: provideUi5LanguageBridge() syncs the language code (e.g. `en`, `de`, `bg`) to UI5 Web Components. It does NOT provide translation strings for your app. You must manage translations separately via a custom I18nService, @ngx-translate, or similar.

Worked example — single component

Before:

// my-app/src/app/app.component.ts
import { Component } from '@angular/core';
import { Button } from '@ui5/webcomponents-ngx/main';

@Component({
  standalone: true,
  imports: [Button],
  template: `<ui5-button design="Emphasized" accessible-name="Save button">Save</ui5-button>`,
})
export class AppComponent {}

After:

// my-app/src/app/app.component.ts
import { Component } from '@angular/core';
import { Button } from '@fundamental-ngx/ui5-webcomponents/button';  // ← import path change

@Component({
  standalone: true,
  imports: [Button],
  template: `<ui5-button design="Emphasized" [accessibleName]="'Save button'">Save</ui5-button>`,  // ← camelCase binding
})
export class AppComponent {}

NGX APIs Now Available

Consumers of the new packages automatically gain access to Fundamental NGX cross-cutting features that were not available in the standalone @ui5/webcomponents-ngx library:

Feature	How it works
Theming	Use ThemingModule.withConfig() or provideTheming() for the initial theme. Optionally use provideUi5ThemingBridge() to auto-sync theme changes. See theming section above for both approaches.
Content density	ContentDensityObserver is injected into every wrapper component. Compact/cozy mode follows the NGX content density setting.
i18n / language	provideUi5LanguageBridge() syncs the active NGX language code to UI5 Web Components. Translation strings must be provided separately.

Steps Summary

1. Install new packages:

npm install @fundamental-ngx/ui5-webcomponents \
               @fundamental-ngx/ui5-webcomponents-fiori \
               @fundamental-ngx/ui5-webcomponents-ai \
               @fundamental-ngx/ui5-webcomponents-base

2. Uninstall old packages:

npm uninstall @ui5/webcomponents-ngx @ui5/theming-ngx

3. Update template bindings - convert kebab-case to camelCase (see Breaking Changes above):

[primary-title] → [primaryTitle]
[value-state] → [valueState]
[accessible-name] → [accessibleName]
etc.

4. Update ValueState enum values:

Error → Negative
Warning → Critical
Success → Positive

5. Replace theming bootstrap (see Import Path Rewrites → Theming above).

6. Provide translation strings if your app used `@ui5/webcomponents-ngx/i18n` — the new wrappers only sync language codes, not translations.

7. Build and verify. No template or input/output changes required.

Migration Tool

The `@fundamental-ngx/mcp` server includes a detailed migration guide. If you have the MCP server connected, run:

get_usage_guide("migrate-from-ui5-webcomponents-ngx")

Out of Scope

This guide covers migrating between the two wrapper libraries only.

Questions and Follow-up Issues

File issues at: https://github.com/SAP/fundamental-ngx/issues

Service	SAP Process Integration Runtime
Plan	API
Roles	TraceConfigurationEdit, TraceConfigurationRead