
Fit evaluation - a necessary step before using an app in your organization, just as getting an evaluation from a coach is necessary before taking part in strenuous exercise. (SAP standard image)

SAP Activate Roadmap Explorer highlighting the roadmap SAP Activate Methodology for RISE with SAP S/4HANA Cloud, private edition

SAP Best Practices Explorer entry page highlighting the SAP S/4HANA best practices

SAP Best Practices Explorer solution scope page highlighting where to select your country and release, and where to expand and select scope items for your process

Best Practices Explorer showing typical accelerators included for a scope item

SAP Fiori apps reference library highlighting the lighthouse scenarios link

SAP Fiori apps library highlighting the main filters on the home page

SAP Fiori apps library showing the sub-filter By Roles

SAP Fiori apps library within the By Roles sub-filter showing the search area and where to select a role

SAP Fiori apps library - where to select an app and the main tabs in the app details

SAP Community topic SAP Fiori for SAP S/4HANA - top of the page showing featured blog posts

SAP Community topic SAP Fiori for SAP S/4HANA - further down on the page you see the featured links for the main phases highlighting the phase Activate and Explore
| Check | Reason for Check |
| App Description | View a high level description of the app’s purpose and intended audience (business role) |
| Best Practices scope item (where available) | Scope items in the Best Practices Explorer contains process flow diagram., test scripts, and task tutorials (where available). These give an insight into configuration advice, step-by-step examples of the process, related business roles, recommended apps/UIs, master data, and other considerations. |
| App Type | The App Type determines what in-app extensions are available and where the app is configured. For example, SAP Fiori elements apps support Adapt UI features, SAP Smart Business KPIs are configured in SAP Fiori app Manage KPIs and Reports |
| App Documentation | Review the detailed documentation – particularly note any mention of configuration options, and any related functionality that can be used with the app (such as notifications, workflows, situation handling, etc.) |
| Feature Comparison documentation (where available) | The feature comparison gives a summary of major feature differences between similar apps, and/or between similar SAP Fiori apps vs closely related GUI transactions. |
| Extensibility Documentation (where available) | Extensibility documentation can be found in: · The SAP Fiori apps reference library Implementation tab for the app in section Extensibility. Look for the link “Extensibility Documentation for this app” · By searching the SAP S/4HANA product assistance in the SAP Help Portal for the term “App Extensibility” The Extensibility documentation lists any available key user extensions and advanced extensions. An app may have both types of extensions, or none. · For Key user extensions: An app may list the business context scenarios that can be used with SAP Fiori app Custom Fields and Custom Logic. Example: App Extensibility: Process Sales Orders · For Advanced Extensions: An app may list frontend controller hooks or backend BADIs. Example App Extensibility: Manage Purchase Orders |
| App History (where available) | This lists any major changes between releases that might affect a now vs. later decision E.g. Track Supplier Invoices IMPORTANT: Changes due to upgrades in the floorplan are not included, e.g. new features export to Excel/PDF. IMPORTANT: In many cases, significant new features are only introduced with a Successor app. |
| Successor and Predecessor apps (where available) | You will find any successors and predecessors in the Related Apps tab of the SAP Fiori apps reference library. The successor app is the current app for this task. Predecessor apps are earlier versions of the app, that were created for an earlier SAP S/4HANA release. The predecessor app may or not be available for your SAP S/4HANA release, i.e. it may be deprecated or obsolete. If you are upgrading from an earlier SAP S/4HANA release: Where a successor app is available for your SAP S/4HANA release you should move to the successor app. The predecessor app will not be improved further and may be made obsolete (removed) in a future release. If you are moving to SAP S/4HANA: avoid using predecessor apps if a successor is available for your SAP S/4HANA release. IMPORTANT: You can now use the Upgrade Impact Analysis tool in the SAP Fiori apps library to cross check your selected apps and classic UIs for successors, predecessors, deprecated, and deleted. Just put your selection list in a comma-separated (.CSV) file and follow the instructions for Running an Upgrade Impact Analysis. |
| Required and target navigation apps (where listed) | You will find any required and target navigation apps in the Related Apps tab of the SAP Fiori apps reference library. These include static (always relevant) navigation links that you must include these apps in your scope to provide full usage of the app. If you wish to exclude certain apps you will need to check on your system the impact of excluding the app, e.g. is the card hidden? Or does the user get a message that this app is not included in the navigation? IMPORTANT: Dynamic (always optional) navigation links are not included. That is, many apps contain a Related Apps button or a list of links dialog that provides dynamic navigation links to all apps listed against a specified Semantic Object). You can find the Semantic Object of an app in the Configuration section of the Implementation Information tab in the SAP Fiori apps reference library. |
| Task Tutorial or Demo video (where available) | You can experience a touch and feel example of using the app. You can find these in the SAP Fiori apps library in the Product Features tab or in the Best Practices Explorer. |
| Check | Reason for Check |
| Does this app use a standard floorplan | Floorplans guarantee consistent basic functionality, behaviour, and personalization features. They often indicate typical configuration and in-app extension features. With standard floorplans you can shortcut fit analysis by focusing on app-specific data and app-specific actions. You can find the main floorplans and their features in the SAP Fiori Design Guidelines section Layouts and Floorplans |
| If app has filters, check Adapt Filters | Review default filters. Identify which additional filter fields are available. Confirm how the filter is used, e.g. text, date, value help, define conditions, etc. |
| If app has table(s), check Table Settings | Identify additional table columns available. Identify additional sorting, filter, and grouping options available. IMPORTANT: If you need to create a hierarchical list, check the grouping options carefully. Grouping creates a hierarchical report - this often automatically includes totals and subtotals for numeric fields. |
| If app has chart(s), check Chart Settings | Identify additional dimensions and measures, and available chart types. |
| If app has cards, e.g. Overview Page apps, review the available Cards | Identify any cards which should be hidden (not relevant, not appropriate or noise). Identify any cards/links which should be added via extension. IMPORTANT: Depending on the app, visibility of cards may be dependent on authorizations. Many overview pages provided Adapt Ui extension options for adding additional cards or adjusting features. |
| Check the available actions that can be performed within the app | Review the available buttons or hyperlinks. Especially check for any app-specific actions. IMPORTANT: Remember that:
|
| Check navigation features | Review the available links and icons (e.g. Expand row icon “>” ). Especially check for dynamic navigation features that can be tailored with configuration and authorizations for preferred/additional targets, e.g. hyperlinks/icons that launch the list of links dialogs and Related Apps icons. |
| Capture the Technical id using About or App Support | The technical id uniquely identifies the app or UI. You can use the technical id to determine the list of apps to include in your custom business role(s). Refer to SAP Fiori for SAP S/4HANA – Finding the technical name of an app |
| Check | Reason for Check |
| Does this app provide Views for filter, table, or chart settings | Save preferred settings for all users. Save role-specific preferred settings (from SAP S/4HANA 2021). You can create multiple views for the same app - e.g. to suit the needs for different roles or for different use cases. You can preset a default view. For filters, identify additional filters available. Adjust which filters are displayed and their default values. For tables, identify additional table columns available, identify additional sorting, filter, and grouping options. Adjust which table columns are displayed, default sorting, filter and grouping settings. For charts, identify additional measures and dimensions. Adjust the default dimensions and measures, adjust chart type (e.g. bar to column chart). Refer to SAP Fiori for SAP S/4HANA – New options for managing Views for filters tables and charts |
| Does this app provide Adapt UI extension options | Adapt UI lets you add, remove, rename, and reorganize fields, sections, cards, actions and other features. Control visibility of optional fields – both standard SAP and custom fields (added with SAP Fiori app Custom Fields) Adapt UI lets you create App Variants – role-specific variants of the app with preset adjusted features. App Variants must be added to launchpad content, then assigned to users via their business role before they can used. This is a similar process to any other app, i.e. create the cross-client Launchpad App Descriptor Item (aka tile/target mapping combination), reference it in a client-specific business catalog, which is the assigned to a business role that is assigned to the user. |
| Does this app provide Custom Fields | You can add custom fields using SAP Fiori app F1481 Custom Fields. You need to check the App Documentation for the relevant business context scenarios. IMPORTANT: Most business context scenarios support adding custom fields centrally to multiple SAP Fiori apps, classic UIs, forms, reports, BAPIs, tables, CDS Views, OData Services, etc. Custom Fields are the most efficient and safest way to add custom fields to a broad range of scenarios. Be aware that the publish process can take some time depending on the number of objects to be updated (more than 30 minutes is not uncommon) - so start it and be patient. WARNING: Avoid attempting to add custom fields through alternative more effortful development-centric approaches (e.g. SE11 Append Structures, CDS View extensions) where Custom Fields are supported. This can lead to clashes that can break the related apps, UIs, etc. and can be tedious to correct. |
| Is this a classic UI that can be adjusted with SAP Screen Personas | You can add/hide/reorganize fields and features on most SAP GUI transactions and Web Dynpro screens. Hint: SAP Screen Personas provides similar capabilities to Adapt Ui in SAP Fiori, however SAP Screen Personas applies to classic UIs only. In SAP Screen Personas you create Flavors - which are role-specific variants of classic UIs. These are typically applied to the classic UI by copying the original Launchpad App Descriptor Item (aka tile/target mapping combination), and adding a parameter specifying the flavor id. In other words, Flavors must be added to the launchpad content, then assigned to users via their business role before they can used. |
| For analytics, know where to adjust the KPI or Report | Tiles that show KPIs and drilldown reports are managed in SAP Fiori app Manage KPIs and Reports. |
| What additional capabilities can be used with this app/process? | Workflow, notifications, situations etc. are typically mentioned in the App Documentation for the app. |
| Check | Reason for Check |
| Is this app supported by in-app extensions? | If the app supports key user extensions via Adapt UI, then more advanced extensions are possible |
| Does this app use CDS Views that can be extended? | You can add additional fields (and associations to related data) through a technical extension of the CDS View. |
| Does this app provide extension hooks? | If the app’s Extensibility Documentation mentions any hooks or adaptation project options, then a developer can use these to add additional features. You must read the Extensibility Documentation carefully to understand what types of extensions are supported. |
| Question | Why you should ask this question |
| What triggers this task for the user... How do they know they should start it? | This helps you understand what information the user has available to them when they start the task. It also gives you some idea of the user’s mindset – is this an urgent task or an everyday activity? |
| Where should the user start the task? | The best place to start a task is not always an app. Search, notifications, situations, or workflows can be better alternatives, especially for occasional (when needed) or urgent (asap) tasks. |
| How does the user get to the next step? | Is there a navigation link or button they can use? Worth considering: If not could an additional navigation be added, e.g. using dynamic link options on Related Apps buttons or list of link dialogs. |
| How does the user know they have reached the end – what tells them it is done? | The end of the task should be clear so the user gets some closure and can confidently move on to other work. For example, a success message, something created, a status change, a situation marked as resolved or dismissed. |
| How does the user handle interruptions (stop / restart) and how? | How can they find what they were working on and restart it? Is this via an app or Search or a notification or something else? |
| Could this task be automated? | Look for mass change apps and robotic process automation options |
| How frequent is the task? How important? | Is it an entry task that needs to be on a launchpad page? |
| What should we optimize to encourage high productivity? | Are there any default values or views we can preset? Are there any workflows or situations that would smooth the flow? |
| Typical Gap Statement | Know your alternatives in SAP Fiori |
| We need to minimize data entry | For commonly used values across many apps, review the available User Defaults in User Actions/Profile menu > Settings For filters create public or role-specific views to preset default values |
| We need want to pre-set the display to minimize personalizations | Views can be used for filters, tables, and charts To preset filters, tables, and charts for multiple users, create public or role-specific views |
| We need to know asap when ... | Check for notification options. These can come from notification provider class, a situation handling scenario, a workflow notification, subscription to a Smart Business KPI tile, etc, |
| We need a regular report | Consider using an Analytical app, such as a Smart Business KPI tile/report, Multidimensional report, Analytical List page, or Overview Page Or create your own report e.g. using SAP Fiori apps Manage KPIs and Reports or Custom Analytical Queries . Lesser options: tile counts – it can be better to centrally create a custom tile in your role if multiple users want it. However be careful! The tile count comes from an OData Service call on the tile itself. |
| We need download to MS Excel | Download to spreadsheet is included as a standard feature in apps that use the List Report and Analytical List Page floorplans |
| We need upload from MS Excel | Check for apps with Import or Upload in the name |
| Others....? | < Feel free to suggest what else we can add here in the comments of this blog!> |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 109 | |
| 37 | |
| 34 | |
| 20 | |
| 19 | |
| 14 | |
| 10 | |
| 9 | |
| 9 | |
| 9 |