SAP Fiori for SAP S/4HANA, SAP Fiori, SAP Fiori Cloud, SAP S/4HANA, SAP S/4HANA, Cloud, SAPUI5

Fiori for S/4HANA – Finding the Delta of New Apps between SAP S/4HANA Versions

The SAP Fiori apps reference library makes it easy to find the apps available for your current SAP S/4HANA version when you install or convert to SAP S/4HANA, n Now a new feature has made it easier to find the delta of new apps between SAP S/4HANA versions when you are upgrading.

As part of the S/4HANA Regional Implementation Group, I have the privilege of working with a lot of customers who are implementing SAP S/4HANA locally, regionally, and internationally. Now that SAP S/4HANA has been available for over 3 years, we are more often finding customers who are upgrading their version, sometimes as part of their initial project, sometimes as a next phase.

Right now, one of my customers is planning their move from SAP S/4HANA 1709 FPS02 to SAP S/4HANA 1809 FPS01 as part of their current project. Another of my customers implemented SAP S/4HANA 1511 and is planning to move to SAP S/4HANA 1809 as part of a next steps project in 2019.

Recently the SAP Fiori apps reference library added a new feature to make it easier to work out the impact of your SAP S/4HANA upgrade.

So, imagine you first implemented SAP S/4HANA 1610 FPS01. Even if you implemented every SAP Fiori app available that was only about 600 apps. Now you want to upgrade to 1809 and there are over 1250 Fiori apps. Conclusion: You need to plan for the new apps you are introducing!

You can do this in a few easy steps:

  1. Select your target apps.
  2. Aggregate your selected apps against your target version.
  3. Select your source version.
  4. Review the list of unavailable apps in your source version, i.e. the delta of new apps that will be available once you upgrade to your target version.
  5. Optionally, download the list for further discussion with your team.

In the examples below the target version of your upgrade is SAP S/4HANA 1809, and the source version is SAP S/4HANA 1610 FPS01.

Step 1: Select your target apps

You can start at the SAP Fiori apps reference library homepage. Start by selecting the apps you want to add as part of your upgrade.

If you want to aim for maximum SAP Fiori coverage, or you simply don’t know what apps you want yet, you can simply multi-select all apps available in your target version. To do this, you select the main filter Fiori apps for SAP S/4HANA.

Then select the sub filter All Apps.

You can see which apps have been selected by the checkbox in front of each app’s name in the left-hand pane.

Once you have selected your list of target apps, you can move straight to the next step or you can refine the list further before continuing.

When you are refining your list, if you want to return to all the apps you have selected, just press the Home button and on the Fiori apps reference library homepage you will find the My Selection filter has been added.

Of course, for your own use cases you can use whatever filters or searches you want to select for your initial list of apps. For example, you might select just the apps you are interested in, or better yet go for holistic business roles or business catalogs that are most relevant to your processes.

IMPORTANT: For the best possible user experience in your SAP S/4HANA version, SAP recommends deploying holistic business roles. This gives your users the maximum Fiori coverage available for their business role. As of SAP S/4HANA 1809, many business roles now have complete Fiori coverage. For those roles where there is not yet a SAP Fiori app for every task, the business role includes the classic apps (SAP GUI and ABAP Web Dynpro) to cover those parts of the role as well. You also get all the navigation & parameter passing details between SAP Fiori & classic apps included natively as part of the standard SAP business role.

Step 2: Aggregate your selected apps against your target version

When looking at your list of selected apps, press the Aggregate button.

Once the aggregation has finished and the Aggregated Implementation Information page is displayed, use the dropdown on the SAP S/4HANA version to select your target version.

If you wish, at this point you can view any unavailable apps in your target version by selecting the line Selected apps not available in SAP S/4HANA ()

This list itself can be useful because any apps that are deprecated between your source and target version will be shown here, including in which S/4HANA version the app was deprecated.

You can also see whether there is a successor app in your target version. If you see the marker Successor also chosen, then the successor app is already listed in the Selected apps available in SAPS/4HANA ().

If you need to, you can optionally download this list of unavailable apps to Microsoft Excel for further review using the download icon above the list.

Lastly to minimize confusion, if you wish you can use the Remove unavailable apps option to remove the apps that are not available in your target version before proceeding to the next step. This leaves just the apps that are available in your target version.

Step 3: Select your source version

Having narrowed down the selected apps for your new version, next you simply use the dropdown again to change the focus of the aggregation to your source version.

By changing the aggregated implementation information to your source SAP S/4HANA version, you can now see which apps among the selection are possible to deploy now in your source version, plus the delta of new apps, i.e. those apps that you will be able to deploy once you upgrade to your target version.

So, in this example, once you change your selection to the source version SAP S/4HANA 1610 FPS01 you can see the delta apps listed as Selected apps not available in SAP S/4HANA

Step 4: Review the list of unavailable apps in your source version

Having found the list, you can then drill down to see further details.

For example, in the Additional Info column you can find out in which version the new app became available.

If you are currently running a predecessor of the same app you can click on the Alternatives available link to see whether the predecessor you are currently using on your source SAP S/4HANA version is still supported on your target SAP S/4HANA version.

Take the Approve Leave Requests example in the screenshot below, You can see the recommended app version for 1809 is Approve Leave Requests (Version 3/Fiori 2.0). In your SAP S/4HANA 1610 system, you might have been running the earlier version Approve Leave Requests (Version 2), perhaps because it was an app you were using in SAP Business Suite before you converted to SAP S/4HANA, and you didn’t want to change the user experience for your business users when you first went live with SAP S/4HANA. You can use the Alternatives available link to see if it is still possible to run Approve Leave Requests (Version 2) once you upgrade to SAP S/4HANA 1809.

This can help you with planning whether the move to the predecessor app is required or just desirable, so that you can include the appropriate app in your organizational change management and testing plans. If the earlier version of the app is not available, then you know you must upgrade to the new version. If the earlier version of the app is still available, then you can choose to keep using it when you upgrade, or decide if you want to use the upgrade to also move your users to the new and improved version of the app.

Step 5: Optionally, download the list for further discussion with your team

Best of all you can download the list of delta apps for further discussion with your team. Just use the Download icon to download the list to an MS Excel spreadsheet.

The downloaded list includes:

  • App Name
  • App ID
  • Link to the app in the Fiori Apps reference library
  • App Type
  • UI Technology
  • Business Catalog
  • Business Role
  • Semantic Object & Action (used to launch the app)
  • Application Component
  • Leading Product Version (e.g. is it part of Fiori for S/4HANA version or part of a S/4HANA add-on)
  • Additional info (e.g. First available version of the app)
  • Alternatives available (e.g. App IDs of any predecessor apps that are still supported in the target version).

Leave a Reply

Your email address will not be published. Required fields are marked *