m {1 Products and Technology Groups Partners Topics. Events. What'sNew Get Startec ni t ‘SAP Community > Products and Technology > Technology > Technology Blogs by SAP > SAP Fiori for SAP SI4HANA - What is Key User Exten... Technology Blogs by SAP Leam how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP. ABAP, SAP Analytics Cloud, SAP HANA, and more Blog What are you looking for today? _ is Key E ibility Who are your Key Users 7) ©” Jocelyn_Dart Product and Topic Expert © 2022 Nov 04 3:44 AM 52Kudos | © 35,394 SAP Managed Tags: SAP Fiori, SAP Fiori for SAP S/4HANA, SAP Build Work Zone, standard edition, SAP S/4HANA, SAP Fiori Launchpad, SAP S/4HANA Cloud Private Edition, SAP S/4HANA Cloud Public Edition Latest Updates: + June 2024: More blogs from Georg Wilhem on custom fields with intent navigation + May 2024: Added some blogs on using custom logic and custom code lists * March 2024: Added a blog on Data Source Extensions Need another field in "Manage Customer Line Items" or "Manage Supplier Line Items"? Data source exte... and another on Custom Fields Custom fields for the "Manage Customer Line Items” app: use case both by Angelika Huber + November 2023: dded a new blog on Extensibility how to implement Custom Fields using Coding Block business context in SAP S/HANA Clo+ June 2023: Adding a brand new blog post on App Variants by valued colleague Leslie Castle SAP Fiori for SAP S/4HANA — App Variants are the EASY way to control App Features * May 2023: Adding a blog with a nice example of Manage Date Functions Creating Dynamic Date filter using the Manage Date Function App + April 2023: Linked in blogs on adapt ui, custom fields, flexible workflow, situation handling, and custom situations. + February 2023: Added a new blog SAP Fiori for SAP S/AHANA ~ Yes Key sers can create default app settings for filters, tables, and c + January 2023: Linked in the blog Custom Reusable Elements, Custom Business Objects and Data Source Extension to add fields in standar... how to create custom objects to extract data for custom analytics. + December 2022: Added a new blog on how key user can preset default values for other users. When it comes to configuring, adapting, and extending your SAP S/4HANA solution, key user extensibility provides powerful low-code/no-code features to manage customer-specific changes for your solution. These changes can be made during your implementation project, during an upgrade project, and at any time you need. Even better, key user extensibility changes can be made by your business experts, a central process governance group, your functional consultants, or used by your technical team. Who makes the changes is really up to you!Key Users are authorized to make changes to apps on behalf of other users. Source: SAP stock images In many cases, key user extensibility is the first option you should consider when you need to make a change to a user interface or to a business process, because compared to other extensions key user extensions are: ‘Simple — no-code/low-code Cost-effective - require minimum cost/effort/skill Upgrade-stable — are automatically retained as you upgrade releases Safe - many of these changes be undone or reset, if needed For example, you can use key user extensibility to add, remove or reorganize fields in many SAP Fiori apps, as shown in this example of SAP Fiori app F1511A Create Maintenance Request with UI Adaptation mode being used to add, remove or reorganize fields on the user interface.‘New Mantenance Request General Data Adapt UI can be used to add, remove, relabel, and reorganize fields and features. Example of UI Adaptation mode as it appears in the SAP Fiori app F1511A Create Maintenance Request You can find videos showing you the Adapt UI process in the SAP Help Portal in the SAP Fiori Launchpad User Guide section Personalizing and Adapting Apps, for example: Adapting SAP Fiori Uls can be this simple. Adapt Ul is just one type of key user extensibility. So keep reading to understand: + Where do you find Key User Extensibility + What types of changes can be made with Key User Extensibility + Who are your Key Users + Key User Extensibility FAQ + Where to find out more about Key usersWhere do you find Key User Extensibility Key user extensibility is a cloud-centric approach to making the most common changes needed to User Interfaces (UIs) and to business processes. This same cloud centric approach is applicable even in on-premise. Key user extensibility is available when using: SAP S/4HANA Cloud, public edition SAP S/4HANA Cloud, private edition SAP S/AHANA on-premise ‘SAP Build Work Zone, standard edition (formerly SAP Launchpad Service) For example, in SAP S/4HANA cloud, private edition and on-premise, key user extensions: * are mostly made directly in SAP Fiori apps, * are built into many SAP Fiori apps + For example, your custom fields can be added to SAP Fiori apps and to GUI transactions at the same time using SAP Fiori app F1481 Custom Fields. You can update at the same time reports, business scenarios, form templates, email templates, and APIs fin some cases, can even change classic Uls - such as GUI transactions - alongside related SAP Fiori apps + can be used to improve your business processes, such as flexible workflow, output management, and situation handling You can even use key user extensions in your own custom Fiori apps. For example: + Provided your developer applies the technique SAPUIS Flexibility Services when building your custom apps, your custom apps can provide the Adapt Ul feature to change the visibility of fields and features. + Public and Role-Specific Views are built-in to custom apps based on SAP Fiori elements floorplansWhat types of changes can be made with Key User Extensibility Key user extensibility is designed to cover the most common changes that, customers typically need to make. For example, in SAP S/4HANA cloud, private edition and on-premise, key user extensibility enables you to: * Add custom fields + Examples for finance Extensi + E.g. To make them available in existing apps, forms, APIs, OData Services, and/or CDS Views how to implement Custom Fields using Coding Block business context in SAP S/4HANA Clou... by Shuge Guo + How to create custom fields in the Business Process with “Custom Field Fiori App (ID F1481)” by s4h_sd_dem + S/4HANA Cloud: Manage Search Model with Custom fields + Custom fields for the "Manage Customer Line Items" app: use case by Angelika Huber + Enrich SAP S/4HANA Key User Custom fields with Intent-Based Navigation by George Wilhelm + Custom field type “Code list based on CDS view”: Finding/defining the right value help view and the ... by Georg Wilhelm + SAP S/4HANA Key User Extensibility: Custom field with context-dependent value help by Georg Wilhelm Add custom logic + Custom Logic to Implement Flexible Billing Document Numbering by Sahil Grover + Debugging custom logic using ADT in SAP S/4Hana Cloud by Cristina Adams Add custom business objects + API operations for Custom Business Objects in S/4HANA Cloud by Varun Venkat + Custom logic with multi-level Custom Business Objects in S/4HANA Cloud by Varun Venkat Add custom reusable elements - such as code lists for value helps + Key User Custom Fields: When to use what type of code list by Georg Withelm Add standard fields to existing apps using Data Source Extensions* Refer to Need another field in "Manage Customer Line Items” or "Manage ‘Supplier Line Items"? Data source exte... by Angelika Huber * Adjust the visibility of fields and features(buttons, tables, tabs, cards, etc.) using Adapt UI + Expose hidden fields and features + Reorganize standard fields and features (buttons, tables, tabs, cards, etc.) + Hide standard fields and features (buttons, tables, tabs, cards, etc.) + Refer to Converting a SAP Fiori “Mana; using Adapt Ul by c.hebbert pp to a Display Only. * Create custom analytics and custom KPIs * Create custom CDS Views, custom business objects, and reusable elements - e.g. to extract data for custom analytics * Refer to Custom Reusable Elements, Custom Business Objects and Data Source Extension to add fields in standar... by makoon * Create saved sets of default values + Refer to SAP Fiori for SAP S/AHANA — Yes Key Users can set Default Values for other Users by jocelyn.dart * Create app views — to pre-set default filter settings, table settings, and chart settings * Refer to SAP Fiori for SAP S/4HANA — Yes Key Users can create default app settings for filters, tables, and c.., by jocelyn.dart + Create app variants - copies of apps with certain features defaulted or hidden + Refer to SAP Fiori for SAP S/4HANA — App Variants are the EASY way to control App Features + Another example is found in Converting a SAP Fiori “Manage” app to a Display Only using Adapt UI by c.hebbert + Maintain translations * Add custom search objects + Manage custom date functions (single dates and date ranges) for analytics + Refer to a simple example of Manage Date Functions Creating Dynamic Date filter using the Manage Date Function App * Manage launchpad layouts (spaces and pages) + Manage teams and responsibilities + Manage flexible workflows + Flexible Workflow in Documents by ivan.ramirez2* Flexible Workflow for Sourcing and Procurement in SAP S/4HANA by chelliah.soundar * Manage situations (available from SAP S/4HANA 1909) + For some examples from our RIG team refer to: «Situation Handling — Case Notification for Managing Financial Transactions by betty.guedez2 « Situation Handling ~ Case Invoice Skipped in Payment Advice by betty.guedez2 + Use Case for Situation Handling ~ MRP Material Exceptions by kusiel.camargo + Situation Handling: Use Case — Confirmation is Overdue for PR Item by jose.marquezmares + Create custom situations (available from SAP S/4HANA 2021 FPS02) * Refer to Custom Situation Use Cases for SAP S/4HANA and the accompanying 6 part series by angelika.salmen : + Custom Situation Cases: Configure Your Own Use Cases (1/6) + Custom Situation Cases: Model Your Own Situation Objects (2/6) + Custom Situation Cases: Create Your Own Situation Scenarios (3/6) * Custom Situation Cases: Confi * Custom Situation Cases: Cor * Custom Situation Cases: Cor jure a Simple Use Case (4/6) ure an Escalation Case (5/6) jure a Complex Use Case (6/6) + Manage machine learning scenarios with the Intelligent Scenarios apps These types of changes can be made on behalf of all users of your solution. + Example 1: You can preset default values for other users, e.g. preset values for newbies, for your team, for different shared services roles. Refer to blog post Yes Key Users can set Default Values for other Users Many of these changes can be made role-specific to a business role. + Example 1: You can create an app variant that limits the available actions of an app, such as creating a display-only version of a Manage+ Example 2: You can create a role-specific view for filter/table/chart settings. Refer to blog post SAP Fiori for SAP S/AHANA — New options for managing Views for filters tables and charts + Example 3: You can choose a team of pilot users to receive situations. Refer to Situation Handling: How to use Responsibility Management efficiently Most of these changes are made via SAP Fiori apps or features. You can find a summary of many of the extension apps in blog post SAP Fiori for SAP Who are your Key Users To put it simply, key users are whomever you authorize to make changes on behalf of other users. For example, only authorized key users can access the Adapt UI feature in the taunchpad. Nev Maintenance Request, Key User Maintenance Techican \ General DateWhen in a SAP Fiori app, authorized key users can access the Adapt UI feature in the User Actions (Profile) menu. In this example you can see Adapt UI just above the Sign Out option. Who you designate as your key users can change over time or differ for different types of key user extensions. You choose how you want to govern key user extensions. You can change your governance approach over time, as your team and your business users build their skills and get comfortable with Key User Extensions. Some governance options are: + During your project, you might designate your functional consultants as your key users to make some initial adjustments as they discuss business needs directly with your business stakeholders + As part of UAT and system handover, you might run some knowledge transfer sessions then designate your subject matter experts as key users. This lets them make any further adjustments needed as you move into your after go-live hypercare period, or for ongoing changes once your solution is running business-as-usual. + Some organizations have a central process governance group who might be designated as responsible for key user changes or for certain types of key user extensions. + For example, you might want your central process governance group to control adding custom fields, so that you don't end up with several teams creating similar fields You might give some key user capabilities to your IT team or even selected developers — as key user functions can be the most effective way to extend your apps and the essential way to add custom fields. * For example, as you build your skills into intelligent technologies, you might want your IT team to make some initial settings for your pilot machine learning or situation handling use cases.Because key user extensibility uses a no-code/low-code approach, by making selected business users responsible for the changes themselves you can minimize lost-in-translation errors and communication overhead between business and IT. Remember that at all times, your technical team still maintains control over who is authorized to make changes, and when and where those changes are applied to your system landscape. Where do key users make their changes While some changes can be made in production, for the most part key users usually make their changes in your development environment. You can understand how this works with a couple of example use cases. + Use case 1 is an example of a change that must be made in development environment and then transported to production. + Use case 2 is an example of a key user change that could be made either directly in your production environment, or in your development environment and then transported through your system landscape. Use case 1 - Creating a Display only copy of a Manage app It's a common need to restrict the features of an app to create a simpler version for a different set of users. Consider the needs of casual users versus experts. Your casual users may need an app to review and check data, but don't have time to build the skills or policy knowledge to make changes. So you want to restrict the actions available. For example, you decide you want to give some casual users who create and track purchase requisitions from time to time, a restricted feature “copy” of SAP Fiori app £2229 Manage Purchase Requisition Professional. You still want to retain the original full-featured app for your more experienced purchasing officers who will use the app every day. Restricting features of an app is something you can do using Adapt Ul. To save your restricted version for your casual users, in Adapt UI you save your changes as an App Variant.An App Variant is effectively a copy of the app with your UI adaptations applied. By creating an app variant you can meet the needs of your casual users, while retaining the original full-featured app for your purchasing officers. Of course, before your casual users can use the app variant: + The App Variant needs to be assigned to your casual users via their business role. + You will need to coordinate with your security administration to assigning your app variant to the correct business roles. * Your security administrator typically updates the business role authorizations in your development environment. Then they will want to check and test them to make sure all the authorizations are correct. So this type of key user change is usually performed in a development environment and then the app variant and the role assignments are transported to. production. To see how this works refer to openSAP microlearning Adapting the Ul of List Report Apps - SAP S/4HANA User Experience Use case 2 - Set a default public view for a Monitor app Many SAP Fiori apps have smart filter bars, smart tables and smart charts that you can use to preset default settings such as filters/columns/measures shown, sort, chart type, etc. For example, for SAP Fiori apps such as £4332 Emission Forecast or £2375 Supervise Collections Worklist or £2358 Monitor Purchase Order Items or F5105. Maintenance Backlog Overview These settings are personalization options that can be set by each individual user for themselves. But what if you are the most experienced person on your team? Rather than teach everyone in your team how to make these settings to get the most out of the app, you want to share the best possible combination of filters, table andchart settings for your team. You might even want to create several different combinations of settings for different use cases - such as one for every day business- as-usual and another for end of fiscal period tasks. Sharing optimal personalization settings with your team is something you can do as a key user by creating public views (for everyone) or role-specific views (for people in one or more business roles). There is no need to change permissions - all of the users you are impacting already have access to the app. So this type of key user change can be made directly in a production environment, if you wish. Hint: Remember that if you create the view in production environment it will only be available in your production environment. This means you cannot use it for testing or training scenarios in your testing/training environments. However, if you create the view in your development environment, you can transport the view to your testing/training environments as well as your production environment. So then your view is available in all environments. To find out what's possible for views, read SAP Fiori for SAP S/4HANA — New options for managing Views for filters tables and charts How to decide which key user changes to make in your development environment Essentially many key user extensions are analogous to configuration changes. Applying the change impacts multiple people depending on their participation in your business processes. Where changes only impact the designated team and do not require further coordination with your administrators, you can consider making the changes in production. For example: public or role-specific views; creating new flexible workflows from exisiting templates; adjusting the notification text of a situation: It's worth keeping in mind, that you may also want to create changes in the development environment to make user testing easier. That is, you want the changes available in your quality assurance / testing system as well as your production environment.Some changes require coordination between you and your administrators, especially where authorizations need to be adjusted to match your changes. That coordination almost always needs to happen in the development environment. You will need everything to be correctly aligned and tested before it impacts your business users. For example: app variants; changes to launchpad layouts; custom fields; and custom logic. Understanding the high level process for making a key user change With most key user changes you will follow a process: 1. Apply the key user extension 2. Coordinate with your administrators, e.g. to adjust any settings for the impacted business roles 3. Deploy the extension to your testing/training environment 4. Test it to make sure it does what you need 5. Deploy the extension to your production environment This means you will capture the changes against a transportable request in your development environment. Not something your business users are comfortable doing? Don't worry! Key user extensibility includes the Adaptation Transport Organizer, which is a mechanism that ensures: + Your business creates changes and controls when changes are published, i.e, marked as ready for transport * Your IT technical team controls the transport process itself, i.e. assigning objects against software packages and transport requests, and exporting/importing the transports to your other systems. There are even companion SAP Fiori apps provided for your IT team to help them manage key user transports such as F1590 Configure Software Packages, F1589 Register Extensions for Transport, and £2587 Extensibility inventory. Key User Extensibility FAQ1. Can we just ignore key user extensibility for now 2. What if we aren't ready to give business users access to our development environment? 3. What are the most common key user extensions? 4, How do | get started with key user extensions? Q1. Can we just ignore key user extensibility for now? ‘Sometimes customers come to the SAP S/4HANA RIG team and say "Key users are new to us. We are taking a Technical Upgrade approach to our move to SAP S/4HANA. Can we just ignore key user extensibility for now?" This is how we usually respond: + Key User Extensibility covers the most common types of changes most customers need. + That means even on a “technical upgrade” project you will probably need to use at least some key user extensions. + For organizations moving to SAP S/4HANA, usually the first key user extensions you will need are: Custom Fields to add additional fields Adapt UI to make adjustments to user interfaces Public/Role-Specific Views to preset optimal defaults for apps Custom Analytical Queries to add your own custom analytics Manage KPIs and Reports to preset optimal settings for SAP- delivered analytics Q2. What if we aren't ready to give business users access to our development environment? Sometimes when we talk to customers about key users the first reaction is... oh we can't do that because we've never done that before. We've never given businessusers access to the development environment. That's ok... ! You can always make your IT team and your project team — e.g. your functional team leads — your pilot key users. That gives you a chance to build your skills. Just don’t forget that changes can come at any time... so make sure you nominate someone to take on this role post your first SAP S/4HANA go-live. Q3. What are the most common key user extensions? The most common key user extensions are: Custom Fields to add customer-specific fields to processes Adapt UI to change the visibility of fields and features Views for filters, tables, and charts Manage KPIs and Reports to adjust settings for SAP-delivered analytics Custom Analytical Queries to create additional reports Q4. How do | get started with key user extensions? The important first steps are: * Try out some of the key user extensions to build your skills and understanding + The most popular tools for new customers are SAP Fiori apps F1481. Custom Fields, F2814 Manage KPIs and Reports, and F1572 Custom Analytical Queries + Adapt UI and Views are delivered built into many SAP Fiori apps so you need to make sure you have authorized key users + Decide who will be responsible for key user extensions and who will make them + Asimple RACI matrix can help here «Start including key user extensibility into your governance and transport processes.Where to find out more about Key users For Business Users: + Find example videos and description of features in the SAP Help Portal for SAP S/4HANA in the SAP Fiori launchpad User Guide section Adapting SAP Fiori Uls at Runtime - Key User Adaptation + You will also find some Task Tutorials in your SAP S/4HANA User Assistant For Solution Architects, Administrators, and your Technical Team: You will find a slide deck summary of the concept at Key User Extensibility Overview for the ABAP Platform. Further references: + Find out about Key users and UI5 Flexibility as a cloud-centric approach in the SAP Help Portal in What is UIS Flexibility for Key Users + Understand the concept of Key User Extensibility vs other extensibility types in the ABAP Platform help in the SAP Help Portal: Key User Extensibility + Find out which Extensibility option suits your needs in the ABAP Platform help in the SAP Help Portal section Extensibility + Find more FAQs for using Key User Extensibility in SAP S/4HANA on- premise and SAP S/4HANA Cloud, private edition in SAP Note 3077994 - Frequently asked questions about Extensibility in SAP S/4 HANA On Premise + Yes you can use Key User extensibility with the SAP Launchpad Service as explained in Key User Adaptation in SAP Launchpad service is available out-of-the-box + For more on the Adaptation Transport Organizer refer to: SAP Fiori for SAP S/AHANA ~ Ad: ort Organizer tation Tran:+ Find out how to configure the Adaptation Transport Organizer in the ABAP Platform help on SAP Help Portal — section Configuration Information: Adaptation Transport Organizer For Developers looking to include SAPUIS Flexibility Services in custom apps refer to the following blog posts: Ic le [a x. fc < eS iS 2 i \ IE i id & is IS id ig. ig iB kn > Po IS a a ey Bx, IS 2 H L it ie Is i 5 is 2 lo iS le iB kp B = 3 E B iB & e 5 e S 2 E ie ls B 5 ge E. B E. > lo > i Ic g E < \Sers Buzz #55: Adaptation Project — your one stop tool for extending SAPUIS5 Applications Customer blogs about key user extensibility: * Quick tip: How to check if the changes from the adaptation project are active? Worth Knowing for your Solution Architects and Technical Team Key user extensibility is sometimes referred to as in-app extensibility. Key user extensibility is part of SAP’s Clean Core paradigm as explained in Custom Extensions in SAP S/4HANA Implementations - A Practical Guide for Senior IT Leaders! You can also find a one level deeper overview in the new guide Extend SAP S/4HANA in the cloud and on premise with ABAP based extensions as explained in New Extensibility Guide for S/4HANA is available. This new guide explains some of the technical background and considerations and is recommended for your solution architects and technical team,Tip: Some more complex extension approaches that support the Clean Core principle are also considered upgrade-stable, such as those included in the on-stack developer extensibility model. So, if you find that key user extensions are not sufficient for your particular use case, you should consider using an upgrade-stable alternative. For your developers: If you are creating custom apps, or using 3rd party apps from a partner, you can apply key user extensibility in your own custom apps via SAPUIS Flexibility Services. Becoming a SAP Fiori for SAP S/4HANA guru You'll find much more on the community topic page for SAP Fiori for SAP S/4HANA Other helpful links in the SAP Community: Follow our tag SAP S/4HANA RIG for more from the SAP S/4HANA Customer Care and RIG See all questions and answers about SAP Fiori for SAP S/AHANA Follow SAP Fiori for SAP S/4HANAfor more blogs and updates Ask a Question about SAP Fiori for SAP S/4HANA Brought to you by the SAP S/4HANA Customer Care and RIG. Labels: Expert Insights Tags: S4HANARIG SAP S4HANA 2022 sap shana rig 11 Comments[ED ThomasSchneider Product and Topic Expert ° 2022 Nov 04 8:53 AM 3 Kudos Hi Jocelyn, a very nice blog, | like it a lot! Here is also a presentation on the different key user tools in the ABAP platform: Extensibility ~ ABAP Platform Best regards, Thomas EY Jocelyn_Dart Product and Topic Expert 2 Kudos Thanks Thomas! I've also linked that into the references section. Much appreciated! ° 2022 Nov 04 8:55 AM gs _ shavneeta Participant o 2022 Nov 07 4:21. AM 1 Kudo Hello Jocelyn, Very Nice Summarized blog, thanks for this. Iwas using this Adaption technique for one of the standard Fiori App delivered by SAP , and the app is Fiori element based app , Record defect app.While , when i click on Adapt UI, i get a pop up : "App is not enabled for Adaption’: Could you please help here , what is missing here ? Thanks and Best Regards , Shavneet Singh 4 S07 Olivercraett Product and Topic Expert 1 Kudo Hello Shavneet Singh. background is SAPUIS5 Flexibility: Enable Your Ay oO 2022 Nov 07 5:40 AM Could you kindly check for the Record defect app and get it fixed in that app, e.g. via an incident to SAP? Thanks a lot, Oliver former_member767710 Explorer 1 Kudo Hey Jocelyn, °Q 2022 Nov 30 7:37 AMLoved the article. Vey well summarized. Savan HelenaSva H Explorer °Q 2023 May 25 11:51 AM Hey Jocelyn, I really appreciate the work that has gone into writ you for making it easier for us! Helena 1g and curating this article. Thank Cc Clara villatobo-Galindo Advisor o 2023 Jun 07 2:18 PM 1 Kudo Excellent blog Jocelyn! Thanks for sharing SeanBeasley Explorer ° 2023 Nov 02 9:22 PM 0 KudosExcellent, Thanks for sharing gs Sabyatats Explorer ° 2023 Nov 14 3:20 AM Thanks Jocelyn! Excellent article. Could you please point out if there was a way to make a field mandatory on a standard Fiori App. ? regards saby p _ Perlundh Participant oe 2023 Nov 24 9:25 AM 0 Kudos Hello Jocelyn, Thanks for another informative blog post! | am sure that the blog posts that you create generate a lot of value around the world, so keep delivering information in this way! One important question that has come up for us is the navigation through links in combination with App Variants. If the user navigate via link in a standard app - that link still refers to the standard app which reduce the usability of this a lot. Or... canwe re-direct to the new app version somehow using Semantic Objects/Actions? And, | guess that it will be difficult redirecting Those are probably hard coded to transactions? ks from "Classical Transactions"? y Vise Explorer © 2024 Feb 15 5:16 PM 0 Kudos This is a beautiful blog... Congrats Jocelyn. @ You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in. Comment Labels In This Area ABAP CDS Views - CDC (Change Data Capture) 2 Advanced Event Mesh i ai 1 ‘Analyze Workload Data —_BS Reclas: ication 1 = BTP 1 Business and IT Integration 2. Business application stu 1 Business Technology Platform 1 Business Trends 1,657 Business Trends 223. CAP1 cf1 Characteristics display Classes 1 Cloud Foundry 1 Confluent 1 Customer COE Basics and Fundamentals 1 Customer COE Latest and Greatest 3. Customer Data Browser app 1 Data Analysis Tool 1 Data Migration 1 data transfer 1_—_Databricks 1 datasphere 2 Event Information 1,396 Event Information 178 Events 1 Expert 1 Expert insights 179 Expert Insights 771 General 2 Getting Started 2 Google cloud 1 Google Next'’241_ GraphQL 1Introduction 1 Kafka 1 Life at SAP 779 Life at SAP. 44. MDG materials 1 MDGM 1 — Migrate your Data App 1 MLFlow1 = MTA1 Network Performance Analysis 1 NodeJS1 PDF1 = POC 1 Product Updates 4,561 Product Updates 857 Replication Flow1 REST API 1 RisewithSAP 1 SAPBTP1 SAPBTPCloud Foundry — SAP Cloud ALM 1 ‘SAP Cloud Application Programming Model 2. SAP Datasphere 2 SAP Datasphere Jue%) cilly (+ Sie! yall Gini 1 SAP MDG Data Quality Management 1 SAPMDGDQM1 SAP s4hanacloud1 SAP S4HANA Migration Cockpit 1 Technical article 1 Technology Updates 6,862 Technology Updates 1,037 Workload Fluctuations 1 Related Content S4HPC Sending Mails Using SMTP CL_BCS_MAIL_MESSAGE Email does not arrived in Technology Q&A Friday (&)& The SAP S/4HANA RISE & SAP BTP - Toolbox & @ in Technology Blogs by Members Thursday Output Management Solutions For LOBs In SAP Business Technology Platform To Keep Core Clean in Technology Blogs by SAP Thursday SAP Sustainability Control Tower: Q3-Q4 2024 Updates & Highlights in Technology Blogs by SAP Monday Integration of ABAP world in SAP Build in Technology Blogs by SAP Monday Popular Blog PostsGet Your SAP HANA Idea Incubator Badge Today! ® Former Member © 40529 ©] 253) dy 1282 SCN ion - SAP HANA Quiz Challenge is now retired ‘ThomasJenewein Product and Topic Expert © 41553 203) 805cS Share your #HANAStory and Win christine_donato ‘Active Participant Cc © 24792 G60 451 Top Kudoed Authors D507 Dominik_Graus & SY FelixDraeger s 1 Sy nageshcaparthy ® =D” Patrizia_Calvia 613 & 10 o9 o8ea SD” Nora_Klemp L S0y tukas_stier View alt Privacy Copyright Trademark Cookie Preferences Follow #Xe Terms of Use Legal Disclosure Support os o7